Skip to main content

ERR_NETWORK_CHANGED: causes and fixes in Chrome and Edge (Windows 11 and 10)

ERR_NETWORK_CHANGED in Chrome or Edge? The causes (VPN, virtual adapters, Wi-Fi, IPv6, power saving) and the commands to fix it.

Published 14 November 2026 · 5 min read

The page starts loading, then stops on an error page with the code ERR_NETWORK_CHANGED. Once, it is nothing. Ten times a day, it is a user who can no longer work, and often a device whose network keeps changing without anyone noticing.

The short answer

ERR_NETWORK_CHANGED means Chrome or Edge detected a change in the network connection while a page was loading. Reload the page; if the error comes back, look for what is changing: a virtual adapter or a VPN that reconnects, switching between Wi-Fi and cable, unstable Wi-Fi or an adapter that power management turns off. Disable unused adapters, turn off power saving on the adapter, update the Wi-Fi driver and reset the network stack. Across a whole fleet, a tool like LongLife continuously tracks the network quality of every device and includes it in the DEX score, which points straight to the devices and sites that drop out.

What does ERR_NETWORK_CHANGED mean?

In the Chromium source code, which Chrome and Edge are built on, error -21 NETWORK_CHANGED is described simply: the network changed. When Windows reports a new IP address, an adapter that appears or disappears, or a change of connection, the browser drops the requests in progress rather than risk an inconsistent response. The usual causes:

  • switching between adapters: Wi-Fi and cable, docking station plugged in or out;
  • a VPN that connects, disconnects or reconnects in a loop;
  • virtual adapters created by Hyper-V, VirtualBox or a VPN client;
  • IPv6: addresses that change often, a badly configured router;
  • unstable Wi-Fi: weak signal, roaming from one access point to another;
  • power management turning the network adapter off to save battery.

Step 1: see when the network changes

Windows logs every connection and disconnection. In PowerShell, this command shows the last twenty events (10000: network connected, 10001: network disconnected):

PowerShell
Get-WinEvent -FilterHashtable @{LogName='Microsoft-Windows-NetworkProfile/Operational'; Id=10000,10001} -MaxEvents 20 |
  Format-Table TimeCreated, Id, Message -Wrap

If the events follow each other a few minutes apart at the times the error appears, you have found the cause: the device's network really is changing.

Step 2: list the network adapters

PowerShell
Get-NetAdapter | Format-Table Name, InterfaceDescription, Status, LinkSpeed

Look at the InterfaceDescription column: Hyper-V Virtual Ethernet Adapter, VirtualBox Host-Only Ethernet Adapter or a VPN client adapter are virtual adapters. Several adapters in the Up state at the same time, or an adapter that keeps switching from Up to Disconnected, are suspects.

Step 3: disable unused adapters

In PowerShell as administrator, disable an adapter you do not use, with its exact name from the previous list:

PowerShell
# Disables the adapter (its connection is cut)
Disable-NetAdapter -Name "Ethernet 2" -Confirm:$false
# To enable it again later
Enable-NetAdapter -Name "Ethernet 2" -Confirm:$false

Never disable the adapter used for a remote session: the connection would be lost. Disabling a Hyper-V adapter (vEthernet) cuts the network of the virtual machines; on a developer's device, warn them first.

Step 4: VPN and IPv6

Disconnect the VPN and retest. If the error goes away, update the VPN client or ask its administrator why it reconnects.

For IPv6, Microsoft advises against disabling it: some Windows components might stop working. It recommends preferring IPv4 over IPv6 instead. In Command Prompt as administrator:

Command Prompt
:: Prefers IPv4 over IPv6 (value 32, i.e. 0x20), then restart
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters" /v DisabledComponents /t REG_DWORD /d 32 /f
:: To go back to the default setting
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters" /v DisabledComponents /t REG_DWORD /d 0 /f

The change only takes effect after a restart. If nothing improves, go back to value 0.

Step 5: Wi-Fi, power management and drivers

  • Power management: in Device Manager, expand Network adapters, right-click the Wi-Fi adapter > Properties, Power Management tab, untick Allow the computer to turn off this device to save power. In the advanced power options, also set Wireless Adapter Settings > Power Saving Mode to Maximum Performance.
  • Wi-Fi driver: install the latest version from the PC or adapter manufacturer.
  • Wi-Fi history: as administrator, netsh wlan show wlanreport produces a report of recent Wi-Fi sessions and their disconnections.

Step 6: reset the network stack

If the error persists, open Command Prompt as administrator:

Command Prompt
:: Clears the DNS cache
ipconfig /flushdns
:: Resets the Winsock catalogue
netsh winsock reset
:: Resets the TCP/IP configuration
netsh int ip reset

Then restart the PC. In Windows 11, Settings > Network & internet > Advanced network settings > Network reset goes further: it reinstalls the network adapters.

In the enterprise: docking stations, VPN and sites

On a fleet, the error often follows recognisable patterns: laptops switching between Wi-Fi and cable every time they sit on a docking station, an always-on company VPN that reconnects at every network change, developer devices covered in virtual adapters, a floor where the Wi-Fi keeps roaming from one access point to another. When every device at a site is affected, look at the access points, the router and the VPN before the devices.

Symptoms, causes and solutions

SymptomLikely causeSolution
Error every time the docking station is plugged inSwitching between Wi-Fi and cableTurn off Wi-Fi when the cable is connected
Error when the VPN is onVPN reconnectingUpdate the VPN client
Several Up adapters in Get-NetAdapterVirtual adaptersDisable unused adapters
Error after a break or on batteryAdapter power managementUntick power saving
Wi-Fi drops visible in the reportSignal, driverUpdate the driver, check the signal
Every device at a siteSite networkAccess points, router, VPN

If the message mentions the cache instead, see our ERR_CACHE_MISS guide, and for other everyday faults, the list of common IT problems.

LongLife: see which devices and sites drop out

One device takes fifteen minutes to diagnose. Fifty devices spread across several sites do not. LongLife does that work continuously:

  • measure: LongLife tracks the network quality of each device and includes it in the DEX score (startup, network, stability, satisfaction). You see whether a single device drops out or a whole site;
  • detect: detectors analyse your fleet continuously and suggest the action to take, with its priority and the cost of doing nothing;
  • fix remotely: the network stack reset runs from a catalogue of signed scripts, written and tested by OPP! and expanded with every update, with a report for each device;
  • decide: when an ageing laptop piles up problems, LongLife helps you choose between keeping, upgrading or replacing it, with the cost and CO₂e of each option.

The free plan covers up to 15 devices. Estimate the gain on your fleet with the simulator, or book a meeting to see your own devices in LongLife.

Sources

Frequently asked questions

What does ERR_NETWORK_CHANGED mean?

It is a Chrome and Edge error code meaning that the PC's network connection changed while the page was loading. The browser then drops the requests in progress. A one-off change is fixed by reloading the page; a recurring error points to a network that keeps changing.

Why does ERR_NETWORK_CHANGED keep coming back?

The most common causes are a virtual network adapter (Hyper-V, VirtualBox, VPN) that connects and disconnects, a VPN that reconnects, unstable Wi-Fi, switching between Wi-Fi and cable on a docking station, and power management turning the network adapter off.

Should I disable IPv6 to fix ERR_NETWORK_CHANGED?

No, Microsoft does not recommend it: some Windows components might stop working. If IPv6 is involved, Microsoft advises preferring IPv4 over IPv6 instead, a setting that is easy to test and to undo.

Is ERR_NETWORK_CHANGED caused by the PC or by the network?

If only one device is affected, look at that device (virtual adapters, VPN, Wi-Fi driver, power management). If every device at the same site is affected, the problem more likely lies with the site's network (Wi-Fi access points, router, company VPN).

How much longer can your fleet last?

The simulator estimates in one minute the budget and CO₂ saved by extending your renewal cycle.

Read next