ERR_INTERNET_DISCONNECTED When Wi-Fi Shows Connected

You open Chrome, type an address, and get ERR_INTERNET_DISCONNECTED. The Wi-Fi icon in the taskbar shows full bars. Your phone loads the same page without a hiccup. What's actually happening here is that Windows has decided your adapter has no usable path to the internet, and Chrome is trusting that verdict. The Wi-Fi link is fine — it's the layer above it that's broken.

Windows uses the Network Connectivity Status Indicator (NCSI) to probe a Microsoft endpoint and decide whether to show that little globe-with-a-slash icon. If NCSI fails, the OS sets the network profile to "No Internet," and Chromium-based browsers short-circuit any request with ERR_INTERNET_DISCONNECTED before the packet even leaves your machine. So you're not debugging DNS or routing yet — you're debugging Windows' opinion about your network.

Cause 1: Stale DHCP lease or bad DNS resolver from the router

This is the one I see most often, and it's the fastest to rule out. Your laptop got a DHCP lease hours ago, the router rebooted (or the lease expired and got renewed with garbage), and now you're holding an IP that the router no longer honors. DNS queries go nowhere because the resolver address Windows cached is stale.

Real trigger: you closed the lid at the coffee shop, drove home, opened it, and Windows kept the coffee shop's DNS servers (192.168.1.1 that doesn't exist on your home network). The Wi-Fi auto-connected to your home SSID, but the DNS handoff didn't happen cleanly.

The fix, in order:

1. Open an elevated Command Prompt (Win + X, then Terminal (Admin) on Windows 11).
2. Run these three commands, one at a time:

ipconfig /release
ipconfig /renew
ipconfig /flushdns

The /release drops your current lease. /renew asks the router for a fresh one. /flushdns clears the resolver cache so you're not holding onto stale A records. If the renew succeeds and you still get ERR_INTERNET_DISCONNECTED, the problem is higher up — go to Cause 2.

One more thing: check that you're not on a static IP by accident. Go to Settings → Network & Internet → Wi-Fi → your network → IP assignment. If it says Manual, that's your bug. Flip it to Automatic (DHCP).

Cause 2: Winsock or TCP/IP stack corruption

If flushing DNS doesn't fix it and other devices on the same network are fine, your Windows socket layer is probably damaged. This happens after a VPN client uninstalls badly, a third-party firewall (looking at you, old Comodo and ZoneAlarm versions) leaves hooks behind, or a Windows Update half-installs a network component. The symptom is specific: ping by IP works, ping by hostname doesn't, and Chrome throws ERR_INTERNET_DISCONNECTED instantly rather than timing out.

Test it. Open Command Prompt and run:

ping 8.8.8.8
ping google.com

If the first succeeds and the second says "Ping request could not find host," your stack is partially working — the IP layer is fine, the name resolution path is corrupted. Reset the stack:

netsh winsock reset
netsh int ip reset
netsh int ipv4 reset
netsh int ipv6 reset
ipconfig /flushdns

Reboot when it tells you to. Don't skip the reboot — the winsock catalog is only rebuilt during boot, and if you test before restarting you'll get the same error and think the fix failed.

The reason step 2 works is that netsh winsock reset rewrites the LSP (Layered Service Provider) chain in the registry under HKLM\SYSTEM\CurrentControlSet\Services\Winsock2\Parameters. VPN and firewall software inserts itself into that chain, and when the software is removed badly, the chain points at nothing. Windows falls back to a null provider, and any TCP connection silently fails.

Cause 3: NCSI probe blocked or Network Location Awareness service stopped

Your internet actually works. Chrome just doesn't believe it. This happens when the NCSI endpoint (www.msftconnecttest.com) is blocked by a DNS filter, a Pi-hole, or a captive-portal-style firewall at a hotel or corporate network. Windows marks the connection as "No Internet," and Chrome obeys.

How to tell this is your problem: open Edge or Firefox. If Edge works but Chrome doesn't, it's not NCSI. If no browser works but ping 1.1.1.1 succeeds, it's NCSI or the Network Location Awareness (NLA) service.

First, check the service. Press Win + R, type services.msc, find Network Location Awareness. It should be Running and set to Automatic. If it's stopped, start it. NLA is what tells Windows "this network is Public/Private/Domain" and whether it has internet. Kill it and every network-aware app gets confused.

If NLA is running, the NCSI probe itself is failing. You can override the probe behavior with a registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet
Name: EnableActiveProbing
Type: DWORD
Value: 1 (default), 0 to disable

Set EnableActiveProbing to 1 if something (a "privacy" tweak tool, usually) set it to 0. That disables the probe Windows uses to detect connectivity, and the OS assumes no internet as a result. This is a common misfeature in "debloat" scripts from 2021–2022 that are still floating around.

After changing the key, restart the NlaSvc service:

net stop nlasvc
net start nlasvc

Or just reboot. Either way, give it 30 seconds to re-probe before you test.

If you're on a corporate network with a captive portal or SSL inspection, disabling active probing makes the error worse, not better. Leave it at 1 and fix the underlying DNS instead.

Quick reference

One last thing: if none of this works, boot a Linux live USB and test the same Wi-Fi. If it works there, the problem is 100% Windows-side and a network reset (Settings → Network & Internet → Advanced network settings → Network reset) will clear it. That wipes every adapter, VPN, and saved Wi-Fi profile, so export what you need first. It's a hammer, but it's the right hammer when the socket layer is a mess you didn't create.