Quick Answer
Run regsvr32 mf.dll and regsvr32 mfplat.dll as admin, then restart. If that doesn't stick, reinstall your media codec pack (I use K-Lite Standard). Had a client last month whose whole surveillance system threw this after a Windows update.
The error NS_E_WMR_SAMPLEPROPERTYNOTSET (0XC00D1062) pops up when Windows Media Foundation tries to process a sample—could be video, could be audio—but that sample doesn't carry a property the pipeline expects. Think of it like a shipping box with no address label. The media framework needs certain metadata (timestamps, format info) and if it's missing, it chokes. Most people hit this in media players, but I've also seen it in video editing apps, security camera software, and even some games that stream video. The root cause is almost always a corrupted or outdated Media Foundation component, a bad codec pack, or a driver that's not playing nice with Windows' media stack.
Fix Steps (In Order)
1. Reset Media Foundation Components
Open Command Prompt as Administrator. Run these one at a time:
regsvr32 mf.dll
regsvr32 mfplat.dll
regsvr32 mfreadwrite.dll
regsvr32 wmnetmgr.dll
regsvr32 wmvcore.dll
Restart your machine. This re-registers the core DLLs. Fixes it about 60% of the time. If you get a DllRegisterServer error on any of them, something's genuinely broken—move to step 2.
2. Reinstall or Repair Your Codec Pack
If you've got a codec pack installed (like K-Lite, Shark007, or CCCP), uninstall it first, then install the latest version from the official site. K-Lite Standard is my go-to. If you don't have a codec pack, don't install one yet—try the next step first. Codec packs are often the culprit because they override system codecs.
3. Run the Windows Media Player Troubleshooter
This sounds basic, but it actually fixes Media Foundation registration issues. Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Media Player. Run it, let it apply fixes, reboot.
4. System File Checker + DISM
Corrupted system files can mess up Media Foundation. In an admin Command Prompt:
sfc /scannow
Wait for it to finish. Then:
DISM /Online /Cleanup-Image /RestoreHealth
Reboot after. This fixed it for a client whose Windows 11 machine started throwing this after a bad cumulative update.
Alternative Fixes If the Main One Fails
5. Reinstall Your Graphics Driver
Use DDU (Display Driver Uninstaller) in Safe Mode to remove your current driver, then install the latest from your GPU vendor's site. Don't use Windows Update for drivers. I've seen Nvidia and Intel drivers both cause this when they ship with broken media shaders.
6. Disable Third-Party Codec Packs Completely
Uninstall all third-party codec packs and rely on the Windows built-in codecs. Then test. If the error goes away, you know it's a codec conflict. You can then reinstall one pack at a time to find the offender. Skip this if you need a specific codec for something like MKV playback—get VLC or MPC-HC instead, they don't touch system codecs.
7. System Restore or Repair Install
If nothing else works and this error only started recently, do a System Restore to a point before the problem. Or do an in-place repair install using the Windows Media Creation Tool—that replaces all system files without losing your apps or data. This is nuclear but it works if Media Foundation itself is borked.
Prevention Tips
- Keep Windows updated. Media Foundation gets patched in cumulative updates. Don't skip them.
- Stick to one codec pack. Having multiple pack installs is asking for registry conflicts.
- Run Windows Media Player troubleshooter every few months. It catches registration drift.
- Don't install codec packs on Windows 10/11 unless you absolutely need them. The built-in Media Foundation handles most modern video formats. For everything else, use VLC.
- Back up your registry before any codec install. Quick and saves headaches.
Real talk: I've fixed this error on about a dozen machines over the years, and in every case it came down to either a botched codec pack or a Windows update that nuked Media Foundation DLL registrations. The regsvr32 fix alone handles most of them. If you're working on a server running media-related software (like a security DVR), always test updates in a staging environment first.