Fix NS_E_MAX_CLIENTS (0XC00D0049) Client Limit Error

What Triggers NS_E_MAX_CLIENTS

You're streaming a video or listening to music—maybe a radio station through Windows Media Player, maybe a security camera feed through an old app—and suddenly it stops. You get NS_E_MAX_CLIENTS (0XC00D0049): "Cannot exceed the maximum client limit." This means the server or service you're connecting to says, "Too many connections from your IP or client ID."

I saw this last month with a small office that had four people streaming the same internet radio station through WMP. One by one, they'd get the error after the third person connected. The radio server wasn't the problem—Windows Media Player's own streaming client was.

This error also pops up with Windows Media Center, some VPN apps that wrap around WMP, and even old-school RDP sessions that redirect audio. The core issue: Windows has a hidden limit on how many simultaneous streaming connections a single client can make. Hit that limit, and you get this error.

Quick Fix: Restart Everything (30 seconds)

Before you tear your hair out, do this:

1. Close all media players—Windows Media Player, VLC, any app using the same streaming source.
2. Restart your computer. Not just sleep/wake—full restart.
3. Try again. Open one media stream at a time. If it works, you had a stale connection hanging around.

This clears out orphaned sessions. I've seen cases where a media app crashed but left the streaming socket open, eating up a client slot. Reboot flushes those.

Moderate Fix: Registry Tweak (5 minutes)

If rebooting helps but the error comes back when you open multiple streams, you need to increase the client limit in the registry.

Warning: Messing up the registry can break things. Back it up first. Run regedit and export the key before editing.

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

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\MediaPlayer\Configuration

3. Right-click the Configuration folder, select New > DWORD (32-bit) Value.
4. Name it MaxClients.
5. Double-click MaxClients, set Base to Decimal, and enter a value. Start with 10 (default is hidden at 3 or 5 depending on Windows version).
6. Click OK, close regedit, restart your PC.

That value controls how many simultaneous streaming connections Windows Media Player will allow. I set it to 20 for that office. No more errors.

If you don't see the Configuration key, create it: right-click MediaPlayer, select New > Key, name it Configuration, then add the DWORD.

Advanced Fix: Reset Windows Media Player (15+ minutes)

The registry tweak didn't stick? Or you're still getting the error even with a high MaxClients value? Something deeper is corrupted. Reset WMP fully.

1. Close WMP completely. Check Task Manager for any wmplayer.exe processes and kill them.
2. Open Control Panel > Programs and Features > Turn Windows features on or off.
3. Uncheck Media Features (this includes Windows Media Player).
4. Click OK and restart your PC.
5. After restart, go back to Turn Windows features on or off and re-check Media Features.
6. Restart again. Windows will reinstall WMP from scratch.

This clears out all corrupted DLLs, registry entries, and cached data. It's nuclear but works when nothing else does.

Pro tip: If you're running Windows 10 or 11 N editions, Media Features might be missing entirely. You'll need to install the Media Feature Pack from Microsoft's website separately. Without it, WMP won't work at all.

Still stuck? Check your network

Sometimes the error isn't on your PC. If you're streaming from a server (like an HTTP radio stream or a DLNA server on your network), that server might cap connections. For example:

• IIS web server limits concurrent connections per IP.
• Windows Media Services has its own client limit setting.
• Home routers can also limit connection counts per device.

Log into your router, check the Advanced > Security or DHCP settings, and see if there's a connection limit per IP. If you're the server admin, bump that limit up or remove it.

One more thing: Check for malware

I've seen a case where malware was using WMP's streaming engine to phone home, eating up client slots. Run Malwarebytes or Windows Defender full scan. If you find something, clean it, then redo the registry tweak above.

That's it. Start with the reboot, move to the registry, and only nuke WMP if you have to. Most people stop at step 2 and never see the error again.