NS_E_TRANSFORM_PLUGIN_INVALID (0XC00D1BE6) Fix

Cause 1: Broken codec pack or third-party filter

What's actually happening here is Windows Media Player or another app is trying to instantiate a Media Foundation Transform (MFT) or DirectShow filter, but the registered plugin DLL points to a missing, corrupted, or incompatible file. This almost always happens after installing or uninstalling a codec pack like K-Lite, CCCP, or Shark007. The pack registers a transform, then later an update or uninstall leaves the registry entry orphaned.

You'll see this error when playing a specific video file — maybe an MKV with HEVC or an AVI with an odd codec. The app can't decode the stream, throws 0xC00D1BE6, and quits.

Fix: Uninstall all codec packs, then reinstall one

1. Open Programs and Features (appwiz.cpl). Uninstall every codec pack you find: K-Lite, CCCP, Shark007, VLC codecs, ffdshow, LAV Filters, etc. Don't skip any — partial cleanup is the reason this fails.
2. Reboot. This clears the DirectShow and MFT caches.
3. Download and install only one pack — I recommend K-Lite Mega Codec Pack. During install, select "Lots of stuff" mode and check "Reset all settings to recommended defaults". Do not install multiple packs — they fight over MFT registration.
4. Test your video again in Windows Media Player. If it works, you're done. If not, proceed to Cause 2.

Why step 3 works: K-Lite's installer replaces corrupted MFT entries with known-good CLSIDs and re-registers all DLLs via regsvr32. The reset wipes out any stale filter merit values that could cause conflicts.

Cause 2: Corrupted Media Foundation store

Windows 10 and 11 keep a local database of MFTs — it's a set of registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MediaFoundation. If a system update or disk error corrupts those keys, any app relying on Media Foundation (including Edge, Photos, and WMP) will fail with NS_E_TRANSFORM_PLUGIN_INVALID. This cause is less common than a codec pack, but harder to spot because there's no obvious third-party software to blame.

You'll see the error on many file types, not just one. Or it fails in multiple apps (WMP and the Movies & TV app).

Fix: Reset Media Foundation via DISM

1. Open Command Prompt as Administrator. Do not use PowerShell for this — DISM has different default flags there.
2. Run these commands in order. Each may take a few minutes:
   

   dism /online /cleanup-image /restorehealth
   sfc /scannow

3. After SFC finishes, reboot. Then run:
   

   reg delete "HKLM\SOFTWARE\Microsoft\MediaFoundation" /f
   regsvr32 /s mf.dll
   regsvr32 /s mfplat.dll
   regsvr32 /s mfreadwrite.dll

4. Reboot again. The Media Foundation store is rebuilt from the Component Store during boot.

Why DISM first: If the Component Store itself is broken, rebuilding the Media Foundation registry from corrupted source files won't help. The restorehealth command pulls fresh copies from Windows Update. Skipping this step is why many guides fail.

Cause 3: Missing system runtime (VC++ redistributable)

Some Media Foundation transforms are actually DLLs compiled against Visual C++ runtimes. If you're missing a specific VC++ redistributable (2015-2022 is the common one), the MFT will fail to load, and the error code points to the plugin being "invalid" — but it's actually just the runtime not being there. This catches people who use codec packs because the pack installer often skips runtime checks.

You'll see this on a fresh Windows install or after running a system cleaner that removed old redistributables (looking at you, CCleaner).

Fix: Install all VC++ runtimes

1. Download the latest Visual C++ 2015-2022 Redistributable (x64) and the x86 version. Install both — even on a 64-bit OS, some MFTs are 32-bit.
2. Reboot. Test playback.
3. If the error persists, also install the Visual C++ 2013 Redistributable — some older filters still reference it.

The ordering matters: 2015-2022 is a unified installer that supersedes 2015, 2017, and 2019, but 2013 is separate. Installing 2013 after the newer one avoids file version downgrades.

Quick-reference summary table

Ninety percent of the time, Cause 1 is your problem. Don't bother reinstalling graphics drivers or running sfc before you've cleaned out codec packs — that's just wasted reboots.