NS_E_WMPXML_ENDOFDATA 0xC00D0FB5 Fix – XML Ran Out of Data

Yeah, this one's annoying. Let's fix it.

You're trying to play something in Windows Media Player and you get hit with error 0xC00D0FB5. The message says the XML parser ran out of data. What that actually means: WMP tried to read a corrupted metadata file or a broken playlist. It happens most often after a crash, an incomplete file transfer, or if you're syncing with an older MP3 player and the device writes junk into the library.

Step 1 – Kill WMP and the background database process

Open Task Manager (Ctrl+Shift+Esc). Look for wmplayer.exe and mfpmp.exe. End both tasks. If you skip this, the next step won't work because Windows locks the database.

Step 2 – Delete the media library database

Press Win+R, paste this, then hit Enter:

%LOCALAPPDATA%\Microsoft\Media Player

In that folder, select everything (Ctrl+A) and delete it. Yes, everything. Don't worry — WMP will recreate it fresh when you relaunch. You'll lose your playlists and ratings, but your actual music files are safe.

Step 3 – Rebuild the library

Open WMP again. Go to Organize > Manage Libraries > Music. Make sure your music folder is checked. Then press Alt to show the menu bar, click Tools > Options > Library, and hit Configure Sharing (or skip sharing if you don't need it).

Now just wait. WMP will rescan your library. Depending on how many files you have and whether they're on a spinning disk or SSD, this takes 30 seconds to 10 minutes. The error won't come back unless a file itself is corrupt (more on that below).

Why this works

The culprit is almost always the CurrentDatabase_372.wmdb file (the number changes between Windows versions). That file holds the XML metadata WMP parses when loading your library. If it gets truncated — from a power loss, a bad USB eject, or a program that wrote garbage into a playlist — the parser hits the end of the data structure before it finishes reading. It throws 0xC00D0FB5.

Deleting the whole folder forces WMP to rebuild that database from scratch. It reads the actual media files, extracts proper metadata, and writes a clean wmdb. Nine times out of ten, that's all you need.

When that doesn't fix it – check the actual files

If the error keeps showing up on a specific song or video, that file itself has broken metadata. WMP's XML parser is strict — one bad tag and it chokes.

• Find the file in Explorer.
• Right-click > Properties > Details. Scroll through the fields. If you see gibberish or missing values, that's your problem.
• Fix it with MP3tag (free, available at mp3tag.de). Open the file, clear the corrupt fields, save.
• Or just delete the file and re-rip or redownload it.

I've also seen this with corrupt ASX playlist files. If the error shows when you double-click a playlist (not a song), open the .asx file in Notepad. Look for mismatched tags like </asx> missing or extra characters. Fix the XML manually or recreate the playlist.

Prevention – stop it from coming back

Three things cause this error more than anything else:

1. Abrupt shutdowns while WMP is running. Shut down WMP before you turn off the PC.
2. Bad USB ejects from portable players or drives. Always use 'Safely Remove Hardware'.
3. Syncing with old devices that write non-standard metadata. Avoid WMP sync with pre-2010 MP3 players.

Also, if you use third-party tag editors (like TagScanner or MediaMonkey), make sure they're writing standard ID3v2.3 or v2.4 tags. WMP hates non-standard frames. I've seen a single 'TXXX' frame with an empty value nuke an entire library scan.

Still broken? Try these

If you followed the steps above and the error persists, run this command in an admin command prompt:

sfc /scannow

That checks for corrupted system files. Rarely helps here, but it's quick. Also check Windows Update — sometimes a WMP patch is all that's missing.

And if you're on Windows 10 N or KN editions (common in Europe), you need the Media Feature Pack. Without it, WMP itself is half-baked and throws random XML errors. Download it from Microsoft's site.

Bottom line: delete the database, rebuild, and if that fails, hunt down the corrupt file. You'll be playing your music again in ten minutes.