0XC00D0020

Fix NS_E_FILE_PLAY_FAILED 0xC00D0020 in Windows Media Player

WMP throws this when a codec or file path is broken. Usually fixed by switching to a different player or reinstalling codecs.

You double-click a video file—maybe a downloaded MP4 or an old AVI from a digital camera—and Windows Media Player pops up with NS_E_FILE_PLAY_FAILED (0xC00D0020). The player window opens, shows a black screen, and then just sits there. Sometimes you get a popup that says "Windows Media Player cannot play the file. The player might not support the file type or codec." That's the classic trigger: a file that WMP doesn't have the right decoder for, or a broken file path.

What's actually happening here is that WMP is trying to read the file, but it fails before it can even start rendering. The error code 0xC00D0020 is generic—it covers everything from a missing codec to a corrupt file header to a path that points to a network location you've lost access to. The root cause is almost always one of three things: the file uses a codec WMP doesn't ship with, the file itself is partially downloaded or corrupted, or the file lives somewhere WMP can't reach (like a disconnected network drive or a path with weird characters).

Here's the thing: WMP is basically abandonware. Microsoft hasn't updated its codec pack since Windows 7. On Windows 10 and 11, it's a legacy feature. So when a file won't play, the fastest fix isn't to battle with WMP—it's to use something that actually supports modern codecs. But if you're stuck with WMP for whatever reason, here's a step-by-step approach.

Fix 1: Check if the file is corrupt or incomplete

Before you go messing with codecs, verify the file itself is playable. If you downloaded it from the internet, it might have cut off mid-download. Right-click the file, go to Properties, and look at the size. Does it match what the source said it should be? If it's smaller by a few MB, that's your problem. Re-download it.

Also, try opening the file in another player. VLC Media Player is free and plays nearly everything. If VLC plays it fine, then the file is fine—it's WMP that's the bottleneck. If VLC also fails, the file is corrupt, and no amount of codec tweaking will help.

Fix 2: Let WMP try to download a codec (it won't work, but try)

WMP has a built-in "Download codec" prompt. When the error appears, you might see a button that says "Web Help". Click it. It'll open a browser window that tries to find a codec. In my experience, this almost never works—Microsoft killed the codec download service years ago. But it's worth a shot if you're desperate. Don't expect miracles.

Fix 3: Install a community codec pack

If you really want to stay in WMP, install the K-Lite Codec Pack (Basic or Standard version). It adds all the decoders WMP is missing—H.264, HEVC, AC3, you name it. Here's the process:

  1. Download K-Lite Codec Pack from the official site (codecguide.com). Don't use third-party download mirrors—they bundle junk.
  2. Run the installer. Choose "Standard" preset—it covers most formats.
  3. During install, it'll ask about file associations. You can leave defaults.
  4. Restart WMP and try playing the file again.

The reason this works is that K-Lite registers DirectShow filters, and WMP uses DirectShow for playback. Once the right filter is in place, WMP can decode the file.

Fix 4: Move the file to a local folder

This sounds dumb, but it fixes a surprising number of 0xC00D0020 errors. If the file is on a network share, a USB drive, or in a cloud-synced folder (like OneDrive Desktop), WMP sometimes can't handle the path. Copy the file to your local C:\Users\YourName\Videos and try again. Also, rename the file to something simple—no special characters, no spaces, no emoji. A file named my_movie_01.mp4 is safer than Final Cut (V2)-final.mp4. WMP chokes on odd characters in some cases.

Fix 5: Re-register the WMP components

Sometimes WMP's own components get unregistered after a Windows update. You can re-register them with a couple of commands. Open Command Prompt as Administrator (right-click Start, choose "Command Prompt (Admin)" or "Terminal (Admin)"). Then run:

regsvr32 wmp.dll
regsvr32 wmploc.dll
regsvr32 wmploc.dll.manifest

This tells Windows to reconfigure WMP's core libraries. It usually takes about a minute. Then restart WMP and try again.

What if it still fails?

If you've tried all that and WMP still won't play the file, cut your losses. Install VLC or MPC-HC (Media Player Classic Home Cinema). Both are free, open-source, and play basically anything you throw at them. The real reason WMP fails is that it's stuck with a 2000s-era codec base, and the media world moved on. Stop fighting it—use a tool that respects modern formats.

One more thing: if the error happens on a specific file but not others, and none of the fixes work, the file is likely corrupt at the container level. Try re-encoding it with HandBrake (free). That'll mux it into a format WMP can handle. But honestly, just switch players. It's not worth the effort.

For reference, this error also shows up in Xbox Media Player and some Windows Phone legacy apps. If you're seeing it there, the fix is the same—it's a codec or path issue.

Related Errors in Windows Errors
0X8004E02D Fix CO_E_NOTCONSTRUCTED (0x8004E02D) COM+ Error 0X80110815 COMADMIN_E_PROGIDINUSEBYCLSID (0X80110815) Fix: COM+ Copy Error 0XC00D1392 NS_E_NAMESPACE_NAME_TOO_LONG (0XC00D1392) fix 0X80290202 Fix TBSIMP_E_INVALID_CONTEXT_HANDLE (0x80290202) in Windows

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.