Fix it now
0x8024402C is WU_E_PT_WINHTTP_NAME_NOT_RESOLVED: the proxy server or target server name cannot be resolved. It is a name resolution failure, not a blocked port. A firewall dropping traffic produces a timeout or a connect failure and a different code.
reg query HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /v WUServer
nslookup wsus.contoso.local
netsh winhttp show proxy
gpupdate /force
- Read the WUServer value first. That is the name the client is actually trying to resolve, and it is frequently not the name anyone expects.
- If nslookup fails on that name, you have the whole answer and nothing else in this article applies. Fix DNS or correct the policy.
- Read the
netsh winhttp show proxyoutput. The update service runs under the system account and uses the WinHTTP proxy configuration, which is not the one in your browser. An empty configuration on a network that requires a proxy fails exactly like this. - If the value is wrong, import a working configuration with
netsh winhttp import proxy source=ie, or clear it withnetsh winhttp reset proxyif the machine should go direct. - Restart the update service and check for updates.
Changing the WinHTTP proxy affects every service running as the system account, not just Windows Update. Note the existing value before you overwrite it.
If the name resolves and a scan completes, you are done. The next section covers the codes people confuse with this one, which point at different layers entirely.
Why it happens
The update client resolves and connects using the WinHTTP stack under the system account. That is the detail that catches most people. The proxy settings in your browser belong to your user profile and are irrelevant here. The update service has its own proxy configuration, set through netsh winhttp or through policy, and if that configuration is empty on a network that requires a proxy, every connection attempt dies before it starts.
0x8024402C is WU_E_PT_WINHTTP_NAME_NOT_RESOLVED, the same condition as ERROR_WINHTTP_NAME_NOT_RESOLVED: the proxy server or target server name cannot be resolved. That is strictly a name resolution failure. A blocked port, a dropped packet or an unreachable subnet produces a timeout or a connect failure, and those carry different codes. If you go looking for a firewall rule because of this code, you are looking in the wrong layer.
The second place a client is pointed at nothing is the policy itself. WSUS is normally addressed by a host name written into policy years ago. If the server was renamed, moved behind a load balancer, or the DNS suffix search order on the client changed, the name stops resolving while the policy stays exactly as it was. The client dutifully tries, fails at DNS, and reports the same code forever without telling you which name it could not resolve. Reading WUServer out of the registry is what tells you.
The companion codes narrow things down, and one of them is routinely stated backwards. 0x8024401C is WU_E_PT_HTTP_STATUS_REQUEST_TIMEOUT, the same as HTTP 408, which is the server reporting that it timed out waiting for the request. That is the server’s clock running out, not the client’s. 0x8024401B is HTTP 407, a proxy demanding authentication the system account cannot supply. 0x8024400A is the SOAP client failing to parse the server’s response, which usually means something other than WSUS answered: a captive portal or a proxy error page.
The WSUS host name no longer resolves
You have this one if nslookup on the name from WUServer fails, while general browsing works.
- Confirm the correct current name and port of the WSUS server with whoever runs it.
- Correct the ‘Specify intranet Microsoft update service location’ policy under Computer Configuration – Administrative Templates – Windows Components – Windows Update rather than editing each client.
- Run
gpupdate /forceon a test client, then confirm the registry value now holds the right URL. - Clear the resolver cache with
ipconfig /flushdnsand retry the scan.
Use a fully qualified name in the policy. A short name relies on the client’s DNS suffix search list, which differs between domain-joined and workgroup machines and is a common reason one group of clients fails while another does not.
The system account has no working proxy configuration
You have this one if Browsing works when you are signed in, but netsh winhttp show proxy reports no proxy or the wrong one.
- Set the proxy explicitly:
netsh winhttp set proxy proxy-server="http=proxy:8080;https=proxy:8080" bypass-list="*.contoso.local". - Add the WSUS server to the bypass list. Microsoft’s own guidance is that in most cases you can bypass the proxy for local addresses, because the WSUS computer is inside the intranet.
- If the machine should not use a proxy at all, clear it with
netsh winhttp reset proxy, which resets the setting to DIRECT. - Restart the update service and rescan.
The proxy demands credentials the service cannot give
You have this one if 0x8024401B, and the proxy logs show authentication challenges against a machine account or an anonymous request.
- Configure the proxy to allow the update endpoints without user authentication. Microsoft’s mitigation for this code is to verify with the network and proxy teams that the device can access the update source without the proxy requiring user authentication.
- Where your proxy supports integrated authentication with machine accounts, permit the computer accounts rather than storing user credentials in a service.
- As an alternative, bypass the proxy for update traffic at the firewall.
- Retest with
netsh winhttp show proxyand a scan.
The URL resolves but the port is wrong
You have this one if nslookup succeeds and Test-NetConnection on the URL’s port returns false.
- Confirm which port WSUS is listening on. Since Windows Server 2012 the defaults are 8530 for HTTP and 8531 for HTTPS.
- Correct the policy URL if it still specifies port 80 from an older deployment.
- Open that port from the client subnets to the WSUS server.
- Retest the port, then rescan. Note that a blocked port does not produce 0x8024402C; if that is still the code you are seeing, the name is still the problem.
Something other than WSUS is answering
You have this one if 0x8024400A or 0x8024402F, and opening a WSUS test URL in a browser returns a login page, a portal or a proxy error rather than content.
- Open
http://<server>:8530/ClientWebService/wusserverversion.xmlfrom the client and read what actually comes back. - If a captive portal or proxy page appears, the traffic is being intercepted. Add the WSUS host to the proxy bypass list.
- For 0x8024402F specifically, Microsoft names Lightspeed Rocket web filtering as a cause and says to add the affected devices to that product’s exceptions list.
- If a certificate warning appears on an HTTPS deployment, fix the certificate name or trust chain before anything else. Clients will not proceed past it.
Full reference
The six codes, and which layer each belongs to
| Code | Published name | Layer |
|---|---|---|
| 0x8024402C | WU_E_PT_WINHTTP_NAME_NOT_RESOLVED | Name resolution: the proxy server or target server name cannot be resolved |
| 0x8024401C | WU_E_PT_HTTP_STATUS_REQUEST_TIMEOUT | HTTP 408: the server timed out waiting for the request |
| 0x8024401B | WU_E_PT_HTTP_STATUS_PROXY_AUTH_REQ | HTTP 407: proxy authentication is required |
| 0x8024402F | WU_E_PT_ECP_SUCCEEDED_WITH_ERRORS | External .cab file processing completed with some errors. Microsoft names Lightspeed Rocket web filtering as a cause |
| 0x8024400A | WU_E_PT_SOAPCLIENT_PARSE | The SOAP client failed to parse the response from the server |
| 0x8024043C | Not published | Absent from Microsoft’s Windows Update error reference. Read the update log for the failing URL rather than the code |
netsh winhttp, precisely
| Command | Documented behaviour |
|---|---|
netsh winhttp show proxy |
Displays the current basic proxy settings for WinHTTP, including any bypass list |
netsh winhttp set proxy proxy-server=<server> bypass-list=<hosts> |
Sets the proxy and an optional bypass list. Entries are separated by semicolons; an empty string bypasses the proxy for all short-name hosts |
netsh winhttp reset proxy |
Resets the WinHTTP proxy setting to DIRECT |
netsh winhttp import proxy source=ie |
Imports proxy settings into the WinHTTP configuration from the Internet Explorer settings |
netsh winhttp show proxy
netsh winhttp set proxy proxy-server="http=proxy.contoso.local:8080;https=proxy.contoso.local:8080" bypass-list="*.contoso.local;wsus.contoso.local"
netsh winhttp reset proxy
The policy the client is reading
| Path | Value | What it does |
|---|---|---|
HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate |
WUServer |
The intranet update server the client scans against, set by HTTP name |
HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate |
WUStatusServer |
The server the client uploads statistics to. Both are set by the same policy and both must be present |
HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU |
UseWUServer |
REG_DWORD. 1 makes Automatic Updates use the intranet server rather than Windows Update |
Both server values come from the same Group Policy setting, ‘Specify intranet Microsoft update service location’, under Computer Configuration – Administrative Templates – Windows Components – Windows Update. They can point at the same server. Correct them there rather than in the registry, because a local edit is overwritten at the next policy refresh.
Confirming the path end to end
- Read
WUServerfrom the policy branch. That is the name in play. - Resolve it with
nslookup. A failure here is the answer to 0x8024402C. - Test the port with
Test-NetConnection <server> -Port 8530, using 8531 for HTTPS. - Open
http://<server>:8530/ClientWebService/wusserverversion.xmlfrom the client’s browser and confirm content comes back rather than a portal or an error page. - Check
netsh winhttp show proxyand confirm the system account’s configuration matches what the network requires. - Run
Get-WindowsUpdateLogand search the generated log for the host name, which shows the URL that failed and how.
Ports, so the URL and the firewall agree
Since Windows Server 2012, WSUS uses 8530 for HTTP and 8531 for HTTPS by default. The pairing is fixed: if the HTTP port is 80 the HTTPS port must be 443, and if the HTTP port is anything else the HTTPS port follows the same scheme. Where HTTPS is configured the HTTP port still has to remain open, because some data such as update licence terms is served unencrypted. A policy URL that names the wrong port is a common inheritance from an older deployment, and it produces a 404 rather than this code.
Why the browser works and Windows Update does not
They use different proxy configurations, and this is the single most common surprise in this article. Your browser uses your user profile’s settings. The update service uses the system account’s WinHTTP configuration. They are set separately, they routinely disagree, and proving that the site loads in your browser proves nothing about what the service can reach. netsh winhttp show proxy is the only reading that matters here.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x8024402C |
WU_E_PT_WINHTTP_NAME_NOT_RESOLVED: the proxy server or target server name cannot be resolved. A name resolution failure, not a blocked port | Microsoft Learn |
0x8024401C |
WU_E_PT_HTTP_STATUS_REQUEST_TIMEOUT: the same as HTTP 408, the server timed out waiting for the request | Microsoft Learn |
0x8024401B |
WU_E_PT_HTTP_STATUS_PROXY_AUTH_REQ: the same as HTTP 407, proxy authentication is required | Microsoft Learn |
0x8024402F |
WU_E_PT_ECP_SUCCEEDED_WITH_ERRORS: external .cab file processing completed with some errors. Microsoft names Lightspeed Rocket web filtering as a cause | Microsoft Learn |
0x8024400A |
WU_E_PT_SOAPCLIENT_PARSE: the SOAP client failed to parse the response from the server | Microsoft Learn |
0x8024043C |
Seen on clients that cannot complete a scan against an update server. Microsoft’s Windows Update error reference does not carry this value, so read the update log for the failing URL rather than working from the code | not published by the vendor |
Confirm the fix worked
- Run
nslookupon the WSUS host name from the client and confirm it resolves to the expected address. - Run
Test-NetConnection <server> -Port 8530and confirm it succeeds. - Open the client web service test URL in a browser on the client and confirm content loads rather than a portal or error page.
- Run
netsh winhttp show proxyand confirm the system account’s configuration is what you intended. - Trigger a scan and confirm the client appears in the WSUS console with a current last-contact time.
Questions people ask about this
Does 0x8024402C mean a firewall is blocking WSUS?
No. It is WU_E_PT_WINHTTP_NAME_NOT_RESOLVED: the proxy server or target server name cannot be resolved. That is DNS. A blocked port produces a timeout or a connect failure with a different code, so if you go hunting for a firewall rule on the strength of this code you are in the wrong layer.
Why does the browser work when Windows Update does not?
Because they use different proxy configurations. Your browser uses your user profile’s settings; the update service runs as the system account and uses the WinHTTP configuration. They are set separately and routinely disagree. Read netsh winhttp show proxy rather than trusting the browser.
Which way round is 0x8024401C?
It is HTTP 408, and the published wording is that the server timed out waiting for the request. That is the server’s patience running out, not the client’s. It points at what is between the client and the server rather than at a slow server.
Is there anything to buy here?
No. This is name resolution, ports and proxy configuration on infrastructure you already run. No licence changes any of it. If the machine also fails activation, that is a separate matter with its own codes.
How do I see which URL the client tried?
Run Get-WindowsUpdateLog in PowerShell and search the generated log for the host name from your policy. It records the URL and the failure against it, which is more use than the code on its own.
