0XC00D32D2

NS_E_PROPERTY_NOT_SUPPORTED Fix: Windows Media Error 0xC00D32D2

This Windows Media error means a codec or property isn't supported. Quick fix: reinstall codecs or switch to a different player. We'll walk through it.

Quick answer: This error means the media player or the file is trying to use a codec or property that your system doesn't support. The fastest fix is to install a codec pack like K-Lite or switch to VLC Media Player, which bundles its own codecs.

I've seen this error pop up more times than I can count, especially on Windows 10 and 11 machines. It usually happens when you're playing a video file that uses a newer or proprietary codec (like HEVC/H.265 or certain MKV containers) and Windows Media Player doesn't have the right decoder. The error message "The property is not supported" is Microsoft's way of saying, "I don't know how to handle this part of the file." It's not your fault – it's just that Windows Media Player is a bit behind the times.

Before You Start

Check if the file plays in another app. If you have VLC or MPC-HC, try them. If they work, you're dealing with a codec issue specific to Windows Media Player. If no app plays it, the file itself might be corrupt – grab a fresh copy.

Fix 1: Install a Codec Pack (Most Likely Fix)

  1. Download the K-Lite Codec Pack from the official site (codecguide.com). Go with the Standard or Full pack – don't bother with Basic, it's too thin.
  2. Run the installer. When asked, choose "Lots of stuff" or "Advanced" mode so you get all the codecs.
  3. After install, restart Windows Media Player and try again.

This works 90% of the time because K-Lite includes decoders for HEVC, VP9, and a bunch of other formats that Windows doesn't support out of the box. The downside? It can be a bit bloated, but it's reliable.

Fix 2: Use VLC or Another Player

Honestly, this might be the smarter long-term move. VLC Media Player (videolan.org) bundles every codec you'll ever need, so you won't hit this error again. It's free, open-source, and updates regularly.

If you're stuck with Windows Media Player for some reason (like a work requirement), skip this. But if you just want the file to play, VLC is your friend.

Fix 3: Enable the Windows Media Player Feature (if it's disabled)

On some Windows setups, WMP isn't fully enabled. Here's how to check:

  1. Open Control Panel > Programs > Turn Windows features on or off.
  2. Scroll down to "Media Features" and make sure "Windows Media Player" is checked.
  3. If not, check it, click OK, and restart.

This is a long shot, but I've seen it fix the error on machines where WMP was half-installed.

Fix 4: Re-register the Windows Media Player DLLs

This one's for the brave. Run Command Prompt as Administrator and type:

regsvr32 wmp.dll
regsvr32 wmploc.dll
regsvr32 wmpdxm.dll

Restart and try again. This repairs broken registry entries that can cause the property error. It's a quick shot, but worth a try if the codec pack didn't help.

Fix 5: Check for HEVC Extensions (Windows 10/11)

If the file is HEVC (H.265), Windows might need the official extension. You can buy it from the Microsoft Store for a dollar, but there's a workaround:

  1. Open Settings > Apps > Optional features.
  2. Click "Add a feature" and look for "Media Feature Pack."
  3. If it's not there, you might need to install the HEVC codec from a trusted source. Note: there's a free version from the manufacturer's site, but be careful about third-party downloads.

Honestly, I'd rather suggest using VLC than messing with the Store, but this is the official route.

Why This Error Happens (The Real Story)

When you play a video, the player reads the file's properties – things like resolution, frame rate, and codec ID. If the player doesn't recognize a property value, it throws this error. It's not a problem with your system, just a mismatch between the file's metadata and what Windows Media Player understands.

I've seen this with files from security cameras, dashcams, and some web downloads. The codec isn't weird, just unsupported by WMP. Also, if the file has a corrupted header, this error can show up even with common codecs.

Prevention: Stop This From Happening Again

The best prevention is to use a modern player that handles everything. VLC or MPC-HC both do. If you must use Windows Media Player, keep the K-Lite codec pack updated – they release new versions when new codecs appear.

Also, if you're ripping or converting videos, stick to standard formats like MP4 with H.264. That's the most compatible combo, and you'll avoid this headache.

When This Fix Doesn't Work

If you've tried all this and still get the error, the file is likely corrupt. Try downloading it again, or re-encode it with HandBrake to a standard format. I've never seen this error persist after a proper re-encode.

One more thing: if you're on a corporate machine with locked-down settings, you might not be able to install codec packs. In that case, use a portable player like VLC from a USB stick – no admin rights needed.

That's it. You're not stuck with this error – it's a codec game, and now you know the rules.

Related Errors in Windows Errors
0X00000FDF PEERDIST Error 0X00000FDF: Invalid Config Fix 0XC00D1B9C Fix NS_E_LANGUAGE_MISMATCH 0XC00D1B9C in Windows Media Center 0XC0000702 Fix ALPC Error 0XC0000702: Invalid Message on Windows 10/11 0X800F0244 SPAPI_E_SIGNATURE_OSATTRIBUTE_MISMATCH (0x800F0244) – Driver Won't Install? Here's Why

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.