How to fix 0x8024402C and 0x8024A10A Windows Update connection errors
This means Windows Update cannot resolve or reach the update server, so it cannot connect. On a normal PC that is a network or proxy problem; on a managed PC it usually means the WSUS server. Jump to your situation below or work through the methods in order.
By Neeraj Singh ~7 min Updated Jun 2026 89% found this helpful
Error message
0x8024402C WU_E_PT_WINHTTP_NAME_NOT_RESOLVED. The proxy or target server name cannot be resolved. (0x8024A10A: the update service was shutting down.)
Summary
0x8024402C (WU_E_PT_WINHTTP_NAME_NOT_RESOLVED) means Windows Update could not resolve the name of the update server or proxy, so it could not connect. On a PC that connects directly to Windows Update this points at a network, DNS or proxy problem. On a PC managed by WSUS it usually means the configured WSUS server name cannot be reached. The closely related 0x8024A10A means the Update Orchestrator service was shutting down in the middle of the operation. Both are connection-and-state issues rather than file corruption. The fix is to confirm the PC has working internet and name resolution, check and reset a bad proxy, correct or temporarily remove a wrong WSUS setting, account for a VPN or firewall, and for 0x8024A10A simply restart and retry.
What this error means
Before it can do anything, Windows Update has to connect to a server, either Microsoft's Windows Update endpoints or an internal WSUS server. 0x8024402C is the WinHTTP layer reporting that it could not resolve that server's name, the same as a browser failing to find a website, so the update never gets off the ground.
On a home PC that means DNS, the internet connection, or a proxy is the problem. On a work PC it usually means the WSUS server name is wrong or unreachable. The sibling code 0x8024A10A is different in nature, it means the update orchestrator was shutting down mid-operation, which a restart and retry resolves.
Common causes
No internet connection, or a DNS resolution failure.
A misconfigured or stale proxy setting.
A wrong or unreachable WSUS server setting on a managed PC.
The WinHTTP proxy points at a server that is gone.
A VPN or firewall blocks name resolution to the update hosts.
The Update Orchestrator service shut down mid-operation (0x8024A10A).
Transient network loss during the update check.
Expert insight
“0x8024402C is the update equivalent of a browser saying site not found, it could not resolve the server name. So I treat it like any connection problem: can the machine reach the internet and resolve names at all? On a work laptop, nine times out of ten it is WSUS, the policy points at a server that is renamed or down. And the lookalike 0x8024A10A is a red herring, that just means the update service was shutting down, so a reboot and retry clears it.”
Manager, Tech Support & Operations · 19+ years fixing Windows and system errors
✓ How to fix it
Method 1
Confirm internet and name resolution
1Open a website to confirm the PC is online, and check that names resolve (run nslookup microsoft.com).
2Fix the connection, Wi-Fi or DNS first if either fails.
3Windows Update cannot start until it can reach a server.
Method 2
Check and reset the proxy
1Reset the WinHTTP proxy that Windows Update uses:
netsh winhttp reset proxy
2Then check Settings, Network and internet, Proxy for a wrong manual proxy.
3If you use a proxy, import it: netsh winhttp import proxy source=ie.
Method 3
Check the WSUS setting on a managed PC
1On a work PC, the policy may point at a WSUS server that is renamed or down.
2Verify the WUServer value, or temporarily remove the WSUS policy so the PC uses Windows Update directly.
3Ask your administrator if it is managed.
Method 4
Account for a VPN or firewall
1Disconnect a VPN and confirm the firewall or web filter is not blocking the update hosts.
2A tunnel or filter can stop name resolution to the servers.
3Retry after disconnecting.
Method 5
For 0x8024A10A, restart and retry
10x8024A10A means the update service was shutting down mid-operation.
2Restart the PC, then run Check for updates again.
3This alone clears that sibling code.
Method 6
Reset Windows Update components
1If the connection is fine but it still fails, reset the update components and clear the cache.
2Restart the services and retry.
0x8024402C is a connection problem, not corruption, so confirm the PC can reach the internet and resolve names first. On a managed PC, suspect a wrong or unreachable WSUS server before anything else. Treat 0x8024A10A separately, it just means the update service was shutting down, so a restart and retry is the fix.
Frequently asked questions
What does error 0x8024402C mean?
WU_E_PT_WINHTTP_NAME_NOT_RESOLVED means Windows Update could not resolve the name of the update server or proxy, so it could not connect. It is a network, DNS, proxy or WSUS problem.
How do I fix it on a home PC?
Confirm the PC is online and can resolve names, then reset the WinHTTP proxy with netsh winhttp reset proxy and clear any wrong manual proxy in Settings, and retry.
Why does it happen on a work PC?
It usually means the WSUS server the policy points at is renamed or unreachable. Verify the WUServer setting, or temporarily remove the WSUS policy so the PC uses Windows Update directly.
What is 0x8024A10A?
It means the Update Orchestrator service was shutting down in the middle of the operation. A restart and retry of Check for updates clears it; it is not a connection fault.
Could a VPN cause 0x8024402C?
Yes. A VPN or firewall can block name resolution to the update hosts. Disconnect the VPN, confirm the firewall allows the update hosts, and retry.
How do I reset the proxy Windows Update uses?
Run netsh winhttp reset proxy from an elevated prompt to clear the WinHTTP proxy, then re-import your proxy if you use one with netsh winhttp import proxy source=ie.
Still not working?
If name resolution works in a browser but Windows Update still fails, the WinHTTP proxy or a WSUS policy is still pointing somewhere wrong. Compare the WinHTTP proxy (netsh winhttp show proxy) with your working browser proxy, and clear any stale WSUS registry values. You can also submit your error to us for a tailored fix.
