ERR_NETWORK_CHANGED: What It Means & How to Fix It

What Is ERR_NETWORK_CHANGED?

ERR_NETWORK_CHANGED is the error Chrome, Edge and other Chromium browsers show with the heading "Your connection was interrupted" and the line "A network change was detected." In Chromium it is net error -21, described in the source simply as "the network changed" (net_error_list.h).

Chrome watches your operating system for network changes: an IP address appearing or disappearing, a network adapter connecting or disconnecting, the default route moving to a different interface. When that happens while a page is loading, Chrome can't be sure the connection it was using still works, so it abandons the request and shows this page instead of hanging.

So the error isn't really about the website. It tells you that something on your side changed. Once is normal, for example when the laptop drops Wi-Fi for a moment and rejoins, or switches to another saved network. If it keeps happening, something on your device or network is changing over and over, and that's what you need to find.

What Counts as a "Network Change"?

Any of these can trigger the error if it happens while a page is loading:

Step 1: Find What Keeps Changing

Before trying random fixes, catch the change in the act. On Windows, three commands do it: a continuous ping shows drops as they happen ("Request timed out" lines mean the link dropped, so leave it running while you browse and stop it with Ctrl + C before running the next command), netsh wlan show wlanreport writes a report of every Wi-Fi disconnect from the last three days (run it in an administrator Command Prompt, then open C:\ProgramData\Microsoft\Windows\WlanReport\wlan-report-latest.html), and ipconfig /all lists every adapter and its state:

ping -t 8.8.8.8
netsh wlan show wlanreport
ipconfig /all

In the Wi-Fi report, red error circles in the summary chart that line up with the errors point to the wireless link. If Wi-Fi looks steady, look at ipconfig /all for extra adapters, such as vEthernet, VirtualBox Host-Only, VMware Network Adapter, or the VPN's TAP or WireGuard adapter. Those are the usual suspects. Visiting What Is My IP twice a few minutes apart also helps: if your public IP changes between visits, your device is switching networks or your VPN is reconnecting.

Fix 1: Make Your Wi-Fi Connection Stable

• Remove saved networks you don't use. If your laptop knows a neighbour's or a phone hotspot's Wi-Fi, it may hop to it whenever your main signal dips. On Windows, Settings → Network & internet → Wi-Fi → Manage known networks → Forget. On a Mac, System Settings → Wi-Fi → the … button next to a network → Forget This Network.
• Stop band and node hopping. Mesh systems and dual-band routers move devices between 2.4 GHz, 5 GHz and different nodes. If the errors happen in one spot, move closer to the router or a node, or give the 5 GHz band its own network name and connect to that.
• Restart the router. Unplug it for 30 seconds. Long-running routers sometimes get unstable, and a restart also gets the latest DHCP lease.
• Use Ethernet for a test. If the error disappears on a cable, the problem is the wireless link, not Chrome.

Fix 2: Check Your VPN

Every time a VPN connects or reconnects it adds or changes a network adapter and the default route, which is exactly what Chrome reacts to. A VPN on a weak connection may reconnect every few minutes, and each reconnect can break whatever page was loading.

Disconnect the VPN and browse for a while. If the errors stop, switch the VPN to a different server or protocol (WireGuard is designed to roam between networks without setting up a new connection; WireGuard), turn off any "auto-switch to the fastest server" option, and update the VPN app.

Fix 3: Disable Virtual Network Adapters You Don't Need

Virtualisation tools create their own network adapters. Hyper-V and WSL2 (the vEthernet adapters), VirtualBox, VMware, Docker Desktop and some VPN apps all do this, and when those tools start or stop, their adapters can appear, disappear or get new addresses, and Chrome sees a network change each time.

Open Network Connections (press Win + R, type ncpa.cpl, press Enter), right-click each virtual adapter you don't need and choose Disable. Leave your real Wi-Fi or Ethernet adapter alone. If you do use the tool, consider closing it while you browse, or test with it closed to confirm it's the cause.

Fix 4: Turn Off Wi-Fi Power Saving and Update Drivers

Windows can switch the Wi-Fi card off briefly to save power, and some drivers reconnect afterwards. Each reconnect is a network change.

• Open Device Manager (right-click Start → Device Manager) → Network adapters.
• Double-click your Wi-Fi adapter → Power Management tab (if your adapter has one) → untick Allow the computer to turn off this device to save power.
• On the Driver tab, choose Update driver, or get the latest driver from the laptop maker or the chip vendor (Intel, Realtek, MediaTek, Qualcomm). Outdated Wi-Fi drivers are a common cause of repeated drops.
• In Settings → System → Power & battery, a battery-saver mode can also reduce Wi-Fi performance. Test while plugged in.

Fix 5: Rule Out IPv6 Prefix Changes (Mac and Linux)

IPv6 is rarely the cause. Chrome on Windows only watches IPv4 address changes (Microsoft), so IPv6 changes there can't trigger this error, and since Chrome 148, Chrome on Linux ignores the temporary IPv6 privacy addresses that are replaced every day (Chromium). IPv6 can still matter on a Mac or Linux PC when a flaky router or ISP keeps handing out a new IPv6 prefix, because every device on the network then gets new addresses.

To test on a Mac, open System Settings → Network → Wi-Fi → Details… → TCP/IP, set Configure IPv6 to Link-local only, and browse for a while. If the errors stop, the real fix is on the router (update its firmware, or ask the ISP about unstable IPv6). Set it back to Automatically afterwards.

Fix 6: Flush DNS and Reset the Network Stack

If nothing above stands out, reset Windows networking to defaults. Run these in an administrator Command Prompt, then restart:

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

After the restart, you can also clear Chrome's own DNS cache: open chrome://net-internals/#dns and click Clear host cache (more in how to flush DNS).

Fix ERR_NETWORK_CHANGED on a Mac

• Remove extra network services: System Settings → Network shows every interface. Bluetooth PAN, iPhone USB, Thunderbolt Bridge and old VPN entries can come and go. Remove or deactivate the ones you don't use.
• Stop auto-joining other networks: System Settings → Wi-Fi → the … button next to a saved network → turn off Auto-Join for the ones you only use now and then, so the Mac doesn't jump to them.
• Check VPN and network extensions: some security tools and VPN clients install network filters. Quit them one at a time to test.
• Renew the lease: System Settings → Network → Wi-Fi → Details… → TCP/IP → Renew DHCP Lease.

Fix ERR_NETWORK_CHANGED on Android and iPhone

Phones switch between Wi-Fi and mobile data automatically, and that switch is a network change. Stock Android moves you to mobile data when Wi-Fi has no internet (Switch to mobile data automatically, under Network preferences) and Samsung when Wi-Fi is slow or unstable (Intelligent Wi-Fi → Switch to mobile data), while the iPhone's Connectivity Assist, which replaced Wi-Fi Assist, does it when Wi-Fi is slow or unusable (Apple). If you get this error often on a weak Wi-Fi network, either turn the feature off while you're on that network or move closer to the router.

Also turn off VPN and ad-blocking apps for a test, since many run as a local VPN, and on Android set Private DNS to Automatic. See the Private DNS guide for what each option does.

ERR_NETWORK_CHANGED vs Similar Errors

If your Wi-Fi stays connected but nothing loads, see Wi-Fi connected but no internet. If pages fail with a reset rather than a network change, see ERR_CONNECTION_RESET, and for DNS problems, DNS server not responding. The Ping Test checks whether a site answers at all, from 11 cities.