Bluetooth disappears or its driver is rejected after an update: install or roll back the compatible driver

After Windows Update or a Bluetooth-driver update, the Bluetooth adapter can disappear from Settings, appear only as a hidden or unknown device, or remain visible with a Device Manager problem code. The underlying hardware can still be present while Windows selects a driver package that does not start, is incompatible with the adapter's hardware ID, is rejected by signature or compatibility policy, or replaces a previously working OEM package.

This procedure first identifies the physical adapter, current driver, problem code, and update sequence. It then uses one of two reversible repairs: roll back to the previously working driver, or install a package that explicitly supports the computer or adapter hardware ID. It does not require a firmware change, and it does not treat the date of a Windows update as proof that the update caused the problem.

Searchable Windows error codes, messages, and identifiers

Use only a problem code that Device Manager actually shows for the affected adapter or its parent device. Do not convert a missing Settings toggle into Code 10, Code 43, or Code 52 without evidence.

Use this procedure when all of the following are true:

• Bluetooth previously worked on the same Windows 10 or Windows 11 computer;
• the Bluetooth radio disappeared, became a hidden or unknown device, or gained a Device Manager problem code after a Windows or driver update;
• the adapter's hardware ID and computer or adapter model can be identified;
• a previously working driver is available through Roll Back Driver, or an exact compatible package can be downloaded before the active package is changed; and
• a non-Bluetooth keyboard and pointing device are available if the computer otherwise depends on Bluetooth input.

It also applies when a current Intel Bluetooth package produces a signature or compatibility warning and Device Manager still offers the immediately previous driver.

Do not use this procedure when only one paired headset, mouse, controller, or phone fails while the Bluetooth adapter is healthy. That is a pairing, profile, device, or application problem rather than an adapter-driver regression.

It also does not apply when:

• Bluetooth is deliberately disabled by Airplane mode, a physical wireless switch, an enterprise policy, or a documented firmware setting;
• the computer never contained Bluetooth hardware;
• the adapter is an external USB device that is physically disconnected or fails on a second known-good computer;
• the entire USB controller or multiple unrelated USB devices have disappeared;
• Device Manager shows a specific hardware-resource, power, or parent-bus problem that remains after a known-good driver test;
• Windows Security identifies a malicious or tampered package; or
• the OEM lists the adapter as unsupported on the installed Windows version.

Stop driver work if the device is absent after a full shutdown, power removal where supported, a documented hardware scan, and a known-good exact driver. Do not reset firmware or flash BIOS merely because Bluetooth is absent.

The exact Windows build, the update's internal reason for selecting a package, the date the radio was manufactured, and whether Windows Update or a vendor utility initiated the change may remain unknown unless compatibility depends on them.

The following may not remain unknown before a driver write:

• the computer model or add-in adapter model;
• the affected device instance and its hardware IDs;
• the current driver provider, version, date, and INF name when available;
• the exact Device Manager problem code, or confirmation that no device currently enumerates;
• the source and stated supported models or hardware IDs of the proposed package;
• whether Roll Back Driver is available; and
• whether a working non-Bluetooth input and a local copy of the replacement package are available.

Do not substitute a similar marketing name for an exact model or hardware ID.

• Administrator access
• A wired or otherwise independent Internet connection, or the exact driver package downloaded locally before changes
• A non-Bluetooth keyboard and mouse or touchpad
• The computer's exact OEM support page, or the adapter vendor's package that explicitly supports the detected hardware ID
• A folder for before-state evidence and exported driver packages
• Enough free space for the package and driver export
• Important data backed up
• Stable power; connect a laptop's AC adapter

Before changing the active driver, create an evidence folder and inventory the current third-party driver store from an elevated Command Prompt:

md "%USERPROFILE%\Desktop\Bluetooth-before"
pnputil /enum-drivers > "%USERPROFILE%\Desktop\Bluetooth-before\third-party-drivers.txt"
pnputil /enum-devices /class Bluetooth /drivers > "%USERPROFILE%\Desktop\Bluetooth-before\bluetooth-devices.txt"

If the second command is not supported by the installed Windows 10 build or returns no class match, use Device Manager and photograph the General, Driver, and Details > Hardware Ids tabs. Do not assume an empty command result proves that no hardware exists.

After identifying the exact current published INF (oem#.inf) for the verified Bluetooth device, export that package before replacing or deleting it:

md "%USERPROFILE%\Desktop\Bluetooth-before\exported-current-driver"
pnputil /export-driver oem##.inf "%USERPROFILE%\Desktop\Bluetooth-before\exported-current-driver"

Replace oem##.inf only with the published name recorded from Device Manager/PnPUtil. Verify that PnPUtil reports a successful export and that the destination contains the INF, catalog, and associated driver files. If the package cannot be exported, document that rollback limitation and do not authorize Driver Store deletion under this article.

1. Save work and connect AC power.
2. Connect a wired keyboard and mouse or confirm that the built-in keyboard and touchpad work.
3. Disconnect nonessential USB Bluetooth dongles so the internal adapter cannot be confused with another radio. Keep any dongle that is the actual target connected.
4. Turn Airplane mode off. Do not repeatedly toggle it as a substitute for diagnosis.
5. Open Settings > Windows Update > Update history and record the driver and quality updates installed immediately before the symptom.
6. Run winver and record the displayed Windows version and build. The build is evidence, not a reason to reject an otherwise exact OEM package unless the package specifies a build requirement.
7. Open Device Manager with devmgmt.msc, select View > Show hidden devices, and leave the device layout unchanged until section 7 is complete.
8. Do not reset BIOS/UEFI, disable Secure Boot, disable driver-signature enforcement, remove all USB controllers, or delete every Bluetooth package from the driver store.

1. Record the exact symptom:

   • no Bluetooth toggle in Settings;
   • no Bluetooth category in Device Manager;
   • a grey hidden adapter;
   • an Unknown USB Device or unknown network device;
   • a yellow warning icon; or
   • a signature or compatibility warning.

2. In Device Manager, inspect Bluetooth, Network adapters, Universal Serial Bus controllers, and Other devices. Do not identify the device from its friendly name alone.

3. For the suspected adapter, open Properties > General and record the complete Device status text and numeric code. Then record:

   • Driver > Driver Provider;
   • Driver Date;
   • Driver Version;
   • Driver Details filenames;
   • whether Roll Back Driver is enabled; and
   • Details > Hardware Ids and Device instance path.

4. If the Bluetooth adapter is hidden, inspect its parent USB device from Details > Parent or View > Devices by connection. A missing or failed parent USB device means the Bluetooth child driver may not be the first fault.

5. Compare the driver date and update history with the first failure. A matching time sequence supports a regression; it does not prove one.

6. Open Reliability Monitor with perfmon /rel. Record any driver installation, Windows update, hardware error, or application failure at the same time. Do not treat an unrelated event on the same day as causal.

7. Determine whether a rollback target exists. Roll Back Driver must be enabled and Device Manager must show that the adapter is the correct hardware instance. If the button is grey, do not use a third-party utility to manufacture a rollback.

8. If rollback is unavailable, obtain the exact replacement package before removing anything:

   • prefer the computer OEM package for an internal laptop or motherboard radio;
   • use the adapter vendor only when the OEM package is unavailable or the OEM explicitly directs it;
   • match the exact model, Windows architecture, and hardware ID where the package supplies an INF list; and
   • reject a package selected only because it says “Intel Bluetooth,” “Realtek Bluetooth,” or a similar family name.

9. Inspect the downloaded file's Properties > Digital Signatures when present. After extraction, the driver catalog and binaries must be signed normally by the package vendor or Microsoft. Stop on an invalid signature, download corruption, or model mismatch.

10. Use the evidence threshold:

    • Strong driver-regression evidence: Bluetooth worked before a recorded driver change, the same hardware instance now has Code 10/28/31/39/48/52, and rollback or an exact package exists.
    • Moderate evidence: the radio disappeared after the change but remains as a hidden device or failed parent USB child with the same instance identity.
    • Insufficient evidence: no device identity, no package match, or persistent Code 43 across multiple known-good packages. Stop rather than cycling drivers.

Choose one branch. Start with rollback when Windows retains the previously working driver. Use package installation when rollback is unavailable or Windows explicitly blocks the current package.

Branch A — Roll back to the previous driver

1. In Device Manager, right-click the verified Bluetooth adapter and select Properties.
2. Reconfirm the hardware ID, provider, version, date, and current problem code.
3. Open the Driver tab and select Roll Back Driver.
4. Choose the reason that accurately describes the regression. Do not enter a fabricated explanation.
5. Complete the rollback and select Restart now if Windows requests it. Otherwise restart from Start > Power > Restart.
6. After restart, reopen the same device and record its new provider, version, date, and status.
7. If Windows immediately reinstalls the rejected version, leave that optional driver update unchecked while the corrected package is obtained. If the driver arrives automatically rather than as an optional item, use only a supported organizational driver-update/device-install policy or the OEM's documented control. Windows Update's general pause control is not a per-driver pause and also delays quality/security updates.

If Roll Back Driver is grey, cancel and use Branch B. Do not manually copy old .sys files into System32\drivers.

Branch B — Install an exact OEM or adapter-vendor package

1. Close Device Manager and all Bluetooth applications.

2. Extract the package to a new local folder. Do not run it directly from an email attachment, network share, or temporary archive view.

3. Follow the exact vendor package method:

   • For a signed executable installer, right-click it, confirm the publisher, select Run as administrator, and choose the Bluetooth component only when the installer offers components.

   • If the exact OEM package supplies a documented install.bat, open an elevated Command Prompt in that extracted folder and run:

     install.bat
     

     Run that command only from the verified package and folder. An arbitrary batch file with the same name is not safe.

   • If the package consists of INF files and the vendor supports manual installation, use:

     pnputil /add-driver "C:\Drivers\Exact-Bluetooth-Package\*.inf" /subdirs /install
     

     Replace the path with the actual extracted folder. Review the PnPUtil result and record which package was added or installed.

4. Restart Windows even if the installer does not demand it; the source-confirmed rollback and package-install outcomes both required the driver stack to be reloaded.

5. Reopen Device Manager and confirm that the same hardware instance now uses the intended provider and version and has no problem code.

Branch C — Refresh the device instance without deleting the known-good package

Use this branch only when the exact compatible package is already local, Branch B completed without binding it, and Device Manager still shows the same device instance.

1. In Device Manager, right-click the verified Bluetooth adapter and select Uninstall device.
2. Do not select Attempt to remove the driver for this device or Delete the driver software for this device on the first pass.
3. Confirm the uninstall, then select Action > Scan for hardware changes.
4. If Windows rebinds the same bad package, do not repeat pnputil /add-driver ... /install and expect ranking to change; PnPUtil will not force a lower-ranked package onto the device. Stop and identify the exact current published INF and the exact intended replacement. A controlled Driver Store removal is permitted only when the current INF was successfully exported, the replacement package is local and verified for the hardware ID, and all devices using that INF have a viable fallback. Otherwise use the OEM installer or Device Manager's supported Update driver > Browse my computer > Let me pick path to select only a compatible installed model, and stop if Windows rejects it.
5. If the device disappears completely, stop. Do not uninstall parent USB controllers or bulk-delete driver-store packages. Perform a normal shutdown, wait 20 seconds, power on, and check once. Persistent absence requires hardware/platform diagnosis.

Removing a specific oem#.inf from the driver store is an advanced escalation, not a routine step. It requires an exported copy, exact provider/original-name verification, and a locally available replacement. This article does not authorize guessing the published INF number.

• The adapter returns with no Device Manager code and Bluetooth works: continue to section 12.
• Rollback works but Windows Update reinstalls the bad version: preserve the working version, obtain the corrected OEM package, and use the supported temporary driver-update control. Do not disable security or all quality updates.
• The new package installs but Code 52 remains: the package is still not accepted. Stop and obtain a properly signed package; do not disable signature enforcement.
• Code 48 remains: Windows still blocks the package as incompatible. Replace it with a corrected vendor release.
• Code 10, 31, or 39 changes after the compatible package: record the new code and driver files. The changed result narrows the problem but is not yet success.
• Code 43 persists with an exact known-good driver: stop driver cycling and evaluate the radio, its USB parent, board power state, and OEM diagnostics.
• The adapter remains absent after a normal shutdown and one hardware rescan: stop. The case is no longer demonstrated as only a Bluetooth driver regression.
• Bluetooth is healthy but one accessory still fails: leave this article and diagnose that device's pairing, profile, firmware, battery, or application.

• Do not disable Secure Boot or driver-signature enforcement to force a rejected Bluetooth driver.
• Do not download “universal driver updater” packages or install by vendor family name alone.
• Do not manually copy or rename .sys, .inf, or .cat files in Windows system folders.
• Do not uninstall every USB controller, network adapter, or Bluetooth package.
• Do not use pnputil /delete-driver ... /force without proving the exact published INF and preserving a working replacement.
• Do not reset firmware defaults or flash BIOS unless an exact OEM advisory independently identifies a platform defect for this model.
• Do not treat KB5011048, or any update installed near the event, as proof of cause without the device and driver evidence.
• Do not repeatedly power-cycle a device that is intermittently enumerating; preserve evidence and investigate the parent bus or hardware.

If the replacement driver creates a new problem:

1. Open Device Manager, verify the same Bluetooth hardware instance, and use Driver > Roll Back Driver when enabled.

2. If rollback is unavailable, rerun the previously downloaded exact working OEM package.

3. If the current third-party package was successfully exported in section 5 before replacement, restore only that exact package:

   pnputil /add-driver "C:\Path\To\ExportedDriver\*.inf" /subdirs /install
   

4. Restart and recheck the driver provider, version, and status.

5. If a newly installed vendor application, not the base driver, caused the regression, uninstall that application from Settings > Apps while retaining the working base driver when the installer allows it.

A System Restore point may reverse some driver and registry changes, but it is not a substitute for the exported package and before-state record. Do not use System Restore as the first rollback when Device Manager can restore the exact driver.

1. In Device Manager, verify that the Bluetooth adapter is present, not hidden, and reports This device is working properly.
2. Record the final hardware ID, driver provider, version, date, and INF package.
3. Confirm that Settings > Bluetooth & devices shows the Bluetooth control and that it can be turned on and off once.
4. Pair or reconnect one known-good Bluetooth device. Test the relevant profile: keyboard input, mouse movement, audio output, or file/device connection.
5. Restart Windows and repeat the Device Manager and device test.
6. Perform a normal shutdown, wait 20 seconds, power on, and test again. This catches a radio that works only until the next cold start.
7. Review Reliability Monitor for a new hardware or driver failure after the repair.
8. Verify that Windows Update has not silently replaced the working package during the test period.

Success requires the same physical adapter to enumerate without a problem code and remain usable across restart and cold start. A returned Settings toggle without a working adapter is not enough.

Confidence is 80% that rollback or installation of an exact compatible package will resolve this symptom when the adapter identity is proven, the failure begins with a driver change, and Device Manager shows a driver-load, compatibility, or signature problem. Two independent source cases explicitly confirmed success: one after running an OEM Bluetooth package's install.bat, and one after rolling back an Intel Bluetooth driver.

The confidence is bounded because the cases were not independently reproduced, one source associated an update package without demonstrating its internal causal path, and a missing Bluetooth radio can also result from parent-USB, firmware, power, or hardware failure.

Stop and escalate when the hardware ID cannot be identified, the proposed package does not explicitly support it, the signature is invalid, the parent bus fails, Code 43 persists across a known-good package, the adapter remains absent after a cold start, or changing the driver affects other critical input or network devices.