0XC00D0010

NS_E_ALREADY_CONNECTED (0xC00D0010) – Network Already Connected

Network & Connectivity Beginner 👁 9 views 📅 Jun 20, 2026

Your machine thinks it's already connected to a network when it's not. The fix clears the stale connection cache – takes about 2 minutes.

Quick answer: Run netsh int ip reset and netsh winsock reset in an admin command prompt, then restart. That clears the stuck connection record.

Why This Happens

This error usually shows up in Windows Media Player or something that uses streaming. It means the OS thinks there's already a network connection active, but there isn't one. The real trigger? A half-broken VPN disconnect, a sudden power loss, or a network cable yanked out while a stream was running. I had a client last month whose whole media server went dark because their kid pulled the ethernet cord during a movie. The OS never got the “disconnect” message, so it refused new connections.

It's not a hardware problem. Your Wi-Fi or ethernet works fine for everything else – web browsing, email, file sharing. But the streaming app checks for a clean connection state, and it sees a stale one.

Main Fix – Clear the Stale Connection Cache

This is the only fix that works 9 out of 10 times. Don't waste time reinstalling drivers or messing with firewalls.

  1. Open Command Prompt as administrator. Press Windows key, type “cmd”, right-click it, pick “Run as administrator”.
  2. Run this command to reset Winsock (the Windows socket API – it's what manages network connections):
    netsh winsock reset
  3. Run this command to reset the IP stack:
    netsh int ip reset
  4. Reboot your machine.

After the restart, try the streaming app again. In most cases, the error is gone. The reset commands clear that phantom connection record. It's the same fix for the “Network connection already exists” error in older Windows versions – it's been around since Windows 7.

If That Doesn't Work – Release and Renew IP

Sometimes the IP address itself is stuck. Do this:

  1. Open admin Command Prompt again.
  2. Type ipconfig /release and press Enter.
  3. Then ipconfig /renew and press Enter.
  4. Then ipconfig /flushdns and press Enter.
  5. Reboot.

Still Stuck? Disable and Re-enable Your Network Adapter

If netsh didn't help, the adapter might be in a weird state. Quick fix:

  1. Go to Control Panel > Network and Sharing Center > Change adapter settings.
  2. Right-click your active connection (Wi-Fi or Ethernet) and pick Disable.
  3. Wait 10 seconds, then right-click again and pick Enable.
  4. Restart your streaming app.

Alternative Fixes – Rare but Worth Knowing

Check for Conflicting VPN or Proxy Software

I've seen this error pop up when a VPN client crashes and leaves a virtual adapter in a connected state. Open Device Manager, expand Network adapters, look for any adapters with “VPN” or “TAP” in the name. Right-click and disable them. Reboot and test.

Reset Windows Media Player (if that's your app)

  1. Close Media Player.
  2. Press Windows key + R, type regedit, press Enter.
  3. Go to HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Player.
  4. Delete the RecentFileList key (right-click > Delete).
  5. Restart Media Player.

Prevention Tip – Shut Down Cleanly

This error is mostly about dirty disconnects. Before you power off or yank a cable, close any streaming apps first. If you use a VPN, disconnect it properly – don't just close the window. And if you lose power, run the netsh commands after the machine boots up. It takes 30 seconds and saves you the headache.

“Had a client who kept getting this error every Monday morning. Turned out their kid was shutting down the PC by holding the power button. Once they learned to shut down properly, the error never came back.”

If you've tried everything here and still see the error, check if your router is assigning duplicate IPs – but that's really rare. 99% of the time, the netsh reset does the job.

Was this solution helpful?