Fix NS_E_NAMESPACE_BAD_NAME (0XC00D1396) – Invalid Node Name

You're trying to play a music file or open a playlist in Windows Media Player, and instead of music you get a box that says "The namespace node name is invalid" with error code 0XC00D1396. Frustrating, right? I've seen this crop up most often after someone syncs a playlist from an MP3 player, copies files from a network share that got interrupted, or imports a playlist file (.wpl or .m3u) that was saved with a bad character in the name—like a trailing space or an unsupported symbol.

What Causes NS_E_NAMESPACE_BAD_NAME?

The error means Windows Media Player can't parse the XML or metadata inside a playlist or media file. The "namespace node name" is basically a tag or identifier in the file's structure that WMP expects to see, but got something else—maybe a scrambled character, a missing closing tag, or a node name that's not valid for the WMP schema. Root cause is almost always a corrupted playlist file or a damaged media file's metadata.

Had a client last month whose entire music library looked fine in File Explorer, but WMP threw this error on every fourth song. Turned out their kid had edited a .wpl file in Notepad and saved it with a Unicode character the player didn't like.

How to Fix It – Step by Step

Step 1: Identify the Culprit File

If you get the error right after double-clicking a file or playlist, note which one triggers it. If you get it on launch, open WMP, go to the Library view, and look for any playlist that shows a yellow warning icon or won't expand. That's your problem child.

Step 2: Delete the Bad Playlist

If a playlist is the issue, delete it from within WMP:

1. Right-click the playlist name under Playlists in the navigation pane.
2. Select Delete > Delete from library only (don't delete the source files unless you want to).
3. Close and reopen WMP.

Nine times out of ten, that's the fix. If you still get the error, move to step 3.

Step 3: Clear the Media Library Cache (If the Error Persists)

Sometimes the corruption lives in the database WMP uses to track your files. Clearing it forces a rebuild:

1. Close WMP completely.
2. Press Win + R, type %LOCALAPPDATA%\Microsoft\Media Player, and hit Enter.
3. Delete everything in that folder (yes, everything—it's just cache).
4. Restart WMP. It will re-scan your monitored folders and rebuild the database.

Step 4: Repair or Reinstall Windows Media Player

If steps 1–3 didn't work, you're looking at a system-level corruption. Try this first:

1. Open Control Panel > Programs and Features > Turn Windows features on or off.
2. Uncheck Media Features (which includes WMP). Click OK, then restart.
3. Go back and re-check Media Features, click OK, restart again.

This re-registers all WMP components without losing your files. If that still fails, run an SFC scan from an elevated Command Prompt: sfc /scannow. Let it finish—takes about 15 minutes—then restart.

What If It Still Fails?

Check if the error happens with a specific file type—like a WMA or MP3 that came from a dodgy converter. Those files can have invalid header information. Convert the file to a clean MP3 using a tool like Audacity or Foobar2000, then re-import it. Also check your folder permissions—if WMP can't read the file's metadata because of a permission issue (rare but happens with external drives), move the file to your local Music folder and try again.

Last resort: switch to a different player. VLC or Media Player Classic handle corrupted metadata way better than WMP. But if you're stuck on WMP for a specific reason, the steps above will get you sorted 99% of the time.