📎 AI Summary:
The thread concerns an HP EliteBook running Windows 11 25H2 where Bluetooth repeatedly disconnects, disappears from Settings, and reports an inaccurate number of connected devices despite driver reinstallation. The response suggests the count reflects repeated profile enumeration and recommends a power reset, checking Device Manager, updating HP BIOS/firmware and wireless drivers, clean reinstalling Wi‑Fi/Bluetooth drivers, disabling power saving, repairing Windows components, and consulting IT before testing the related update; overall, the issue is treated as likely a wireless-module, firmware, power-state, or device-enumeration problem rather than faulty accessories.

jessekos

Member
Joined
Aug 25, 2026
Messages
1
Thread Author #1
Good morning,

Since a few days ago, my Bluetooth has started behaving unexpectedly. Connected devices continuously connect and disconnect, and sometimes Bluetooth disappears completely from both Quick Settings and the Windows Settings menu.

Another symptom is that the Bluetooth tile constantly shows a different number of connected devices. The number fluctuates from 2 to 9 and everything in between, even though there are only 2 devices actually connected.

We have already reinstalled the Bluetooth drivers, but unfortunately this did not resolve the issue.

I am using an HP EliteBook with an Intel® Core™ Ultra 5 135U processor and am currently running Windows 11 25H2 (Build 26200.9106).

Has anyone experienced similar issues or knows how to resolve this? Any assistance would be greatly appreciated. This makes my work basically impossible.

Thank you in advance.
 

WindowsForum AI

AI
Staff member
Robot
Joined
Mar 14, 2023
Messages
113,819
Good morning, Jesse.
The fluctuating device count likely represents Bluetooth profiles/endpoints being repeatedly enumerated rather than nine physical devices. Because Bluetooth also disappears from Settings, this points more toward a wireless-module power/firmware failure or Windows device-enumeration problem than an issue with the paired accessories.
Build 26200.9106 is the August 11, 2026 hotpatch KB5120994. Microsoft currently lists no known Bluetooth issue for that update. The regular 25H2 channel is on build 26200.9168, although managed hotpatch devices can legitimately remain on .9106. (support.microsoft.com)

Recommended troubleshooting order​

1. Perform a complete power reset​

A normal restart may not reset the Bluetooth side of the Intel wireless module.
  1. Save your work.
  2. Disconnect USB devices, the dock, and power adapter.
  3. Open Terminal as administrator and run:
shutdown /s /f /t 0
  1. After shutdown, hold the laptop’s power button for approximately 20 seconds.
  2. Reconnect power and start it normally.

2. Check what happens in Device Manager​

  1. Open Device Manager.
  2. Select View > Show hidden devices.
  3. Expand Bluetooth, Network adapters, Other devices, and Universal Serial Bus controllers.
  4. Check the Intel Bluetooth adapter for a warning icon.
  5. Open its Properties and note any error such as Code 10, Code 43, or Code 45.
  6. If Bluetooth disappears again, check whether the Intel Wi-Fi adapter remains present.
If both Wi-Fi and Bluetooth disappear, that strongly suggests a shared wireless-module, firmware, or power-state issue.

3. Update the complete HP firmware stack​

The processor model is not sufficient to identify the exact EliteBook. Use the laptop’s product number/serial lookup in HP Support Assistant or HP Image Assistant, then install:
  1. The latest HP BIOS/UEFI
  2. Intel chipset drivers
  3. Intel Management Engine firmware/driver
  4. HP-provided WLAN driver
  5. HP-provided Bluetooth driver
  6. Any HP firmware update relating to USB-C, Thunderbolt, or the wireless module
Connect AC power and do not interrupt a BIOS update. On a work-managed laptop, involve your IT department first.

4. Clean-install both wireless drivers​

Reinstalling only Bluetooth might leave the shared Wi-Fi/Bluetooth module in a broken state.
  1. Download the correct HP WLAN and Bluetooth packages first.
  2. Create a restore point.
  3. Disconnect from the Internet.
  4. In Device Manager, uninstall the Intel Wireless Bluetooth adapter.
  5. Select Attempt to remove the driver for this device if offered.
  6. Uninstall the Intel Wi-Fi adapter under Network adapters, again removing the driver if offered.
  7. Shut down rather than restart.
  8. Perform the power reset from Step 1.
  9. Install the HP WLAN package first and the Bluetooth package second.
  10. Restart and pair only one device initially.
Undo: Reinstall the downloaded HP driver packages. Keep an Ethernet or USB-network option available because removing the WLAN driver temporarily removes Wi-Fi.

5. Disable wireless power saving temporarily​

  1. Open the Bluetooth adapter’s Properties > Power Management.
  2. Clear Allow the computer to turn off this device to save power.
  3. Do the same for the Intel Wi-Fi adapter if that option exists.
  4. Test after sleep and after normal usage.
Undo: Re-enable the same checkboxes.

6. Repair Windows components​

Open Terminal as administrator and run:
Code:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Restart after both commands finish.

7. Test whether the August update triggered it​

Because .9106 corresponds to KB5120994, check whether that update was installed immediately before the symptoms started.
  1. Open Settings > Windows Update > Update history.
  2. First install any newer update offered by your organization.
  3. If none is available and the dates match exactly, ask IT to test uninstalling KB5120994 or moving the machine temporarily off the hotpatch policy.
Do not remove a security update on a managed work computer without IT approval. Reinstalling the update reverses the rollback.
4b0b84ffa825.webp

If it continues, please post the exact EliteBook model/product number, Intel Bluetooth and Wi-Fi driver versions, and any Device Manager error code visible while the problem is occurring. Also confirm whether Wi-Fi disappears at the same time. Those details will distinguish an update/driver problem from a failing wireless module or motherboard connection.