Logitech K810 and new Surface Pro 3 firmware update not playing nicely Bluetooth Problem

Anonymous
2014-09-17T14:52:37+00:00

Hi there,

There's an active discussion over on the Surface forums regarding the 9/9/2014 firmware update causing Bluetooth issues, primarily w/ the K810 (but I'd imagine this could be w/ other BT keyboards as well).

http://www.surfaceforums.net/threads/logitech-k810-keyboard-and-9-9-14-firmware-update.11391/

Prior to this firmware update I was able to use my Logitech K810 without issue with my Surface Pro 3. However, now it just goes into a connect/reconnect loop. I'll see "driver error" briefly. And then it'll try connecting again.

Looking into the event log for Administrative events, I see this:

Bluetooth HID device  either went out of range or became unresponsive.

I also see another event within seconds that says this:

Metadata staging failed, result={66F5F5A4-2104-53C0-BCDF-9DD1AF9AE33F} for container '0x80070490'

All of this appears to be an issue with the driver and/or firmware.

Furthermore, the keyboard works when pairing (typing in the keycode), but immediately after pairing it fails. So there is certainly something wrong and I don't believe it's the keyboard.

Anyone?

-Steve

Surface | Surface Pro | Network

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 No comments
Answer accepted by question author
Anonymous
2014-10-06T18:36:55+00:00

Hi all, I just installed the 10/6/2014 System Hardware Update this morning and appear to be having no issues with my Logitech Keyboard anymore.  You may want to installed it.

You want to give a try.  So far, no issues encountered.  Hoping it stays that way.  ;-)

Hope this helps!

Was this answer helpful?

0 comments No comments

73 additional answers

Sort by: Oldest
  1. Anonymous
    2014-09-17T15:51:16+00:00

    I just rolled back the driver and tried...no such luck.

    The date on the driver before rolling back was 8/19, so I'm led to believe that it's the firmware not the BT driver.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-09-17T16:18:37+00:00

    On Wed, 17 Sep 2014 15:51:16 +0000, LookitsPuck wrote:

    >>I just rolled back the driver and tried...no such luck.

    >>

    >>

    >>

    >>The date on the driver before rolling back was 8/19, so I'm led to believe that it's the firmware not the BT driver.

    I'm thinking that the only way you can get attention is to open a support

    ticket. And if someone who is afflicted can actually go to a Microsoft store

    with the SP3 and the Logi keyboard and demo the issue with the Logi and ask to

    try it with the store's Sculpt keyboard, that MIGHT get someone's attention.

    Try to open a support case on this. (Warning, they will most likely ask you to

    refresh/reset your Surface, so be prepared for pain).

    __________________________________________________________________________________________________

    Barb

    Windows Entertainment and Connected Home MVP

    My Blog - http://digitalmediaphile.com/

    Please mark as answered if this answers your question

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-09-17T19:46:23+00:00

    I'm having the same issues as listed by the thread OP.  My Logitech k810 Bluetooth keyboard is no longer functioning properly with the 9/9/14 firmware update (Bluetooth driver 15.68.3055.107).   It's not acceptable for me to do another system reset since I've already reset my Surface Pro 3 four times in the last 2.5 months.  I would hope Microsoft picks up this issue and provides a fix in a future Firmware update.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-09-18T16:03:30+00:00

    I'm having exactly the same issues with this keyboard and it only started after the  September patches. I haven't tried this with another bluetooth keyboard yet. I have no idea what the problem is. I may have to return this keyboard and buy Microsoft's new universal mobile keyboard (perhaps that was their plan all along?)

    Was this answer helpful?

    0 comments No comments