0XC00D105A

Fix NS_E_WMR_PINNOTFOUND (0XC00D105A) on Windows 10/11

Windows Errors Intermediate 👁 0 views 📅 May 26, 2026

This DirectShow error means you tried to connect a filter pin that doesn't exist. Almost always a codec or filter graph problem. Here's the real fix.

1. Third-party codec packs are the real culprit (most common fix)

This error almost always pops up because you've got a codec pack like K-Lite, CCCP, or a random DirectShow filter that's messed with the default filter graph. The system tries to connect a pin — like an input pin on the Windows Media Renderer — and it can't find it because a third-party filter hijacked the connection.

Here's how I've fixed this hundreds of times:

  1. Open Control Panel (press Win + R, type control, hit Enter).
  2. Go to Programs and Features (or Add or Remove Programs on Windows 11).
  3. Look for K-Lite Codec Pack, CCCP, LAV Filters, ffdshow, or any other codec pack. Select it, then click Uninstall.
  4. Reboot your PC — don't skip this step. After the restart, test your playback. If the error's gone, we're done.

If you absolutely need a codec pack (for example, you play MKV files with weird audio tracks), install the latest LAV Filters instead — but only after uninstalling the old pack. LAV is cleaner and rarely breaks the filter graph.

After uninstalling and rebooting, you should be able to play the file without seeing the error. If not, move to the next fix.

2. The DirectShow filter graph is corrupted — reset it with regsvr32

Sometimes the problem isn't a codec pack, but a corrupted system filter. The Windows Media Renderer or another built-in filter gets unregistered or damaged. You can re-register the key DLLs without reinstalling anything.

  1. Press Win + X and select Terminal (Admin) or Command Prompt (Admin).
  2. Run these commands one by one, pressing Enter after each. You'll see a success message after each one if they're working:
    regsvr32 quartz.dll
    regsvr32 wmp.dll
    regsvr32 msdxm.ocx
    regsvr32 dx8vb.dll
  3. If you get a failure on any of these — like a missing DLL error — that's a sign of a deeper system file corruption. Skip down to the third fix in that case.
  4. After all four register successfully, close the terminal and try your playback again.

What you should see: a popup after each regsvr32 command that says DllRegisterServer succeeded. If you get anything else (like an access denied), you didn't run as admin. Right-click the terminal and pick Run as administrator.

This fix covers the most common missing pin scenario — the quartz.dll file handles the DirectShow filter graph manager. If it's unregistered, the graph can't find its own pins.

3. Corrupted system files or missing DirectX components

Less common, but when the first two fixes fail, you're dealing with a damaged Windows installation. This can happen after a bad update or a virus cleanup that deleted system files.

  1. Open Terminal (Admin) again.
  2. Run the System File Checker first:
    sfc /scannow
    This takes 10-15 minutes. Let it finish completely. If it finds corrupt files, it'll try to repair them automatically.
  3. After SFC completes, run the Deployment Image Servicing and Management tool:
    DISM /Online /Cleanup-Image /RestoreHealth
    This also takes time — maybe 20 minutes. Don't close the window.
  4. Reboot after both finish.
  5. If the error still shows up, download and run the DirectX End-User Runtime Web Installer from Microsoft's site. It's a small installer that fills in any missing DirectX 9.0c components (yes, even on Windows 11).

I've seen this error on a Dell laptop that had a botched Windows 10 update. After SFC and DISM, the DirectShow graph worked perfectly again. It's rare, but when you need it, you need it.

Quick-reference summary table

Cause Fix Time to try
Third-party codec pack broke the graph Uninstall the codec pack, reboot 5 minutes
Corrupted DirectShow filter registrations Run regsvr32 commands for quartz.dll and wmp.dll 2 minutes
System file or DirectX corruption Run SFC + DISM, then reinstall DirectX runtime 30-40 minutes

Was this solution helpful?