NS_E_METADATA_LANGUAGE_NOT_SUPORTED 0XC00D32D8

What triggers this error

You'll see NS_E_METADATA_LANGUAGE_NOT_SUPORTED (0XC00D32D8) when you try to play an MP3 or WMA file in Windows Media Player (version 12 on Windows 10/11). The player starts to load the file, the progress bar appears for a second, then it stops with that error. The file plays fine in VLC or any other player — that's your first clue the problem isn't the audio itself.

I've seen this most often with files downloaded from streaming sites or ripped from CDs with custom tagging software. One user reported it on a podcast MP3 that had a Language tag set to EN instead of ENG. Another had XX as a placeholder from an old iTunes library.

What's actually happening here?

Windows Media Player uses the Language metadata field to determine how to decode the audio track. The spec says language codes must follow ISO 639-2 (three-letter codes like eng, fra, deu). When the tag contains anything else — a two-letter code, a number, or even a blank entry — WMP's metadata parser chokes and throws 0XC00D32D8.

The reason other players don't care is they either ignore the language field entirely (VLC) or fall back to a default decoder. WMP tries to be strict and fails.

The fix: strip or rewrite the language tag

You've got two clean options. I prefer the first one — it's faster and doesn't risk losing other metadata.

Option 1: Remove the language tag with a command-line tool

1. Download Mp3tag from mp3tag.de (free, no installer needed if you grab the portable version).
2. Open Mp3tag, drag the offending file into the window.
3. Select the file in the list, then go to Convert > Extended Tags.
4. Find the Language field. Delete it entirely. Don't try to fix it — just remove it.
5. Click OK. That's it. WMP will now play the file without error because there's no language tag to trip over.

Option 2: Set a valid language code via PowerShell

If you prefer keeping the tag but making it valid:

1. Open PowerShell as admin.
2. Run this command, replacing the path with your file's actual path:

$shell = New-Object -COM Shell.Application
$folder = $shell.Namespace('C:\Path\To\File')
$file = $folder.Items().Item('song.mp3')
$folder.GetDetailsOf($file, 17)  # This shows the current language tag

PowerShell can't directly write ID3 tags via COM, so this approach is read-only. Use Mp3tag instead — it's the right tool for the job.

Why Mp3tag works and other tools don't

Windows 10/11's built-in file properties dialog won't let you edit the Language field for audio files — it's read-only. Most free tag editors either leave the field alone or write invalid codes. Mp3tag follows the ID3v2 spec correctly and lets you remove the field without corrupting the file.

Still failing? Check these

• File permissions. If the file is on a network share or external drive with read-only attributes, WMP might still error out after the tag fix. Copy the file to your local Music folder first.
• Corrupted ID3 header. Rare, but possible. Run mp3val.exe -f -nb from the command line to fix any structural errors in the MP3 file. Then try the tag fix again.
• WMP library corruption. If the file plays once then errors again, your Windows Media Player library database might have cached the bad metadata. Go to Settings > Personalization > Media Player and click Clear library. Rescan after fixing the tag.

That's it. You don't need to reinstall WMP, disable codecs, or go digging in the registry. The cause is literally a one-line tag, and removing it is a ten-second fix.