Quick answer for pros: Run sfc /scannow in an admin command prompt. If that doesn't fix it, rebuild the WMP database by deleting the CurrentDatabase_372.wmdb file in %LOCALAPPDATA%\Microsoft\Media Player. Then restart WMP.
You're trying to play a video or music file in Windows Media Player, and instead of your content, you get error 0XC00D1070. I know this error is infuriating — especially when the file plays fine in VLC or even in the Movies & TV app. What's happening is that WMP can't read the file's metadata (things like title, artist, album art). This usually hits when you have partially downloaded files, files from sketchy sources, or media that's been moved around between drives. I've seen this most often on Windows 10 version 22H2 and Windows 11 23H2 with WMP 12.
Why This Error Shows Up
The error code NS_E_WMX_ATTRIBUTE_UNRETRIEVABLE translates to "cannot retrieve the specified attribute." WMP uses a database to cache metadata for all your media. When that database gets corrupted — say, from a crash or an unexpected shutdown while WMP was scanning — it can't read metadata for new or changed files. Another trigger: files with DRM (Digital Rights Management) that's expired or missing a license. I've also seen it with .wmv files exported from old video editing software like Windows Movie Maker.
Fix 1: Run System File Checker
Start with the easiest thing. Corrupted system files can mess with WMP's ability to read metadata. Open Command Prompt as Administrator (search for "cmd," right-click, "Run as administrator"). Then run:
sfc /scannow
Wait for it to finish — takes about 5-10 minutes. If it finds and fixes corrupted files, restart your PC and try the file again. This fixes maybe 30% of cases, but it's worth doing first because it costs you nothing.
Fix 2: Rebuild the Media Player Database
This is the real fix for most people. WMP stores metadata in a database file that can get bloated or corrupted over time. Here's how to reset it:
- Close Windows Media Player completely — check Task Manager to make sure it's not running in the background.
- Press Win + R, type
%LOCALAPPDATA%\Microsoft\Media Player, and hit Enter. - Delete the file named
CurrentDatabase_372.wmdb. If you don't see it, enable "Show hidden files" in File Explorer's View menu. - Also delete any
.wmdbfiles that start with "CurrentDatabase" — sometimes you have multiple versions. - Don't delete the folder itself, just the database files.
Open WMP again. It will rebuild the database from scratch, scanning your library. This takes a few minutes but should clear the error for all your files. I've used this fix on dozens of machines and it works 9 times out of 10.
Fix 3: Remove and Re-add Your Media Folders
If rebuilding the database didn't help, the metadata might be stuck in a corrupted cache. Instead of resetting everything, just remove the affected folder from WMP's library and add it back:
- In WMP, go to Organize > Manage Libraries > Music (or Videos, depending on the file).
- Select the folder that contains the erroring file, click Remove, then OK.
- Go back to Organize > Manage Libraries > Music again, click Add, select the same folder, and click Include folder.
- Let WMP rescan the folder — it'll re-read metadata fresh.
This is less invasive than deleting the entire database, and it usually works for single-folder issues.
Alternative Fix: Use a Different Player
If none of these work, the file itself might have irreparably broken metadata headers. WMP is picky about metadata structure — it expects things in a specific order. Try playing the file in VLC Media Player or MPC-HC. If it plays fine there, the issue is WMP's parser, not your file. You can also use a tool like MP3Tag to strip and re-add metadata fields. Open the file in MP3Tag, remove all tags (or rewrite them cleanly), save, then try WMP again. I've saved a few "dead" files that way.
Prevention Tip
WMP's database gets cranky when you add or remove large numbers of files at once. If you regularly move media around, close WMP first, then move files, then reopen it. Also, avoid running WMP as administrator — it writes temp metadata files to your user folder, and elevated mode can corrupt those writes. And for the love of all that is holy, don't store media on a network drive that drops connection. WMP tries to index files over a flaky network and the database gets poisoned. Keep your music on local SSDs.
That's it. You should be able to play your files now without that ugly error. If it still shows up, you're probably looking at a corrupted file, not a WMP issue — check it in another player to confirm.