A fix for this issue is now available through Windows Update. Please review the Surface Book 3 Update History page.
Eddy.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have a SB3 connected to a Surface Dock which has FullHD touch monitor, USB keyboard and mouse connected to it. I have used this setup without any issues for over 2 years with Surface Laptop 1.
With the SB3 the keyboard and mouse 'stutter' meaning characters are lost or autorepeat due to missing down or up codes. Mouse motion ceases then resumes.
I have a video of the mouse re I continuously move the mouse in a circle
https://1drv.ms/v/s!ArzFfLr\_MuyC294iYcJ4cavRP\_nIvA?e=qdqCjY
I have tried plugging the mouse into one of the SB3 USB ports and get the same result.
I know others have seen this problem. It should be easy to reproduce. Can someone from Microsoft try this please.
This looks to be a level USB message handling problem. Note that the USB is not unloading.
David
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.
A fix for this issue is now available through Windows Update. Please review the Surface Book 3 Update History page.
Eddy.
Also, I confirm that only happen with HID devices like keyboards and mouses.
I've connected an external mutichannel audio interface (Steinberg UR22 MK2) and runs perfect with no issues, connected in the other USB port among the keyboard and mouse. Both still had the same glitches.
About the bluetooth alternative, none of my devices has this feature. The keyboard is cable only and the mouse (Sharkoon) works using a custom RF USB dongle. (It can also use a cable, tho)
I have, for many months, been running Folding@Home at 30%ish CPU usage to prevent this issue occurring.
In that entire time I have not once had the issue occur, as long as the F@H client is operating. This is with normal wired keyboard and mouse, external USB hub attached to the dock, and multiple USB devices.
As soon as I stop running F@H, the issue returns. So it's demonstrably related to some level of power management caused through low CPU / idle CPU states. Keep the CPU somewhat busy, problem does not occur.
So while running a third party piece of software like F@H just to make an expensive laptop work properly is not ideal, it's worth pointing out that as long as you do so, the SB3 runs completely 'normally' with no further workarounds required.
It's the best workaround solution I've found so far as it requires zero change to any other usage or preference - no need to use special keyboards or dongles or anything. Run F@H in background, problem goes away, use SB3 as normal.
I've been in contact with MS Support again.
Just wanted to share the information here, they are confirming that they know about the issue and the hardware team is working on a fix. No ETA except "it is going to be resolved soon".
Go with the XPS 15 or 17. That is what I did and IT. IS. GREAT!