Microsoft released the Windows 11 KB5124010 update on September 22 as an optional non-security preview for Windows 11 24H2 and 25H2.
The update targets several Bluetooth problems, including a misleading Settings toggle, an audio-streaming crash with error code 0x139, microphone compatibility problems, inaccurate connection status, and reliability issues with Bluetooth Classic, LE Audio, and Shared Audio.
Because KB5124010 is a preview, installing it now is optional. Microsoft says its changes will appear in the next security update, expected on October 13.
Anyone actively dealing with Bluetooth problems has a reason to install early. PCs working normally can wait for the regular security rollout.
What's New in Windows 11 KB5124010: Bluetooth Fixes Explained
Microsoft's KB5124010 support page now documents the Bluetooth changes directly.
The update fixes a Settings mismatch where the Bluetooth radio could be off while the toggle under Settings > Bluetooth & devices still appeared on.
It also improves the accuracy of Windows' connection status when an accessory unexpectedly disconnects.
For audio devices, Microsoft lists several additional changes:
Improved microphone compatibility with some Bluetooth Classic Audio accessories.
A fix for a crash with error code 0x139 during Bluetooth audio streaming.
Improved reliability and performance for LE Audio accessories.
Improved reliability for Shared Audio.
Better stability on the Bluetooth & devices Settings page.
Bluetooth Classic accessories also get a small interface improvement.
During a voice call, changing volume with the accessory's physical controls now brings up Windows' volume flyout, giving visual confirmation that the volume changed.
These changes first appeared in Release Preview builds on September 10. They are now included in Microsoft's public KB5124010 notes rather than being limited to Insider documentation.
What the Bluetooth Fixes Mean in Practice
The changes address several different failure modes rather than one underlying Bluetooth bug.
The incorrect Settings toggle is primarily a state-reporting problem. Windows could show Bluetooth as enabled even after the radio had actually been turned off.
The connection-status fix addresses a similar mismatch when accessories disconnect unexpectedly.
The microphone change is more specific to Bluetooth Classic audio hardware and should matter most to people using headsets for calls, meetings, or voice chat.
The 0x139 fix targets a system crash that could occur while streaming Bluetooth audio.
LE Audio and Shared Audio get broader reliability and performance improvements rather than one named bug fix.
Microsoft doesn't identify specific headset models affected by most of these problems, so there's no official hardware list to check against.
If a particular headset or accessory has been unreliable, the practical test is installing the update and checking whether that exact problem improves.
How to Install KB5124010
KB5124010 applies to all editions of Windows 11 24H2 and 25H2.
The resulting builds are:
Windows 11 25H2: OS Build 26200.9550
Windows 11 24H2: OS Build 26100.9550
To install it through Windows Update:
Open Settings.
Select Windows Update.
Open Advanced options.
Select Optional updates.
Download and install KB5124010 if it appears.
Microsoft also offers standalone packages through the Microsoft Update Catalog.
The Catalog route can require prerequisite checkpoint cumulative updates, so Windows Update is the simpler choice for most users.
One lifecycle detail matters for 24H2 users: Microsoft says KB5124010 is the final non-security preview update for Windows 11 24H2.
Windows 11 24H2 Home and Pro reach end of support on October 13, 2026. Enterprise and Education remain supported longer.
Install Now or Wait for October?
KB5124010 is a non-security preview.
That means it doesn't contain a new monthly security patch that users need to install immediately.
Microsoft says the changes will appear in the next security update. PCWorld identifies that rollout as the October 13 Patch Tuesday update.
Installing now makes the most sense if one of the fixes addresses a problem you're already experiencing, particularly:
Bluetooth audio crashes.
Headset microphone compatibility.
Incorrect Bluetooth connection status.
LE Audio reliability.
Shared Audio problems.
The Bluetooth toggle showing the wrong state.
If none of those issues affects the PC, waiting for the regular October update avoids installing a preview solely for fixes you don't need yet.
KB5124010 Fixes File History, Not Breaks It
One important correction to early coverage: KB5124010 fixes a File History problem.
Microsoft says some PCs could fail to back up or restore files to an external drive or network location and display "Reconnect your drive" even when a compatible backup destination was connected and working.
KB5124010 addresses that issue.
So File History is not a newly introduced reason to avoid this preview.
Anyone already affected by the September File History problem has an additional reason to install KB5124010 rather than wait.
Other Changes in the September Preview
Bluetooth isn't the only area touched.
KB5124010 also adds or changes several Windows features, some through a gradual rollout.
Highlights include:
Emoji 17.0 support, including new Unicode characters.
Improved File Explorer previews for downloaded files.
Better thumbnail previews for cloud files.
Improvements to the Personalization > Background page.
DIB image support for desktop backgrounds.
Better slideshow wallpaper behavior across multiple desktops.
A new Tips widget.
Additional precision-touchpad scrolling controls.
An option to remap the Copilot key to Right Ctrl or the Context Menu key.
A setting that can automatically open apps maximized.
Microsoft notes that gradually rolled-out features might not appear immediately after installing the update.
The normal-rollout fixes, including File History, don't carry that same staged availability language.
Known Issue: Active Directory Trust Relationships
Microsoft does list known issues for KB5124010.
One affects some domain-joined PCs.
After the September 8 security update, KB5124008, or later updates, certain devices using Credential Guard-protected machine accounts can lose their secure channel with an on-premises Active Directory domain.
Affected users can receive an error saying the trust relationship between the workstation and domain failed, even with valid credentials.
Microsoft says the problem is tied to Machine Identity Isolation being enabled in environments that don't meet its Windows Server 2025 domain-functional-level requirements.
This isn't a general consumer-PC issue.
It primarily matters to managed enterprise environments where that feature was already configured.
Microsoft provides Intune, Group Policy, and registry-based workarounds in the KB article and says a future Windows update will temporarily prevent the problematic enforcement while the feature is improved.
Enterprise admins should follow Microsoft's current instructions rather than relying on third-party registry steps.
Known Issue: Some USB Audio Devices Still Have Problems
Microsoft also lists a separate problem with USB Audio Class 1.0 hardware.
Some affected devices can:
Fail to start with Device Manager error Code 10.
Produce no audio.
Show unresponsive volume controls.
Make Windows sound settings unavailable or unresponsive.
This problem originated with the September 8 Windows security update rather than with KB5124010 itself.
Microsoft's release-health documentation says the issue is limited to USB Audio Class 1.0 devices and remains only partially resolved.
That distinction matters because the Bluetooth improvements in KB5124010 shouldn't be confused with the separate USB-audio problem.
If a wired USB headset stopped working after the September security update, installing KB5124010 specifically for its Bluetooth fixes isn't evidence that the USB problem will disappear.
What to Check Before Installing
For most home users, the decision is straightforward.
Install KB5124010 early if:
Bluetooth reliability problems are actively disrupting use.
File History stopped working after the September update.
One of the other preview features is useful enough to justify installing early.
Waiting is reasonable if:
Bluetooth already works normally.
File History isn't affected.
The PC is business-critical and preview updates are normally avoided.
Domain-joined business PCs deserve more caution because Microsoft explicitly lists the Active Directory trust issue.
Users relying on older USB Audio Class 1.0 hardware should also check Microsoft's Windows 11 release-health page for the latest status before updating.
What to Do Next
If Bluetooth disconnects, microphone problems, or the 0x139 streaming crash are getting in the way, KB5124010 is the first public Windows 11 update that bundles Microsoft's latest fixes for those issues.
Install it from Settings > Windows Update > Advanced options > Optional updates.
If everything is already working, there's less urgency. The same changes are expected to move into the regular October 13 security update.
For business PCs, check the Active Directory known issue first.
And if the problem involves a wired USB headset rather than Bluetooth, treat it separately. Microsoft still lists an unresolved USB Audio Class 1.0 issue originating with the September 8 security update.
Comments
Be the first, drop a comment!