A phone call that gets cut off mid-sentence. That is 0x80072EFE: your PC reached Microsoft’s update servers, the conversation began, and then something hung up. Unlike its timeout cousin 0x80072EE2 — where nobody picks up — here the line goes dead after someone answered, which points at an active intervention rather than mere slowness. Formally this is WININET_E_CONNECTION_TERMINATED: a live connection, deliberately cut mid-exchange.

This is not a timeout (nobody answered) or a DNS failure (nobody found). In this case the server — or an intermediary — intentionally hung up. Laptop cases usually implicate strict firewalls ending long sessions, VPN tunnels collapsing under load, flaky Wi-Fi, or an ISP middlebox tampering with traffic.

Terminated connections are often environmental, so the first fix is diagnosis, not repair: confirm the pattern before touching Windows. The steps below start with that confirmation and escalate only when the environment is exonerated — there is no point rebuilding the update engine for a crime the network committed.

Why this happens

  • Firewall ending long sessions. Stateful firewalls with tight timeouts destroy update sessions mid-transfer.
  • Wobbly VPN tunnel. Tunnels flapping under load shed precisely the long-lived connections updates require.
  • Shaky Wi-Fi. Momentary wireless dropouts end connections that cannot pick up cleanly.
  • Antivirus web shield severing links. Traffic inspection that elects mid-stream to halt the transfer.
  • ISP middlebox meddling. Carrier-grade NAT or transparent proxies occasionally reset such connections.
  • The proxy severs idle streams. Overzealous proxy timeouts cut connections that pause between phases. Corporate proxies are notorious for this, silently enforcing idle limits far shorter than an update session needs.
  • Server-side shedding drops the session. Rare — Microsoft’s edge occasionally sheds load by cutting slow sessions.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Check if the connection itself is shaky

Dropped connections usually come from the environment — verify the pattern before repairing Windows.

  1. Attempt a large file download via the browser — pick something over 500 MB so the connection stays open long enough to matter.
  2. Should it also stall or reset, the network is broadly unstable.
  3. When Windows Update alone fails while other lengthy downloads succeed, proceed — something is singling out update traffic.

Fix 2: Stabilize the network path

Strip the usual connection-killers out of the path before faulting Windows. Each removal doubles as a diagnostic — the moment the error vanishes, you have identified the culprit.

  1. Drop any VPN and test again — a flapping VPN is the prime suspect for this code.
  2. While on Wi-Fi, switch to Ethernet or sit nearer the router to eliminate wireless dropouts.
  3. Sever the VPN entirely and leave it down for the full attempt.
  4. Retry the update check.

Fix 3: Reset the Windows network stack

When the configuration looks clean but connections keep dying, stale network state may be at fault. Winsock and IP settings accumulate corruption over months of sleep-wake cycles and network changes — a full flush clears every layer at once and is harmless to your files.

  1. In an elevated Command Prompt, run netsh winsock reset to rebuild the socket layer.
  2. Then run netsh int ip reset to rebuild the IP configuration.
  3. Restart — the resets only take effect across a reboot.
  4. Check for updates and confirm the connection holds.

Fix 4: Keep security software from severing the connection

Web shields and firewalls severing connections mid-stream generate precisely this error. Running one controlled test with inspection disabled reveals the culprit.

  1. Switch off the web shield in your third-party security suite for this test; keep the main antivirus active.
  2. Retry the update immediately while the shield is still off.
  3. On success, add a Windows Update exclusion rather than leaving protection switched off.
  4. Restore the shield immediately after testing, regardless of outcome.

Fix 5: Allow the troubleshooter an attempt

The troubleshooter detects broken network configurations and stuck states, repairing them automatically without touching your files.

  1. Bring up Settings and sail to System > Troubleshoot > Other troubleshooters.
  2. Discharge the Windows Update entry and pursue its prompts.
  3. Reboot the PC and re-try the check.

Fix 6: Rebuild the Windows Update components

If the network is exonerated but the error persists, the local update pipeline may be contributing. This is less common — termination is usually environmental — but a corrupted engine state can mishandle reconnections, and a full reset eliminates that possibility.

  1. Drop the services: net stop wuauserv, net stop bits, net stop cryptsvc.
  2. Stow the folders: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old.
  3. Revive the services: net start wuauserv, net start bits, net start cryptsvc.
  4. Look for updates and confirm the error has gone.

Fix 7: Fetch the update by hand from the Catalog

A browser download resumes and retries on its own terms, unbothered by the engine’s connection handling. The Microsoft Update Catalog lists every cumulative release, and your browser’s downloader tolerates exactly the flaky connections that defeat Windows Update.

  1. Copy the KB number from Update history first.
  2. Pull the x64 Windows 11 package through your browser.
  3. Execute the .msu file and reboot afterward if asked.

Closing

Dropped calls want a steadier line: stabilize the path, calm the middleboxes, and the update completes. Note which fix worked, because termination causes love to return — VPNs reflap, firewalls update their rules, and Wi-Fi degrades — and the same repair will serve you again. For laptops that travel between networks, consider running the update check on a known-good home connection before troubleshooting the hotel Wi-Fi. When connections hold yet downloads later falter, the 24H2 update-error compendium takes on the download codes, and the troubleshooter handles the automated network checks. Microsoft’s Windows support hub documents connection troubleshooting.

Frequently asked questions

What does error 0x80072EFE mean?
WININET_E_CONNECTION_TERMINATED: an established connection to the update servers was cut off mid-exchange. Unlike a timeout (nothing answered) or a DNS failure (nobody found), here the server — or something in the middle — actively dropped the call. It is a termination, not a silence.
How is this different from error 0x80072EE2?
0x80072EE2 is a timeout — the request waited too long for any response. 0x80072EFE is a termination — the connection was established and then actively cut. Timeouts suggest slowness; terminations suggest something in the path is deliberately killing long-lived connections, like an aggressive firewall or flapping VPN.
Can my Wi-Fi really cause this?
Yes. Brief wireless drops terminate connections that cannot resume cleanly, and update downloads are long-lived enough to catch every blip. On Wi-Fi, try Ethernet or move closer to the router to rule out wireless drops. If every long-lived connection breaks, the network is the patient, not the PC.
Should I disable my firewall to test?
A controlled test with the third-party firewall’s inspection off identifies the culprit — but keep Windows Firewall on and re-enable the shield right after the test, whatever the result. If the update works with inspection off, add an exclusion for Windows Update instead of leaving protection disabled.