run dseob (or whatever the fuck its called)
enabled test mode (DONT FUCKING RESTART)
extract hidusbf folder somewhere
run setup in hidusbf folder
click filter on device, select 500hz.
click install service (ONLY DO THIS ONCE DONT FUCKIN DO IT MORE THAN ONCE)
click restart (dont exit the setup)
run dseob again
sign a system file
sign "C:\Windows\System32\Drivers\hidusbf.sys"
restart pc (the hidusbf setup should still be open and let windows close it as it shuts down)
???
500hz profit

works like a charm, thanks!

np

What happens if you clik "install service" more than once?

COOLLER appears and smashes your keyboard over your head.

Just follow this youtube guide
http://www.youtube.com/watch?v=0_hZipKt72M

gl

hm... what about that watermark?

here
https://dl.dropboxusercontent.com/u/7879581/RemoveWatermark_w7.7z

Such bullshit ,was easier back in the days. I will probably mess that up so im stuck with 125hz....

Unless you're 15 years old with no money, save yourself some trouble and upgrade to a gaming grade mouse, so you don't have to keep repeating the process, especially it gets annoying ( not sure if everyone had the problem ) but if you unplug your mouse from the USB port, you had to re do the process.

FUCK...THAT.

spend roughly 50 dollars and never worry about it again.

to anyone stumbling on this thread from google or wherever:

The answer is that the usb poll rate fix video and other instructions dont work for 64 bit win 7 is because you have your mouse plugged into a 3.0 usb port. you need to plug it into a 2.0 port Or you can disable xHCI in bios to disable 3.0 and then the methods above will work!

Fuck my life. I don't have USB 3.0 and no option about "xHCI" whatever that is, on my bios (I have a X38-dq6). I have done this a million times. For some reason, I CANT make it to work now. Did they fuck anything up with any recent Win 7 updates? I have done this a million times with my WMO before and now it doesn't work. Tried #1 method and the one in the jackfrags video.

http://www.youtube.com/watch?v=0_hZipKt72M

None of them work. I just get a dead mouse, so I have to uninstall the driver from device manager, then unplug and plug it again to recover the USB port.

Yes im on test mode, yes I did install the HIDUSBF.INF file, yes I did open setup.exe in admin mode and yes I did sign

C:\Windows\System32\Drivers\HIDUSBF.sys

C:\Windows\SysWOW64\Drivers\HIDUSBF.sys

still not working. What in hell?

PS: Btw, there's no "HIDUSBF.sys" in C:\Windows\SysWOW64\Drivers\, is this normal?

I just tried by copying hidusbf.sys from the system32/drivers folder and it didnt work. What in hell is going on? serious.

The only mouse related thing I did prior to this was opening:
Windows_7_MouseFix_TextSize(DPI)=125%_Scale=1-to-1_@6-of-11.reg

In any case, I dont think this is relevant and I tried doing the process 5 times and it didnt work, it always ends up with a dead mouse (not even the red light from the WMO is on)

I have exactly the same problem as you do. One difference is that I have z97 socket mobo :/

So I guess Microsoft is trying to ruin it for us. Hopefully someone can help us so we aren't forced to buy one of these Fatal1ty motherboards with the forced 500hz ports for pete's sake.

man as someone on ESR told me, isn't the USB port 3.0 much better for HDMI on 120hz? does the energy/plug/whaever have any effect in it? Im just curious how it changed from 2.0 500hz to 3.0 -00hz :0

Not sure what the question is but from what I understand USB 3.0 devices don't need to poll like USB 2.0 devices. So it would be like having your keyboard plugged into a ps2 port. Unfortunately gaming peripheral companies haven't taken advantage of this in anyway. I think it would be better for mice. And no plugging your mouse into usb 3.0 doesn't make it do anything differently.

sorry if i made a post that wasn't that clear to understand, but yeah i got ya!

How it always works for me:

Open command prompt (cmd.exe) -> type: bcdedit -set TESTSIGNING ON

Restart the PC

Right-click hidusbf.inf -> install

Run dseo13b.exe -> sign a system file -> C:\Windows\System32\drivers\hidusbf.sys

Exit dseo13b.exe

Open Setup.exe -> select the mouse -> check Filter On Device -> select the desired polling rate from the drop-down menu -> do nothing else

Now, while leaving the Setup.exe interface open, restart the PC.

Doesn't work. Dear god microsoft fucked this up with some update or something god.

Are you using Windows 7? Works for me.

Make sure prior to this process, you uninstall the hidusbf.sys driver (right-click on hidusbfu.inf that is also provided with the other files and hit install). Also open a command prompt and type: bcdedit /enum and check whether "testsigning" status is "Yes".

Also, how exactly doesn't it work? The mouse does not work? It's stuck at 125Hz? What mouse are you using?

I did everything what you said and it's not working for me either.
It's weird because I've changed Hz for WMO many times before with no problems.
It's stuck at 125Hz.

Windows 7?

Win 7 x64 SP1

Did you first uninstall hidusbf.sys using hidusbfu.inf? You are positive you are in testmode?

Did you by any chance download a Windows update called "Microsoft Drawing Pointing - Microsoft Hardware USB"?

"Microsoft Drawing Pointing - Microsoft Hardware USB"

IN what way is that relevant? also how do I check for that?

Also yes im on test mode.

Windows Update recently offered me that as an optional update. Maybe you auto-installed it. Not sure how it would be relevant, but if it used to work for you but doesn't anymore - something has gotta have changed, right?
Again, it works for me. Something else must cause this issue for you. You can go to Windows Update and check the update history. From there you can uninstall updates as well.

"Did you first uninstall hidusbf.sys using hidusbfu.inf? You are positive you are in testmode?"

Yes, I'm 100% positive.

"Microsoft Drawing Pointing - Microsoft Hardware USB"

Dunno :/

Check your update history.

Really strange you guys are having problems. What did you do that you now have to overclock the mouse again - format? New mouse?

No, same mouse, WMO.
I searched for "USB" in the "installed updates" list and nothing shows up.

Yeah, but why do you have to change your polling rate then? When you used to have it at 500Hz, did it change to 125Hz on its own?

No, I had a format, reinstalled Win 7, but I didnt play quake for months so I left it at 125hz. Now I wanted to play and I get this shit.

Make sure your WIN7 copy and loader are clean (if you didn't use an official copy of WIN7). Do you have all updates installed?

The loader is downloaded from the mydigitallife forum thread, yeah all updates are installed and 1000hz doesnt work as well.

Oh btw, I get this when I install hidusbf.sys

http://wss.boman.biz/Lists/Posts/Attachments/...83EA33.png

(this pic but with hidusbf.sys instead)

I never got the last times ive tried.

It's not necessarily normal for that to pop up, but people have reported that the driver patch works even when it does.

If you still have a copy of hidusbf.sys in your SysWOW folder, delete that.

At this point, you should maybe consult google for general signing problems. That the mouse is dead after restarting instead of being stuck at 125Hz means that your OS does not accept the unsigned driver. Maybe has something to do with testmode not being set up correctly, or some registry value. Maybe also has to do with your user account's rights of changing stuff. Maybe post in a Windows support forum to get help on how WIN7 even in testmode could still deny the use of unsigned/third-party signed drivers.

Yeah, it seems like that's the problem because i get this when i look on device manager with the dead mouse:

http://km.support.apple.com/library/APPLE/APP...52--en.png

So for some reason hidusbf.sys is getting rejected even after being signed and booting on testmode.

You could also try to play around with the process a bit. First testmode, restart, install hidusbf.inf, restart, sign driver, restart, Setup.exe, restart.

Probably you have tried playing around with that already though. Seems like I cannot really help you with that. There are cases where people failed to get the OS to accept the driver, but they mostly solved it by changing the signing process...

I tried this:
http://forum.notebookreview.com/gaming-softwa...7-x64.html

And somehow I still get the code 52 error and my mouse doesn't work after restart. Im lossing my patience as I have to get down and unplug/plug the mouse on every failed attempt. This seems pointless.

OKay,i've found a shitty workaround. I do the usual steps, but I boot with use F8 option to manually "disable digital signature enforcement". I have to do this on every boot manually so its a pain in the ass, but at least I have 500hz again. It seems doing this at boot does an actual override of driver signature while the other methods fail.

That's strange. "disable signature enforcement" is nothing else than testmode. Did you activate testmode as I told you to (-set TESTSIGNING ON in administrator mode)?

Yes I did. And I still need to do it manualy.

Welp, doesn't make sense to me. You will have to venture out into the net to find answers how it can be that testmode is not equal to testmode. Maybe it has to do with "Secure Boot". Or maybe there's some registry-sided things going on that are bypassed when selecting "disable driver signature enforcement".

I cant find anything. Im just searching for a way to automate this:
https://www.youtube.com/watch?v=k4RwaI4mn6Y

The result is a dead mouse, aka not even the red led is ON. Im using WMO. When I go to device manager, the driver is faulty, it seems hidusbf.inf is not correctly signed or some shit.

Windows 7? Made sure to uninstall hidusbf.sys prior to the process?

Also, you should try different USB ports (make sure not to use 3.0 ports).

Yes to all. This shit doesnt work anymore.

Also try and see whether there's a BIOS update for your motherboard and chipset - USB hub drivers specifically.

I have the latest BIOS before the beta one, im not gonna put beta shit as BIOS firmware.

http://gigabyte.com/products/page/mb/ga-x38-dq6/download/

They dont even list what does it do.

@ stirner could you comfirm that as of 3 august 2014 that still works for you too using w7 64bit?

@ nemecel you should proceed to a full HDD format and erase everything on it and instal a fresh new win 7 64bit and then try to set the wmo to 1000hz.

Oh for god's sakes im too lazy for that. And I don't trust 1000hz, I go 500hz tops.

Try 1000Hz, maybe 500Hz strangely doesn't work?

Okay i will try. But isn't 1000hz too unstable and cause glitches?

The WMO polls 1kHz consistently. 500Hz is a tad bit more stable, but that also has to do with the amount of data the mouse produces, which is not consistent itself naturally. No problems @ 1000Hz for me.

I just uninstalled hidusbf.sys and repeated the process as outlined by me above. My WMO is running at 1000Hz again. Can confirm.

Good to hear it :) what motherboard do you have?

Gigabyte GA-870A-USB3 Rev. 3.1

Since this thread was already bumped, here is a pointless rant.

I can't stand when people use the term 'overclock' for increasing the polling rate of the mouse. It's totally incorrect. The USB spec allows for 1 ms polling.

This 'overclock' folk lore is one of the reasons why support for 500-1000 Hz isn't more widespread. People who are unfamiliar with it think it will fry something, and this includes people at microsoft who have made it very difficult to increasing polling rate in windows 7 and especially windows 8 for mice that don't have it built in.

it follows the literal definition of overclocking.

I really don't think that is why the people at Microsoft make it difficult to overclock USB ports. The reason it is difficult has nothing to do with mice. But even if it did the reason would be because half of the people that try this end up with a dead USB port and don't realize it is incredibly easy to fix. And then they may proceed to try another port and may end up with no ports left. I will also add I really don't think most companies have much trouble with the term overclocking. Most motherboards have automatic overclocking that would easily burn up a cpu without proper cooling or cause some serious errors which would require a reinstall of your os or at the very least would decrease the lifespan of your cpu and motherboard. Luckily there are also features that will throttle the cpu to lower temperature and just make your cpu run with low performance and probably cause some errors and the cpu might still get hot enough to trigger the pc to just shut off.

Here's my understanding of the 'overclocking wmo' situation. I feel like i have to dump this before I forget and/or stop caring about it, in case somebody else with more motivation and technical background wants to follow it further.

USB spec allows for 1ms polling for low speed usb 1.1 devices, such as the WMO. Problem is that the WMO's endpoint descriptor sets binterval (polling interval for isochronous devices such as mice) to 10 (retrieved from usbview). Actual USB spec says this should be interpreted as milliseconds even for low speed devices (http://mprolab.teipir.gr/vivlio80X86/usb11.pdf page 220). Windows USB implementation says values 0-15 should be interpreted as 8ms http://msdn.microsoft.com/en-us/library/windows/hardware/ff539317(v=vs.85).aspx -- hence 125Hz out of the box.

The polling rate hack should only have to exist as a lower filter driver for the mouse that intercepts the usb endpoint descriptor upon initialisation and tells the OS to use something else, like 1 or 2 for 1000hz or 500hz operation. For some reason, usbport.sys enforces minimum 8ms poll interval for low speed devices (see msdn link earlier). Since Windows protects its system files from being modified on disk, the hidusbf fix has to patch usbport.sys in memory to remove this limitation.

The only difference between low and full speed (in terms of how usb 1.1 devices are identified) is the location of a resistor (http://www.beyondlogic.org/usbnutshell/usb2.s...tification). It MAY be possible to mod a WMO pcb to change this.

tl;dr If it were possible to flash a new binterval value onto the WMO AND make it present itself as a full speed usb 1.1 device, we would have a WMO that would work without specific software hacks.

Same problem here, after reinstalling the OS i've done the procedure to get 500hz with my WMO.
It died, damn... :(

i tried unistall with hidusbfu.inf but nothing.

Weird thing is mouse led doesnt even turn on on every USB port, but with front case usb ports it works.

You can revive "dead" ports by plugging the mouse in them and uninstalling the mouse driver the OS accesses at that point (from the device manager).

There's something you guys are doing wrong. Are you enabling testmode via dseo13b? Use cmd.exe.

sorry i dont understand what you mean

How can i fix this?
Yes i have enabled test mode via dseo13b, but when i plug mouse it doesnt appear on device manager.

Activate testmode manually.

If you plug the mouse in one of the "dead" ports, it will show up in the device manager in one way or another (most likely as an unidentified HI device). You maybe have to set your device manager to show "disconnected" devices. Or use the "scan for changed hardware" option for it to show up. From there, you can uninstall the driver associated with that device for that specific port.

im complete noob, how can i activate testmode manually?

It doesnt appear anything on device manager when i plug the mouse on "dead ports"

Prior to doing this, disable the testmode with dseo13b.
Open cmd.exe with administrative right. Type: bcdedit -set TESTSIGNING ON, now the prompt will tell you whether that operation has been executed successfully. Type exit. Restart the PC. Open the command promt again with admin rights. Type bcdedit /enum. Check whether "testsigning" status is "Yes".

Hard to help you with the device not showing up. That only happens when the mouse is dead and not the driver causing communicative issues. But since the mouse works on other ports, it is obviously not dead. You can try and deinstall your USB drivers from the device manager. They will be automatically reinstalled, maybe the device-specific driver information will be swept away as well.

no way, i've done allthis stuff but it still doesnt work..

I also tried to unistall USB3.0 drivers.

Fortunately i have another WMO, it works on every port, i will use this with 125Hz

Thanks anyway for the help

LIke I said, use this:

https://www.youtube.com/watch?v=k4RwaI4mn6Y

I'm convinced microsoft has broken this somehow. I couldn't get my ie3.0 to 500hz a week or two ago, last night I reinstalled windows and had no problem doing it.

What windows do you installed? XP 7 8.1 ?

7 x64

SP1?

Yes, all important updates except kb971033

How could "Microsoft have broken this" when it works for you now? Not that I have an idea what is causing this problem for you guys (going from what nemecel reports though, possibly has something to do with testmode complications), but if it works for you after a format with all updates installed, the problem must have been something else than the OS.

Because it didn't work for me with every update installed but it worked fine on a fresh install with no updates installed.

So, now that you have "all important updates except kb971033", it again does not work?

1000hz right now. I don't want to risk trying to change it now as I've just gotten everything set up.

Am I not understanding you here or...?

You said the OS must have caused your issues, then you reinstalled WIN7 and all updates, and now it works. So, how can the OS be the problem? Or did you NOT install the updates? Because that's what you said you did.

I'm saying microsoft must have broken the process but the effect stays even if you update everything.

Are you a microsoft employee or something? You seem to be very negative about this whole thread.

Oh, so you had set the poll interval and then installed updates? Makes sense. I'm just trying to understand because should not being able to set pollingrate become a thing with WIN7, I want to know how to circumvent it.

From what there is to gather in this thread right now, it seems as if there was some update that changed how testmode handles driver signing specifically. I will install the "Microsoft Drawing Pointing - Microsoft Hardware USB" update and see whether that's it.

I've tried everything in this thread, cant get it to work. Mouse isnt dying tho so im guessing thats a plus... :P

You guys got it to work? I've tried all of the above as well. :/

I didn't. In the end I bought a FK1 and I'm pretty happy with it.

its easy as fuck...

https://www.youtube.com/watch?v=0_hZipKt72M

WMO stable with 500Hz, 1000 Hz here

Hello peeps. I know how to get It too work after my 1 year searching and buying 2 Zowie EC2 Evo mouses with fucking Laser sensor glitch.

I got my 3.0 back and I was like "LETS GET THIS FUCKING 500 HZ I CAN'T PLAY CSGO WITHOUT MY FUCKING 3.0"

Found an excellent guide:
http://www.overclock.net/t/596276/changing-us...t_21152245

Yes, THIS WORKS. I had the struggle where I couldn't switch to 500 hz for over a year, so I can approve. THIS WORKS.

If you don't have "xHCI" in BIOS like I didn't at first. UPDATE YOU BIOS.

Hopefully after almost a year there are still people having this trouble and will see this. Hope you get as happy as I did when you get the 500/1000 hz on a IME 3.0.

/Raxx

you can also do 1000hz

you sure? i thought it was reliable?

you can also do it in 2014

Has anyone ever managed to get this working on Windows 10? Some guy claimed he did and made a tutorial (https://www.youtube.com/watch?v=QGl5n3To70Q). Despite having strictly followed the steps, my WMO remains stuck to 125hz :/

Did not work for me. The only thing I got out of this tutorial is a Test Mode logo on the bottom right of my monitor.

Yeah, test mode seems to be enabled but for some reason Windows won't install the unsigned driver.