Windows 10’s error 0x80072EFE is the update client reporting that its download connection was aborted — started fine, died partway. It is one of the more honest error codes: something between your laptop and the update server broke the transfer. The detective work is figuring out whether the break came from flakiness (a dying Wi-Fi signal, a congested link) or from force (a VPN, proxy, or security product deliberately cutting the connection).

That distinction drives everything below. Flaky connections get stabilized: wired links, power management fixes, bandwidth discipline. Forceful intermediaries get removed from the path during updates. And in both cases, the damaged partial downloads left behind must be cleared, because the client keeps tripping over its own wreckage when it tries to resume.

If a big feature upgrade is what keeps aborting, pair this guide with our 24H2 failure recovery article — large upgrades stress marginal connections the hardest.

Why this happens

  • Wi-Fi instability: Signal drops, band steering, and power-saving disconnects mid-transfer.
  • VPN drops: Tunnel reconnects killing everything routed through them.
  • Proxy resets: Middleboxes closing long-lived connections on policy.
  • Security software kills: Antivirus terminating streams it cannot inspect quickly.
  • Router timeouts: Aggressive idle-connection cleanup on cheap or misconfigured routers.
  • Corrupt resume state: Damaged partial files causing every resume attempt to abort.
  • Congested uplink: Saturated connections starving the download’s acknowledgment traffic.

How to fix it

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

Update downloads want a boring connection: stable, uncongested, and preferably wired. Excitement in the form of roaming, band-switching, or power-saving disconnects is exactly what aborts transfers.

  1. Use an Ethernet cable for the update session if at all possible.
  2. On Wi-Fi, open Device Manager, find your wireless adapter, and in Properties > Power Management uncheck Allow the computer to turn off this device to save power.
  3. Forget and rejoin the network to clear any stale roaming state, then stay put during the download.
  4. Pause OneDrive, Dropbox, and streaming while updates download.

Fix 2: Take intermediaries out of the download path

Every middleman is a suspect when connections die mid-transfer. VPNs, proxies, and even some browser VPN extensions can reset the update client’s connections without any visible warning.

  1. Disconnect the VPN and fully exit its client.
  2. In Settings > Network & Internet > Proxy, disable every proxy option.
  3. If you use a third-party firewall, set it to allow the update services explicitly or disable its filtering during the download.
  4. Run the update on the naked connection and see if it completes.

Fix 3: Power-cycle the network gear

Routers develop amnesia: NAT tables fill, firmware glitches accumulate, and long connections start dying. A clean reboot of the network path is the fastest way to rule the gear in or out.

  1. Unplug the router and modem (if separate) for a full 30 seconds.
  2. Plug the modem back in first, wait for its lights to stabilize, then the router.
  3. Reconnect the laptop and confirm internet works normally.
  4. Retry the update download immediately.

Fix 4: Purge the aborted partial downloads

Every abort leaves fragments, and the client’s resume logic chokes on damaged ones — producing a maddening loop where each attempt aborts at the same point. Deleting the fragments forces one clean pass.

  1. Open an elevated Command Prompt and run net stop wuauserv and net stop bits.
  2. Open C:\Windows\SoftwareDistribution\Download and delete everything inside it.
  3. Run net start wuauserv and net start bits.
  4. Check for updates — the download restarts from zero, cleanly.

Fix 5: Run the troubleshooter for BITS

The Background Intelligent Transfer Service is the actual download engine, and the Windows Update troubleshooter knows how to interrogate and repair it specifically.

  1. Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters.
  2. Run the Windows Update troubleshooter and apply its recommendations.
  3. Restart the laptop fully afterward.
  4. Test the download on the stabilized connection.

Fix 6: Tune Delivery Optimization as a workaround

When the direct server path keeps aborting, alternate sources can succeed. Delivery Optimization lets the client pull pieces from local peers or Microsoft’s CDN endpoints differently, sometimes dodging the broken path.

  1. Go to Settings > Update & Security > Delivery Optimization.
  2. Ensure Allow downloads from other PCs is on, set to PCs on my local network.
  3. Retry the update — the client may now source chunks that complete.
  4. If it still aborts, turn the option off again to keep troubleshooting clean.

Fix 7: Fetch the failing package from the catalog

The browser is a far more resilient downloader than the update client — it resumes aggressively and tolerates interruptions. For the specific package that keeps aborting, the Microsoft Update Catalog is the pragmatic bypass.

  1. Identify the KB number from Update history.
  2. Download the matching x64 .msu from the Update Catalog.
  3. Double-click to install, then reboot when prompted.
  4. Return to Windows Update for the remaining smaller items, which usually download fine.

Fix 8: Update the network adapter drivers

Network drivers that predate your Windows build often mishandle sustained high-throughput transfers, dropping connections that casual browsing never stresses. Update downloads are the ultimate driver stress test, and fresh drivers from the manufacturer frequently end the abort cycle where all the settings tweaks failed.

  1. Open Device Manager and expand Network adapters.
  2. Identify your Wi-Fi and Ethernet adapters by exact model.
  3. Download the latest drivers from your laptop maker’s support page — not from Windows Update, which may offer the same old build.
  4. Install both, reboot, and retry the update download on the fresh drivers.
  5. If the laptop uses Intel wireless, cross-check with the Intel Driver & Support Assistant for the newest validated release.

Closing

On Windows 10, 0x80072EFE is a connection autopsy waiting to happen: stabilize the link, remove the middlemen, clear the wreckage, and downloads complete. Pay attention to the abort pattern — same-percentage failures scream intermediary, random failures scream flaky link — and you will fix it in half the steps. Once the queue is clear, you can put the VPN and proxy back; just remember they were suspects if the code ever returns. If you also manage Windows 11 machines, our 0x80072EFE Windows 11 guide covers the same repair there.

Frequently asked questions

Why does Windows 10 abort update downloads with 0x80072EFE?
The network connection was severed during the transfer. Common causes are unstable Wi-Fi, a VPN dropping mid-download, a proxy resetting the connection, antivirus terminating the stream, or a firewall closing the session between download chunks. Each cause leaves a slightly different abort pattern, so watch closely.
The download reaches a percentage then fails every time. Why?
Consistent failure at a similar point suggests either a marginal link that cannot sustain long transfers or an intermediary (proxy, VPN, security software) killing connections after a set time or size. Clearing partial downloads plus removing intermediaries usually breaks the pattern.
Could my router be causing 0x80072EFE?
Yes. Routers with aggressive connection timeouts, buggy firmware, or QoS rules that deprioritize background traffic can all abort long update downloads. A router firmware update or a temporary direct-modem test can confirm it. QoS rules meant for gaming can starve background update traffic specifically.
Does Delivery Optimization affect this error?
It can help work around it: peer-to-peer sources sometimes complete downloads the direct server path cannot. Our Windows 11 version of this fix covers the same ground with Windows 11 paths if you manage mixed machines.