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)
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.
Interestingly, The Microsoft Designer Keyboard misses the first couple of keystrokes following a pause when connected to a non-microsoft OS. (macOS High Sierra Version 10.13.6)
This also appears to have occurred since December 2017
Could the introduction of support for Bluetooth Mesh networking protocols introduced in 2017 have revealed incompatibilities in the code running on this Keyboard that Microsoft are attemting to address in their driver releases?
I have this same problem with my Wireless Desktop 850 set. I did some digging which might help shed some light.
In my device manager I have a device named Keyboard and under that MS USB Dual Receiver Wireless Keyboard (similar for mouse also). I looked at the device details and saw under Power Data that the power state mappings are as such:
I did a Google search on the states (S0-S5) and mappings (D0-D5) and from my readings S0 is when the device is at full power and all keystrokes work but anything else is Sleep (device not system) and given a D2 which means:
In general, most device context is lost by the hardware. Frequently, this state preserves the part of the context that is used to signal wake events.
I'm thinking that this is the cause of the issue and when you hit the first key it signals the wake event and then once device context is regained it switches state the to S0. If someone wanted to rewrite this driver and change the state I that would eliminate the issue as long as everything is equal to D0. I also checked on my PC and these drivers are from build 16299 (WinBuild.160101.0800).
I'm not sure why these power settings were picked in the first place. I'll assume there was good reason or intention at Microsoft for this. If someone can explain that to me that would be cool but in my mind changing this would eliminate the problem.
One other note. I forced Windows to update the driver (using search automatically so that it would pull from Windows Update) and it did update to Wireless Keyboard Filter Device. It did not find a Mouse driver update. I'll update this if I notice a change in performance.
No dongles on any of the PCs I use: Bluetooth is built in. Indeed, the PCs are Microsoft Surface PCs.
I encountered the same problem, turns out it had to do with the USB port (or in this case the extender) that the dongle was plugged in. Moving to another port fully resolved the issues for me. Makes sense given that the dongles have a whole host of other problems (not being recognised, randomly not working in certain ports, crashing the whole system when plugged in).
I noticed the same behavior von my Wireless Desktop 900 and Windows 10 1803 (build 17134) setup recently.
