Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Windows Update error 0x8024402C: the proxy or WSUS server name cannot be resolved

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

A Windows Update scan that fails with 0x8024402C could not turn a server name into an address. Microsoft's Windows Update error list gives the code as WU_E_PT_WINHTTP_NAME_NOT_RESOLVED, "Same as ERROR_WINHTTP_NAME_NOT_RESOLVED - The proxy server or target server name cannot be resolved." The name that fails is either the proxy the client is told to use, or the WSUS server the client is told to scan.

Two settings decide that: the WinHTTP proxy on the client, and the WSUS server name in policy. Read both before you change either. Microsoft documents a fix for each, and applying the wrong one leaves the fault in place.

What the error means

The Windows Update Agent uses WinHTTP to scan for updates. Microsoft's configuration page for scan failures puts 0x8024402C among four errors "caused by proxy-related issues" (0x80244021, 0x8024401B, 0x80240030 and 0x8024402C) and describes this one as "The proxy server or target server name cannot be resolved". It says that when a proxy sits between the client and the WSUS computer, the proxy settings must be correct on the clients so they can talk to WSUS "by using the computer's FQDN".

Microsoft's page on proxy detection explains where the client gets its proxy. The Automatic Updates service runs as Local System and can only discover a proxy in two ways: one set manually with the Netsh command, or Web Proxy Auto Detect (WPAD) settings published in DNS or DHCP. For the scan itself, the system proxy (WinHTTP) is tried first. If the Windows Update Agent fails to reach the service because of certain proxy, service or authentication errors, the user proxy is then tried; Microsoft says that is generally the signed-in user's Internet Explorer settings. For an intranet WSUS server, the "Specify intranet Microsoft update service location" setting is used to choose the proxy behaviour.

An archived Microsoft support-team blog post covers the other half. When a client's WindowsUpdate.log shows "WARNING: Send failed with hr = 80072ee7." followed by "error 0x8024402c", Microsoft's post gives the cause as "an incorrect WSUS server name (FQDN)" set through Group Policy or the client registry, and the resolution as "correct the server name used by the clients".

Likely causes

Cause What you see How to confirm
WSUS server name in policy or registry is wrong Client shows 0x8024402C; clients are missing from the WSUS console Read WUServer and WUStatusServer and try to resolve and browse to the name
WinHTTP proxy points to a name that does not resolve Scan fails; the proxy host name is stale or mistyped netsh winhttp show proxy lists a proxy name that does not resolve
WinHTTP proxy copied from Internet Explorer settings no longer matches WinINET and WinHTTP settings differ Microsoft says WinHTTP settings "aren't necessarily the same" as Internet Explorer settings; compare them
WPAD in DNS or DHCP hands the client a proxy it cannot resolve A proxy name in the client's settings that nobody entered by hand Check the WPAD record in DNS and the WPAD option in DHCP; Microsoft lists these as the two WPAD sources the service uses

Prove the cause before changing anything

All of these checks only read. Run them on a client that fails, in an elevated command prompt.

  1. Show the WinHTTP proxy:
netsh winhttp show proxy
  1. Read the WSUS server name the client has been given. Microsoft's pages name the key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate and the values WUServer and WUStatusServer:
reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v WUServer
reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v WUStatusServer
  1. Browse to the three addresses Microsoft gives as the connectivity test, replacing the server name with your own: http://SUPSERVER.CONTOSO.COM:8530/Selfupdate/wuident.cab, http://SUPSERVER.CONTOSO.COM:8530/ClientWebService/wusserverversion.xml and http://SUPSERVER.CONTOSO.COM:8530/SimpleAuthWebService/SimpleAuth.asmx. Microsoft's page says that if any test fails, you should "check for name resolution issues on the client" and "Verify that you can resolve the FQDN of the WSUS computer". The page names no command for that check; use the name-lookup tool your team already uses.

Write down what each command returns. Those values are the way back for the fixes below.

Example (illustrative): at contoso.com.au the Group Policy sets WUServer to http://wsus1.contoso.com.au:8530, but the server is called wsus01. Clients on 10.0.20.0/24 fail with 0x8024402C and do not appear in the WSUS console. netsh winhttp show proxy reports direct access, so the proxy is not the problem, and the name in WUServer does not resolve. That points to the policy fix.

Fix

Make only the change your checks point to.

The WSUS server name is wrong

Before you change it, record the current policy values from the reg query output above, and note whether the policy is Enabled, Disabled or Not Configured.

Risk: the next steps change which server every client under this Group Policy Object scans for updates. A wrong name sends all of them to a server that does not exist.

Microsoft's post gives the Group Policy route:

  1. In the Group Policy Object Editor, expand Computer Configuration, then Administrative Templates, then Windows Components, then Windows Update.
  2. In the details pane, select "Specify intranet Microsoft update service location".
  3. Select Enabled. Type the HTTP(S) URL of the WSUS server in the "Set the intranet update service for detecting updates" box and in the "Set the intranet statistics server" box, using the same address in both. Microsoft's example is http(s)://servername. If the port is not 80 for HTTP or 443 for HTTPS, add it, for example https://servername:portnumber.
  4. Select OK.

To undo it: open the same policy and put back the values and the Enabled, Disabled or Not Configured state you recorded.

For a computer set up through the registry and not through policy, Microsoft says WUServer and WUStatusServer are REG_SZ values that "must be set to the same value in order for them to be valid". Microsoft's post gives no command for editing them, so use the same Group Policy route where you can.

The WinHTTP proxy is wrong

Before you change it, record the output of the first command in the checks above, netsh winhttp show proxy. Note the proxy name, port and any bypass list. Microsoft's pages give a command for the name and port only, so a bypass list shown in the output cannot be restored with the commands below; if one is listed, change the proxy only after you know how that list was set.

Risk: the next command changes the system-wide WinHTTP proxy on that client. Other services on the machine that use WinHTTP will also use the new setting, and Microsoft's page does not list them.

Microsoft's pages give three ways to change it. To configure direct access to the internet, which removes the proxy:

netsh winhttp reset proxy

To set a named proxy, replace the placeholders with the proxy's fully qualified name and port (Microsoft's example is proxy.domain.example.com:80):

netsh winhttp set proxy <proxyservername>:<portnumber>

Microsoft's scan-failure page adds a third: where the Internet Explorer proxy is correct, you can import it:

netsh winhttp import proxy source =ie

Use one of the three, not all of them.

To undo it, run the command that matches the output you recorded. If the output said direct access:

netsh winhttp reset proxy

If the output listed a proxy, enter the name and port you recorded:

netsh winhttp set proxy <proxyservername>:<portnumber>

Microsoft's scan-failure page also says "In most cases, you can bypass the proxy for local addresses because the WSUS computer is located within the intranet." The page gives no command for a bypass list.

Confirm the fix

  • Run netsh winhttp show proxy again and compare it with what you wrote down.
  • Browse to the three test addresses; each should respond without a name-resolution error.
  • Trigger a scan. Microsoft's post says that after the server name is corrected "clients should start showing up in the WSUS console and installing updates".
  • Check WindowsUpdate.log: the 0x8024402c lines should stop.

What to watch afterwards

  • Clients that did not change. A policy fix reaches a client only when it applies the policy, so some clients may still fail for a time.
  • A proxy that is handed out by WPAD. Microsoft names DNS and DHCP as the two sources; a corrected client can pick up a bad proxy again from either.
  • Code 0x8024401B (proxy authentication required) or 0x80244021 (bad gateway) next, because Microsoft groups them with this one as proxy-related.

Risks and limits

These commands have not been run or lab-tested.

The archived post on 0x8024402c was written in 2008 for the WindowsUpdate.log format of that time, and it sits in Microsoft's blog archive; the registry key in it is the same one the current scan-failure page refers to. Microsoft's pages describe the proxy detection order but give no version range for the netsh winhttp import proxy command beyond "Windows Vista and later". Microsoft's pages do not cover third-party proxy products or TLS inspection.

Sources