DEV Community

TJ Reyes
TJ Reyes

Posted on

Windows 11 Hid My Bluetooth Adapter. It Was Still on the Board.

The last time this happened to me, Settings had no Bluetooth toggle, Quick Settings had no tile, and Device Manager had no Bluetooth branch at all. It looked like the radio had been removed from the laptop. It hadn't. The adapter was still on the wireless card; Windows had just stopped enumerating it.

A surprising number of Windows 11 laptops don't have a standalone Bluetooth device. The radio is a function of the Wi-Fi card — Intel AX, MediaTek, Realtek, Qualcomm, take your pick — hanging off PCIe or an internal USB bus. If the parent device is disabled, stuck in a bad driver, or powered down by airplane mode, the Bluetooth child never appears. Reinstalling "a Bluetooth driver" you found by name doesn't help, because the thing you need is the vendor's wireless combo package.

Here's the path I take before I open the BIOS.

Confirm the radio is missing, not just off

I start in an elevated PowerShell window:

Get-PnpDevice | Where-Object {
  $_.FriendlyName -match 'Bluetooth|Wireless|Wi-Fi|WiFi|Airplane' -or
  $_.Class -in 'Bluetooth','Net','Radio'
} | Sort-Object Class, Status | Format-Table Status, Class, FriendlyName, InstanceId -Auto
Enter fullscreen mode Exit fullscreen mode

I'm looking for three outcomes:

  1. A Bluetooth device is present but Error or Unknown. That's a driver or start-failure problem, not a missing device. The adapter is there; it just won't start.
  2. No Bluetooth class devices, but a wireless adapter is Error, Disabled, or missing its usual children. The parent is the lead.
  3. Nothing wireless at all, including Wi-Fi. That's firmware, a killed radio switch, or a bus problem. I don't chase Bluetooth in isolation.

I also turn airplane mode off in Quick Settings, even if Wi-Fi still works. I've seen the radio management stack drop Bluetooth while leaving Wi-Fi up.

Show hidden devices before you reinstall anything

Device Manager's default view hides devices that are present in the PnP tree but not currently started. A Bluetooth adapter that failed to come back after a feature update often sits there as a greyed-out ghost.

In Device Manager: View > Show hidden devices. Then check Bluetooth, Network adapters, and System devices (sometimes the radio enumerates under a USB or Qualcomm/Intel bus device). If a hidden Bluetooth or "Generic Bluetooth Adapter" node is there, I uninstall it — and I only check "Attempt to remove the driver" if I already have the vendor package ready — then scan for hardware changes.

From PowerShell, hidden and disconnected nodes show up once you include them:

Get-PnpDevice -Class Bluetooth -PresentOnly:$false |
  Format-Table Status, Problem, FriendlyName, InstanceId -Auto
Enter fullscreen mode Exit fullscreen mode

If Problem is a code (43, 10, 45, 22), I treat that code as the actual problem and stop calling the device "missing."

Fix the parent wireless device first

This is the step I used to skip, and it's the one that usually works.

I open the Wi-Fi adapter's Properties, check the driver date and provider, and compare it to the package on the laptop maker's support page — not to Intel's generic package if this is an OEM-customized card, and not to a driver aggregator. After a Windows 11 cumulative update, I've had the inbox driver take over and lose the Bluetooth function even though Wi-Fi still associated with an access point.

I install the OEM wireless combo driver, reboot, and rerun Get-PnpDevice. If Bluetooth reappears, I stop. If the OEM package is older than the inbox driver and Wi-Fi is healthy, I still try it once; the Bluetooth function is often tied to that signed combo stack.

If the wireless adapter itself is disabled or in Error, I enable it, roll back a driver that landed yesterday, or uninstall and let Windows rediscover it. Bluetooth usually comes back with it.

Services and the radio stack

If the parent looks healthy and the Bluetooth device still never enumerates, I check the services that own the stack:

  • Bluetooth Support Service (bthserv)
  • Bluetooth Audio Gateway (BTAGService)
  • Radio Management Service (RmSvc) — this one matters when the toggle is gone after sleep or a Fast Startup boot
  • Device Association Service

They should be running, or at least set to Manual and able to start. RmSvc in particular has left me with no Bluetooth tile after a Fast Startup "shutdown," which is really a hybrid hibernate. A full restart, or turning off Fast Startup, is a fair test here.

Microsoft's own walkthrough, Fix Bluetooth problems in Windows, is worth running in parallel: airplane mode, the Get Help troubleshooter, and a driver reinstall. It's written for pairing and toggle issues, but the same checks apply when the adapter is gone from Device Manager. The related page on updating Bluetooth drivers is the official sequence for a roll-back or a clean reinstall if the adapter is visible and just failing to start.

For a complete GUI sequence — show hidden devices, the troubleshooter, restarting the support service, and a clean driver reinstall — I keep this guide to Bluetooth missing from Device Manager in Windows 11 bookmarked. That's the click-through I send people who don't want to live in PowerShell.

When I actually open the BIOS

Only after the PnP tree and the vendor driver have failed do I reboot into firmware settings. I look for a Wireless / Bluetooth / WLAN + Bluetooth toggle and make sure it's enabled. Some business laptops also have a "wireless switch" or a function-key radio lock that survives Windows.

If BIOS has Bluetooth on, the parent device is healthy, and Get-PnpDevice still shows nothing in the Bluetooth class, I do one last hardware check: a different Windows boot (a Windows 11 USB in trial mode is enough) to see whether the radio enumerates there. If it doesn't, I'm done with software. If it does, I repair-install Windows and keep apps and files.

What I won't do

I won't install a random "Bluetooth driver" from a ranking page that asks me to run a scanner. I won't disable Microsoft's driver signature checks. And I won't assume the card is dead because Device Manager looks empty.

On Windows 11, an empty Bluetooth branch usually means the radio is powered down, hidden, or detached from a failed parent wireless driver. Ask the PnP tree first. The adapter is often still on the board.

Top comments (0)