You're in the middle of a video call or a large file transfer on Windows 10 or 11, and the connection drops. The next thing you see is a notification or an event log entry with STATUS_HOPLIMIT_EXCEEDED (0xC000A012). It's not a typical error you can just ignore — it means something in your network path is rejecting packets because they've exceeded the maximum number of hops allowed. This happens most often when you're using a VPN client, or when your network stack has IPv6 enabled but your router or ISP isn't handling it correctly. I've also seen it on corporate laptops that connect to multiple VLANs.
What's actually happening here is a hop limit issue
Every IP packet has a field called hop limit (in IPv6) or TTL (in IPv4). Each router the packet passes through decrements this number by one. When it hits zero, the router discards the packet and sends an ICMP message back to the sender — that's the "Time Exceeded" message. Windows maps that ICMP error to STATUS_HOPLIMIT_EXCEEDED. So the error isn't a local problem; it's a network path problem. The packet's hop limit is too low for the number of routers between you and the destination.
Why would that happen on a healthy network? Two common reasons:
- VPN tunnels add extra hops. Some VPN protocols (especially older IPsec or PPTP) set a conservative hop limit on encapsulated packets, and if your traffic goes through multiple internal networks before hitting the public internet, you can exhaust the limit.
- IPv6 misconfiguration. Windows prefers IPv6 when available. If your ISP or router has broken IPv6 routing, packets may loop or take inefficient paths, bumping into the hop limit.
- Misbehaving router or firewall. Some enterprise firewalls incorrectly generate ICMP Time Exceeded messages or block them, making Windows think the hop limit was exceeded when it wasn't.
The fix that works most of the time
I'll give you the steps that resolve this in roughly 80% of cases. Start with step 1 and move down if needed.
- Restart your router and modem. Yes, the classic. But here's the nuance: a power cycle clears the router's ARP cache and resets any half-open NAT sessions, which can fix transient hop limit issues. Unplug for 30 seconds, not 5. Then reconnect.
- Disable IPv6 temporarily. This is the most direct test. Right-click the network icon in the system tray, open Network & Internet settings, then Change adapter options. Right-click your active adapter (Wi-Fi or Ethernet), select Properties, uncheck Internet Protocol Version 6 (TCP/IPv6), and click OK. Restart the network adapter by disabling and re-enabling it. If the error disappears, you've found the culprit.
- If you're on a VPN, change the VPN protocol. Most modern VPN clients (OpenVPN, WireGuard) handle hop limits fine, but older PPTP doesn't. Switch to OpenVPN or WireGuard if your provider supports it. If you can't change, try increasing the MTU on the VPN interface — sometimes a lower MTU causes fragmentation that messes with hop limits. In an elevated command prompt, run
netsh interface ipv4 set subinterface "VPN Interface Name" mtu=1400 store=persistent. - Check your router's firewall settings. Log into your router's admin page (usually 192.168.1.1 or 192.168.0.1). Look for ICMP filtering or WAN ping. If it's set to ignore or block ICMP time-exceeded messages, enable them. Some routers have a toggle called Respond to ICMP echo — that's not the one. You want Allow ICMP time exceeded.
If those don't clear it, dig deeper
If you're still getting the error after the above, it's time to see the actual path and where packets are dying. Run tracert to the destination that's failing. Open Command Prompt as admin and type:
tracert -d example.comThe Request timed out lines might not mean much, but if you see a jump where the hop count suddenly increases (like from 10 to 20), that's your problem router. Check if that router is under your control. If not, you're at the mercy of your ISP — but you can still work around it by setting a higher hop limit on your Windows machine, though this is a last resort.
Setting a higher hop limit (advanced)
Windows allows you to change the default hop limit for IPv6 and IPv4. This is a registry tweak, but it's safe if you know what you're doing. Open regedit and navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\ParametersCreate a new DWORD (32-bit) called DefaultTTL and set it to 64 (decimal). The default is usually 128, but some VPNs drop it to 32. Setting it to 64 gives you more headroom. Restart your PC. If that doesn't help, you can try 128, but don't go above that — you're just masking the issue.
Still failing? Check these things
If you've done all that and the error persists, it's not a hop limit problem at all. Here's what to check next:
- Check the Windows Event Log. Look under Windows Logs > System for the error. The source will tell you if it's TCPIP or the network adapter driver. If it's the driver, update it — a buggy NIC driver can misfire ICMP errors even when the network is fine.
- Check if the destination is actually reachable. Sometimes the error is misleading. The host might be down or blocking ICMP entirely. Try pinging the IP directly — if you get Request timed out but no hop limit error, the remote end is the issue.
- Disable any third-party firewall or antivirus. I've seen ZoneAlarm and some McAfee products generate this error because they intercept ICMP and mess with the TTL field. Disable them temporarily, not uninstall, just to test.
One last thing: if you're on a corporate network, this error often appears because of internal routing loops. Talk to your network admin — they may need to check their OSPF or BGP configurations. But for home users, the steps above will fix it 9 times out of 10. Network issues are rarely as complex as they seem.