Windows Update error 0x8024402c, explained and fixed

0x8024402c is WU_E_PT_WINHTTP_NAME_NOT_RESOLVED: the Windows Update client could not resolve the name of Microsoft’s update servers, a DNS or proxy problem, not a broken update. It appears at the very start, when checking for updates, before any download begins.

The fix, in order

  1. Confirm ordinary browsing works, then retry. If the web is fine but updates fail with this code, the fault is in the update client’s own network path, which the next steps clear.
  2. Remove proxy settings. Settings → Network and internet → Proxy: turn off any manual proxy you do not deliberately use. Then in an admin Command Prompt run netsh winhttp reset proxy to clear the separate WinHTTP proxy the update client actually uses.
  3. Flush the DNS cache. Admin Command Prompt: ipconfig /flushdns. A poisoned or stale cache entry for the update servers produces exactly this code.
  4. Check the hosts file. Open C:\Windows\System32\drivers\etc\hosts in Notepad. Entries mapping Microsoft or update domains to 0.0.0.0 or a local address (sometimes left by blocking tools or malware) override DNS and break name resolution for updates; remove them.
  5. Disconnect the VPN, or test another network. VPN DNS handling and restrictive networks (hotel, school, some workplaces) can fail to resolve the update endpoints. A phone hotspot test separates network causes from PC causes cleanly.

If it still happens

If the PC resolves names nowhere (browsers also failing), the network adapter’s DNS settings are the problem: set DNS to automatic in the adapter properties, restart the router, and run a full malware scan, since DNS hijacking is a known trick. If only this PC on an otherwise healthy network still fails, the component reset on other pages plus DISM/SFC are the remaining steps.

Common questions

Why do websites work while updates get 0x8024402c? Because the update client resolves names through WinHTTP with its own proxy configuration, separate from the browser’s. A stale WinHTTP proxy or a hosts-file entry can break the update client’s resolution while the browser, using different settings, sails on.

Can my router or ISP cause this? Yes, if their DNS fails on Microsoft’s update domains or the network filters them. Switching the PC temporarily to a phone hotspot is the fastest way to prove it: if updates check fine there, the home network’s DNS or filtering is the culprit.

Related errors

Windows Update error 0x80072ee2 · Windows Update error 0x80072f8f · Windows Update error 0x80070422