Short description. This driver/program is intended to "overclock" USB mice (or other devices) under Windows 98, 98SE, ME, 2000, XP, 2003, Vista, 7, 8, 8.1, 10, 11 including x64 versions. Also may be used for downclocking (and downclocking shall work always).

!!! Warning - overclocking may not work for Low Speed USB devices which controlled by non Microsoft USB stack, like OEM USB 3.x drivers at Windows 7 or with the newest Microsoft drivers.

!!! Warning 2 - you SHALL disable Memory Integrity to load patching versions of HIDUSBF driver under recent versions of Windows 10 x64 or Windows 11.

Program changes rate on selected devices only, not touching other devices on USB.

You can learn more about theory and the program here: http://www.overclockers.ru/lab/15925/Razgon_USB_myshi_ili_Software_nanosit_otvetnyj_udar.html (in Russian language(*))

I have personally tested it under Windows 98SE, 2000 SP2/SP4, XP RTM/SP1/SP2/SP3, XP x64 SP2, 2003 x86 SP2, Vista 32 bit RTM/SP2, Vista 64 bit RTM, 7 x86 SP1, 7 x64 SP1, 8 x64, 8.1 x64, 10 x64 1803, 1809, 1909, 20H2, 21H1, 21H2, 22H2, 11 22H2. The first testing on x64 platform was performed by Dark_Cloud under Windows XP x64 SP1.

Installation.
Downclocking (all devices and drivers) or overclocking of Full Speed USB devices is possible always and there is no need to patch system code.

So, if you use program for this purpose - take drivers from directories DRIVER\NTX86[_AS]\NOPATCH\ and DRIVER\AMD64[_AS]\NOPATCH\ and replace drivers from directories DRIVER\NTX86[_AS]\ and DRIVER\AMD64[_AS]\

Because Windows 2000 doesn't have restrictions for overclocking Low Speed USB devices in driver code for OHCI and UHCI controllers you can use the driver from DRIVER\NTX86\NOPATCH. Windows 98 and ME also don't have such restrictions, so there is no patch version of driver for these OSes at all.

If you use your device with pure EHCI controller (without companion UHCI or OHCI controllers and with integrated USB2.0 Hub) or with any EHCI controller through USB2.0 Hub on Windows 2000 then just use ordinary version of driver (with patch). And there is special unofficial version of USBPORT.SYS for Windows 98 and ME without any restrictions of polling rate for such cases.

For OSes begining from Windows XP for successful overclocking of Low Speed USB devices is REQUIRED the presence original (not altered by other programs) version of system driver USBPORT.SYS (%sytemroot%\system32\drivers\usbport.sys). Windows 8 beginning also works with USBXHCI.SYS (%sytemroot%\system32\drivers\usbxhci.sys). And under Windows 7 is supported Intel xHCI driver (IUSB3XHC.SYS) (see additions in HIDUSBFN.ZIP)
Install my driver HIDUSBF.SYS. For this purpose execute SETUP.EXE (there should also be .INF and .SYS files UNZIPPED). Click [Install Service]. You may see quick flash of installation process, or you may not see anything, because this process is really fast. It doesn't matter, the subsequent installation of the filter does to verify that the service is actually installed, so move on to the next step, which is to install the filter on the device (Filter On Device).

In case of HIDUSBF service wasn't installed through SETUP.EXE (button [Install Service]) you may try to do this by OS standard possibility: mouse right button click on HIDUSBF.INF / HIDUSBF_AS.INF -> Install By default (in SETUP.EXE) HIDUSBF.INF applies to all OSes up to Windows 8 and HIDUSBF_AS.INF starting from Windows 8.1. It is enough to install the service once for each OS instance.

Then choose the row with your device and put a checkmark Filter On Device. Check that in the column Filter? it says Yes. After that choose desired refresh rate. After that push [Restart]. Check if the refresh rate has really changed (for example with the program Mouse Rate Checker).

If your rate did not change, then you should either reboot, plug-out and plug-in mouse cable or stop and then start your mouse in Device Manager.

If the rate does not increase more than 125Hz, then you should try DECREASE it to 31Hz or 62Hz. If the rate does decrease, then the driver functions properly, however or you mouse is not overclockable; or USBPORT.SYS/USBXHCI.SYS was altered or simply too new and so unknown to the program.

Uninstall.
Unlink driver from mouse through SETUP.EXE (Filter = Unchecked)
For removing a service and file of driver: Setup.EXE -> mouse right button click on [Install Service] -> [UnInstall Service] or mouse right button click on HIDUSBFU.INF -> Install in Explorer
If you have delete a driver but not unlink it from mouse then the mouse will stop working. To make mouse working you can just delete device, corresponding to mouse in Device Manager, then scan for new devices. Or use SETUP.EXE -> [All] or [with Problem] or [with HIDUSBF] Devices -> [Filter On Device] is Unchecked -> [Restart]
Contacts. You can access the newest version at this link: https://github.com/LordOfMice/hidusbf

Recent info https://www.overclock.net/threads/usb-mouse-hard-overclocking-2000-hz.1589644/ (the end of the first post and recent posts in thread)

Good luck in overclocking mice :) SweetLow

History.

Added 2025/11/05:

Patching versions of drivers are compatible now with USBPORT.SYS of Windows 11 22H2+ (old UHCI, OHCI and EHCI USB Controllers).
For patching version of drivers for modern OSes (AMD64_AS / NTx86_AS) it's possible now to disable patching of different drivers (USBXHCI.SYS for XHCI USB Controllers and USBPORT.SYS for UHCI, OHCI and EHCI USB Controllers) separately by Registry parameters:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HIDUSBF\Parameters] or [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\HIDUSBF] PatchUSBPort=dword:00000001 PatchUSBXHCI=dword:00000001

where PatchUSBPort has 0 and 1 values (0 - disable patching, 1 - enable) and PatchUSBXHCI has 0,1,2 and 3 values: 0 - disable patching 1 - 1k patching 2 - 2k-4k patching 3 - 4k-8k patching

And strictly speaking 1k, 2k-4k and 4k-8k versions of driver are different now by PatchUSBXHCI default value only.

Thanks to Battle Beaver Customs https://www.battlebeavercustoms.com/ once again for invaluable help.

Added 2025/04/09:

The latest NoPatch version of x64 drivers (AMD64_AS) rebuilt to conform Memory Integrity requirements of Windows 10 x64 or Windows 11. Thanks to Battle Beaver Customs https://www.battlebeavercustoms.com/ once again for recurrent signing.
README clarification of [Install Service] behaviour.
Setup - clarification for Errors #193 and #577.

Added 2024/07/23:

The latest version of drivers are signed by Microsoft Attestattion Signing. Thanks to Battle Beaver Customs https://www.battlebeavercustoms.com/ At this point there should no longer be a problem with Secure Boot, but see Warning 2. The process of modification the drivers to work with Memory Integrity enabled is in progress but not finalized at this time.
Setup

modified for the installation of new drivers: starting with Windows 8.1 drivers with the setup information HIDUSBF_AS.INF and the location in AMD64_AS / NTx86_AS are used
as a thank for the signed drivers added a link to Battle Beaver Customs (visible if runs on OSes for which new drivers are used).
[About] added

Added 2024/04/09:

Setup

added uninstalling service in Setup.EXE (mouse right button click on [Install Service])

Added 2022/07/18:

Setup

added message on USB Low Speed devices overclocking to higher USB Speed Class

Added 2022/07/13:

Setup

USB High Speed devices support
OS Version and Bus Speed name on [Copy IDs]

Added 2021/04/02:

Setup

correctly shows long error messages

Added 2020/06/05:

Setup

added check for hidusbf service can run

Added 2020/03/29:

Setup

real versions of files on Copy IDs on modern OSes
VIA xHCI Controller Driver (XHCDRV.SYS) marked as good

Added 2019/10/26:

Setup v2.0

literally everything is improved: the form is simplified, display of the whole essential information added, all reasonable checks are implemented

Added 2019/06/21:

Improved Setup

added check for the presence of an runnable driver service at the time of installation filter on device

Added 2018/12/16:

Improved Setup

added "CopyIDs" button to copy DeviceInstanceID and HardwareIDs (for use in any external program restarting device (using atsiv method))
added dpiAware tag to manifest

Added 2017/01/08:

Setup now always wants/asks to run with Admin ri

Hidusbf

Install / Use

README