Question Why does my BT show as having an issue in Device Manager

boed

Senior member
Nov 19, 2009
461
7
81
Hello,

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


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

1657677315466.png

1657677324791.png

It does this 22.150.0 as well as 22.120.3 (same issue on other machine - different BT unit - tried latest drivers
1657677363540.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.

Is there another service besides bluetooth services I should look at?
 
Last edited:

Zoozuu

Member
Oct 21, 2020
140
20
41
which bluetooth units? how are you connecting them? are these onboard or usb? it seems like one is onboard through a dell and the motherboard is a asrock. are the drivers actually for windows 11? some drivers can be compatible with windows 10 and 11 but there are a lot of drivers that are only good for one or the other.

EDIT: ah I see it says code 43 so your connecting these through usb then? did you just buy these?
 
Last edited:

boed

Senior member
Nov 19, 2009
461
7
81
I tried a samsung NP900X5N-X01US, Dell XP15 and a Asrock Taichi z390. It has the last firmware available for the motherboard.
 

boed

Senior member
Nov 19, 2009
461
7
81
The onboard built in BT device won't start after a reboot unless I uninstall it and scan for changes. I've complete uninstalled every BT driver in the various device manager views, I've uninstalled the intel software. I've tried the intel direct and Asrock recommended drivers (slightly different). I've uninstalled and removed all drivers inbetween. I've reinstalled - same issue on every reboot.
 

boed

Senior member
Nov 19, 2009
461
7
81
So it turns out when I imaged it to a few PCs I kept updating the image with the new hardware. Usually I can just disable a service or reinstall the intel drivers. In this case, I needed to uninstall the widcom driver package and it resolved the issue.
 

ASK THE COMMUNITY