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: Newest
  1. Anonymous
    2014-10-07T01:33:36+00:00

    Yep! I can confirm that my problems are fixed, at least so far! yay!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-10-06T19:01:42+00:00

    OK, I'm still seeing a little bit of anomalous behavior, but not super bad.  It's useable now. :-)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-10-06T06:56:50+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

    Steve and all in the thread,

    Thank you for the sensible coverage re this Logitech K810 keyboard pairing connect/disconnect issue. I had the same problem with my Surface Pro2, but bought my Pro3 on a recent overseas business trip, all was good until I came home and paired with my K810 and within a day, pairing was dropping in and out. Same messages as all have detailed. I was about the throw the K810 out!

    Hopefully MS can put some focus into this problem.

    Peter

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-10-04T17:52:03+00:00

    i have had similar issues- cant get it to pair thought it was the keyboard and have returned it brian

    Was this answer helpful?

    0 comments No comments