Windows Update error 0x80072EFD

Windows Update error 0x80072EFD appears when Windows tries to check for or download updates and cannot reach the Microsoft update servers. The code is the system's network error ERROR_INTERNET_CANNOT_CONNECT (12029), produced by the WinINet connection layer. Unlike errors that point at damaged files, 0x80072EFD almost always means a networking problem: the PC looked for the update server and no connection could be established, so the download never started.

What it means

Windows Update does not download updates directly from a single address. It first resolves the update host names over DNS, then opens a secure HTTPS connection, and finally transfers the files through the Background Intelligent Transfer Service (bits). Error 0x80072EFD is raised at the very first of these steps: the connection attempt itself failed. Because the failure happens at the transport layer, it says nothing about whether the updates themselves are correct — only that the machine could not talk to the server.

Several things can sit between your PC and the update server and break that connection. A proxy server configured in Internet Options may be down or wrong. A firewall or third-party security suite may be blocking the update hosts. A VPN can route the traffic through a network that filters it. A stale DNS cache or a misconfigured DNS server can send the lookup nowhere. And a corrupted WinHTTP proxy setting, left behind by an old installer, is a surprisingly common culprit.

Because the cause sits on the network path, the same code can appear on a home PC after a router change, or on a business PC behind a strict firewall. The correct approach is to work outwards: confirm the internet works at all, then the proxy, then DNS, then the local firewall. A quick sanity check is to open a normal website — and, if you can, the update host in a browser; if that also fails, the problem is system-wide rather than specific to Windows Update, which tells you to repair the connection before touching any update components.

Common causes

• No working internet connection, or the network dropping mid-download.
• A wrong or unreachable proxy server configured in Windows.
• A firewall, VPN or third-party security suite blocking the update servers.
• DNS problems — a stale cache or an unreachable DNS server.
• The Background Intelligent Transfer Service (bits) is stopped.

How to fix it

1. Check the basics. Confirm that other websites load and that the date and time are correct. A wrong clock makes secure connections fail before they even begin.
2. Clear the proxy settings. If you do not use a proxy, remove it under Settings › Network & Internet › Proxy and turn off any manual proxy. From an elevated prompt you can also run:

   netsh winhttp reset proxy

3. Flush DNS and reset the network stack. In an elevated prompt run:

   ipconfig /flushdns
   netsh winsock reset
   netsh int ip reset

   Then reboot the PC.
4. Make sure BITS is running:

   sc config bits start= delayed-auto
   sc start bits

5. Rule out security software. Temporarily disable the VPN, firewall or third-party antivirus and retry, re-enabling them afterwards. Then run the troubleshooter under Settings › System › Troubleshoot › Other troubleshooters and choose Windows Update.

How to prevent it

Keep Windows' networking at its defaults. If you do not need a proxy, do not set one; if you use one at work, ask IT for the correct address so the background service is not handed a proxy that breaks on authentication. Prefer a stable, trusted network for large updates, because a flaky connection that drops mid-download is one of the most common triggers for this error.

Avoid stacking security tools. Running two firewalls or an aggressive web filter often blocks the update endpoints, producing 0x80072EFD on an otherwise healthy PC. Keep Microsoft Defender as your primary protection unless you have a clear reason to replace it. Finally, keep your router firmware and DNS settings sensible, and if a single PC fails while others on the same network update fine, focus on that PC's proxy and BITS settings rather than the router.