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: Most helpful
  1. Anonymous
    2014-09-23T11:11:12+00:00

    On Mon, 22 Sep 2014 17:45:25 +0000, CharlieBird wrote:

    >>What's frustrating is the deafening silence from Microsoft on the matter.   It would be nice to see some sort of acknowledge that a problem exist and that a solution is being developed.

    I've complained about the silence as well. I've also asked that the previous

    working driver be posted.

    __________________________________________________________________________________________________

    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
  2. Anonymous
    2014-09-23T10:58:43+00:00

    On Mon, 22 Sep 2014 18:01:59 +0000, TomSong999 wrote:

    >>Where to download the older drivers for BT? I have the similar issue with my Asus Transborad BT keyborad when connecting to my pro3. The key board can not work properly with pro3 while it is working perfectly with lenovo x220 (Win7)

    Microsoft removed the old drivers from their official site. If you search the

    web, you might find places like Softpedia that have them but there is no

    guarantee that they are official and malware free, so use at your own risk if

    you find them.

    __________________________________________________________________________________________________

    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-22T18:01:59+00:00

    Where to download the older drivers for BT? I have the similar issue with my Asus Transborad BT keyborad when connecting to my pro3. The key board can not work properly with pro3 while it is working perfectly with lenovo x220 (Win7).

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-09-22T17:45:25+00:00

    It's becoming pretty obvious that Microsoft released a Bluetooth driver that isn't functioning quite right.  Since I work in the industry I'm fairly understanding that these things happen.  It's almost impossible to test every combination of devices.   What's frustrating is the deafening silence from Microsoft on the matter.   It would be nice to see some sort of acknowledge that a problem exist and that a solution is being developed.

    Was this answer helpful?

    0 comments No comments