Unknown Device in Device Manager After 1803 Update

Basically i made a USB stick and made an in-place upgrade repair. This fixed the BTH\MS_BTHL2CAP.

boombastic...thanks so much. Your idea worked. It takes a little while but still much easier than a reinstall and having to install drivers and apps all over again. I posted in the Dell Community as well and there are others with this issue. For those on here that need the help here's the link for an in-place upgrade repair....Repair Install Windows 10 with an In-place Upgrade Windows 10 Tutorials . Just make sure to update your installation media to the 1803 April Update iso.

Thank you so much folks! now the unknown device in device manager gone! i'm using in place upgrade bootable usb drive with windows 10 version 1803 in it...

mccnavy said:

boombastic...thanks so much. Your idea worked. It takes a little while but still much easier than a reinstall and having to install drivers and apps all over again. I posted in the Dell Community as well and there are others with this issue. For those on here that need the help here's the link for an in-place upgrade repair....Repair Install Windows 10 with an In-place Upgrade Windows 10 Tutorials . Just make sure to update your installation media to the 1803 April Update iso.

Hello Guys,

Could you please make a backup of the driver and upload it?

I want to try if I can manually install the driver, it would be easier than perform a in place upgrade.

Thanks

mgcarnevali said:

Hello Guys,

Could you please make a backup of the driver and upload it?

I want to try if I can manually install the driver, it would be easier than perform a in place upgrade.

Thanks

I would upload it but I just went and looked and while the in-place upgrade worked, it didn't add the driver in question. I still don't see it....the upgrade-in-place repair resolved the issue without simply adding the driver back.

mccnavy said:

I would upload it but I just went and looked and while the in-place upgrade worked, it didn't add the driver in question. I still don't see it....the upgrade-in-place repair resolved the issue without simply adding the driver back.

Hello,

You have to expand the bluetooth section in the device manager in order to see the device and the driver version, I think that there is no way to fix the issue without installing a driver.

Thanks

Max

mgcarnevali said:

Hello,

You have to expand the bluetooth section in the device manager in order to see the device and the driver version, I think that there is no way to fix the issue without installing a driver.

Thanks

Max

Yep...expanded and no new devices were added. The device with hardware ID BTH\MS_BTHL2CAP is no longer listed...and its driver folder is not in the driverstore. The issue may have simply been a Windows 10 error that is now fixed. I don't see it in my other machines either.

For anyone interested, I could only resolve this with a Windows 10 install/repair from a USB thumb drive. After completion, "BTH\MS_BTHL2CAP" is no longer present. After the install/repair process, I ran a complete dump of all Hardware IDs from my machine (using DevCon) to see if it was hiding somewhere, but it's nowhere to be found. I was hoping to snag a driver from it and host it, but no such luck. THANKS for the recommendation to install/repair!
*Running a Dell XPS 8920 with the latest drivers and updates. SFC scans and countless other repairs had no affect on this missing driver.

Same problem here. For me it's with an external USB Bluetooth adapter. It looks like some sort of stray component that doesn't get handled properly in the 1803 upgrade and shouldn't be showing up or getting enumerated.

I delved deeper by plugging in the same USB Bluetooth adapter into a fresh machine, made sure to install the same manufacturer drivers, and paired the same phone with it. When I went into Device Manager I made sure to show hidden devices, and then compared the two systems side by side. I didn't see any extra or missing Bluetooth components or Bluetooth Virtual Devices that the offending machine should have.

Practically speaking, Bluetooth functionality is working, but this issue causes that annoying yellow exclamation mark under Devices and Printers, and I think Windows superficially acts as if the device is not installed correctly, even though it still works.

One way I found to get around the exclamation mark is to just force install onto this unknown device a driver for, say, the Broadcom L2CAP Interface (even though I already have the L2CAP Interface present). This causes a duplicate L2CAP Interface entry in Device Manager, but at least it gets rid of the exclamation point, though I'd rather not do this.

Ideally, we need to have a way to just remove this unnecessary, "phantom" "BTH\MS_BTHL2CAP" component (not the real L2CAP Interface) from the registry so that Windows doesn't create it or re-detect it -- as uninstalling the unknown device from the Device Manager doesn't solve the problem; it just comes right back the next time you enable the device or turn on Bluetooth.