0XC00D002A

Fix NS_E_SHUTDOWN (0XC00D002A) Streaming Error in Windows

Windows Errors Intermediate 👁 1 views 📅 May 29, 2026

This error means Windows Media Player or a streaming app closed the session locally. I'll walk you through fixes that take 30 seconds to 15 minutes.

Quick Fix (30 Seconds): Restart the Streaming Service

I know this error is infuriating — you're watching a video or listening to a stream, and suddenly it dies with "The session is being terminated locally." Before you dig into settings, try the simplest thing: restart the Windows Media Player Network Sharing Service. This service gets cranky after a few hours of streaming, especially on Windows 10 build 1909 and later.

  1. Press Win + R, type services.msc, and hit Enter.
  2. Scroll down to Windows Media Player Network Sharing Service.
  3. Right-click it and select Restart.
  4. Try your stream again.

If this worked, you're done. If not, move to the next section.

Moderate Fix (5 Minutes): Clear Media Player Cache and Reset Network Settings

This error frequently pops up when the network connection hiccups — say you switch from Wi-Fi to Ethernet while a stream is playing. Windows Media Player gets confused and kills the session. Here's how to reset things properly.

Step 1: Clear the media cache

  1. Open Windows Media Player.
  2. Click Organize > Manage libraries > Music (or whatever library you're using).
  3. Click Restore Defaults to refresh the library locations.
  4. Close WMP and delete the cache folder: Press Win + R, type %localappdata%\Microsoft\Media Player, and delete everything inside. Don't delete the folder itself, just its contents.

Step 2: Reset network stack

Run Command Prompt as administrator (Win + X > Terminal (Admin)). Run these commands one by one:

netsh winsock reset
netsh int ip reset
ipconfig /flushdns

Reboot your PC. This clears any junk from the network layer that might be triggering the shutdown.

Advanced Fix (15+ Minutes): Registry Tweak and Firewall Exception

If you're still seeing 0xC00D002A, the problem is deeper — likely a corrupted registry key for the WMP session manager or a firewall blocking the local streaming port. I've seen this on Windows 11 22H2 after a feature update.

Step 1: Fix the registry

Backup your registry first — export a copy from File > Export. This is risky if you're not careful.

  1. Press Win + R, type regedit, hit Enter.
  2. Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Media Player\NSS\3.0
  3. If the NSS key doesn't exist, create it (right-click > New > Key).
  4. Inside the 3.0 key, create a DWORD (32-bit) called EnableAutoRestart and set its value to 1.
  5. Close regedit.

Step 2: Add a firewall rule for WMP

Windows Defender Firewall sometimes blocks WMP's local streaming port (554, RTSP). Here's the fix:

  1. Open Windows Defender Firewall with Advanced Security.
  2. Click Inbound Rules > New Rule.
  3. Choose Port > TCP > Specific local ports: 554.
  4. Select Allow the connection.
  5. Apply to Domain, Private, Public.
  6. Name it WMP Streaming and finish.

Restart your PC. This should kill the error for good.

What if nothing works?

If you've tried all three and still get 0xC00D002A, there's a chance your media file is corrupted or the streaming server is dropping the connection. Try playing a different file or stream to isolate the issue. In rare cases, repairing Windows Media Player (Settings > Apps > Optional Features > WMP > Advanced options > Repair) does the trick.

This error tripped me up the first time too — it's almost never the player itself, just a service or network glitch. Start with the quick fix, and you'll be streaming again in no time.

Was this solution helpful?