ERR_NETWORK_CHANGED: What It Means and How to Fix It

What ERR_NETWORK_CHANGED Actually Means

Chrome tracks the source IP address and network interface associated with each open socket. When a page is loading, Chrome compares the current network state against what it was when the connection was opened. If the IP address, default gateway, or active adapter has changed — even momentarily — Chrome considers those in-flight requests invalid and abandons them with ERR_NETWORK_CHANGED. A simple reload after the network stabilises is all that is needed in most cases.

The error is not a sign of a broken site, a security problem, or a failed server. It is purely a client-side signal that the network path underneath an open connection changed mid-flight.

What Triggers the Error

Any event that causes the OS to assign a new IP address or switch the active network adapter will trigger ERR_NETWORK_CHANGED on pages that were loading at that moment:

• IP address changed mid-session — a DHCP lease expired and the router issued a different IP. This is rare with reasonable lease times (typically 24 hours) but can happen on networks with very short leases or when the router restarts.
• NIC switched from Wi-Fi to Ethernet or vice versa — plugging in an Ethernet cable on a laptop that was using Wi-Fi causes Windows or macOS to shift traffic to the wired adapter. The source IP changes, active connections break, and Chrome reports the error.
• DHCP lease renewed with a different address — most DHCP renewals return the same address, but if the router's lease table was cleared or the pool was modified, the renewal may return a different IP.
• VPN connected or disconnected — connecting a VPN creates a new virtual network adapter with its own IP and routes all traffic through it. Disconnecting removes that adapter. Either event changes the source IP of active connections. Split-tunnel VPNs that only route some traffic are particularly prone to causing intermittent ERR_NETWORK_CHANGED if the tunnel flaps.
• Roaming between Wi-Fi access points — on mesh networks and enterprise WLANs, clients roam between access points. If the roam assigns a new IP (layer 3 roam) rather than maintaining the existing one (layer 2 roam), Chrome detects the change.
• IPv6 address changes — Windows uses Privacy Extensions (RFC 4941) to generate temporary IPv6 addresses that rotate periodically. If Chrome opened a connection on a temporary IPv6 address that expired mid-session, the source address changes even if IPv4 is unchanged.

How to Fix ERR_NETWORK_CHANGED

Step 1: Reload the page

Most occurrences are one-off events. Press F5 or Ctrl+R after the network settles. Chrome will open a fresh connection on the current network state and the page will load normally.

Step 2: Disable automatic adapter switching (Windows)

Windows automatically prefers Ethernet over Wi-Fi when both are connected, switching traffic the moment a cable is plugged in. To prevent the switch from disrupting active sessions, either disconnect Wi-Fi manually before plugging in Ethernet, or adjust adapter metrics. In Network Connections (ncpa.cpl), right-click the Wi-Fi adapter → Properties → Internet Protocol Version 4 → Advanced, and set the Interface Metric to a higher number (e.g., 50) than Ethernet (default 10–25). This discourages automatic switching without fully disabling Wi-Fi.

Step 3: Disable Wi-Fi when wired

The cleanest solution for desktop and docked laptop use is simply disabling the Wi-Fi adapter when an Ethernet cable is connected. On Windows: Settings → Network and Internet → Wi-Fi → turn off. On macOS: click the Wi-Fi menu bar icon → Turn Wi-Fi Off. This eliminates adapter switching entirely.

Step 4: Set a static IP to prevent DHCP-triggered changes

If the error recurs on a device that rarely moves between networks — a desktop, NAS, or home office machine — assigning a static IP removes DHCP lease renewals as a variable. Use an address outside the router's DHCP pool range to avoid conflicts. On Windows: Settings → Network and Internet → Ethernet → the connected network → IP assignment → Edit → Manual. Set IP, subnet mask, gateway, and DNS manually.

Step 5: Update NIC drivers

Outdated Wi-Fi or Ethernet drivers sometimes cause spurious link-down/link-up events that trigger IP changes even when the physical connection is stable. Download the latest driver from the adapter manufacturer's site (Intel, Realtek, Broadcom, Qualcomm) or the laptop vendor's support page. Avoid relying solely on Windows Update for NIC driver updates — vendor sites often have newer versions.

Step 6: Disable IPv6 if causing dual-stack flapping

On networks where IPv6 is partially configured or where Privacy Extensions cause frequent address rotations, disabling IPv6 on the affected adapter can stop ERR_NETWORK_CHANGED from recurring. On Windows: Network Connections → right-click adapter → Properties → uncheck Internet Protocol Version 6. This is a targeted workaround, not a universal recommendation — only apply it if IPv6 address churn is confirmed as the cause.

Step 7: Stabilise VPN connections

If the error coincides with VPN activity, the VPN tunnel is flapping — briefly disconnecting and reconnecting, changing the virtual adapter's IP each time. Reconnect the VPN, check for VPN client updates, and review whether the VPN's split-tunnel or DNS leak prevention settings are causing interface churn. Some corporate VPN clients have a "network lock" or "kill switch" mode that holds traffic during tunnel re-establishment rather than letting it fall back to the physical adapter, which prevents the source IP change that triggers the error.

Step 8: Check mesh network roaming settings

If you have a mesh network and the error happens as you move around the home, the mesh is performing layer 3 roams that assign a new IP. Check the mesh admin app for options to force layer 2 roaming, enable "sticky client" settings, or adjust the roaming threshold (the signal level at which the system reassigns a client to a different node). A higher threshold means fewer roams.

Network Manager Settings on Windows and macOS

Both operating systems have settings that affect how aggressively adapters switch. On Windows, the key locations are: adapter properties for metric adjustment, the Wi-Fi settings page to disable auto-connect on specific networks, and the Power Management tab on the NIC device in Device Manager where "Allow the computer to turn off this device to save power" should be unchecked for adapters prone to unnecessary resets. On macOS, System Settings → Network → the active adapter → Details lets you configure DNS and TCP/IP. For adapter priority, drag adapters in the Network list to set preference order — connections higher in the list are preferred.

Still Not Fixed? Rule Out Your Connection

If the error keeps recurring despite stable network settings, verify the underlying connection is healthy. Run a speed test — if download, upload, and ping come back normal, the error is intermittent and tied to a specific adapter event. If the speed test shows packet loss or inconsistent results, the physical connection or ISP link is unstable and that instability is what is triggering the network changes Chrome detects.

Frequently Asked Questions

Is ERR_NETWORK_CHANGED a virus?

No — it is a normal transient error when your network changes. Persistent occurrence usually means Wi-Fi or VPN instability, not malware. Malware rarely causes this specific error pattern.

Why does it happen more on laptops than desktops?

Laptops move between networks, have both Wi-Fi and Ethernet adapters, connect to VPNs, and roam between mesh nodes — all of which cause network state changes. Desktops with a single wired connection almost never trigger this error unless the Ethernet link itself is physically unstable.