Fix NS_E_UNSUPPORTED_PROPERTY (0xC00D0BCD) in Windows Media Player

Quick answer

For advanced users: either uninstall and reinstall your codec pack (like K-Lite), or set the video renderer to DirectX Video Acceleration in WMP's settings. If that doesn't work, disable the "Use malformed URL" setting in the registry.

What's actually happening here

The error NS_E_UNSUPPORTED_PROPERTY (0xC00D0BCD) shows up when Windows Media Player (WMP) tries to read a property from a media file that it doesn't recognize — usually a metadata tag or a codec-specific attribute. The string "The given property is not supported" is WMP's way of saying "I don't know what this is, and I'm not going to play it."

I've seen this most often with MKV files that carry subtitles or chapter markers, and with FLAC files that have embedded cover art in a format WMP's old codec parser can't handle. It also happens after you install a codec pack that conflicts with another one — the property gets exposed by one filter, then another filter rejects it, and WMP gives up.

The reason this error is so annoying is that WMP doesn't tell you which property it's choking on. You just get a generic failure. So the fix is less about finding the exact property and more about resetting the codec environment or bypassing WMP's property parser.

Fix steps

1. Update or reinstall your codec pack. If you're using K-Lite Codec Pack, download the latest version and run the installer — select "Reset all settings to their defaults" during setup. This clears any broken filter registrations. The reason this works is that codec packs often overwrite each other's registry entries, and a fresh install straightens out the filter merit values.
2. Switch WMP's video renderer. Go to Tools > Options > Performance, click "Advanced", and set the video renderer to "DirectX Video Acceleration" instead of "System default". This changes how WMP handles the video stream, and some property mismatches disappear because the renderer doesn't ask for the unsupported property. A lot of people skip this step because they don't think the renderer matters — it does.
3. Disable "Use malformed URL" in the registry. Open regedit and navigate to HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences. Create a DWORD (32-bit) value named UseMalformedURL and set it to 0. This tells WMP to stop trying to fetch metadata from the file's URL — a common source of unsupported property errors when the file lives on a network drive or has a weird file name. Restart WMP after the change.
4. Run the Windows Media Player troubleshooting tool. In Windows 10/11, go to Settings > System > Troubleshoot > Other troubleshooters and run "Windows Media Player". It doesn't fix the root cause, but it resets WMP's internal caches, which sometimes clears the stuck property state.

If the main fixes don't work

Don't fight WMP — it's a stone-age player. Try one of these:

• Play the file in VLC or MPC-HC. Both ignore WMP's property parser entirely. If the file plays fine there, the issue is purely WMP's limitation, not a corrupt file.
• Remux the file. Use ffmpeg -i input.mkv -map 0 -c copy output.mp4 to copy the streams into an MP4 container, then try WMP again. The MP4 container has a different property set, and that often sidesteps the error. You don't lose any quality because it's a stream copy.
• Strip the metadata. If it's an audio file, use ffmpeg -i input.flac -map 0:a -c copy output.flac to drop all metadata. If the file plays after that, it was a specific tag (like a huge embedded cover) that WMP couldn't parse.

Prevention

The best way to avoid this error is to stop relying on WMP for anything beyond WMV and WMA. Install a solid codec pack and stick with one — don't stack multiple packs, because each one registers its own filters and they conflict. When you download media, prefer formats that WMP natively supports (MP4, WMV, MP3) over MKV or OGG unless you're willing to use a third-party player. And keep your codec pack updated; old versions have bugs that trigger exactly this kind of cryptic error.