I bumped mine down to 3500 and haven't had an issue since. I wish there was an actual fix and we didn't have to resort to workarounds though.
They need to get serious about this problem.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi there :)
I post this to know if some other people are getting this issue too with the Surface Book 2 (15" model here).
Since the last firmware / drivers update (August 2018 / link), my mouse (G502, connected via USB) randomly stops working after a few seconds / minutes. The cursor just freezes, and the mouse becomes unresponsive (while the mouse is still powered by the Surface). After a while, the cursor starts to move again as usual.
Depending on the battery mode, the random freezes are more or less frequent (more if I use max performance mode), as the mouse cursor movement has an influence on the clockspeed of the processor.
I tried my mouse on a Macbook Pro to see if it was hardware related or not, and it's not, the cursor didn't hang once while on macOS. So I guess it's software related (W10) since the last SB2 update ?
I also tried to switch between the two USB ports, same thing.
I tried to see if it wasn't related to a firmware update of my mouse via the Logitech suite, but no nothing has changed.
Any idea ?
Regards :)
Ps : Here is a link to the Reddit post I wrote (link)
EDIT :
Today I tried to uninstall the Logitech Gaming Software (used to customize the mouse), and until now it seems to fix the issue.
Actually, Logitech did an update of his software that I missed, so I installed it a few hours after I installed the Surface Book 2 firmware update.
Maybe the two are now incompatible ?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I bumped mine down to 3500 and haven't had an issue since. I wish there was an actual fix and we didn't have to resort to workarounds though.
They need to get serious about this problem.
I bumped mine down to 3500 and haven't had an issue since. I wish there was an actual fix and we didn't have to resort to workarounds though.
Thanks. That works!
If 4000 doesn't work, try 3800. I have this issue just like you but this fix does helped a lot.
Had tried this fix, does NOT WORK!!
Fixing is super simple by 3 steps: