ERR_NETWORK_CHANGED fix: Chrome between Wi-Fi and hotspot

Nothing kills momentum like switching from your office Wi-Fi to your phone's hotspot and Chrome just sits there with ERR_NETWORK_CHANGED. You're not alone. I've seen this on Windows 11, Mac, even Linux. Let's fix it fast.

The fix that works 90% of the time

Don't restart your laptop yet. Don't reset your network stack. Open Chrome and type this into the address bar:

chrome://net-internals/#sockets

Click Flush socket pools. Then go to:

chrome://net-internals/#dns

Click Clear host cache. That's it. Close the tabs and reload the page that failed.

Had a client last month whose entire team hit this every morning when they moved from the break room Wi-Fi to their desks. Flushed sockets, problem gone. Took 15 seconds.

Why this works

Chrome keeps old network connections in its socket pool. When you switch from Wi-Fi to hotspot, those sockets are dead — they point to an old IP, old adapter, old gateway. Chrome tries to reuse them, fails, and bails with ERR_NETWORK_CHANGED. Flushing the pool forces Chrome to open fresh connections. The DNS cache holds stale records from the old network too. Clearing both gives Chrome a clean slate.

If the flush doesn't help

Sometimes the problem is deeper. Here's what else I've seen work:

1. Disable Chrome's built-in QUIC

QUIC is Google's protocol over UDP. It's aggressive about connection migration and can choke on network switches. Type this:

chrome://flags/#enable-quic

Set it to Disabled. Relaunch Chrome.

A client in a coffee shop had this exact issue — switching from their laptop's Ethernet to the shop's Wi-Fi. QUIC was the culprit. Disabled it, no more errors.

2. Turn off proxy settings

If you're on a corporate network with a proxy, the old proxy might be unreachable on the new network. Go to Chrome Settings > System > Open your computer's proxy settings. Turn off any proxy that isn't dynamic. On Windows, uncheck "Automatically detect settings" too — it's often the problem.

3. Flush your OS DNS and renew IP

Open Command Prompt as admin and run:

ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh winsock reset

Reboot. This wipes any stale entries your OS is hanging onto. I've seen this fix cases where even Chrome's internal flush didn't work.

Less common variations

IPv6 mismatch

Some hotspots use IPv6, some Wi-Fi networks don't. Chrome can get confused if the old network had IPv6 disabled and the new one has it enabled (or vice versa). Go to chrome://flags/#disable-ipv6 and toggle it. Restart Chrome to test.

Antivirus or firewall interference

Had a client using Bitdefender — it would block new network profiles for 30 seconds after a switch. Turn off the firewall temporarily to test. If that fixes it, whitelist Chrome or adjust the network profile rules.

Wi-Fi vs mobile hotspot authentication

If your hotspot requires a login page (captive portal), Chrome may try to redirect an old session. Go to http://192.168.43.1 (common for Android hotspots) or whatever your hotspot's gateway is. Authenticate again.

Prevention tips

Disable Chrome's QUIC permanently if you switch networks often. It's under flags and doesn't break anything for most users.
Set a static DNS on both networks. Google's 8.8.8.8 and 8.8.4.4 work everywhere. Stops DNS from freaking out on transitions.
Turn off proxy if you don't use one. Chrome's automatic proxy detection can lag.
Bookmark the flush pages — chrome://net-internals/#sockets and chrome://net-internals/#dns. You'll use them again.

Bottom line: Flush sockets and DNS first. It's fast, free, and fixes almost every case. If not, kill QUIC and check proxies. Don't waste time restarting your whole machine.