Originally Posted by qsxcv
doesn't work with my laptop (win10 1903)
downclocking works but my wmo isn't going above 125hz
Ok, i rechecked setup procedure once again on Windows 10 x64 1809 - no reboots needed and without any problems, of course.
The last one that i can do to help is description of results of setup stages:
0. Disable Secure Boot (or make equivalent registry changes).
1. Unzip hidusbf.zip and run setup.exe. On modern Windows you will have prompt for privileges elevation.
2. "Install Service" button. Two things happen:
a. hidusbf.sys is copied to %windir%\system32\drivers
b. Registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\servic es\hidusbf\ is created (or updated).
3. "Filter On Device" checkbox:
"hidusbf" string (the name of service) is added to registry parameter HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\% DeviceInstanceID%\LowerFilters
4. "Restart" button:
All previous changes are applied. hidusbf.sys is loaded, executed and remains in memory. If you have "died" device in this point - see the 0., 2. or pay attention to the color of line.
If you can downclock device - then hidusbf.sys is working as expected, but some of the overclocking is not possible on recent Windows 10 versions due to restriction in system files (usbport.sys and usbxhci.sys) - drivers of USB controllers:
a. Low Speed devices over 125 Hz
b. Low and Full Speed devices over 1000 Hz (on USB3.x controller and Windows 8+)
5. Running atsiv.exe -f hidusbfp.sys with elevated privileges:
this patches images of usbport.sys and usbxhci.sys in memory to allow all possible overclocking. But to apply result you shall restart device once again. atsiv driver (embedded into atsive.exe) is extracted, loaded, executed and remains in memory. hidusbfp.sys is loaded, executed and unloaded.
P.S. And yes, i know how to unload atsiv driver.
P.P.S. Setup is enhanced to check the presence of driver service when "Filter On Device" is set (i.e. 2. performed before 3.)