This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
There is a big issue in the recent firmware/driver update pushed to the surface book 2. The usb mouse became not really usable. There is a frequent lag/freeze happened to the mouse. Such issue was not there before the firmware update.
The mouse I tried including Logitech G703, G402, microsoft wireless mouse, etc.
Many people have discussed this now but not solution is provided and the problem cannot be solved now:
https://www.reddit.com/r/Surface/comments/97804b/surface\_book\_2\_mouse\_freezes/
A further test can now confirm that the issue is either in the UEFI version 389.2268.769.0 or the system aggregator version 728.128.137.0.
After updated these two modules to those versions, the issue start to appear. This has been confirmed on more than one surface book 2 devices.
The previous version of the UEFI starting from 388 and aggregator version 728.77.137.0 do not have such issue. I can see at the moment, the 389 version of UEFI is not pushed anymore and the firmware/driver pack downloaded from Microsoft has the 388 version now.
But for those surface book 2 which has already got the 389 version pushed cannot revert back to the 388 version. Please fix this asap.
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.
Not only just bluetooth, but also the USB mouses. It's a really strange issue with not only just the blue tooth nor usb. it seems that the internal usb bus is fArked up so that everything is not working fine when the load is heavy and CPU is at a high frequency.
WE NEED THE MEDIA TO PUT SOME PRESSURE ON THIS, AND WE NEED TO REACH OUT AS MUCH AS WE CAN.
Those "recommended accessories" sometimes are simply not good enough to trigger this issue since they usually has a rather low polling rate.
The polling rate is some how critical to trigger this issue. AFAIK, the Microsoft IE3.0 remake mouse can trigger this problem, because it has a polling rate of 1000. Normal mice like the Surface or Designer mouse has a polling rate of 125, which is not enough to reproduce the problem.
Has anyone tested it with official Microsoft surface mice?
I would be interested to know if there is no issue with their recommended accessories, which would probably be relevant in their lack of interest to solve the issue.
I tweeted @SatyaNadella and @Surface on Twitter.
If we could get attention from the press that might pressure them to do something, but how the heck do we get that to happen?
My one tweet might go ignored, but if we can make a ruckus... I just can't believe Microsoft can really sit on a $2500 defective product.
One thing I can add to the technical discussion:
I have 3 bluetooth devices connected to my Surface Book 2:
I notice I only have the mouse stuttering issue when I am playing music on my headphones.
I don't know if this is true, but it's almost like the bluetooth chip is getting too bogged down transmitting so much data that the mouse starts stuttering.
It was me who said that I've got a internal contact.
I've told him the whole story, and he filed a bug in the internal bug tracker, but it seems that they've noticed the bug and just don't know how to reproduce it and can't confirm...
Since then he's been unavailable to me since we were not like some close friends... just an acquaintance.
I have some other friends who are working in the Microsoft, but they either can't reach or force the Surface team to solve the issue, or don't have enough power / level to make the team HIGH ABOVEnoticed.
It's just such a disgrace. Maybe we should all work together to sue the Microsoft so that someone inside might get some real stuff work about this issue. So next question, which lawyer should we call at this moment?
