Chrome ERR_CONNECTION_RESET after Windows update — fix it

Quick answer: Open Command Prompt as admin, run netsh winsock reset then netsh int ip reset, reboot. That's it 80% of the time.

If you're seeing ERR_CONNECTION_RESET in Chrome right after a Windows update, you're not alone. What's actually happening here is that the update has silently modified your Winsock catalog or TCP/IP stack. Windows updates — especially cumulative patches or feature updates — can overwrite certain network drivers or reset internal state incorrectly. Chrome is the canary here because it's more sensitive to these changes than, say, Edge or Firefox. The connection gets established, then immediately dropped, hence the "reset" message. The browser reaches the server, the server responds, but something in the network layer yanks the connection away. That's the Winsock corruption.

Why the update causes this

Windows updates often touch the network stack. A 2023 update (KB5025221) famously broke TLS 1.3 on certain builds, causing exactly this error. Another culprit: the update might replace tcpip.sys or alter registry keys under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip. You don't need to dig there — just reset the whole stack.

Step-by-step fix — the one that works

1. Run Command Prompt as Administrator. Hit Win+R, type cmd, then Ctrl+Shift+Enter. Accept the UAC prompt.
2. Type netsh winsock reset and press Enter. You'll see "Successfully reset the Winsock Catalog."
   Why this step: Winsock is the API that applications — including Chrome — use to speak TCP/IP. The update may have injected a bad LSP (layered service provider) or corrupted the catalog. This flushes it.
3. Type netsh int ip reset and press Enter. This resets your TCP/IP stack to default. You'll see a log file path — don't bother opening it unless you're curious about what was changed.
4. Type ipconfig /flushdns and press Enter. Clears your DNS cache, which might have stale entries from before the update.
5. Reboot. Not a soft restart — do a full shutdown via Shift+Shutdown, then power on. This ensures the kernel reloads the network stack cleanly.

Open Chrome. The ERR_CONNECTION_RESET should be gone. If not, move to the alternative fixes.

Alternative fixes if the reset doesn't work

1. Disable IPv6

Windows updates sometimes enable IPv6 on interfaces where it was previously disabled. Chrome can trip over a misconfigured IPv6 route.
Go to Network and Sharing Center → Change adapter settings → right-click your active adapter → Properties → uncheck "Internet Protocol Version 6 (TCP/IPv6)". Click OK, restart Chrome. Not a permanent solution, but useful for testing.

2. Check for proxy settings

An update might have flipped on "Automatically detect settings" or a proxy script. In Chrome, go to Settings → System → Open your computer's proxy settings. Ensure "Automatically detect settings" is ON (it's fine), but that you don't have an explicit proxy set unless you use one. If you see a proxy address and you don't know what it is, disable it.

3. Reinstall the network adapter driver

Windows updates can push a generic driver over your manufacturer's driver. Open Device Manager, find your network adapter under "Network adapters", right-click → Uninstall device. Check "Delete the driver software for this device" if you're on Windows 10/11. Then reboot — Windows will reinstall the default driver. If that doesn't work, download the exact driver from your motherboard or laptop vendor's site (Realtek, Intel, Killer, etc.) and install manually.

4. System Restore — the nuclear option

If you have a restore point from before the update, roll back. Type "Create a restore point" in Start, click System Restore, choose a point dated before the update. This undoes the Winsock changes at the kernel level. It's heavy, but it works.

Prevention tip — block future updates from breaking your network

Before installing any major Windows update, manually back up your Winsock catalog just in case. Open admin CMD and run netsh winsock show catalog > C:\winsock_backup.txt. That doesn't back up the catalog itself — it dumps the current state into a text file. If something breaks later, you can compare. But the real trick: use Group Policy (Windows Pro/Enterprise) to defer feature updates by 60 days. Search for gpedit.msc → Computer Configuration → Administrative Templates → Windows Components → Windows Update → "Select when Preview Builds and Feature Updates are received". Set it to 60 days. That gives Microsoft time to patch any network-breaking bugs before you get them.

One last thing: if you use a VPN or third-party firewall, disable them entirely and test Chrome. They sometimes hook into Winsock and get corrupted by updates. If the error vanishes, reinstall or update your VPN software.

ERR_CONNECTION_RESET after a Windows update is annoying, but it's rarely a hardware issue. The stack is fixable in two minutes with netsh commands. You don't need to reinstall Chrome, reset Windows, or buy a new router.