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)
I am on my second keyboard/cover for my new Surface Pro 11 and am experiencing the following issue: On some startups -- not the majority of them -- the keyboard does not pair with the Surface Pro unit. The only solution has been to detach the keyboard from the unit and reattach it. I have cleaned the contacts (although this issue arose almost immediately out of the box after purchase), and followed a few other suggestions that I found online. One thing I have not done is reinstall the drivers. I can't imagine that they are out of date and a check of each says that they are up to date and the best drivers for the unit.) So, my question is this: if two different, new keyboards have experienced the same problem, does it sound like the issue is with the Surface unit itself? And if so, what other remedies are there before I turn it over to an expert?
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.
This might have been fixed in KB5058499 (currently public preview).
I don't have this issue at all anymore on my Surface Pro 11 (I don't use sleep but hibernate).
[USB] Fixed: Certain USB devices might become disconnected after sleep, until you reboot your PC.
I have the same issue using HIBERNATE. @Microsoft: Are you joking? Prioritize fixing this issue ffs.
@Anyone: Since it seems to be related to sleep/hibernate, I bet a script could refresh the devices and "fix" this, maybe with Scheduled Tasks it could even be fully automated. Maybe someone could do that?
If we all raise support tickets regarding this issue, a fix is likely to be prioritised.....
I've just raised this as a support ticket with Microsoft from the Surface application.
Surface app > sign in at top right > click 'click for help' icon top right > enter brief description:
Can you update me on fix for known issue with type cover keyboard not being recognised after surface pro starts up
brief chat, described issue:
(I copy/pasted Miles' description from post from 31/1- thanks Miles_891 )
This is a 100% re-creatable problem:
1: Shutdown using Windows "Shut down".
2: Fold keyboard/cover over display/screen immediately.
3: Lower keyboard/cover and turn on computer with the power button.
When the computer boots, the keyboard will be unresponsive.
the Microsoft support representative confirmed it is a known issue and is being worked on.
After purchasing eight surface pro, this will be the last. Microsoft does not care for its clients.
I have the same issue as everyone else here, and YUP, I can reproduce it 100% using your method. It seems this is related to the sleep function, and that it is not "waking" the keyboard properly. This *MIGHT* be a software fix, but Microsoft needs to get off their collective behinds and fix this. We need to publicize this problem. Twitter, Facebook, contacting media, whatever it takes to wake up Microsoft to fix this issue.