Fix 0xC00A000C No Carrier Error on Windows VPN & Remote Desktop

Quick fix (30 seconds): Reboot your modem or router

I know this error is infuriating—especially when you're in the middle of a remote work session and everything just freezes. But before we dig into registry settings or VPN reconfigurations, do this: unplug your modem and router, wait 30 seconds, plug them back in. I've seen this simple step fix 0xC00A000C on Windows 10 and 11 more times than I can count.

Why? Because the error literally says carrier detection failed. Your modem lost its handshake with the ISP. A power cycle forces a fresh negotiation. If you're using a cellular modem (like a 4G/5G hotspot), also check that the SIM card isn't loose and that you have signal bars. No signal? Move the device to a window.

Try reconnecting your VPN or Remote Desktop session. If it works, you're done. If not, move to the next step.

Moderate fix (5 minutes): Restart the VPN service and check your credentials

This error loves to pop up after a Windows update or a sleep/wake cycle. The VPN client might have lost its state. Here's what I do first:

1. Press Win + R, type services.msc, and hit Enter.
2. Find the service named Routing and Remote Access. Right-click it and select Restart.
3. Also restart Remote Access Connection Manager and Telephony.

Now try your connection again. Still no? Then it's often a credential or authentication mismatch. Here's the thing—Windows sometimes caches old domain credentials that confuse the carrier negotiation. Open a Command Prompt as admin and run:

rasdial /disconnect

Then reconnect from the network icon in the taskbar. If you're using a VPN like Cisco AnyConnect or OpenVPN, log out and log back in fresh. I've had cases where a simple password change on the server side caused this error because the client still had the old credentials in memory.

If that doesn't do it, let's move to the deeper stuff.

Advanced fix (15+ minutes): Check PPP settings and disable modem compression

This error is rooted in the Point-to-Point Protocol (PPP). Windows has a setting called LCP extensions that sometimes causes carrier drops on older routers or corporate VPNs. I've seen this on Windows 10 20H2 and later builds.

Here's the fix:

1. Open Control Panel > Network and Sharing Center.
2. Click Change adapter settings on the left.
3. Right-click your VPN or dial-up connection and select Properties.
4. Go to the Networking tab, select Internet Protocol Version 4 (TCP/IPv4), and click Properties.
5. Click Advanced, then go to the IP Settings tab.
6. Uncheck Use default gateway on remote network only if you know you don't need it (sometimes this causes routing conflicts that drop the carrier).
7. Back in the connection Properties, click Configure on the modem or adapter, go to the Advanced tab, and set Compression to Disabled. This is a common trigger—compression negotiation fails and the carrier drops.

Still failing? You might need to edit the registry. This is my go-to when nothing else works:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\Parameters

Create a new DWORD called DisableLcpExtensions and set its value to 1. Reboot. This tells Windows not to use LCP extensions that some old or custom PPP servers don't support.

If you're on a corporate network, also check with your IT team whether they require MS-CHAP v2 authentication. Switch to that in the connection's Security tab if available. I've seen this error happen with Windows 11's default to Automatic negotiation—it tries something the server doesn't understand and the carrier just dies.

Finally, if you're using a physical modem (yes, some of us still do), check the phone line or cable for static noise. On a DSL line, too much noise kills the carrier signal. Run ping -t 8.8.8.8 and watch for timeouts. If you see them, call your ISP.

That's the full flow. Start at the top, stop when it works. Nine times out of ten, the modem reboot does it.