Fix 0XC00D107E Windows Media Player Error

What's actually happening here

Windows Media Player (WMP) tries to create a playback graph — a chain of filters that decode and render audio or video. The error 0XC00D107E means WMP failed to get the marshaled graph event handler interface. In plain English: WMP can't hook up its internal event system to the DirectShow graph. The graph starts building, then falls apart because something blocks or breaks the connection between WMP's UI and the rendering engine.

You'll see this error when opening an audio file (MP3, WMA) or a video file (WMV, AVI). It's not specific to one file type — it's a system-side failure. Common triggers: a third-party codec pack that registers a corrupt filter, a broken WMP plugin, or a permissions problem in the user profile.

We'll fix this in three passes. Start with the 30-second fix. If that doesn't work, move to the 5-minute fix. Only the third one takes serious elbow grease.

The 30-second fix: reset WMP's internal state

Open Windows Media Player. Press Ctrl+M to show the classic menu bar (if it's hidden). Go to Tools > Options. Click the Player tab. Under Automatic updates, find Reset the Player — click it. Confirm the dialog box that warns you this will reset your library, playlists, and settings.

Why this works: WMP stores its filter graph registration in a private database. A corrupt entry there prevents the marshaled event handler from being created. Resetting the player nukes that database and rebuilds it from scratch. Takes about 10 seconds. If the error is gone, stop here.

If the error persists, close WMP and try the next fix.

The 5-minute fix: disable third-party codecs and plugins

Third-party codec packs — K-Lite, CCCP, Shark007 — register DirectShow filters that hook into WMP's graph. One of them is probably the culprit. The error code points to a marshaling problem, which specifically happens when a filter tries to communicate across threads or processes, and it fails because the filter is poorly written or conflicts with another filter.

Open WMP. Press Ctrl+M for the menu bar. Go to Tools > Options. Click the Plug-ins tab. Look at the list under Category — check Background, Visualizations, and Other. Disable any non-Microsoft plugin by unchecking it. Don't delete it, just disable it.

Now test playback. If it works, re-enable plugins one by one to find the bad one. If it doesn't, we need to go after codec packs.

Open a Command Prompt as Administrator (right-click Start > Command Prompt (Admin) or Terminal (Admin)). Run these two commands to re-register WMP's core DLLs — this forces Windows to rebuild the filter graph with default Microsoft filters:

regsvr32 wmp.dll
regsvr32 wmpeffects.dll

Restart WMP and test.

The 15+ minute fix: nuke the DirectShow filter registry

If the first two fixes didn't work, we're dealing with a deeply corrupted filter registration. The marshaling interface failure can be caused by a filter that registers itself in the wrong COM apartment model (e.g., an Apartment-threaded filter registered where Free-threaded is required). This is common with old codec packs that weren't updated for Windows 10 or 11.

We'll delete the filter cache and force DirectShow to rebuild it. This won't break anything — Windows will recreate the entries on next boot.

Open Regedit as Administrator. Navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Media\Setup

Delete the value named PluginCache. Don't delete the whole key — just that value.

Now navigate to:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\MediaPlayer\Preferences

Delete the value named PluginCache if it exists.

Restart your computer. WMP will rebuild the filter cache from the registered codecs on next launch. This bypasses the corrupted marshaling data.

If the error still shows up, we go nuclear — remove all non-Microsoft codec packs. Uninstall any codec pack from Settings > Apps > Installed apps. Reboot. Test WMP. Then re-install only what you need, one at a time, testing after each. I've seen K-Lite's ffdshow filter cause this exact error on Windows 10 22H2.

One last thing: check your user profile

If none of the above works, the issue might be in your user profile itself. Create a new local user account (Settings > Accounts > Family & other users > Add someone else). Log into that account, open WMP, and test a file. If it works, your original profile has a corrupted registry hive that WMP can't read. You can migrate your data to the new profile or use Microsoft's User Profile Service cleanup tool (rundll32 sysdm.cpl,UserProfiles — advanced, not for the faint of heart).

The root cause in this case is typically a permissions problem — the marshaled event handler requires COM interface marshaling between the WMP process and the DirectShow graph. If your user profile's COM permissions are borked, the marshaling fails silently, and you get this error.

Fix the profile, fix the issue.