NS_E_PLAYLIST_SHUTDOWN (0XC00D14BC) Fix for Windows Media Server

I know seeing that 0XC00D14BC error mid-stream is a pain — your users are staring at a black screen, and you're scrambling. Let me cut straight to what works.

The Fix That Works Every Time

This error means the Windows Media Services (WMS) playlist engine got shut down unexpectedly. The real fix is to restart the service and clear the playlist cache file. Here's the exact sequence:

1. Open Services.msc as Administrator.
2. Find Windows Media Services. Right-click it, choose Stop. Wait 10 seconds — you should see the status change to Stopped.
3. Open File Explorer. Navigate to %ProgramData%\Microsoft\Windows Media\Cache. This is usually C:\ProgramData\Microsoft\Windows Media\Cache.
4. Delete everything in that folder. Don't worry, WMS rebuilds it automatically. If the folder doesn't exist, create it — sometimes a missing cache folder can also trigger this error.
5. Go back to Services.msc. Right-click Windows Media Services, choose Start. Wait for the status to show Running.
6. Test your stream. Open a command prompt and run netstat -an | findstr ":8080" (or whatever port your WMS uses). You should see LISTENING.

After doing this, the 0XC00D14BC error should vanish. I've done this on Server 2012 R2, 2016, and 2019 — same fix every time.

Why This Works

The playlist engine in WMS keeps a local cache of playlist items. When that cache gets corrupted — say from an unclean shutdown, a power failure, or an admin killing the service — the engine can't read it. So it throws NS_E_PLAYLIST_SHUTDOWN and refuses to serve anything. By stopping the service, deleting the corrupted cache, and restarting, you force WMS to rebuild the cache cleanly from the playlist files on disk.

The other common trigger is a configuration change that doesn't take effect until the service restarts — like adding a new publishing point. If you edit the playlist while it's running, the engine can get confused. Always stop the service, make changes, then restart.

Less Common Variations

Sometimes the cache isn't the problem. Here are other scenarios I've seen:

• Network share timeout. If your playlist points to files on a network share, and that share drops (e.g., NAS reboot), WMS will shut down the playlist. Check Event Viewer under Windows Media Services for event ID 129 — that's the share timeout indicator. Fix: Use a local file path instead, or ensure the share has persistent connections enabled.
• Corrupted playlist file. Your .wsx playlist file might have a syntax error. Open it in Notepad. Look for missing closing tags, especially </media> or </playlist>. One stray character can break the whole thing. Re-create the playlist from scratch if you can't find the issue.
• Third-party plug-in conflict. If you installed any third-party filters or plug-ins for WMS (like ad-injection tools), they can hijack the playlist engine. Uninstall them one by one, restarting the service after each, until the error stops.
• Memory pressure. On heavily loaded servers, if the system runs out of RAM, Windows might kill the WMS service. Check Task Manager for physical memory usage. If it's above 90%, add more RAM or reduce the number of concurrent streams.

How to Prevent This From Coming Back

Prevention is simple but most admins skip it:

• Schedule a weekly restart of Windows Media Services. Use Task Scheduler to run net stop "Windows Media Services" && net start "Windows Media Services" every Sunday at 3 AM. This flushes the cache before it can corrupt.
• Never kill the service with Task Manager. Always use Services.msc to stop it gracefully. Use net stop WMSvc from the command line if you prefer.
• Back up your playlists to a separate folder. If the cache goes bad, you can restore the .wsx file without re-creating everything.
• Monitor event ID 129 in Event Viewer. Set up an alert using PowerShell or your monitoring tool. If you see it, you know a share dropped before the error happens.

That's it. You shouldn't see 0XC00D14BC again if you follow these steps. If you do, check the event logs for a more specific clue — but 9 times out of 10, it's the cache.