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!
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.
My Razer Orochi 2013 Bluetooth mouse also shows GREATLY REDUCED SMOOTHNESS when moving after the September Firmware update. Also experienced Logitech BT keyboard issue with mine, but not K810. Uninstalling SetPoint did help with that, but I've had no luck with the Orochi mouse's smoothness issue, which is clearly more important to me as I sometimes play games on my Surface Pro 3.
On Wed, 24 Sep 2014 01:36:45 +0000, hy3301 wrote:
>>I have spend nearly one hour chatting with the customer service. I have give him the link of this thread. He said he will inform the team to review this problem, and he promised that a fix will come (but who knows when), as for now, the workaround is to reset to previous version of the firmware. I guess if rolling back the driver version won't work, we are left with the only solution to reset the system totally, that will be too painful to do.
did they give you a support case #? what is it?
With the caveat that I can't vouch for the authenticity or whether or not the
download is malware free, I found the previous drivers and bits at
July- the previous version of the BT driver appeared in the July update:
August - same version BT driver as the one in the July update
If anyone wants to try installing the older driver (at their own risk), I'd
suggest first doing a system restore checkpoint so you can roll back completely
before trying this. I'd be interested if installing the older driver providers a
solution to these issues.
__________________________________________________________________________________________________
Barb
Windows Entertainment and Connected Home MVP
My Blog - http://digitalmediaphile.com/
Please mark as answered if this answers your question
On Wed, 17 Sep 2014 14:52:37 +0000, LookitsPuck wrote:
>>All of this appears to be an issue with the driver and/or firmware.
With the caveat that I can't vouch for the authenticity or whether or not the
download is malware free, I found the previous drivers and bits at
July- the previous version of the BT driver appeared in the July update:
August - same version BT driver as the one in the July update
If anyone wants to try installing the older driver (at their own risk), I'd
suggest first doing a system restore checkpoint so you can roll back completely
before trying this. I'd be interested if installing the older driver providers a
solution to these issues.
__________________________________________________________________________________________________
Barb
Windows Entertainment and Connected Home MVP
My Blog - http://digitalmediaphile.com/
Please mark as answered if this answers your question
