Windows 10 missing first keystrokes from Microsoft Designer Bluetooth Keyboard after Fall Creators' Update

Anonymous
2017-12-02T19:37:50+00:00

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.

Windows for home | Windows 10 | Devices and drivers

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

99 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-01-10T21:26:23+00:00

    Thanks for your answer TimLeon.

    There are some twenty five different solutions listed on the link you provided. At first site none of them appear to refer to the issue at hand (Microsoft Designer Keyboard missing keystrokes). Would you specify which of them you believe will fix the problem please.

    Are you a Microsoft employee?

    Thanks

    David.

    Not only that but the same useless advice was given somewhere near the beginning of this thread and was reported as such.  This is a f#@5&ing joke.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-01-02T17:54:43+00:00

    Exactly the same as my experiences with 2 different computers using the Microsoft Designer Keyboard. 

    Despite several attempts to contact MS using their "feedback hub" I have to tell you that doesn't work either - so there is no way of getting any response or action from them.

    Very frustrating, particularly as I personally know two other people using the same equipment with the same problem also starting from the "fall update" fiasco.

    Perhaps one day someone from MS will see this and decide to provide a meaningful answer?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2017-12-13T18:42:57+00:00

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2017-12-13T09:06:52+00:00

    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?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2017-12-12T00:55:27+00:00

    Hi Argel

    I am using a Surface Book where the drivers are updated by Microsoft.

    My keyboard and mouse worked perfectly before FCU. Since FCU they have been awful.

    The keyboard misses keystrokes, repeats keystrokes and is generally slow to respond.

    The mouse often lags many seconds behind the physical movement.

    All the drivers are up to date, as checked via device manager. Windows Update is fully up to date.

    FYI: I am a Microsoft MVP and ex-Employee of 13.5 years as an Escalation Engineer and this is something that Microsoft broke in the latest update and something they will need to fix ASAP.

    David

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments