Bluetooth not working in Windows 11: separate pairing, connection and audio problems

“Bluetooth is not working” can describe several different failures. The Bluetooth switch might be missing, headphones may never appear for pairing, a known keyboard may refuse to reconnect, or a connected headset may play no sound. A useful check must match the symptom. Removing every accessory does not make those problems equivalent.

This guide covers Windows 11 with its built-in Bluetooth settings and supported diagnostic tools. Menu details vary by release, and the accessory's own pairing procedure still matters. Microsoft documentation was reviewed October 19, 2026; no device-specific compatibility or hands-on test is implied.

Choose the problem you actually have

1. Keep a usable input method

Before changing anything involving a keyboard or mouse, ensure you can still operate the PC. Use its built-in keyboard and touchpad or an already available wired alternative. Do not remove your only working Bluetooth input device while depending on it to complete the instructions. On shared or work equipment, check whether the accessory and its pairing are managed.

Record the PC model, accessory model and exact status. Names such as “Headphones” can be ambiguous when several similar devices are nearby. The goal is to troubleshoot your accessory without inadvertently selecting a colleague's device or changing a working connection.

2. Check the Windows radio and accessory separately

1. Open Settings, then Bluetooth & devices.
2. If the switch is available, confirm Bluetooth is on and Airplane mode is off.
3. Charge the accessory or check its batteries.
4. Place it near the PC and use its manual to enter pairing mode.
5. Check whether the expected model appears among available devices.

Microsoft's Bluetooth troubleshooting overview also notes that some USB devices can interfere with nearby Bluetooth connections. As a comparison, move the accessory away from an unshielded USB hub without disconnecting storage that is currently in use.

If the switch is absent, check the PC's specifications before assuming a radio failure. A desktop can have Wi-Fi without the Bluetooth capability you expected. Do not buy an adapter until you understand what the existing computer supports.

3. Pair intentionally, then test one function

Open the Bluetooth device picker in Quick Settings or the Add device control under Bluetooth & devices. Select the accessory you recognize and follow its prompts. Check any displayed confirmation rather than accepting an unexpected connection. Microsoft explains the supported route in its pairing guide.

For a keyboard, type a short harmless line in a blank document. For headphones, play a short familiar sound at low volume. For a mouse, check pointer movement before trying advanced buttons. A narrow test tells you whether the basic connection works without involving a complex meeting app or an accessory-specific feature.

If an accessory remains paired to another nearby device, use that device's normal Bluetooth controls to disconnect it for a comparison, when you own and control that connection. Do not erase all of its pairings or apply a factory reset merely to see what happens.

4. Treat connected-but-silent headphones as an audio branch

Open Settings, System, Sound, and inspect the selected output. If the laptop's speakers are selected, choose the connected headphones and test again. Then check the app's own output setting and mute controls. Microsoft's sound troubleshooting guide covers choosing an output and checking volume.

For example, a headset can work for a Windows notification while a meeting continues through a monitor. That comparison points toward the meeting app's destination rather than proving a damaged Bluetooth radio. Test outside the call, then reopen the app's audio settings. Keep microphone and speaker choices separate; hearing sound does not prove that the intended microphone is selected.

5. Use Get Help before changing the installation

Search Start for Get Help and describe the specific Bluetooth symptom. Microsoft's troubleshooting overview recommends this diagnostic route for Windows 11. Record what it reports and any requested action. If it recommends restarting, save your work and use Start, Power, Restart normally. Test the same accessory function afterward.

For a personally managed PC with an internet connection, review Windows Update for applicable updates. The official driver guide also describes Device Manager's Update driver control. Finding no newer driver does not prove the hardware is faultless; it only describes that search's result. This guide stops before uninstalling adapters or applying driver downloads.

A repeatable comparison prevents unnecessary re-pairing

Imagine that headphones connect successfully at the desk but stutter beside a crowded hub. Test at the same volume with the same audio file, then change only their position. If the symptom follows the location, preserve that observation. If the problem follows one app instead, preserve the app name and version. Neither result requires claiming that every cause has been ruled out.

When a previously working accessory reconnects, verify it once after a normal restart. Check that the intended device is selected, rather than accepting sound from the PC's speakers as success. Note the condition that improved the result so you can reproduce it.

Common mistakes and the stopping point

Repeatedly selecting Add device while an accessory is not discoverable wastes time. Removing the only usable keyboard can leave you stranded. Treating a sound-output mistake as a pairing failure adds unnecessary changes. Downloading a generic “Bluetooth fixer” introduces another unknown without establishing compatibility.

Stop when the radio remains absent despite confirmed hardware support, Windows reports an adapter error, a managed setting blocks the route, or the accessory fails on more than one supported device. Give official support the two model names, the exact stage that fails and the results of your controlled test. Keep any functioning alternative available while the hardware or driver question is investigated.

Prepared with AI assistance from the linked documentation. This is a source-led explanation, not a claim of hands-on testing across every device. Read the editorial policy.