Windows Update error 0x80072ee2, explained and fixed

0x80072ee2 is a timeout: the update client waited for Microsoft’s servers and heard nothing back in time (the WinINet/WinHTTP timeout, ERROR_INTERNET_TIMEOUT). It appears while checking for or downloading updates, and it is the most transient code on this page: busy servers and busy networks both produce it.

The fix, in order

  1. Wait and retry. On Patch Tuesday and the days after, Microsoft’s servers are saturated and this code appears on healthy PCs. Trying again in a few hours is a legitimate first fix, not a cop-out.
  2. Restart the PC and the router. Clears stalled network state at both ends of the connection.
  3. Use a wired connection if you can, and pause other heavy traffic. A weak Wi-Fi signal plus streaming or cloud backups on the same network starve the update download into timing out.
  4. Temporarily disable third-party antivirus and firewall web filtering. HTTPS inspection features can stall update traffic specifically. Test once with them off; Windows Firewall and Windows Security remain in place.
  5. Flush DNS and reset the WinHTTP proxy. Admin Command Prompt: ipconfig /flushdns, then netsh winhttp reset proxy. Stale resolution and proxy data can send update requests into a dead end.
  6. Run the Windows Update troubleshooter. Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run. It catches stopped services, cache problems, and registration faults automatically.

If it still happens

If the timeout is permanent on this PC but other devices update fine, reset the Windows Update components (the standard stop-services, rename SoftwareDistribution and catroot2, restart-services procedure) and run DISM/SFC. On a work or school PC, WSUS or proxy policies may route updates to an internal server that is down, which only the network’s administrators can fix.

Common questions

Is 0x80072ee2 my fault or Microsoft’s? Either, and the timing tells you which. Right after the monthly updates land, it is usually server load and clears itself. If it persists for days on a quiet network, it is local: filtering software, DNS, or the connection itself.

Why does the download restart from zero after this error? Update downloads resume where possible, but a timeout during certain stages discards the partial state for safety. A stable wired connection and retrying off-peak are the practical counters.

Related errors

Windows Update error 0x800705b4 · Windows Update error 0x8024402c · Windows Update error 0x80072f8f