This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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
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.
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!
OK, I'm still seeing a little bit of anomalous behavior, but not super bad. It's useable now. :-)
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
i have had similar issues- cant get it to pair thought it was the keyboard and have returned it brian
Not sure if there is a better thread to post to. I have the problem with the keyboard but fortunately I have alternative keyboards that work pretty well. However my issue is that no Bluetooth connection seems to last more than about an hour. I've checked all of the device drivers and they're all up to date, which could of course be the problem. The neat thing about my problem is that I have a surface pen and surface touch Bluetooth device. Both of these fail every hour or so. And of course, that means that the problem must clearly be a Microsoft problem. If you folks feel that it would make sense I'm happy to also open a ticket at Microsoft.
