Bluetooth Not Working on Windows 11? How to Fix
Short answer: Most Bluetooth failures on Windows 11 are driver conflicts from Windows Update, not dead hardware. Open Device Manager — if your adapter shows up with no yellow warning, the problem is software. Check for recent Windows Updates that broke things (24H2 was terrible for this), restart all three Bluetooth services, and uncheck 'Allow the computer to turn off this device to save power' on both the adapter and every USB Root Hub.
Open Device Manager (Win+X, pick it from the list) and expand Bluetooth. If your adapter shows up with no yellow warnings, the hardware is fine — the problem is software. About eleven out of twelve Bluetooth tickets I handle are software-fixable. Code 10 in Device Status means the device can’t start, which is almost always a driver issue. Code 43 is trickier and could be driver corruption or genuine hardware failure. If the entire Bluetooth category is missing, click View and check “Show hidden devices” — a grayed-out adapter means the driver got wiped or corrupted and reinstalling it usually brings everything back.
If Bluetooth doesn’t appear at all even with hidden devices, check your BIOS — Bluetooth gets disabled there more often than you’d think, especially after a BIOS update resets defaults to factory. On combo WiFi/Bluetooth cards, if WiFi also stopped working at the same time, the whole card’s driver failed and fixing WiFi usually brings Bluetooth back too.
Windows Update Broke It
This is where the majority of my Bluetooth tickets come from. Microsoft rolled out 24H2 and things went sideways fast. Headsets that worked on 23H2 suddenly showed “Connected” in Settings but played zero audio — the January 2025 cumulative patch did that, and Microsoft took weeks to push a fix even though over 1,300 users were screaming about it on the Q&A forums. A few months later the visibility bug hit: devices paired and working but invisible in Quick Settings and the Settings app. Microsoft pushed an emergency hotpatch outside the normal Patch Tuesday schedule for that one, which tells you how bad it was.
On top of the Windows issues, Intel’s Bluetooth driver version 23.60 shipped with those 24H2 updates and broke auto-reconnection on the entire AX200/AX210/AX211 lineup. Instead of headphones reconnecting when you powered them on, you had to go into Settings, remove the device, put headphones in pairing mode, re-pair, every single time. A customer did this ritual twice a day for three weeks before calling us.
If your Bluetooth died right after an update, check Settings, Windows Update, Update history to see what installed recently. If the dates line up, uninstall the offending patch — scroll to “Uninstall updates,” find the KB, remove it, restart. If you aren’t sure which one, go to Settings, System, Recovery, “Go back” — that rolls your entire Windows build back to what was running before, though the option vanishes after 10 days so don’t sit on it. Once it’s fixed, grab Microsoft’s “Show or Hide Updates” tool to block the same update from sneaking back. Otherwise Windows pushes the same broken patch again within a week.
For Intel adapters specifically, go directly to Intel’s driver download page rather than using what Windows Update provides. Intel’s own driver is almost always a version or two ahead. If you installed version 23.60 and auto-reconnect broke, roll back in Device Manager — right-click the adapter, Properties, Driver tab, Roll Back Driver. Our driver update guide covers the full process.
Power Management
My single favorite Bluetooth fix because it’s so well-hidden and causes the most maddening symptom: Bluetooth works fine for a while, randomly disappears, comes back on its own, disappears again.
Device Manager, find your Bluetooth adapter, right-click, Properties, Power Management tab. Uncheck “Allow the computer to turn off this device to save power.”
Now the part that trips everyone up: do the same thing for every USB Root Hub listed under Universal Serial Bus controllers. On most laptops the Bluetooth adapter connects through an internal USB bus. When Windows puts the USB hub to sleep to save power — which it does aggressively on battery — it takes Bluetooth down with it. A customer had her Logitech MX Master 3S disconnecting every 15-20 minutes on an HP Envy. No pattern, nothing in Event Viewer. The USB Root Hub was going to sleep after 15 minutes of what it considered “inactivity” — even though the mouse was sending position data the whole time. Unchecked one box, zero disconnects since. This same USB power management issue also kills webcams mid-call. If your Bluetooth mouse specifically is the device dropping, the mouse troubleshooting guide covers the HID driver and adapter-specific fixes beyond power management. Bluetooth keyboards have their own quirk too — if a wireless keyboard starts typing wrong characters after reconnecting, Windows sometimes switches the input language during the re-pair and you end up on a different layout without realizing it.
While you’re in there, open services.msc and check three services: Bluetooth Support Service, Audio Gateway Service, and Bluetooth User Support Service. All three need to be running. The Support Service is the main one — if it shows “Running” but nothing works, restart it anyway because sometimes it gets wedged in a bad state where it’s technically alive but not processing connections. Restarting a service that’s already “running” fixes maybe one in eight tickets where everything else checks out.
Connected But No Sound
The headset is paired, Windows says connected, volume isn’t muted, but nothing comes through.
Bluetooth headsets run two separate audio modes. A2DP handles stereo music — decent quality, no microphone. HSP/HFP handles calls — terrible quality, mono, but includes the mic. When Windows switches to HSP/HFP mode because any app requested microphone access, stereo audio stops because the headset can’t do both simultaneously over classic Bluetooth.
Right-click the speaker icon in the taskbar, Sound Settings, scroll to output device. You’ll see two entries for the same headset — one labeled “Stereo” and one “Hands-free AG Audio.” Select Stereo for music and video. If Stereo isn’t listed, Windows locked the headset into call mode and you need to close whatever app grabbed the microphone. If your headphones aren’t being detected at all — wired or wireless — the problem might be upstream of Bluetooth entirely.
Windows 11 24H2 introduced Low Energy Audio, which is supposed to be better — higher quality, lower latency, supports stereo and mic simultaneously. But it breaks a lot of older headphones. A customer had Sony WH-1000XM5s that connected fine but played zero audio — worked perfectly on his phone. The fix: Settings, Bluetooth & devices, click the headphones, turn off “Use LE Audio when available.” LE Audio was trying to negotiate a connection mode the headphones couldn’t handle and instead of falling back to A2DP, it just failed silently.
If your Bluetooth is flaky rather than dead — drops during large downloads, audio stutters while streaming — your WiFi is probably stepping on it. Most laptops use a combo card where WiFi and Bluetooth share the 2.4GHz band. Force your WiFi onto 5GHz and the drops stop. If your WiFi also keeps disconnecting, fixing the connection stability often fixes both, and if you’ve been through everything here and nothing sticks, we can check adapter status, driver versions, and event logs remotely — usually takes about fifteen minutes to find the exact cause.
Frequently Asked Questions
Does restarting my PC actually fix Bluetooth problems?
Sometimes. A restart clears the Bluetooth driver stack and reinitializes all three services. If the issue was a one-time service crash or a glitch during a Windows Update reboot, restarting genuinely fixes it. But if it comes back after every restart, you've got something persistent — driver conflict, power management, hardware — that restarting doesn't touch.
Can a Windows Update really break Bluetooth?
It has happened multiple documented times. KB5050009 broke Bluetooth audio in January 2025. KB5084897 was an emergency fix for a visibility bug. Intel driver v23.60 bundled with 24H2 caused auto-reconnect failures across the AX200/AX210/AX211 lineup. The Microsoft Q&A forums have threads with over 1,300 users reporting 24H2 Bluetooth issues specifically.
Is it worth buying a USB Bluetooth dongle?
If your built-in adapter is dead or chronically unstable, a $13 TP-Link UB500 is the easiest fix that exists. It uses completely different hardware and drivers from your internal adapter, so whatever Windows Update or chipset bug caused the internal one to fail won't affect the dongle. Only downside is it takes up a USB-A port.
My headphones connect but the mic doesn't work on calls.
Audio profile switching. Calls need HSP/HFP mode for the microphone, but some headsets handle the switch from A2DP badly. Check that 'Hands-Free Telephony' is enabled — Settings, Bluetooth & devices, click your headphones, scroll down. If it's already on and still broken, the headset firmware might be out of date.
Why does Bluetooth drop whenever I download something large?
Your WiFi and Bluetooth are sharing the 2.4GHz band on a combo card. Heavy WiFi traffic pushes Bluetooth out of the way. Force your WiFi onto the 5GHz band and the Bluetooth drops stop.