Hi David,
For more information on how to send a feedback to Microsoft with the Feedback Hub app, click this link.
Don't hesitate to get back to us if you have other concerns.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
After updating to the Fall Creators' Update, Windows misses the first several keystrokes from my Microsoft Designer Bluetooth Keyboard. This occurs when after rebooting, first logging in or simply after the keyboard has been idle for a bit. The problem happens not only in Windows, but in all applications, too.
I have replaced the keyboard batteries and the problem persists.
I have tried another identical keyboard and the problem persists with that keyboard, too.
I have checked for driver updates, but Device Manager indicates that I have the latest drivers.
The problem did not happen before updating to the Fall Creators' Update.
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.
Hi David,
For more information on how to send a feedback to Microsoft with the Feedback Hub app, click this link.
Don't hesitate to get back to us if you have other concerns.
I have tried to use the "Feedback Hub". Unfortunately I was unable to follow your instructions as the flow through the hub was almost entirely different. I did discover it was not possible to trace anything remotely like the BT keyboard problem introduced by Windows Update - so not able to add anything. The Hub experience was completely confusing (probably exactly what MS want) so I won't be wasting any more time with it.
Perhaps MS would respond using this forum - at least you can search and find the issue here...
For those following this thread who've reported sluggishness problems with the Microsoft Designer Bluetooth Mouse, I've created a problem report on the Feedback Hub for that, too.
Please follow the link to upvote this problem report, as well.
Per your recommendation, I have entered a problem report on the Feedback Hub.
Others following this thread, please follow the link to upvote this problem report!
To the Microsoft folks, thanks for your help in attempting to solve this problem. It is discouraging, however, after working through this issue for several days, to have it simply dumped into the "black hole" of the Feedback Hub rather than escalated for further investigation -- especially for current Microsoft hardware products.
I think what your customers want is that defects are repaired or fixed by MS. Sending a message asking to be informed in yet another way is of no use whatsoever, is it?