NS_E_GRAPH_NOAUDIOLANGUAGESELECTED (0XC00D10C6) Fix

You're watching a video file in Windows Media Player — an MKV or an AVI with multiple audio tracks — and boom: NS_E_GRAPH_NOAUDIOLANGUAGESELECTED (0XC00D10C6). The player window stays black, no sound, and that's it. This usually hits after a Windows Update, or after installing a codec pack that trampled over existing filters.

What's Actually Happening Here

The error comes from DirectShow's filter graph manager. When WMP tries to build a playback graph for your file, it needs to connect a video renderer and an audio renderer. The audio part requires the source filter to expose a language selection — typically for multi-language files. If something — a bad codec, a corrupted filter registration, or a stale DirectX component — breaks that chain, the graph manager can't figure out which audio language to pick. It defaults to nothing, and you get error 0XC00D10C6.

The root cause is almost never a missing audio language in the file itself. It's a filter graph that can't negotiate the connection because a filter in the chain is misbehaving or registered incorrectly. The most common culprit: old or conflicting codec packs like K-Lite or CCCP that override Microsoft's built-in filters.

The Fix

Skip reinstalling WMP or running SFC — those won't touch the filter graph. Here's what actually works.

Step 1: Reset the Filter Graph Manager

The Filter Graph Manager caches filter lists in the registry. Clearing that cache forces a fresh enumeration.

1. Press Win + R, type regedit, hit Enter.
2. Navigate to HKEY_CURRENT_USER\Software\Microsoft\DirectShow\
3. Delete the key named MostRecentlyUsedFilters (right-click → Delete). If it's not there, skip.
4. Still in DirectShow, delete the PreferredFilters key too if it exists.

Close regedit. This wipes the filter history and preferences, forcing WMP to rebuild the graph from scratch the next time you play a file.

Step 2: Re-register DirectShow Filters

Sometimes a filter's COM registration gets corrupted. Re-registering the base ones fixes that.

1. Open Command Prompt as Administrator (search cmd, right-click → Run as administrator).
2. Run these commands one by one:

regsvr32 /s quartz.dll
regsvr32 /s msdmo.dll
regsvr32 /s amstream.dll
regsvr32 /s wmvcore.dll
regsvr32 /s wmpdmod.dll

Each should return success. If any fails with The module was loaded but the entry-point DllRegisterServer was not found, that's a sign the file itself is missing — run SFC /scannow in that case.

Step 3: Disable Third-Party Codec Filters

This is the step that usually nukes the problem. Third-party codec packs often register splitter filters that override Microsoft's. For MKV files, the LAV Splitter is a common offender — it works great until it doesn't.

1. Open Start → type System Configuration (msconfig) → go to Services tab.
2. Check Hide all Microsoft services.
3. Look for services named after codec packs: K-Lite Codec Pack, CCCP, LAV Filters, FFDShow. Disable them (untick).
4. Also go to Startup tab → Open Task Manager → disable any codec-related startup entries.
5. Restart the machine.

After reboot, test WMP with the same file. If it works, you've got a codec conflict. You can re-enable codec services one by one to find the exact filter that's breaking things — but honestly, if you're using WMP, you don't need third-party codecs for most modern files. WMP 12 on Windows 10 can handle H.264 and AAC natively. For MKV, install the HEVC Video Extensions from the Microsoft Store — they're signed and don't mess with the filter graph.

If It Still Fails

Two more things to check:

• Custom audio renderer: Some sound cards install their own DirectShow audio renderer (Realtek, Creative). Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectShow\AudioRenderer and delete any subkeys that don't look like Default DirectSound Device. Backup first.
• File-specific issue: Open the file in MediaInfo (free tool). Look at the Audio section — if the language tag says und (undefined) and you have only one audio track, that can trip up WMP. Remux the file with MKVToolNix to set a language tag (e.g., eng).

If you're still stuck after these steps, the problem is likely a deeper DirectX installation issue. Run the DirectX End-User Runtime Web Installer from Microsoft — it'll repair missing or corrupted files. Last resort: a full Windows repair install using DISM /Online /Cleanup-Image /RestoreHealth followed by SFC. But nine times out of ten, steps 1-3 kill this error dead.