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-30T16:18:40+00:00

    i'm hoping this coming patch Tuesday, it will be fixed. i'm holding onto the keyboard (not returning it) in hopes that a fix comes soon. There's no other keyboard for the Surface as good as this one.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-09-30T04:10:12+00:00

    I am relieved that I'm not going insane and others are experiencing the same issue I am with their Logitech keyboard. I am going to follow thus thread and sincerely hope a resolution is pending. I'd love my surface even more if it worked as expected... ;-)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-09-25T02:12:24+00:00

    No, they didn't. But they have registered my email, they said they will keep me updated on this issue. If I got an email from them, I will post it here.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-09-24T17:29:38+00:00

    I spoke with Logitech customer service regarding the Keyboard issue yesterday.  They said they have tickets open with Microsoft about the issue, and there is not a lot they can do from their end.  Their reasons were as follows (to the best of my understanding):  They technically don't have software that specifically supports Windows 8.1 because, as they said, it's an operating system that is not yet in it's final version.  Because it is still a work in progress, they can't release software for a moving target.  They and other vendors have been asking for MS to finalize the OS so they can release software to match.  They said many vendors are facing similar frustration with 8.1.   They said a workaround that worked for some was to uninstall the Windows 8.0 Setpoint, restart, and install the XP setpoint software.  I attempted it, but I couldn't get it to install.  

    For now, I exit Setpoint when use the keyboard to eliminate the worst of the issues, and re-inable it when I need the added button functionality of my Logitech mouse.  Kind of a pain, but seems to be the best of the bad choices at this point.  From what Logitech says, the ball is in Microsoft's court.

    Don't kill the messanger... just relaying what I've heard.

    Was this answer helpful?

    0 comments No comments