Fix STATUS_REMOTE_DISCONNECT (0XC000013C) – Virtual Circuit Closed Error

You're in the middle of a Remote Desktop session or an SMB file transfer when—bam—the connection drops. You see the error: STATUS_REMOTE_DISCONNECT (0XC000013C). The message says "The network transport on a remote computer has closed a network connection." I've been there: it's infuriating, especially when you're halfway through a critical task.

This error almost always happens after a few minutes of inactivity. Maybe you walked away for coffee, or the remote computer went to sleep. It can also pop up when a corporate firewall or VPN kills the session due to an idle timeout. The root cause? The remote machine's network stack—usually the TCP connection—got yanked by power management, network policy, or a misbehaving driver.

What Actually Triggers 0XC000013C

Here are the three most common scenarios I've seen in the trenches:

1. Remote computer sleeps or hibernates – Even if you set it to never sleep in Windows, the network adapter might still power down.
2. Idle timeout on a VPN or firewall – Many corporate VPNs drop idle TCP sessions after 15-30 minutes.
3. Network adapter driver power-saving feature – Windows lets the NIC go to sleep, killing the virtual circuit.

Fix It in 5 Steps

Skip the generic advice—these steps work. I've used them on Windows 10 (all builds) and Windows 11. Do them in order.

Step 1: Disable Network Adapter Power Saving

This is the #1 culprit. Windows loves to turn off your NIC to save a few cents of electricity, but it breaks persistent connections.

1. Open Device Manager (right-click Start > Device Manager).
2. Expand Network adapters.
3. Right-click your active NIC (usually Intel, Realtek, or Qualcomm) > Properties.
4. Go to the Power Management tab.
5. Uncheck Allow the computer to turn off this device to save power.
6. Click OK. Reboot.

Step 2: Prevent the Remote Computer from Sleeping

Even if you set the power plan to "High Performance," Windows Update can reset it. Lock it down.

1. Open Command Prompt as admin.
2. Run: powercfg /change standby-timeout-ac 0 and powercfg /change hibernate-timeout-ac 0.
3. Also run: powercfg /h off to disable hibernation entirely.

Step 3: Increase or Disable Idle Timeout for RDP

If you're using Remote Desktop, the server might kick you after inactivity. This is a server-side setting.

1. On the remote machine, open gpedit.msc (Group Policy Editor).
2. Go to: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits.
3. Enable Set time limit for active but idle Remote Desktop Services sessions and set it to Never.
4. Also enable End session when time limits are reached and set it to Disabled.

If you don't have gpedit (Windows Home), use PowerShell as admin: Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services' -Name 'MaxIdleTime' -Value 0.

Step 4: Disable TCP Chimney Offload (If You're Stuck)

This is an advanced NIC feature that sometimes causes this exact error. I've seen it on older Intel NICs.

1. Open Command Prompt as admin.
2. Run: netsh int tcp set global chimney=disabled.
3. Reboot.

Step 5: Check VPN or Firewall Idle Timeouts

For corporate VPNs (like Cisco AnyConnect, Palo Alto GlobalProtect), the admin might have set a session timeout. You can't always bypass it, but you can work around it:

• Use a keepalive tool like ping -t [remote IP] in a background command prompt. This sends a packet every second, tricking the firewall into keeping the circuit alive.
• Or set up a scheduled task that runs a short PowerShell script every 5 minutes to maintain the session.

What If It Still Fails?

Rarely, the issue is a bad network driver. Check the manufacturer's site for an updated driver for your exact NIC model. If you're on Windows 11 22H2, there's a known bug with Realtek PCIe GbE controllers—roll back to an older driver from 2021.

One more thing: check the remote computer's Event Viewer under System logs for source Tcpip or Ntfs. If you see event ID 4226, that's a TCP/IP connection limit being hit. But that's rare after Windows 10 version 2004. For 99% of cases, steps 1-3 will fix it.

You got this.