Tech Community Live: Windows edition
Jun 05 2024, 07:30 AM - 11:30 AM (PDT)
Microsoft Tech Community
SOLVED

Why does my BT show as having an issue in Device Manager on Windows 11?

Iron Contributor

I have this on 2 different Windows 11 machines - different hardware, different BT units.

BoeDillard_0-1657679281200.png

 

 

BoeDillard_0-1657675093186.png

 

If I uninstall the device, it will come up fine if I rescan

BoeDillard_1-1657675140573.png

BoeDillard_2-1657675173786.png+

 

It does this 22.150.0 as well as 22.120.3

 

BoeDillard_0-1657675264843.png

 

 

But when I reboot it goes back to the same thing.  I've tried downloading the latest drivers and installing but it does the same thing on reboot.

 

7 Replies
What if anything does the event viewer say as to why Windows is shutting down the device? Is this an OEM computer or one you built? Have you tried upgrading the BIOS and chipset firmware/software?

Best,
bp

This particular one is a homebuilt Asrock Taichi z390 with the latest motherboard firmware.

 

The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.

 
- <System>
  <Provider Name="BTHUSB" />
  <EventID Qualifiers="49157">17</EventID>
  <Version>0</Version>
  <Level>2</Level>
  <Task>0</Task>
  <Opcode>0</Opcode>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2022-07-13T02:30:23.2350320Z" />
  <EventRecordID>8278</EventRecordID>
  <Correlation />
  <Execution ProcessID="4" ThreadID="9992" />
  <Channel>System</Channel>
  <Computer>CSD-ASROCK1</Computer>
  <Security />
  </System>
- <EventData>
  <Data />
  <Binary>000000000100000000000000110005C0000000000000000000000000000000000000000000000000</Binary>
  </EventData>
  </Event>
 
 
 

 

 

A command sent to the adapter has timed out. The adapter did not respond.
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="BTHUSB" />
<EventID Qualifiers="32773">3</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-07-13T02:53:13.1265456Z" />
<EventRecordID>8400</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="664" />
<Channel>System</Channel>
<Computer>CSD-ASROCK1</Computer>
<Security />
</System>
- <EventData>
<Data />
<Binary>000008000100000000000000030005800110000000000000000000000000000000000000000000000110000000000000</Binary>
</EventData>
</Event>

Got it. From the event log, it looks like a potential hardware failure. Are you able to get your hands on a USB BT dongle and try that? I have a strong feeling that that would resolve your issue (having disabled the built in BT from device manager).

Best,
Bp
It worked great right up until the point I installed Win 11. That very hour it started having issues. I'll reformat again and keep an eye on it but was hoping someone had encountered this before.
I am thinking a future of revision of driver set from Asrock should remedy the issue. You can also try to see if you can create a separate boot partition, load Windows 10 and see if the issue goes away and if so then the issue is with the drivers and its compatibility with Win 11.

Best,
Bp
I have the original Win 10 disk - works fine. I have this issue on a Dell XPS and a Samsung laptop as well.
best response confirmed by Boe Dillard (Iron Contributor)
Solution
So it turns out I was being a dork. I image my disk to several typs of pcs and laptops. Usually I just keep adding drivers to the image file until all my machines work. Usually I don't need to uninstall any drivers for my hardware to come up OK but in this case, I needed to uninstall a widcom driver package.
1 best response

Accepted Solutions
best response confirmed by Boe Dillard (Iron Contributor)
Solution
So it turns out I was being a dork. I image my disk to several typs of pcs and laptops. Usually I just keep adding drivers to the image file until all my machines work. Usually I don't need to uninstall any drivers for my hardware to come up OK but in this case, I needed to uninstall a widcom driver package.

View solution in original post