Fix STATUS_VIRTUAL_CIRCUIT_CLOSED (0xC00000D6) Error on Windows 10/11
The STATUS_VIRTUAL_CIRCUIT_CLOSED error pops up when a network connection dies mid-transmission. Here's the fix that works 9 times out of 10.
You're in the middle of something important, and suddenly that error pops up. It's frustrating, I get it. The 0xC00000D6 error means Windows lost a virtual circuit — a persistent TCP connection — before the data finished flowing. The good news: this is almost always fixable from your command line in under five minutes.
What You'll See
You might be copying files, running a database query, or streaming video. The error text reads STATUS_VIRTUAL_CIRCUIT_CLOSED, often accompanied by a message like "An established connection was aborted by the software in your host machine." This happens most often on Windows 10 version 22H2 and Windows 11, especially when using SMB file shares or VPN connections.
The Fix: Reset Your Network Stack
Skip the fancy tools. The real fix is a clean reset of your TCP/IP stack and Winsock catalog. Here's exactly what to do, step by step.
- Open Command Prompt as Administrator. Press the Windows key, type
cmd, then right-click Command Prompt and choose Run as administrator. Click Yes if Windows asks for permission. - Release and renew your IP address. Type this command and press Enter:
After a few seconds, you should see a list of adapters with IPv4 addresses set to 0.0.0.0. That's normal — your computer dropped its current IP lease.ipconfig /release - Renew the IP address. Type:
This might take 10–15 seconds. Wait until you see your IP address restored (for example, 192.168.1.10). If it hangs longer than 30 seconds, press Ctrl+C and try again.ipconfig /renew - Flush the DNS cache. Type:
After this, you'll see "Successfully flushed the DNS Resolver Cache."ipconfig /flushdns - Reset Winsock. Type:
You'll see "Successfully reset the Winsock Catalog. You must restart the computer in order to complete the reset."netsh winsock reset - Reset the TCP/IP stack. Type:
Same message about restarting. That's fine.netsh int ip reset - Restart your computer. Close the Command Prompt and reboot. Don't skip this step — the resets only take effect after a restart.
After the restart, try whatever you were doing before. In most cases, the error is gone.
Why This Works
The 0xC00000D6 error happens because the TCP stack's internal state got corrupted. Maybe a VPN disconnected improperly, or a power surge caused a packet loss cascade. Resetting Winsock clears out any bad socket configurations that are stuck in memory. The IP reset rebuilds the TCP/IP registry settings from scratch. Together, they give your network stack a clean slate.
Think of it like rebooting a router that's half-frozen. You're not replacing hardware — you're just clearing the junk that built up over time.
Less Common Variations
If the reset above doesn't work, try these one at a time.
Disable IPv6 Temporarily
Some older VPNs and network drivers fight with IPv6. Here's how to turn it off:
- Open Control Panel > Network and Sharing Center > Change adapter settings.
- Right-click your active network adapter (likely Ethernet or Wi-Fi) and choose Properties.
- Uncheck Internet Protocol Version 6 (TCP/IPv6).
- Click OK. You don't need to restart — just try the connection again.
If the error stops, leave IPv6 disabled. Most home networks don't use it anyway.
Update Your Network Driver
A bad driver can drop virtual circuits randomly. Go to your adapter manufacturer's site — Realtek, Intel, Qualcomm — and grab the latest driver. Don't rely on Windows Update. Install it, then reboot.
Check for Third-Party Firewall Interference
If you use something like Norton, McAfee, or Comodo, it might be killing idle connections too aggressively. Try disabling the firewall temporarily (just for testing). If the error disappears, adjust the firewall's connection timeout settings.
Prevention Tips
- Don't yank your network cable or disconnect Wi-Fi abruptly. Always disconnect properly through the network icon in the system tray before moving your laptop.
- Keep your network driver updated. Check for updates every couple of months, especially after a major Windows feature update.
- If you use a VPN, make sure it's the latest version. Old VPN clients are a common trigger for this error. Update or switch to WireGuard-based VPNs if you can.
- Run the netsh reset commands every few months as maintenance. It's like defragging your network stack.
That 0xC00000D6 error is annoying but it's not a hardware problem. You can fix it with a few commands and a restart. If it comes back after a month, just run the same steps again. And if it keeps coming back every week, that's a sign your network card might be dying — but that's a rare case.
Was this solution helpful?