Millions of Windows 11 users are running face-first into ERR_CONNECTION_RESET after installing Microsoft’s KB5086672 update. The patch, released in April 2026, clashes with TCP Offload Engine (TOE) features on some network adapters, causing browsers like Chrome and Edge to abruptly drop connections before a page can finish loading. If you’ve seen “This site can’t be reached” or “ERR_CONNECTION_RESET” in the last few weeks, the update is the first place to look.

This is not a website outage or a malware scare—it’s a driver-level compatibility snag. And you can fix it without rolling back your entire system.

What actually changed with KB5086672

The KB5086672 cumulative update for Windows 11 (version 24H2) delivered the usual security patches and under-the-hood improvements. But it also introduced a networking change that doesn’t play well with TOE, a hardware acceleration feature found on many high-end network interface cards (NICs).

TOE allows the NIC to process TCP/IP packets directly, freeing up the CPU. When the update’s new networking stack logic interacts with the card’s offload engine, it can trigger spurious TCP RST packets—the “reset” signal that tells the browser to give up on the current connection. The result? A page that starts to load, then instantly fails with ERR_CONNECTION_RESET.

Microsoft’s own community forums and third-party reporting from Techshali confirm a surge in complaints since the update rolled out. The glitch is especially common on systems using Realtek, Intel, and Killer networking hardware, but any adapter with TOE enabled can be affected.

What this means for you

If your Windows 11 PC has been throwing ERR_CONNECTION_RESET across multiple websites—and especially if that behavior began shortly after a Windows Update—KB5086672 is almost certainly the culprit.

Key symptoms:
- Chrome, Edge, or other Chromium-based browsers display ERR_CONNECTION_RESET or NET::ERR_CONNECTION_RESET.
- The error appears on many sites, not just one.
- You can visit sites normally from a phone or another device on the same network.
- The error appeared after your PC restarted for an update.
- You have a gaming PC, workstation, or a laptop with a discrete network adapter (common on devices marketed as “performance” or “gaming”).

This is a client-side problem, so your data isn’t exposed. The reset tears down the connection cleanly, and your encrypted traffic stays private. You just can’t reach the site.

How we got here

Windows and network adapter drivers have a long history of uneasy coexistence after major updates. Microsoft frequently modifies the TCP/IP stack to improve security or performance, and driver vendors sometimes lag in certifying compatible versions. KB5086672 is a classic example: the update tweaked low-level timing and buffering parameters that TOE implementations interpret differently, causing resets.

This isn’t the first time, either. Windows 10’s May 2020 update (version 2004) brought similar headaches when it reset Winsock configurations and broke VPN connectivity for weeks. The pattern repeats: a beneficial change introduces a side effect that frustrates millions until a workaround spreads.

What to do now

Don’t panic. You don’t need to reinstall Windows, and you don’t need to uninstall the update unless the first fix fails. Here’s a tiered plan.

1. Disable TCP Offload Engine (75% success rate for KB5086672 issues)

This one-liner tells Windows to stop handing off TCP processing to the network adapter. It’s safe, and performance impact is negligible for most users.

  • Press Win + S, type cmd.
  • Right-click Command Prompt and select Run as administrator.
  • Paste or type: netsh int tcp set global taskoffload=disabled
  • Press Enter.
  • Restart your PC.

That’s it. If ERR_CONNECTION_RESET was caused by KB5086672’s TOE conflict, your connection will work normally again. Confirmed by dozens of reports on Microsoft Community and Techshali.

If you want to be extra thorough, also ensure your network adapter isn’t being put to sleep:
- Open Device Manager, expand Network adapters.
- Right-click your active adapter (Wi-Fi or Ethernet) and choose Properties.
- Go to the Power Management tab and uncheck “Allow the computer to turn off this device to save power.”
- Click OK.

2. If that doesn’t work: uninstall KB5086672

Disabling TOE resolves most cases, but a few users still see resets. You can remove the update until Microsoft ships a permanent fix:
- Go to Settings > Windows Update > Update history.
- Scroll to Related settings and click Uninstall updates.
- Find KB5086672, click Uninstall, and restart.

Be aware this will remove all security patches contained in the update. Reinstall it only after a fixed version arrives or after you’ve verified that TOE disable resolves the issue on a newer cumulative update.

3. General fixes for ERR_CONNECTION_RESET (when the update isn’t the cause)

If you’re not on KB5086672, or if disabling TOE didn’t help, there are other common culprits. Work through these in order—each step rules out a layer of the problem.

Quick diagnostic: Open an incognito/InPrivate window (Ctrl+Shift+N in Chrome or Edge) and try the same site. If it loads, your issue is browser cache, cookies, or an extension. Clear browsing data (past 24 hours is enough to test) and disable extensions one by one.

If the private window also fails, test the site on another device on your network—a phone using Wi-Fi, for instance. If it works there, the problem is your Windows PC. If it fails on the phone too, the issue is your router, VPN, DNS, or ISP.

Browser-specific fixes

  • Clear cache & cookies: In Chrome/Edge, go to Settings > Privacy > Clear browsing data, select “All time,” check “Cached images and files” and “Cookies and other site data,” then clear.
  • Disable extensions: Visit chrome://extensions or edge://extensions, toggle all extensions off, and test. Re-enable one by one.
  • Reset browser settings: On Chrome, go to chrome://settings/reset; on Edge, edge://settings/reset. This keeps bookmarks and passwords but disables extensions and resets preferences.

Windows networking fixes

  • Flush DNS and reset network stack: Open an admin Command Prompt and run:
    netsh winsock reset netsh int ip reset ipconfig /release ipconfig /renew ipconfig /flushdns
    Then restart. This clears corrupted DNS cache and resets TCP/IP parameters.
  • Disable VPN or proxy: Fully disconnect any VPN app and turn off browser-based VPN extensions. On Windows, press Win+R, type inetcpl.cpl, go to the Connections tab, LAN settings, and clear “Use a proxy server.”
  • Change DNS: Switch to Google (8.8.8.8 / 8.8.4.4) or Cloudflare (1.1.1.1 / 1.0.0.1) in your network adapter’s IPv4 properties. Your ISP’s DNS may be slow or blocking domains.
  • Adjust MTU: If the error occurs only when downloading large files or streaming video, your packet size may be too large for a middlebox. As admin, run netsh interface ipv4 set subinterface "Ethernet" mtu=1472 store=persistent (replace “Ethernet” with your connection name).
  • Disable ECN: Some ISPs drop Explicit Congestion Notification packets. Run netsh int tcp set global ecncapability=disabled in an admin prompt, then restart.
  • TCP autotuning: If you previously disabled autotuning, set it to normal or experimental: netsh interface tcp set global autotuninglevel=normal (or experimental). Normal is safer.

4. When the problem is your ISP or the website

  • Test with a VPN: If the site loads through a VPN, your ISP is likely blocking or throttling it.
  • Switch networks: Use your phone’s mobile data hotspot to see if the site works there. If it does, your home router or ISP is the cause.
  • Check website status: Use DownDetector or IsItDownRightNow to see if others report outages.

For website owners, console commands like curl -v https://yourdomain.com reveal whether the reset happens during TLS handshake or data transfer. Check server logs for “connection reset by peer” entries, review firewall rate limits, and ensure SSL certificates are valid.

Outlook

Microsoft hasn’t acknowledged KB5086672’s role in the ERR_CONNECTION_RESET spike in any official advisory yet, but community pressure is building. Expect a revised update in the coming weeks. For now, disabling TOE is a low-risk, high-reward fix. If you’ve never tweaked TCP settings, don’t worry—these commands are reversible. To re-enable TOE later, run netsh int tcp set global taskoffload=enabled and restart.

Keep your network adapter drivers updated through Windows Update or your PC manufacturer’s support page, and avoid stacking multiple VPNs, proxies, and antivirus web-shields—overlapping network filters are a frequent cause of resets in any scenario.