Bluetooth drivers
Fix wireless peripheral connections, pairing issues, and missing Bluetooth toggles.
You might also need
Bluetooth drivers we cover
What does a bluetooth driver do?
A Bluetooth radio driver connects the operating system to the Bluetooth controller over the Host Controller Interface, the standardised HCI command and event channel defined by the Bluetooth specification. On most laptops the controller shares a combo module with the Wi-Fi radio, so the same M.2 card carries both, and the driver arbitrates the shared 2.4GHz antenna between them. Above HCI, Windows runs the Bluetooth stack that exposes profiles to applications.
Discovery and pairing are the driver's most visible jobs. It drives inquiry scans to find nearby devices, exchanges capabilities, and runs the pairing exchange that produces a bond, a stored long-term key so the two devices trust each other on future connections. Secure Simple Pairing and, for Low Energy, the LE Secure Connections model both run through commands the driver issues to the controller.
Why keeping it updated matters
Bluetooth is a busy, backwards-compatible protocol, so its driver accumulates fixes for a long list of quirky accessories. A new pair of earbuds might advertise an aptX Adaptive codec or an unusual HFP version that an older driver mishandles, and the symptom is garbled call audio or a headset that connects for music but not for calls. Refreshed builds add the codec negotiation and profile handling that make those accessories behave.
Coexistence with Wi-Fi is another reason to stay current. Because the combo module shares one 2.4GHz antenna, the driver runs a coexistence scheme that time-slices the radio between Bluetooth and Wi-Fi. A stale coexistence table shows up as a mouse that stutters the moment a large download starts, and updated firmware and drivers retune that arbitration so both radios stay usable together.
Common warning signs of bluetooth driver failure
- Bluetooth headphones stutter or cut out whenever a large Wi-Fi download runs on the same combo radio
- A paired mouse or keyboard reconnects slowly after wake, or lags noticeably during quick cursor movement
- Headset call audio sounds muffled because the link drops to the Hands-Free Profile whenever the microphone is used
- Devices pair successfully once but never reconnect automatically, so they must be removed and paired again
- The Bluetooth radio vanishes from Device Manager with Code 43 after the laptop resumes from modern standby
- Low Energy accessories such as a stylus or fitness band fail to expose their GATT services and show as unknown
How to fix bluetooth driver problems
Restart the Bluetooth support service
Open the Services console, find Bluetooth Support Service, and restart it. This clears a hung stack state that leaves paired devices unable to reconnect, without disturbing the driver or the controller firmware.
Cycle the radio in Device Manager
Expand Bluetooth, right-click the radio, choose Disable device, wait a moment, then Enable device. This re-issues the HCI reset command to the controller and clears a wedged coexistence state left over from a busy Wi-Fi session.
Remove and re-pair the accessory
In Settings, under Bluetooth and devices, remove the misbehaving device, then put it back into pairing mode and add it again. This rebuilds the bond and long-term key, which fixes devices that pair once but never reconnect.
Reinstall the Bluetooth driver cleanly
Right-click the radio, choose Uninstall device, tick 'Attempt to remove the driver for this device', and reboot. Windows reinstalls a fresh copy, stripping corrupted profile registrations that block A2DP or GATT services.
Error codes linked to this hardware
This device cannot start (Code 10)
A generic error indicating that the device driver failed to load or initialize properly, often due to power state issues or corrupted driver files.
This device is disabled (Code 22)
Windows can see the hardware, but the device is switched off in Device Manager by a user, an application, or a power-management action.
Windows has stopped this device because it has reported problems (Code 43)
The device hardware or driver failed. Most commonly seen on Graphics Cards and USB devices.
Helpful guides
Should You Use Driver Updater Software?
Driver updater tools promise one-click fixes but add risk. Here's what they really do, when they cause problems, and the safe way to check drivers yourself.
DCH vs Legacy Drivers in Windows 10/11
DCH drivers split hardware support from control-panel apps in Windows 10/11. Why the change happened and how to tell which type you have.
How to identify unknown devices with hardware IDs
A practical walkthrough for naming every mystery entry in Device Manager using hardware IDs, driver details, and Windows' built-in tools.
Frequently asked questions
Why do my Bluetooth headphones stutter whenever I start a big download?
Your combo module shares one 2.4GHz antenna between Wi-Fi and Bluetooth, and heavy Wi-Fi traffic starves the audio stream of airtime. The driver's coexistence scheme time-slices the radio, so an updated combo driver retunes that arbitration, and moving the download to 5GHz Wi-Fi removes most of the contention.
Why does my Bluetooth headset sound muffled the moment I join a call?
On a call the link switches from the high-quality A2DP profile to the Hands-Free Profile so the microphone can work, and HFP uses a much lower-quality codec. This is a protocol limitation rather than a fault; a headset and driver that support LE Audio with the LC3 codec avoid the quality drop.
Why do my Bluetooth devices pair once but never reconnect automatically?
Automatic reconnection depends on the stored bond and long-term key surviving on both ends, and a stale or corrupted bond breaks it. Removing the device in Settings and pairing it again rebuilds the key, and restarting the Bluetooth Support Service clears a hung stack that blocks reconnection.