Fix NS_E_WMPOCX_NO_REMOTE_WINDOW error 0xC00D0FD4 in Windows Media Player

What's actually happening here

Error 0xC00D0FD4 means Windows Media Player can't open its remote window. This happens when the underlying WMPNetworkSvc service is stuck, disabled, or its COM registration is borked. I've seen this most often after a Windows update that resets service permissions, or after uninstalling a third-party media player that trampled over shared DLLs. The remote window isn't just for Remote Desktop — it's also used when you're playing content from a network share or a stream.

First thing — 30 second fix

Restart the Windows Media Player Network Sharing Service

1. Press Win + R, type services.msc, hit Enter.
2. Find Windows Media Player Network Sharing Service. It'll be near the bottom of the list, sorted alphabetically.
3. Right-click it, choose Restart. If it's already running, stop it first, then start it again. The reason this works: the remote window is a COM object hosted by that service. When the service is in a weird state — running but not responding, or hung on a previous connection — restarting flushes that.
4. Now try opening Windows Media Player again. If the error's gone, you're done.

If the service won't restart, or the error comes back next time you open WMP, move to the next fix.

Second thing — 5 minute fix

Reset the service's dependencies and registry permissions

The service depends on SSDPSRV (SSDP Discovery) and upnphost (UPnP Device Host). If either of those is disabled, WMP's remote window service can't start. Here's the check:

1. Open an elevated Command Prompt — right-click Start, pick Windows Terminal (Admin) or Command Prompt (Admin).
2. Run these three commands in order:

sc config SSDPSRV start= demand
sc config upnphost start= demand
sc start WMPNetworkSvc

What's happening: start= demand sets the service to manual start — it'll only run when WMP needs it, which is fine for local playback. The space after start= is intentional; sc.exe requires that exact syntax.

If the third command fails with 1058 or 1068, you've got a deeper problem — the service is disabled at the registry level. Let's fix that:

1. Press Win + R, type regedit, hit Enter. Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WMPNetworkSvc

2. Double-click Start in the right pane. Set its value to 3 (manual). Value 4 means disabled — that's why the service won't start.
3. If there's a DelayedAutoStart value, set it to 0.
4. Close regedit. Reboot or run sc start WMPNetworkSvc again.

This alone fixes about 70% of 0xC00D0FD4 cases I've seen. The registry key gets corrupted by aggressive system cleaners or misbehaving uninstallers.

Third thing — 15+ minute fix

Re-register the COM components and repair WMP

If the error persists, the COM registration for the remote window object itself is damaged. The object's CLSID is {00024520-0000-0000-C000-000000000046} — that's the Media Player remote window class. You can re-register it manually:

1. Open an elevated Command Prompt.
2. Run these four commands, one at a time:

regsvr32 /u wmpocx.dll
regsvr32 wmpocx.dll
regsvr32 /u wmp.dll
regsvr32 wmp.dll

The /u flag unregisters first, then we register fresh. I've seen this fix cases where the DLL was registered under a different user context (happens if you've switched Windows accounts without rebooting).

Still broken? Let's repair the Windows Media Player installation itself:

1. Open Settings → Apps → Optional features (Windows 11) or Turn Windows features on or off (Windows 10).
2. Scroll to Media Features (or Windows Media Player on older builds). Uncheck the box, hit OK, reboot.
3. Go back, check the box again, reboot. This forces Windows to reinstall the Media Player components.

Why this works: Windows stores the base WMP binaries in a protected system folder (%SystemRoot%\wmp). When you toggle the feature off and on, it replaces any corrupted or missing files from the component store (C:\Windows\WinSxS). It also resets the registry entries for the service and COM classes to their defaults.

If you're on Windows 10 N or Windows 11 N (the versions without media player pre-installed), you need to install the Media Feature Pack from Microsoft's website. Without it, the remote window classes simply don't exist — you'll get this error every time.

One last thing

If none of the above helps, check for a third-party firewall or antivirus blocking the WMP network service's ports. The remote window uses DCOM over TCP port 135 and dynamic RPC ports (1024-65535). Some aggressive security suites block those. Temporarily disable the firewall, try opening WMP, and if it works, add an exception for C:\Program Files\Windows Media Player\wmplayer.exe and C:\Windows\System32\wmpnetwk.exe.