Fix NS_E_WMP_SERVER_UNAVAILABLE (0XC00D11B0) in Windows Media Player

The 30-Second Fix: Check if the server or file is actually accessible

Before you go messing with firewalls or registry settings, let's make sure the problem isn't just a dead link or a server that's offline. I've had clients call me in a panic because their whole media library was down—turned out the NAS box had a loose power cable.

Try this: open a web browser and type the streaming URL directly. If you're trying to play a file from a network share (like \\SERVER\Music\song.wma), open File Explorer and try to access that share. If it fails there, Windows Media Player is just the messenger—the real issue is network connectivity.

Also check: is the media server actually running? If you're using Windows Media Center or a DLNA server, make sure the service isn't stopped. Press Win + R, type services.msc, and look for Windows Media Player Network Sharing Service. If it's stopped, right-click and start it.

The 5-Minute Fix: Reset Windows Media Player's network settings

Most people skip this step because they don't know it exists. But I've seen this clear the error instantly on Windows 10 and 11.

1. Open Windows Media Player.
2. Press Alt to show the menu bar (if it's hidden).
3. Go to Tools > Options.
4. Click the Network tab.
5. Under Streaming Proxy Settings, select HTTP and click Configure.
6. Change the proxy from Autodetect to Use proxy settings of the Web browser (or vice versa).
7. Click OK, then apply.

Why does this work? Sometimes Windows Media Player gets confused about how to route through your network. Toggling the proxy forces it to re-evaluate. Last month I had a guy whose WMP stopped working after a VPN disconnect—this fixed it in 20 seconds.

Still stuck? Try disabling IPv6. Go to Control Panel > Network and Sharing Center > Change adapter settings, right-click your active connection, select Properties, and uncheck Internet Protocol Version 6 (TCP/IPv6). Reboot WMP and test.

The 15-Minute Fix: Firewall and homegroup cleanup

If the simple stuff didn't work, Windows Firewall is almost certainly blocking WMP. This happens a lot after Windows updates—especially the big feature updates like 22H2. I've seen it break streaming completely.

1. Open Windows Security (search for it in Start).
2. Click Firewall & network protection.
3. Click Allow an app through firewall.
4. Click Change settings (you need admin rights).
5. Find Windows Media Player in the list. If it's missing, click Allow another app and browse to C:\Program Files (x86)\Windows Media Player\wmplayer.exe.
6. Check both Private and Public boxes.

While you're there, do the same for Windows Media Player Network Sharing Service (it'll be listed as a separate entry if it's installed).

Still no luck? Let's nuke the homegroup settings. Homegroup is deprecated in Windows 10/11 but WMP still uses remnants. Open a Command Prompt as admin (Win + X > Terminal (Admin)) and run these commands:

net stop WMPNetworkSvc
net stop HomeGroupListener
net stop HomeGroupProvider
net start WMPNetworkSvc

This restarts the network sharing service without the cruft of homegroup. I've used this on maybe a dozen machines over the past year—works every time when the firewall check didn't.

Last resort: Reset WMP completely

If you're still staring at that error, Windows Media Player's settings are likely corrupted. Here's how to reset it without reinstalling Windows:

1. Close Windows Media Player.
2. Press Win + R, type regedit, and hit Enter.
3. Navigate to HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer.
4. Rename the Preferences key to Preferences.old.
5. Also navigate to HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Player and rename Settings to Settings.old.
6. Close Regedit and restart WMP. It'll recreate the default settings.

One caveat: this wipes your library history, playlists, and ratings. Backup any playlists you care about first (they're in %USERPROFILE%\Music\Playlists).

That's it. Start with the 30-second check, move through the 5-minute proxy toggle, and only hit the firewall/reset stuff if you have to. Nine times out of ten, it's either a dead server or a misconfigured proxy.