Windows bugs and fixes October 12 2026: no fix
Chapters
What broke after KB5124010?
KB5124010 can crash Windows 11 applications that decode AC-3 through Windows, according to Finance Biggo on October 8, 2026.
The optional preview has been available since September 22, 2026, contains no security fixes, and targets Windows 11 versions 24H2, 25H2, and 26H2, according to Finance Biggo. Affected applications may fail to launch, close without warning, or work normally until a feature such as music playback invokes AC-3 decoding, according to Finance Biggo.
The Windows 11 bug is concentrated in software that relies on the decoder built into Windows, while applications with their own decoding components are unaffected, according to Finance Biggo. DVD player apps are one example in the report, while Microsoft cited games, media players, and certain line-of-business applications as potentially affected, according to Finance Biggo.
I would connect a new launch failure or unexplained closure to KB5124010 only after checking whether the application handles Dolby Digital audio through Windows. I would treat it as a Windows KB update problem only when the update is installed and the decoder path matches. The symptom alone is not enough.
TL;DR
Windows 11 apps that use Windows' AC-3 decoder can crash after the September 22, 2026 KB5124010 update, gHacks reported on October 6, 2026. No public fix, workaround, Known Issue Rollback, or release date has shipped, according to gHacks.
- KB5124010 can close games, media players, and productivity applications, according to gHacks.
- Windows 11 versions 24H2, 25H2, and 26H2 are affected, according to gHacks.
- Skipping the optional preview avoids the trigger but delays its other changes, according to gHacks.
- Microsoft plans a future Windows update but has given no release date, according to gHacks.
Has a Windows update fix shipped?
No public AC-3 fix has shipped, and Microsoft gave no release date, according to gHacks.
Microsoft said a resolution would arrive in a future Windows update but supplied no workaround or Known Issue Rollback and did not confirm an October Patch Tuesday release, according to gHacks.
Windows 11 Insider Preview Build 26220.9606, dated October 7, 2026, went to the Beta Channel and fixed recent crashes in some apps and games, Notebookcheck reported on October 10, 2026. The build is based on Windows 11, version 25H2, and is delivered through an enablement package, according to Notebookcheck.
The release notes do not identify the affected software, explain the beta crash, connect it to AC-3, or say when the correction will reach a public release, according to Notebookcheck. A beta correction is not a shipped public repair. I would not install an Insider build on a work computer merely because the symptoms look similar.
Which Windows versions and applications are affected?
Windows 11 versions 24H2, 25H2, and 26H2 are affected, Mixed News reported on October 8, 2026.
KB5124010 and later updates are the documented trigger, while server editions are listed as unaffected and Microsoft has named no individual affected title, according to Mixed News. Games, media players, and certain productivity applications can close unexpectedly when they require AC-3 audio decoding, according to Mixed News.
Legacy applications face greater exposure because they commonly rely on Windows built-in audio decoding, whereas many modern applications include their own decoder, according to Mixed News. A program can fail immediately, close without warning, or run until it reaches AC-3 music or another feature that requires the Windows decoder, according to Mixed News.
I would check the installed Windows version, the presence of KB5124010, and the application's audio path before changing anything. An unaffected application on the same computer does not clear the update. Different applications can decode the same audio format differently.
Why isn't the beta crash fix proof?
Microsoft has not connected the beta crash fix to the AC-3 issue, according to Notebookcheck.
The timing and symptoms appear related, but Microsoft has not said the problems are identical or named the cause of the crashes corrected by Build 26220.9606, according to Notebookcheck. Insider features can also change, disappear, or never leave the Windows Insider program, according to Notebookcheck.
The Windows known issues record is more useful than a symptom match because Microsoft marked the AC-3 problem Confirmed and promised a future resolution, according to Mixed News. The record identifies the affected versions, trigger, symptoms, and current fix status without requiring an application vendor to diagnose Windows.
I treat the confirmed servicing record as the boundary of what is known. The beta build shows that Microsoft is correcting crashes. It does not prove that KB5124010 is fixed. For continuity, read Windows bugs and fixes October 11 2026: AC-3 crashes.
What can a person do today?
Uninstalling KB5124010 is the only current way to address the issue, The Register reported on October 5, 2026.
If Windows Update still offers the optional preview, I would not select Download and install on a computer that depends on older games, media players, or productivity software using Dolby Digital. Most systems receive KB5124010 only after that selection, although Windows 11 version 24H2 devices with Get the latest updates as soon as they're available enabled receive it automatically, according to gHacks.
Skipping the optional preview delays its other changes until they arrive in a regular monthly update, which is the cost of avoiding the known trigger, according to gHacks. If KB5124010 is already installed and the symptoms match, I would record the failing application, remove the preview, restart Windows, and test the same AC-3 action again. The practical cost is the interruption required to remove, restart, and retest.
A temporary switch to software with its own AC-3 decoder may avoid the affected Windows component because applications that perform their own decoding are unaffected, according to Finance Biggo. I would not install Build 26220.9606 as a substitute because Microsoft has not linked its beta correction to KB5124010 or given a public release date, according to Notebookcheck.