NS_E_MPDB_GENERIC (0XC00D0FCC) – WMP Library Corruption Fix

Cause 1: Corrupted Library Database File

What's actually happening here is that the CurrentDatabase_372.wmdb file – the SQLite-based database Windows Media Player uses to track your music, videos, and playlists – has become corrupt. This typically happens after a crash, improper shutdown, or if you've added a file with mangled metadata (like an MP3 with a 4GB embedded cover art). I've seen it most often when someone copies a large collection from an external drive that was disconnected mid-transfer.

The fix is to delete that database. WMP will rebuild it automatically on next launch.

1. Make sure WMP isn't running. Check Task Manager – kill wmplayer.exe if you see it.
2. Open File Explorer and paste this path: %LOCALAPPDATA%\Microsoft\Media Player
3. You'll see a bunch of files including CurrentDatabase_372.wmdb. Delete that file and the entire Media Player folder contents except the MLS subfolder (leave that alone).
4. Restart WMP. It'll rebuild the database – this can take a few minutes on a large library.

The reason step 3 works is that WMP expects a fresh database, and deleting the old one forces it to re-scan your watched folders. If you have playlists you want to keep, back them up first – they're stored in the Playlists folder under your Music library, not in the WMP database.

On Windows 11, this still works. The folder path hasn't changed since Windows 7. If you're on Windows 10 22H2 or newer, you might also need to delete CurrentDatabase_372.wmdb from %APPDATA%\Microsoft\Media Player – older versions stored it there too.

Cause 2: Bad Audio/Video File in Library

Sometimes the database itself is fine, but one specific file causes the error when WMP tries to read its metadata. The error shows up when WMP is scanning or opening the library – you might see it right after adding a new album. The culprit is often an MP3 with a corrupted ID3 tag, a WMA file with DRM that's been revoked, or a video file with a broken header.

Here's how to track it down:

1. Open WMP and go to the library view. If you can't even get that far, skip to Cause 1.
2. In the navigation pane, right-click the Music node and choose Add to library. Change the monitored folders to None, then apply. This tells WMP to stop scanning everything.
3. Close WMP and restart it. If the error goes away, start adding folders back one at a time. When the error returns, you've found the folder with the bad file.
4. Use a tool like MP3tag or MediaInfo to inspect files in that folder. Look for files with unusually large metadata, zero-length duration, or weird characters in the title.
5. Delete or re-encode the offending file. I've found that re-saving the MP3 with MP3tag (just a simple save, no changes) often clears the corruption.

The reason step 4 works is that MP3tag rewrites the ID3 tags cleanly, which fixes any malformed frames that WMP's parser chokes on. Most common on files downloaded from sketchy sites or converted with old tools like CDex.

Cause 3: Corrupt Windows Media Player Configuration

This is less common but happens after a Windows update that changes WMP's internal registry settings. I've seen it on Windows 10 22H2 after the KB5022834 update. The error code is the same because WMP can't load its library configuration.

Fix: Reset WMP using the Microsoft Fix It tool or manually:

1. Press Win + R, type regedit, and hit Enter.
2. Navigate to HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences.
3. Delete the LibraryConfiguration key (not the whole folder).
4. Close regedit and restart WMP.

If that doesn't work, you can run the Windows Media Player troubleshooter – it's buried in Settings > System > Troubleshoot > Other troubleshooters. But honestly, the registry cleanup is more direct. The troubleshooter only re-registers DLLs, which rarely helps here.

On Windows 11, the registry path is identical. After a feature update, I've had to delete the entire MediaPlayer key (backup first) and let WMP recreate it. Only do that if step 3 fails.

Quick-Reference Summary