- Status: Confirmed / Investigating — no official fix deployed yet, according to Neowin.
- Triggering update: KB5124010
- Affected build: Windows OS Build 26300.9550
- Symptom: Legacy apps that rely on Windows’ built-in Dolby Digital (AC-3) decoders crash abruptly on startup.
Microsoft’s latest cumulative update has turned out to be a headache for anyone running older media software on the newest Windows preview. According to reporting from Neowin, update KB5124010 is causing legacy applications that lean on the operating system’s built-in decoders for AC-3 audio decoding to crash on startup — a problem affecting systems on OS Build 26300.9550.
If you’ve noticed your favorite older media player or audio application suddenly closing on you after installing this update, you’re not imagining things. Here’s what’s happening, who’s impacted, and what you can do about it.
What exactly changed
The core issue centers on AC-3 audio decoding, the technology behind Dolby Digital soundtracks. Windows ships with a set of built-in media decoders that let applications play AC-3 audio without requiring you to install third-party codec packs. Many older, “legacy” applications were written to depend on these system-provided decoders rather than bundling their own.
After installing KB5124010, those applications are reportedly crashing abruptly — closing without warning rather than simply failing to produce sound. The distinction matters: this isn’t a missing-audio glitch you can work around by adjusting settings, but a hard failure that prevents the app from running at all.
Microsoft has not yet deployed an official fix, according to Neowin, which first flagged the issue. No patch or rollback guidance has been published as of the report.
Who is affected
The affected systems are those running OS Build 26300.9550 — a build tied to Windows’ newer preview channel. In practical terms, this means the problem is concentrated among users testing the latest builds rather than the general public on stable releases.
Within that build group, the crash is specific to applications that call on Windows’ built-in Dolby Digital decoders for AC-3 playback. If your software uses its own audio pipeline or doesn’t handle AC-3 content, it likely won’t be impacted. But if you run older media players, home-theater PC (HTPC) software, or any application built to lean on the OS’s native decoders, you’re in the risk zone.
Why AC-3 audio decoding matters
AC-3, marketed as Dolby Digital, has been the standard audio codec for DVDs, broadcast television, and countless movie and game files for decades. Rather than forcing every application to ship its own decoder, Microsoft has historically included system-level AC-3 support in Windows. This lets a wide range of software — including software that predates modern codec frameworks — decode Dolby Digital audio out of the box.
The trade-off is that this convenience creates a shared dependency. When something in the underlying decoder layer changes, every app leaning on it can break at once. That’s exactly what appears to be happening with KB5124010.
What you can do about it
Since Microsoft hasn’t released a fix, your options are somewhat limited for now. The most reliable way to avoid the crash is to stay off the affected build until Microsoft publishes a corrected update. If you’re on OS Build 26300.9550 and not yet experiencing the problem, pausing feature updates or rolling back to a previous build could keep your media software working.
If you’re already hitting crashes, check whether your application offers an alternative audio output mode that bypasses the system decoder — some players let you select a different audio path or bundle their own codecs. Uninstalling the problematic update is another route, though Windows may simply reinstall it on your next check, so you’d want to pause updates afterward.
What this means for you
For most everyday Windows users, this is unlikely to cause daily disruption — the crash only touches applications that specifically depend on the built-in Dolby Digital decoder. If you stream music or use modern players that handle their own audio, you probably won’t notice anything.
But for owners of home-theater PCs, collectors of movie libraries, or anyone running older media software, a broken decoder can be a genuine roadblock. The best move right now is to hold off on installing KB5124010 on affected builds until Microsoft ships a fix, and keep an eye on official update channels for word on a patch.
Source: Neowin
Over to you: Do you run a home-theater PC that depends on Dolby Digital, and would you hold off on this update to stay safe?
