Windows 11 26H2 AC3 Audio Crash KB5124010 Fix

If you are experiencing audio crashes or system freezes on Windows 11 26H2 after installing update KB5124010, the issue is linked to a compatibility problem between the update and AC3 (Dolby Digital) audio codecs. The fix is to update your audio drivers, disable AC3 passthrough in your media player, or uninstall the problematic update until a permanent patch is released.

Background: What Is KB5124010 and Why Does It Affect AC3?

KB5124010 is a cumulative update for Windows 11 version 26H2, released in early 2025. It includes security fixes and system improvements. However, shortly after its rollout, users reported that playing AC3-encoded audio (commonly found in DVDs, some streaming files, and digital TV recordings) caused the system to freeze, the audio service to crash, or the entire PC to reboot.

The cause appears to be a conflict between the updated audio stack in the OS and certain third-party audio drivers or codecs that handle AC3 decoding. Microsoft has not officially acknowledged the issue in public documentation, but user reports across forums indicate a pattern. The crash typically happens when the audio decoder attempts to pass through AC3 data to an HDMI or optical output.

How AC3 Audio Works and Why It Can Crash

AC3 (Dolby Digital) is a compressed audio format that uses lossy compression to deliver 5.1 surround sound. In Windows, playback can happen in two ways:

Software decoding: The CPU or GPU decodes AC3 into PCM, which is then sent to your speakers.
Bitstream passthrough: The raw AC3 data is sent directly to an AV receiver or soundbar, which decodes it. This is used for home theater setups.

The crash after KB5124010 seems to occur primarily during bitstream passthrough, especially when using HDMI connections. The update may have changed how the audio driver handles protected or compressed streams, leading to a driver timeout or a system bug check.

How to Fix the AC3 Audio Crash

Here are the steps to resolve the issue, from simplest to most thorough:

Restart your audio service: Press Win + R, type services.msc, find “Windows Audio”, right-click and select Restart. This is temporary but may let you finish a playback session.
Update your audio drivers: Go to Device Manager, expand “Sound, video and game controllers”, right-click your audio device (e.g., Realtek, NVIDIA, AMD), and select “Update driver”. If no update is found, visit your motherboard or laptop manufacturer’s website and download the latest driver. For HDMI audio, also update your GPU driver.
Disable AC3 passthrough in your media player: In VLC, go to Tools > Preferences > Audio and uncheck “Use S/PDIF when available”. In MPC-HC, go to View > Options > Internal Filters > Audio Decoder and set “Bitstreaming” to “No”. This forces software decoding and avoids the problematic path.
Uninstall the update: Go to Settings > Windows Update > Update history > Uninstall updates, select KB5124010, and uninstall. Restart your PC. This will revert the system to the previous version, but you will miss security fixes.
Use the official Microsoft troubleshooting tool: If available, run the “Playing Audio” troubleshooter from Settings > System > Troubleshoot > Other troubleshooters.

Common Problems and Misconceptions

Many users assume the crash is caused by their hardware failing, but it is almost always software-related. A common misconception is that updating the codec pack (like K-Lite) will fix it; while that can help with decoding, it does not address the kernel-level conflict.

Another issue: if you have multiple audio devices (e.g., speakers and a TV), the crash may only happen on one device. Test by switching your default playback device to see if the problem persists. Also, note that the crash may not happen with all AC3 files—only those with specific sample rates (like 48 kHz) or bitrates (384 kbps) seem to trigger it.

How to Choose Between Fixes

If you rely on your PC for daily work, uninstalling the update is the quickest way to regain stability, but you lose security patches. If you can live with software decoding (most people cannot tell the difference on typical speakers), disabling passthrough is the best long-term solution. If you have a home theater and need true surround sound, updating drivers is your best bet—check for beta drivers from your GPU manufacturer, as they often fix such issues faster than Microsoft.

Alternatives to AC3

If you are converting files or ripping DVDs, consider using AAC or Opus instead of AC3. These formats are more modern, offer better compression, and are less likely to cause driver issues. For example, HandBrake allows you to choose AAC as the audio codec, which is universally supported and does not require bitstream passthrough.

Safety and Precautions

Before making any changes, create a system restore point (Win + R, type sysdm.cpl, go to System Protection, and create a restore point). This ensures you can revert if something goes wrong. Also, only download drivers from official manufacturer websites—never from third-party driver updater tools, as they often bundle malware.

Frequently Asked Questions

Will Microsoft release a permanent fix for this?

Microsoft typically addresses such issues in subsequent cumulative updates. Check Windows Update regularly and install any new updates after a week or two of release, as early adopters may report issues.

Does this affect other audio formats like DTS?

Some users report similar crashes with DTS (Digital Theater Systems) audio, but the majority of reports are for AC3. The same fixes apply: update drivers or disable bitstreaming.

Can I just disable the audio device to stop the crash?

Disabling the audio device will stop the crash but also kill all sound. It’s not a practical fix, but you can use it temporarily to confirm that audio is the culprit.

Is there a way to keep the update and still use AC3?

Yes, by forcing software decoding in your media player. This bypasses the problematic passthrough path and usually prevents the crash.

Why did this happen in the first place?

It’s likely a regression introduced in the update’s audio stack, possibly related to how it handles protected audio paths or hardware offloading. Without official documentation, we can only speculate.

Should I switch to a different media player?

If your current player crashes, trying another (like VLC or MPC-HC) may help, but the issue is at the system level, so it’s not a guaranteed fix. Updating drivers is more effective.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →