NS_E_PLAYLIST_TOO_MANY_NESTED_PLAYLISTS (0XC00D14BB) Fix

You're trying to stream a live radio feed or a playlist from a server, and Windows Media Player or the streaming service throws error 0XC00D14BB. The message says something about nested playlists exceeding the server's limit. This usually happens when someone—maybe the radio station's tech—created a playlist that references itself, or a chain of playlists that loops back. I've seen this with a client who ran a small online radio station; their m3u file pointed to another m3u that pointed right back to the first one. Infinite loop, instant crash.

What's actually causing this error?

The server has a hard limit on how deep playlist nesting can go. Most streaming servers cap it at 4-5 levels. When a playlist includes another playlist, which includes another, and so on, that's nesting. If one of those playlists references a parent playlist (circular reference), the server sees infinite recursion and kills the connection. This isn't a bug—it's a safety measure to prevent the server from melting down. The root cause is almost always a bad m3u or m3u8 file that has a circular link.

How to fix it

Skip the fluff. Here's what works:

1. Find the playlist file – Look for the .m3u, .m3u8, .asx, or .wpl file you're trying to open. It's often on the server or in your local Downloads folder.
2. Open it in a text editor – Notepad++ or VS Code works. Just not Word. You need to see the raw content.
3. Check for nested playlist references – Look for lines that start with #EXTINF and then point to another playlist file (ends in .m3u, .m3u8, .asx). If you see http://example.com/stream.m3u, that's a nested playlist.
4. Trace the chain – Open each referenced playlist file. If you find a playlist that points back to the first one, you've got a circular reference. Break the loop by removing that line or replacing it with a direct stream URL (like an MP3 or AAC stream).
5. Flatten the structure – The server can handle maybe 3-4 levels. If your chain is longer than that, collapse it. For example, instead of Playlist A → Playlist B → Playlist C → stream, just make Playlist A point directly to the stream.
6. Test locally – Before you put it back on the server, open the fixed playlist in VLC or Windows Media Player on your machine. If it plays without error, you're good.
7. Update the server file – Replace the broken playlist with your fixed version. If it's on a web server, just overwrite the file. If it's inside a streaming service backend (like Icecast or SHOUTcast), you'll need to restart the service after the change.

Still failing? Check these

If the error persists:

• Check the server logs – Look for lines like "playlist recursion detected" or "max depth exceeded." That confirms it's still a nesting issue.
• Verify the stream URL – Make sure the final stream URL (the MP3 or AAC link) is actually alive. If it's dead, the server might keep trying to fallback to a nested playlist. Use a tool like curl -I or VLC to test the URL directly.
• Clear your media player cache – Windows Media Player caches playlist data. Go to Tools → Options → Players → Clear cache. This forces it to re-read the fixed file.
• Try a different player – VLC handles nested playlists more gracefully. If VLC works but WMP doesn't, the problem is WMP's stricter nesting limit. In that case, flatten the playlist to just one level.

Last month I fixed a hospital's streaming system that had this exact error. Someone had built a 7-level deep m3u chain for their overhead music. Two levels too many. I collapsed it to a single direct URL and it's been running smooth since. You'll be fine too.