4
1
I've got three different Bluetooth keyboards that I use on my Windows 8.1 PC.
- Apple Wireless Keyboard
- Logitech K810
- Generic knockoff version on an Apple Wireless Keyboard by iClever
I've been using the knockoff Apple Wireless Keyboard for about six months, and yesterday I decided to switch to the Logitech K810. I went to Devices and Printers in the Control Panel and selected Add a device. I picked out the K810 from the list of available devices, and then I got a message saying
"That didn't work", "Try again, and make sure your keyboard is still discoverable."
I tried restarting my PC and that didn't work, so I tried adding my Apple Wireless Keyboard, and I got the same message that I got when attempting to add the K810. After getting this message, I have to restart the Bluetooh Support Service in order to get my device to show up when clicking on Add a device.
I have removed and readded the Knockoff keyboard a few times, so I know Bluetooth is working. For some reason I cannot add either the Apple or Logitech keyboard. Does anyone know how to get these keyboards paired successfully
In my Event Viewer, I can see a couple of messages:
Log Name: System
Source: BTHUSB
Date: 12/2/2014 9:14:44 AM
Event ID: 3
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: dana
Description:
A command sent to the adapter has timed out. The adapter did not respond.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="BTHUSB" />
<EventID Qualifiers="32773">3</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-12-02T14:14:44.574266200Z" />
<EventRecordID>419031</EventRecordID>
<Channel>System</Channel>
<Computer>dana</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Binary>00000800010000000000000003000580570C00000000000000000000000000000000000000000000570C000000000000</Binary>
</EventData>
</Event>
Log Name: System
Source: BTHUSB
Date: 12/2/2014 9:14:40 AM
Event ID: 5
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: dana
Description:
The Bluetooth driver expected an HCI event with a certain size but did not receive it.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="BTHUSB" />
<EventID Qualifiers="49157">5</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-12-02T14:14:40.560627300Z" />
<EventRecordID>419030</EventRecordID>
<Channel>System</Channel>
<Computer>dana</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Binary>00000C000100000000000000050005C00E000000000000000000000000000000000000000000000024000000040000000E040157</Binary>
</EventData>
</Event>
Log Name: System
Source: BTHUSB
Date: 12/2/2014 9:14:40 AM
Event ID: 28
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: dana
Description:
The local adapter does not support Bluetooth Low Energy.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="BTHUSB" />
<EventID Qualifiers="32773">28</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-12-02T14:14:40.560627300Z" />
<EventRecordID>419029</EventRecordID>
<Channel>System</Channel>
<Computer>dana</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Binary>0000000001000000000000001C000580000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
Log Name: System
Source: BTHUSB
Date: 12/2/2014 9:14:40 AM
Event ID: 18
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: dana
Description:
Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="BTHUSB" />
<EventID Qualifiers="16389">18</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-12-02T14:14:40.545001800Z" />
<EventRecordID>419028</EventRecordID>
<Channel>System</Channel>
<Computer>dana</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Binary>00000800010000000000000012000540000000000000000000000000000000000000000000000000E000000000000000</Binary>
</EventData>
</Event>
The K810 manual says it is only discoverable for 15 minutes after pressing its connect button. See also Using Apple Wireless Keyboard on Windows.
– harrymc – 2014-12-09T20:59:12.177Any comments on the above? – harrymc – 2014-12-11T20:39:04.157
No, no comments. Of course I'm trying to connect within 15 minutes of pressing the connect button. – coder1 – 2014-12-15T13:16:14.660
Good. Now do you have any comments on the procedure in the linked article? – harrymc – 2014-12-15T13:24:49.140
I've done that as well. Still no luck. – coder1 – 2014-12-15T13:51:37.137
Verify in Device Manager / Network adapter that the correct driver is used. – harrymc – 2014-12-15T13:57:29.590
I don't believe either keyboard shows up in the device manager. – coder1 – 2014-12-15T14:43:42.157
I meant the wireless adapter. See also if Windows Update has optional updates that relate to hardware drivers. – harrymc – 2014-12-15T15:06:29.530
I really appreciate the help, but it's still not working. – coder1 – 2014-12-15T18:30:58.710
I think you have a problem with the driver for the wireless adapter. It would help to know the adapter's model (BTH?) and what driver is assigned; for the driver go into Device Manager / Network adapter / right-click wireless adapter / Properties / Driver tab / Driver Details button, and post a screenshot of the dialog. – harrymc – 2014-12-15T18:42:46.033
Having the exact same problem on a Windows 10 machine, Bluetooth works, a magic mouse and bluetooth speaker connect fine, it is my Logitech K810 that has the exact same "That didn't work", "Try again, and make sure your keyboard is still discoverable." when pairing, wish I could fine an answer, oh well, just have to buy a Logitech keyboard that works with a Unifying receiver – Brian Ogden – 2016-11-24T21:10:54.727