Windows 11 AC-3 Audio Fix: Stop Apps Crashing After KB5124010
Microsoft confirmed that KB5124010 can crash Windows 11 apps using AC-3 audio decoding. Learn how to identify the problem and use supported recovery options.
On this page
Microsoft confirmed on October 3 that Windows 11 systems affected by the September KB5124010 update can crash some applications that depend on AC-3, the Dolby Digital audio format, for decoding. The issue affects Windows 11 24H2, 25H2, and 26H2, and Microsoft says a permanent resolution is still being developed. If an older game, media player, or business application suddenly closes when audio starts, this guide shows how to check whether KB5124010 is involved and what you can do while waiting for Microsoft's fix.
Why KB5124010 can make an application crash
KB5124010 is the September 22, 2026 non-security preview update for Windows 11 24H2, 25H2, and 26H2. Microsoft added the AC-3 problem to the update's known-issues section on October 3, describing applications that use Windows' AC-3 decoding as the affected group. Depending on the software, the failure can happen when the application launches, when it begins playing audio, or when a particular audio feature is activated. Microsoft says the issue primarily affects older applications that rely on Windows' built-in decoding rather than applications that provide their own decoder.
AC-3, commonly called Dolby Digital, is an audio compression format used by older games, media files, and other software. There is an important complication here: Microsoft stopped including the AC-3 codec with clean installations beginning with Windows 11 24H2, although upgraded systems can retain an existing codec and device manufacturers can provide one. That means two PCs running the same Windows version can have different AC-3 behavior depending on how Windows was installed and which software or manufacturer components supplied the decoder.
Independent reports provide examples of that difference. A Winstep developer reported crashes involving the Windows audio decoder in its software and said similar reports appeared with older games, while another technical report documented a business softphone crashing when it attempted to play its ringtone. These reports do not establish that every application using AC-3 is affected, but they fit Microsoft's description of a problem that depends on how individual applications use the decoder.
Check whether KB5124010 is installed
Before changing codecs, reinstalling an application, or blaming an audio driver, check the Windows update history. Microsoft identifies September 22's KB5124010 and later updates as the affected update path, so the presence of a later cumulative update matters too. This is a useful first check because the same application can work normally on one PC and fail on another even when the application version is identical.
Open Settings and select Windows Update.
Open Update history and inspect the installed quality and preview updates.
Look for KB5124010, the September 2026 cumulative update preview.
Also check whether a newer cumulative update was installed after September 22.
Open Settings > System > About or run
winverto record your Windows version and build.
Microsoft lists the September preview builds as 26100.9550 for 24H2, 26200.9550 for 25H2, and 26300.9550 for 26H2. Those numbers are useful when comparing a failing PC with a working machine, but a higher build number does not prove the problem has been fixed because Microsoft says the issue applies to KB5124010 and later updates until a resolution is released.
Confirm that the crash is actually related to AC-3
The timing of a crash is a useful clue, but it is not proof. An application that began crashing after an update may have a separate compatibility problem, so test the behavior around the audio function that triggers the failure. If the program starts normally but closes when it plays a particular sound, video, game effect, or other AC-3 content, the Microsoft-documented issue becomes a stronger possibility. Microsoft specifically says affected applications can either fail to launch or close without warning when certain audio features are used.
Older software is worth checking first because Microsoft says the problem primarily affects applications that rely on Windows' built-in decoder. Modern applications that include their own decoding components can avoid the affected Windows path. Reports from software developers and users also show that the same decoder-related failure can appear in games, media software, and communications applications, so the problem is not limited to one product category.
Use the safest immediate workaround for a broken app
Microsoft has not published a dedicated workaround for the AC-3 problem and says it is working on a resolution for a future Windows update. If the affected application is essential and you have confirmed that the problem started with the update, rolling back the problematic quality update is one available recovery route. This is a temporary compatibility measure rather than a permanent fix, and removing an update can remove other changes delivered with it.
Because KB5124010 is a non-security preview update, the decision is different from removing a monthly security update. Even so, Windows Update can contain multiple fixes and changes in the same package, so do not remove an update merely because an unrelated application is crashing. First reproduce the problem, record the current build, and make sure you have a recovery path before changing the operating system. Microsoft's own support documentation says update removal should be used when a recently installed update is causing errors or other problems and warns that some updates cannot be removed.
How to uninstall KB5124010 from Windows 11
If you have confirmed that the update is associated with the crash and the application cannot be used until Microsoft releases a fix, Windows provides an uninstall path through Settings. Open Settings > Windows Update > Update history, select Uninstall updates, find the relevant update, and choose Uninstall. Microsoft documents this procedure for Windows 11 and notes that not every update is removable.
Open Settings.
Select Windows Update.
Choose Update history.
Select Uninstall updates.
Locate KB5124010 if it is still listed as removable.
Select it and choose Uninstall.
Restart Windows and test the application again.
Do not assume that removing the September preview will always solve the problem on a machine that has already received a later cumulative update. Microsoft's issue description explicitly says the affected state can continue with later updates until the resolution is delivered. If KB5124010 is no longer removable because a newer package superseded it, use the Windows Recovery Environment's latest quality-update removal option rather than deleting Windows system files or replacing decoder DLLs manually.
What to do if Windows will not let you remove the update
If Windows is unstable enough that Settings cannot be used normally, Microsoft provides an update-removal option through Windows Recovery Environment, the recovery system that runs outside the normal desktop. Enter Windows Recovery Environment, choose Troubleshoot > Advanced options > Uninstall Updates, and use the option for removing the latest quality update. Microsoft documents this path specifically for situations where a recently installed update causes problems.
There is no reason to jump straight to manually replacing msmpeg2ac3dec.dll or copying an older decoder from another Windows installation. Community reports have described DLL replacement and third-party decoder approaches, but those are not Microsoft's supported resolution for this issue and can create a second compatibility problem. The cleaner diagnostic path is to establish the update relationship first, then either roll back the update when appropriate or wait for Microsoft's official correction.
Why installing a random codec pack is not the first fix
Windows 11's AC-3 situation is already more complicated than it appears because Microsoft removed the codec from clean installations starting with 24H2. Some PCs can still have AC-3 support because they were upgraded from an earlier Windows installation or because an original equipment manufacturer installed a codec. Installing an unrelated codec pack therefore does not necessarily address the component that an older application is actually calling.
There are reports that alternative DirectShow decoders such as LAV Filters can work around the failure for particular applications, and one business environment reported success after testing that approach. That evidence is useful as a troubleshooting lead, but it is not the same as a Microsoft-supported fix, and compatibility depends on whether the affected application can use the alternative decoder. If the software has its own documented codec-selection option, that is a better place to start than changing system-wide media components.
Test the application after the workaround
After removing the update or changing the application's supported audio path, test the exact operation that previously caused the crash. Launch the application from a normal desktop session, open the same type of media or project, and trigger the audio function that failed before. If the program now remains open, repeat the test after a restart because some audio components and applications initialize differently during boot. The goal is to establish whether the workaround changed the failure rather than simply confirming that the application opened once.
If you removed an update, also check Windows Update afterward so you know which build is currently installed. Keep a record of the update number and application version, especially on PCs used for business software or older games that cannot easily be replaced. Microsoft has not yet provided a release date for the permanent correction, so the useful next step is to watch the Windows 11 release-health entry for a new resolution and then retest before restoring the affected update path.
Wait for Microsoft's fix rather than treating rollback as permanent
Microsoft's current status is straightforward: some applications that require AC-3 decoding can close unexpectedly after KB5124010 or later updates, the affected client versions are Windows 11 24H2, 25H2, and 26H2, and a future Windows update is expected to contain the resolution. There is no published dedicated fix yet in Microsoft's October 3 update entry.
That makes the update history and application behavior more useful than repeatedly reinstalling the affected software. If the crash disappears after rolling back the relevant update, keep the application's version and Windows build recorded so you can test again when Microsoft publishes the correction. Once the fixed Windows update arrives, install it and verify the previously failing audio workflow before returning the PC to its normal update schedule.
Written by
