Surface Book 3 - external keyboard and mouse

Anonymous
2020-06-26T07:37:06+00:00

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

Surface | Surface Book | Power and battery

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.

0 comments
Answer accepted by question author
Anonymous
2021-01-26T17:42:18+00:00

A fix for this issue is now available through Windows Update. Please review the Surface Book 3 Update History page.

Eddy.

Was this answer helpful?

10+ people found this answer helpful.
0 comments

432 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-10-28T19:34:01+00:00

    That's the most response I have seen.  Couple days ago I was emailing with one of their techs and told him to look at these posts to get all the details of what's going on, so maybe enough of us reported it that they are now listening??  We can only hope.

    Along the same lines, I just bought a bluetooth keyboard/mouse combo, Logitech MK850, and installed their software.  Only been using is a short time, but no issues so far.  Maybe something to try until MS has a fix....

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-10-28T18:58:29+00:00

    Thank you for reporting this issue.  We are aware of the issue and are actively working on a resolution.

    Thanks,

    Eddy.

    Am I dreaming? A answer from Microsoft? Haha... must be a joke. What happened? Is a big portal or magazine now talking about this?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-10-27T23:10:13+00:00

    So the plot thickens somewhat. It appears the primary culprit is the Modern Standby function which Microsoft forced down everyone's throats with the May 2020 update, which removed all the power plans except Balanced and completed disabled S3 sleep.

    Something between the interaction between Modern Standby, the Surface Dock 2, and the Surface 3's own power management, is causing external USB devices to go through 'micro sleeps', and those micro sleeps are what is causing the pauses or repeats evident when using external keyboards on USB.

    Anything, anything at all, that elevates CPU usage sufficiently to prevent the Surface 3's power management components from trying save power, fixes the issue as long as that CPU usage is elevated. As soon as it's no longer elevated, the issue reliably and predictably recurs.

    I don't think we'll see a fix for this. In order for a fix to occur, whoever MS executive it is who decided enforcing Modern Standby and removing the ability to change it was a good idea, would have to eat humble pie and revert the change. That isn't going to happen.

    We've all just become expensive victims in a poorly implemented chapter in the ideological battle about what the future of computing should look like.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-10-27T22:44:27+00:00

    So i've had a fun morning. Folding@Home has been a good workaround for many weeks - but this morning, they have no work units available...

    So until they do, F@H is not doing any work, and my CPU is back to idling. And the problem starts again.

    The issue is so clearly linked to low CPU usage and therefore power usage that I'm surprised that MS hasn't issued a simple fix.

    It's a perfect storm of a hardware issue combined with the dumbing-down of Windows power management that came with release 1903 that disabled visibility on options like Disable USB Selective Suspend that would have helped a lot with diagnostics.

    'Noone will ever need advanced power management' seems like it might rank up there with 'Noone will ever need more than 640KB RAM' as one of Microsoft's flawed visions.

    Was this answer helpful?

    0 comments