Fix ERR_NETWORK_CHANGED in Chrome (No Reboot)

Quick answer: Chrome is killing the request because your operating system switched network interfaces (or routes) mid-flight — disable IPv6, pin your default route, and flush DNS.

I know this error is infuriating. You're mid-checkout, mid-upload, mid-anything, and Chrome slams a wall up that says the network changed. It's not lying. Somewhere between the moment you hit Enter and the moment the server answered, your computer decided a different network path was better. That could be Wi-Fi handing off to Ethernet because you docked your laptop. It could be a VPN reconnect. It could be Windows 11 deciding your 5GHz signal dropped one bar so it hopped to 2.4GHz. Chrome watches this via the network change notifier and cancels in-flight requests when it fires. Most of the time it shouldn't — so we make it stop.

Fix It: Step by Step

Confirm what's actually switching. Open a terminal and run ipconfig /all (Windows) or ifconfig / networksetup -listallhardwareports (macOS). Watch the output for 30 seconds while you trigger the error. If you see two active adapters (Wi-Fi + Ethernet, or Ethernet + VPN tap), that's your culprit.
Disable IPv6 temporarily to test. On Windows, open Network Adapters, right-click your active adapter, Properties, and untick Internet Protocol Version 6 (TCP/IPv6). On macOS: networksetup -setv6off Wi-Fi. Reload the page. If the error stops, IPv6 route flapping is the cause. I've seen this most on Comcast Xfinity and some AT&T fiber setups where the router advertises IPv6 but the ISP drops it every few minutes.
Kill the secondary connection. If you're on Wi-Fi and Ethernet at the same time, disable one. Windows 11 has a nasty habit of keeping both up with different metrics. In ncpa.cpl, right-click the adapter you don't want and pick Disable. Yes, every time. Until you set a static metric (see below).
Flush DNS and reset the network stack. In an admin Command Prompt:
```
ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh winsock reset
netsh int ip reset
```
Reboot once after this — the only reboot in this whole process. Then don't reboot again.
Turn off Chrome's network change notifier flag. Go to chrome://flags/#network-service-in-process and chrome://flags/#enable-network-change-notifier (the flag name shifts between Chrome versions — search "network" in flags). Set both to Disabled. Restart Chrome. This tells Chrome to stop caring so aggressively when the OS reports a route change.
Pin your route metric. If you must keep two adapters up, set one to a lower metric so Windows stops flip-flopping. In PowerShell as admin:
```
Set-NetIPInterface -InterfaceAlias "Ethernet" -InterfaceMetric 10
Set-NetIPInterface -InterfaceAlias "Wi-Fi" -InterfaceMetric 50
```
Now Windows always prefers Ethernet. No more mid-download swaps.

If That Doesn't Work

Sometimes the switch is happening one layer above what you control. Try these in order:

Update your Wi-Fi driver. Intel AX200/AX210 cards on Windows 11 had a firmware bug in 2022–2023 that caused roaming between APs to fire the network change notifier constantly. Grab the latest driver from Intel's site, not Windows Update.
Check your VPN. NordVPN, ExpressVPN, and corporate AnyConnect clients all rebuild the tunnel periodically. If the error coincides with VPN keepalives, switch to a different protocol (WireGuard instead of OpenVPN usually helps).
Use a different browser to confirm it's not Chrome-specific. Open the same URL in Edge. If Edge is fine, it's Chrome's notifier. If Edge also dies, it's the OS or your adapter.
Roll back to a known-good Chrome version if the error started right after an update. Chrome 116 and 120 both shipped notifier regressions that broke downloads on dual-homed machines.
Disable "Fast Startup" in Windows. Control Panel → Power Options → Choose what the power buttons do → Change settings that are currently unavailable. Untick Fast Startup. It leaves the network stack in a half-initialized state that confuses Chrome on the first request after wake.

Prevention

Pick one network path and stick with it during long transfers. If you're on a laptop that docks, set Ethernet to the lower metric and Wi-Fi to a higher one so Windows treats Ethernet as the boss. Also, if you tether on mobile hotspots frequently, give that adapter a fixed metric too — I've watched Chrome kill 40-minute uploads three times in a row because a phone hotspot kept re-negotiating. One more thing: keep your router firmware current. ASUS and Netgear both shipped fixes in 2024 for route advertisement bugs that triggered this exact error on otherwise healthy networks.

None of this requires a reboot beyond the one after the winsock reset. If a support rep told you to "just restart," they were right about the symptom and wrong about the cause.