If Bluetooth stopped working, disappeared, or won't connect after installing KB5101650 (the July 2026 Patch Tuesday update, Build 26200.8875 for 25H2 or 26100.8875 for 24H2), the fastest fixes are: run the built-in Bluetooth troubleshooter, restart the Bluetooth Support Service, and reinstall your Bluetooth driver from Device Manager. Most reports resolve with a driver reinstall. A small number of Dell PCs are affected by a separate, officially confirmed issue involving shutdowns and overheating, not Bluetooth directly, and Microsoft has already paused the update on those machines. Full steps below.
Issue Overview
Microsoft released KB5101650 on July 14, 2026, updating Windows 11 25H2 devices to Build 26200.8875 and Windows 11 24H2 devices to Build 26100.8875. It's a large update. Microsoft's own release notes cite more than 570 security fixes, and it was marketed with a notable line: this is meant to be the biggest Bluetooth reliability fix Windows 11 has had in years, improving pairing stability and audio device handling.
Which makes the timing awkward. Within days of rollout, Bluetooth complaints started showing up on Microsoft's own Q&A forums and community sites like Techdows: vanished Bluetooth adapters, devices that pair but produce no audio, and radios that show a yellow warning icon in Device Manager. An update sold as the fix has, for a subset of users, become the thing they're troubleshooting.
Separately, and this is worth being precise about, Microsoft has confirmed a real, acknowledged problem with KB5101650, but it isn't Bluetooth. It's a compatibility issue on certain Dell PCs that causes unexpected shutdowns, overheating, and battery drain, and Microsoft has already blocked the update from installing on affected Dell hardware while a fix is prepared. The two issues are getting conflated online, so this guide treats them separately, based on what's actually confirmed.
Why It Happens
Two different mechanisms are in play here, and they shouldn't be mixed up.
The confirmed Dell issue traces back to a June 23, 2026, preview update, KB5095093, which introduced a new Windows USB-C Connection Manager interface. That interface conflicts with the Intel Innovation Platform Framework (IPF) Processor Participant driver used on certain Dell systems. Because KB5101650 folds in all of June's non-security changes, PCs that never installed the June preview can still hit this conflict the first time they install the mandatory July update. Microsoft has stated this can cause unexpected shutdowns, poor performance, increased heat, and battery drain, and has paused the update on the affected Dell models until a fix ships.
The Bluetooth complaints are a different story and, importantly, not yet an officially acknowledged "known issue" tied specifically to KB5101650. What we do know: this is a recurring pattern with Windows 11 servicing in 2026, not a one-off. Earlier updates this year KB5074109 in January, KB5085516 in March, and KB5095093 in Jun each generated similar user reports of Bluetooth adapters vanishing from Device Manager or failing to reconnect after installation. The common thread across these threads is usually a driver-to-OS mismatch: Windows updates the Bluetooth stack or a related USB/power-management component, and the vendor driver (commonly Intel or Realtek chipsets) hasn't been revalidated against the new build yet. The radio hardware is fine; the software handshake between Windows and the driver is what breaks.
If you see a Blue Screen referencing stop code 0x9F (DRIVER_POWER_STATE_FAILURE) around the same time, that's a power-state handling failure in a driver, consistent with the broader pattern of USB/power-management changes in this update cycle causing friction with older or unrevalidated drivers, Bluetooth included.
Step-by-Step Fixes
Work through these in order. Most people resolve the issue in the first three steps.
1. Rule out the simple stuff first
- Check that Airplane Mode is off (Settings > Network & Internet).
- Confirm the Bluetooth toggle is actually on (Settings > Bluetooth & devices).
- If your laptop has a physical Wi-Fi/Bluetooth kill switch or Fn-key combo, make sure it isn't disabled.
- Restart the PC. This sounds obvious, but a large share of post-update Bluetooth glitches clear after one full restart, since it forces Windows to re-initialize the radio and reload the driver stack.
2. Run the built-in Bluetooth troubleshooter
Go to Settings > System > Troubleshoot > Other troubleshooters, and run Bluetooth. It automatically checks for a missing or disabled radio, restarts the relevant services, and reinitializes the adapter. Microsoft's own troubleshooting documentation lists this as the first recommended step before touching drivers manually.
3. Restart the Bluetooth Support Service
- Press Win + R, type
services.msc, and hit Enter. - Find "Bluetooth Support Service," right-click it, and select Restart.
- Confirm its Startup type is set to Automatic, not Manual.
- Do the same check for "Bluetooth Audio Gateway Service" if it's present.
4. Repair the device from scratch
Remove the affected device from Settings > Bluetooth & devices, restart the PC, then pair it again as new. Stale pairing data left over from before the update is a common cause of "connects but no audio" or "pairs then immediately disconnects" symptoms.
5. Check Device Manager for a yellow warning
Open Device Manager, expand Bluetooth, and look for a yellow exclamation mark next to your adapter. Right-click it and check Properties > Device status for an error code (10, 43, and 45 are common after driver mismatches). If the adapter has vanished from the Bluetooth section entirely, check under "Other devices" or "Universal Serial Bus controllers" for an unrecognized device that's often the Bluetooth radio showing up unbound from any driver.
Driver Fix (Intel / Realtek)
Most laptop and desktop Bluetooth radios run on either an Intel or a Realtek chipset, and this is where the majority of post-update fixes actually land.
For Intel-based Bluetooth adapters:
- In Device Manager, right-click the Bluetooth adapter and select Uninstall device. Tick "Attempt to remove the driver for this device" if offered.
- Restart the PC. Windows will usually reinstall a generic driver automatically.
- If Bluetooth still isn't right, go to Intel's Driver & Support Assistant (downloadable from Intel's support site) and let it detect and install the correct, current Bluetooth driver for your exact chipset rather than relying on Windows Update's generic version.
For Realtek-based Bluetooth adapters:
- Follow the same uninstall-and-restart process in Device Manager first.
- If that doesn't resolve it, go directly to your PC manufacturer's support page (Dell, HP, Lenovo, ASUS, etc.) rather than Realtek's generic site. Laptop vendors customize Realtek Bluetooth drivers for their specific hardware, and a generic Realtek driver can behave worse than the OEM-tuned one.
- Install the manufacturer-specific version, restart, and re-pair your devices.
In both cases, avoid installing a driver that's older than what you had before the update unless you're specifically rolling back as a temporary workaround. Mismatched driver-to-OS-build combinations are exactly what cause this class of problem in the first place.
Registry Fix (If Needed)
This step is a last resort for advanced users, not a first move. A small subset of persistent cases,s particularly where the Bluetooth service itself refuses to start even after a clean driver reinstall, ll has been traced to corrupted service entries in the registry.
Back up your registry before touching it (type regedit, then File > Export). Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT
Confirm the Start value is set to 2 (Automatic) rather than 3 (Manual) or 4 (Disabled). If it's been reset to something else by the update, correcting it and restarting can bring the service back online. If you're not comfortable editing the registry directly, skip this step and use System Restore instead;ead it accomplishes something similar without the manual risk.
Temporary Workarounds
- USB Bluetooth dongle: If you need Bluetooth working immediately and troubleshooting is taking too long, a $10–15 USB Bluetooth adapter bypasses the affected internal radio entirely and works independently of the built-in driver conflict.
- Wired fallback: For headsets and mice specifically, switching temporarily to a wired connection or a USB dongle receiver (like a Logitech Unifying receiver) sidesteps the issue while you wait for a driver update.
- Pause further updates: Settings > Windows Update > Pause updates can buy you time to stabilize your current state before another cumulative update lands on top of an already-broken driver stack.
Rollback and Restore Options
If none of the above resolves it, Windows gives you two ways to undo the update itself.
Point-in-Time Restore (new in this update)
KB5101650 introduces Point-in-Time Restore, a full-system snapshot recovery tool that goes further than a traditional System Restore point;oint it captures apps, settings, and personal files, not just system and registry state. If a restore point exists from before you installed the update, this is now the most complete way to roll your whole system back to that state. Access it through Settings > System > Recovery.
Uninstall the update directly.
- Go to Settings > Windows Update > Update history > Uninstall updates.
- Find KB5101650 in the list and select Uninstall.
- Restart when prompted.
Note!
This option disappears after roughly 10 days, since Windows cleans up the old files automatically. If it's already gone from that list, Point-in-Time Restore or a full System Restore point (if one exists) is your remaining option.
Treat rollback as a last resort, not a first move; you'll also lose July's 570 security fixes until Microsoft ships a corrected version, and for most people, the driver-level fixes above resolve Bluetooth without needing to give up the security patch.
Microsoft's Official Status: Confirmed vs Unconfirmed
Officially confirmed by Microsoft: A compatibility issue on select Dell PCs with Intel IPF Processor Participant drivers, causing unexpected shutdowns, poor performance, overheating, and battery drain. Microsoft has blocked KB5101650 from installing automatically on affected Dell systems via Windows Update and is working with Dell on a fix. This is documented on Microsoft's Windows release health dashboard.
Not officially confirmed as a known issue: The broader wave of Bluetooth, audio, camera, mic, Start menu, and boot complaints being reported on Microsoft Q&A and community forums following KB5101650. These are real, widely reported user experiences, but as of this writing t, they haven't been added to Microsoft's known-issues list for this specific update. Given the recurring pattern across January, March, and June 2026 updates, it's a reasonable bet that at least some of these will get an official acknowledgment eventually, but treat it as unconfirmed until Microsoft's release health page says otherwise.
If you're affected and want to help get it formally recognized, reporting it through Feedback Hub (Windows key > search "Feedback Hub") adds to the count Microsoft tracks internally when deciding what qualifies as a known issue.
FAQ
Why did Bluetooth stop working after the Windows update?
In most reported cases, it's a mismatch between the updated Windows Bluetooth stack and a vendor driver (commonly Intel or Realtek) that hasn't been revalidated against the new build yet. The hardware itself is rarely the problem.
Does the July 2026 update fix or cause Bluetooth problems?
Both, in a sense. Microsoft built KB5101650 around meaningful Bluetooth stability improvements after a multi-release effort in 2026. But the update has also triggered a new wave of Bluetooth complaints for some users, the same pattern seen with several earlier 2026 updates.
How do I reinstall Bluetooth drivers?
In Device Manager, right-click your Bluetooth adapter, select Uninstall device, restart, and let Windows reinstall a generic driver. If issues persist, download the specific driver from Intel's site or your PC manufacturer's support page rather than using the generic version.
Is Microsoft aware of this issue?
Microsoft has confirmed and is actively fixing a shutdown/overheating issue on certain Dell PCs tied to this update. It has not, as of this writing, listed the broader Bluetooth complaints as an officially confirmed known issue for KB5101650.
Can I roll back the update?
Yes, via Settings > Windows Update > Update history > Uninstall updates, within about 10 days of installing it. After that window closes, Point-in-Time Restore or a System Restore point is your remaining option.
Which PCs are officially confirmed to be affected?
Only certain Dell PCs using the Intel Innovation Platform Framework Processor Participant driver, and the confirmed sysymptoms arehutdowns/overheating/battery drai,n not Bluetooth. Microsoft hasn't published a full model list publicly as of this writing.
Final Verdict
If your Bluetooth broke after installing KB5101650, the odds are good it's a driver-revalidation problem, not a hardware fault or a sign your PC is one of the confirmed Dell-affected units. Run the troubleshooter, restart the Bluetooth service, and reinstall the driver from your manufacturer's site. That combination resolves the large majority of reported cases. Save the rollback for genuinely stuck situations, since you'd be giving up 570 security fixes to get there. And if you're on an affected Dell system seeing shutdowns rather than Bluetooth trouble, don't force-install the update manually;lly let Microsoft's block do its job until the real fix ships.
