NS_E_WMPCORE_COCREATEFAILEDFORGITOBJECT (0XC00D107D) Fix

Cause 1: Corrupt COM Registration for atmlib.dll and actxprxy.dll

This is the most common trigger. The error 0XC00D107D shows up right when you launch Windows Media Player (any version on Windows 10 20H2 through 22H2, and Windows 11 21H2). You click the icon, the player window appears for half a second, then you get the error. The system can't create the Global Interface Table because two critical COM DLLs aren't registered properly.

I've seen this happen after a Windows Update that partially mangles the COM Infrastructure, specifically KB5006670 on Windows 10. Skip any registry cleaners or SFC scans for this — they won't touch COM registration.

How to fix it

1. Press Windows Key + X and choose Windows Terminal (Admin). Click Yes on the UAC prompt.
2. In the terminal, run this command exactly:
   

   regsvr32 atmlib.dll

   You should see a popup: "DllRegisterServer in atmlib.dll succeeded."
3. Now run:
   

   regsvr32 actxprxy.dll

   You'll see the same success message.
4. Close the terminal and restart your PC.
5. Launch Windows Media Player. The error should be gone.

Why this works: atmlib.dll handles Active Template Library (ATL) security, and actxprxy.dll manages proxy/stub for COM objects. Re-registering them rebuilds the entries in the registry under HKEY_CLASSES_ROOT\CLSID. The Global Interface Table depends on these being present.

Cause 2: Corrupt Windows Media Player User Profile or Settings

The second most common scenario: you've had WMP crash before, or you migrated a user profile from an older Windows version. The player stores its configuration in %LOCALAPPDATA%\Microsoft\Media Player. If that folder is damaged — like a half-written XML file from a crash — the GIT creation fails.

This fix is non-destructive. You won't lose your media library, but you will lose custom playlists and equalizer presets. If you have important playlists, back up the folder first.

How to fix it

1. Close Windows Media Player completely. Check Task Manager to be sure — sometimes WMP runs in the background.
2. Press Windows Key + R, type %LOCALAPPDATA%\Microsoft\Media Player, and hit Enter.
3. Select everything inside that folder. Press Ctrl + A to select all.
4. Press the Delete key. Confirm if asked.
5. Restart your PC.
6. Open Windows Media Player. It'll rebuild the folder fresh.

What to expect: First launch after this fix might take 10-15 seconds longer than usual. That's the player recreating the default settings. After that, it'll fire up normally.

Pro tip: If you can't delete those files because they're in use, open Task Manager (Ctrl+Shift+Esc), find any "Windows Media Player" or "wmplayer.exe" process, right-click and End task. Then try again.

Cause 3: Component Services (COM+) Application Pool Corrupted

This one's rare but nasty. The COM+ infrastructure itself gets corrupted — usually from a failed .NET Framework update or a repair install gone wrong. The error still says NS_E_WMPCORE_COCREATEFAILEDFORGITOBJECT, but re-registering DLLs won't help. You'll know this is the case if you've already tried Cause 1 and Cause 2, and the error persists.

How to fix it

1. Press Windows Key + R, type dcomcnfg, and hit Enter. This opens Component Services.
2. In the left pane, expand Component Services > Computers > My Computer > COM+ Applications.
3. Look in the list for .NET Utilities or System Application. Right-click each one and choose Shut down. (If they're already stopped, skip.)
4. Close Component Services.
5. Open an elevated Command Prompt (admin).
6. Run these commands one at a time:
   

   net stop comsysapp

   net start comsysapp

7. Now reboot.

Alternative if that doesn't work: Run the System File Checker:

1. Open Command Prompt as admin.
2. Type sfc /scannow and press Enter.
3. Let it finish — takes 10-20 minutes. It'll repair any corrupted system files, including COM+ components.

I've only needed this fix on three machines in 12 years, but when it works, it's a lifesaver.

Quick-reference summary table