Fix NS_E_VIDEO_CODEC_ERROR (0XC00D0BC5) in Windows 10/11

The 30-second fix: try another player

The quickest sanity check: open the same video file in VLC Media Player or MPC-HC. If it plays fine, the problem isn't the file or your system—it's Windows Media Player's codec support. Windows Media Player relies on system codecs, and that can break with certain formats (like HEVC/H.265 or VP9).

If VLC plays it, you're done in 30 seconds. The rest of this guide is for when the video won't play anywhere, or you really want to fix Windows Media Player.

The 5-minute fix: install missing codecs

What's actually happening here is that Windows 10 and 11 ship with codec support for older formats (MPEG-4, H.264) but not for newer ones like HEVC (H.265) or VP9. The error 0XC00D0BC5 fires because the decoder DMO doesn't exist for the file's compression.

Install the HEVC Video Extensions from Microsoft (free, but Microsoft hides it):

1. Open this link in your browser: ms-windows-store://pdp/?ProductId=9n4wgh0z6vp0
2. If it doesn't work, search the Microsoft Store for "HEVC Video Extensions from Device Manufacturer".
3. Install it. Restart Windows Media Player.

For VP9 videos: Install the VP9 Video Extensions from the Store (free). Same drill, search for it.

For old or rare codecs: Grab the K-Lite Codec Pack Basic (safe, no adware). Only check the boxes for the codec you need—do not install the full pack unless you know what you're doing. Too many codecs can conflict.

The 15-minute fix: repair system files and re-register codecs

If codecs are installed and the error persists, the video file itself could be corrupt, or Windows's codec infrastructure got messed up—maybe after a bad update or third-party uninstall.

Step 1: Run System File Checker

Open Command Prompt as admin (right-click Start → Windows Terminal (Admin)), then run:

sfc /scannow

Wait for it to finish. If it finds corrupt files and fixes them, reboot. Try the video again.

Step 2: Check the file's integrity

Use a tool like ffmpeg to verify the file. Open CMD in the folder with the video and run:

ffmpeg -v error -i "yourfile.mp4" -f null -

If ffmpeg reports nothing, the file is likely fine. If it shows errors like "invalid data found when processing input", the file is damaged. Try re-downloading or converting it with HandBrake (set output to H.264, AAC, MP4).

Step 3: Re-register Windows Media Player and codec DLLs

Open Command Prompt as admin. Run these one by one:

regsvr32 wmp.dll
regsvr32 wmvdmoe2.dll
regsvr32 wmvencod.dll
regsvr32 wmspdmod.dll

Each should say "DllRegisterServer succeeded". Restart.

Step 4: Reset Windows Media Player

Go to Settings → Apps → Apps & features. Search for "Windows Media Player". Click it, select Advanced options. Click Reset. This deletes your library database but clears any corrupt state.

Step 5: Use DISM to fix the component store

If SFC didn't fix everything, the system image might be damaged. Run:

DISM /Online /Cleanup-Image /RestoreHealth

This takes 10-15 minutes. Reboot after it finishes. Then run sfc /scannow again.

When to give up on Windows Media Player: If you've done all this and the error still shows, the codec simply isn't supported by WMP's architecture. Some codecs require a directshow filter that WMP can't load. Install VLC or MPC-HC and move on. They handle nearly everything without this error.

Why step 3 works

The reason re-registering those DLLs works is that Windows Media Player uses DirectShow filters as codec wrappers. If a registry entry for wmvdmoe2.dll (the Windows Media Video decoder) gets corrupted or deleted by a third-party installer, WMP can't locate the decoder. Running regsvr32 rewrites the CLSID entries in HKEY_CLASSES_ROOT\CLSID and rebuilds the filter graph.

One more thing: if you see this error on all videos, not just one, suspect a broken codec pack or a Windows update that borked the media foundation framework. In that case, run the DISM command first, skip the file check, and reset WMP. That's your best bet.