0XC00D32DA

NS_E_METADATA_NOT_AVAILABLE (0XC00D32DA) – When Windows Media Player Can't Find Song Info

This error means Windows Media Player can't read or download metadata for a media file. The fix depends on the source – local files, network shares, or streaming content.

1. Corrupted or Incomplete Local Media Files

The most common trigger for this error is a media file with damaged or missing internal metadata tags. This happens often with files downloaded from peer-to-peer networks or converted with buggy tools. Windows Media Player tries to read the ID3 tags (for MP3) or other embedded metadata, and if the structure is off, it throws 0XC00D32DA instead of showing blank fields.

Your fix

  1. Right-click the file in Windows Media Player's library and select Edit. Manually fill in the artist, album, or title. If the fields don't save, the file's metadata is hosed.
  2. Use MP3tag (free, portable) to remove all tags and then re-add them. What's actually happening here is MP3tag rewrites the tag structure cleanly, which WMP can then parse.
  3. If the file plays but has no cover art, that's a separate issue – the error references any metadata item, not just title/artist.

For video files (AVI, MKV, MP4), the metadata is stored differently. Tools like MKVToolNix or MediaInfo can show you what's there. If the container is corrupted, remux the file with ffmpeg -i input.mkv -c copy output.mkv. This copies streams without re-encoding, just rebuilding the container.

2. Windows Media Player's Metadata Downloading Is Blocked

Windows Media Player 12 (built into Windows 7 through 11) tries to fetch album art, artist bios, and track info from the internet. If your network blocks these requests – corporate proxy, VPN, or even outdated DNS – you get 0XC00D32DA when it fails to download.

Check this first

  1. Open Windows Media Player, press Alt to show the menu bar, go to Tools > Options > Library tab.
  2. Look for Retrieve additional information from the Internet. Uncheck it if it's checked. Then click Apply.
  3. Close WMP, reopen it, and try the file again. If the error disappears, the problem was a network block.

If you want metadata from the internet but it's blocked, the real fix is to add music.microsoft.com and metadata.smcloud.com to your proxy/firewall allowlist. On a corporate network, that's not always your call, so offline metadata (from tools like MusicBrainz Picard) is your next bet.

3. Registry Setting That Disables Metadata Retrieval

Less common but sneaky: a group policy or registry tweak can disable all metadata fetching for Windows Media Player on a system level. This can persist even after you uncheck the option in WMP's UI.

The fix (requires admin rights)

  1. Press Win + R, type regedit, and hit Enter.
  2. Navigate to HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences.
  3. Find the DWORD value InternetMetadata. If it's set to 0, that's your culprit. Change it to 1.
  4. If the key doesn't exist, create a new DWORD (32-bit) named InternetMetadata and set it to 1.
  5. Close Regedit, restart Windows Media Player.
Path: HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences
Value: InternetMetadata (DWORD)
Set to: 1

Why this works: The UI checkbox writes to a different location sometimes, or a cleaner tool might have set this key directly. The registry override takes precedence over the UI setting.

4. Outdated or Corrupted Library Database

Windows Media Player caches metadata in a database file (CurrentDatabase_360.wmdb). If this database gets corrupted – from a power failure during a library scan, for example – the error can pop up even for healthy files.

Rebuild the database

  1. Close Windows Media Player completely.
  2. Press Win + R, type %LOCALAPPDATA%\Microsoft\Media Player, and press Enter.
  3. Delete all files and folders inside that directory. Don't worry – they'll be rebuilt.
  4. Open Windows Media Player again. It'll scan your monitored folders and rebuild the library. This takes a few minutes for large collections.

If the error was database corruption, this fix is permanent. If it comes back, check the next cause.

5. Network Share Permissions for Metadata Files

When playing files from a NAS or another PC on your LAN, WMP also tries to store metadata locally. If the share is read-only or the local cache path is broken, you get 0XC00D32DA. This one's easy to miss because the file plays fine – just the metadata fails.

Fix the cache location

  1. Go to Tools > Options > Rip Music tab in Windows Media Player.
  2. Change the Rip music to this location to a local folder (like C:\Users\YourName\Music\WMP Metadata).
  3. Click Apply and restart WMP.

The reason this works: WMP stores downloaded metadata and album art in the rip location. If that's on a network drive that's sometimes offline, it fails silently and shows the error. Move it local.

Quick-Reference Summary Table

CauseFixTime
Corrupted local file tagsUse MP3tag or remux video with ffmpeg5 minutes
Network blocking metadata downloadUncheck "Retrieve additional information from the Internet" in WMP options1 minute
Registry InternetMetadata = 0Set to 1 in Regedit2 minutes
Corrupted library databaseDelete contents of %LOCALAPPDATA%\Microsoft\Media Player5 minutes + rebuild time
Network share cache locationChange rip music location to local folder2 minutes

One last thing: if you're on Windows 10 or 11 and don't use Windows Media Player much, consider VLC or MPC-HC. They don't depend on Microsoft's metadata service and won't throw this error at all. But if you're stuck with WMP for work or habit, the fixes above cover every scenario I've seen in ten years of Windows support.

Related Errors in Windows Errors
0X80100068 Smart Card Reset (0x80100068) — Fix the Shared State Error 0X00000117 STATUS_BUFFER_ALL_ZEROS (0x00000117) Fix – Empty Buffer Bug 0X000003F0 Fix ERROR_NO_TOKEN (0X000003F0) on Windows – Token Gone Wrong 0X000004FA Fix 0X000004FA: Group Policy Sync Foreground Refresh Required

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.