80072EFE means the connection between your PC and the update servers was cut mid-conversation. Nothing is wrong with the updates themselves - something on the path is dropping the line: the router, a VPN or proxy, an overzealous firewall, or a corrupted update cache retrying a broken download forever. The checks below go from the most common cause to the rarest.
Quick answer
Restart the router (power off, 30 seconds, on) and disconnect any VPN or proxy, then check for updates again. If the error persists, temporarily disable third-party antivirus web protection and retry - and if that is not it, reset the update cache (method 3).
A router in a bad state, flaky Wi-Fi or an ISP hiccup cuts long HTTPS transfers - update downloads are long transfers.
VPNs and proxies reroute update traffic; some firewalls and antivirus web shields inspect it and break the connection mid-stream.
A half-downloaded package makes Windows retry the same broken transfer - clearing SoftwareDistribution forces a fresh start.
On long-unpatched systems (Windows 7 era) the update agent and certificates are too old to talk to today's servers - the same code appears for that deeper reason.
Re-enable protection right after the test - the point is to identify the cause, not to run unprotected.
net stop wuauserv and net stop bits.ren C:\Windows\SoftwareDistribution SoftwareDistribution.old.net start bits, net start wuauserv, then check for updates - the download starts clean.DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow; restart and retry.Outbyte PC Repair scans for more than 100 common problems - junk files, heavy background processes, vulnerabilities, privacy issues - and fixes them from one place. Useful when you would rather not run the tools above by hand, or want regular maintenance done automatically.
Download PC Repair Downloads Outbyte PC Repair for Windows 11, 10, 8 and 7. Free by-category trial included.Intermittent 80072EFE is the signature of an unstable path - flaky Wi-Fi, a struggling router or an ISP issue. Method 1 (and a wired connection for the update session) usually settles it.
Windows 7 stopped receiving regular updates in January 2020, and its stock update agent struggles to reach today's servers at all - the error is expected there. For a machine you still rely on, the realistic path is upgrading to a supported Windows.
Yes - "privacy" tweaks and some tools add Microsoft update hosts to the hosts file or a blocking DNS. Check C:\Windows\System32\drivers\etc\hosts for microsoft/windowsupdate entries and remove them, or switch DNS back to automatic.