Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Error Code | 0x8024402C (WU_E_PT_WINHTTP_NAME_NOT_RESOLVED) | Windows Update Log and CBS Log | Indicates DNS resolution failure for Microsoft Update servers. |
| Affected OS Builds | Windows 10 / Windows 11 | Microsoft Documentation | Applies to all relevant builds of Windows 10 and 11. |
| Registry Key | HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WUServer | Registry Editor | Check if WUServer points to a resolvable hostname. |
| Relevant URLs | windowsupdate.microsoft.com, update.microsoft.com, delivery.mp.microsoft.com | Windows Update Client Logs | Hostnames that must resolve for updates to proceed. |
| Log Signature | '0x8024402C' and 'WINHTTP_CALLBACK_STATUS_NAME_NOT_RESOLVED' | WindowsUpdate.log and CBS.log | Search logs for these strings to confirm the issue. |
Log Files to Check
C:\Users\%USERNAME%\Desktop\WindowsUpdate.logC:\Windows\Logs\CBS\CBS.log
What This Error Actually Means
The error code0x8024402C (WU_E_PT_WINHTTP_NAME_NOT_RESOLVED) indicates that the Windows Update client failed to resolve the DNS hostname of Microsoft's update servers. Specifically, the WinHttp component used by Windows Update encountered a WINHTTP_CALLBACK_STATUS_NAME_NOT_RESOLVED error when attempting to contact one or more of the following URLs:
windowsupdate.microsoft.comupdate.microsoft.comdelivery.mp.microsoft.com
Affected Versions and Scope
This error affects:- All builds of Windows 10 (from version 1607 onwards)
- Windows 11 (all versions)
- Windows Server operating systems (which use a different update mechanism)
- Non-Microsoft operating systems
Where To Look First: Logs and Event IDs
The error can be identified in the following logs:C:\Users\%USERNAME%\Desktop\WindowsUpdate.log: Generated by runningGet-WindowsUpdateLogin an elevated PowerShell session. Search for'0x8024402C'and'WINHTTP_CALLBACK_STATUS_NAME_NOT_RESOLVED'.C:\Windows\Logs\CBS\CBS.log: Search for'0x8024402C'if the error was triggered during a DISM operation.- Event Viewer (
eventvwr.msc): Filter by Source: WindowsUpdateClient and Event ID: 25 (update download failure). The event details will include the failing server hostname and the0x8024402Cresult code.
Root Causes
The following are the most common root causes for this error:1. DNS Resolution Failure
The DNS server assigned to the network interface cannot resolve the Microsoft Update hostnames. This could be due to:- A DNS server being offline or unreachable
- DNS records for the Microsoft Update servers being blocked or filtered
- Misconfigured DNS settings on the client or DNS server
2. Incorrect WinHTTP Proxy Configuration
A proxy is configured vianetsh winhttp show proxy that cannot resolve external hostnames. This could include:
- An invalid or unreachable proxy server
- Missing bypass rules for Microsoft Update domains
3. Misconfigured WSUS Policy
The Windows Update client is configured to use an internal WSUS server via theHKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WUServer registry key, but:
- The specified hostname cannot be resolved by DNS
- The WSUS server has been decommissioned or its DNS record removed
4. Incorrect DNS Suffix Search List
The client's DNS suffix search list is appending an incorrect domain suffix to the Microsoft Update hostnames, resulting in an invalid FQDN. This can be checked viaipconfig /all.
Fix Procedure
- Test DNS Resolution: Open PowerShell and run:
If these commands fail withResolve-DnsName -Name windowsupdate.microsoft.com -Type A Resolve-DnsName -Name delivery.mp.microsoft.com -Type A0x0000232B RCODE_NAME_ERROR, proceed to step 2. - Check WinHTTP Proxy Settings: Run:
If a proxy is configured, test resolution through it or add bypass rules:netsh winhttp show proxynetsh winhttp set proxy proxy-server=': ' bypass-list='*.microsoft.com;*.windowsupdate.com' - Verify WSUS Configuration: Check the WUServer registry key:
If WUServer points to an internal hostname, verify it resolves with:Get-ItemProperty 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate' | Select-Object WUServerResolve-DnsName - Check DNS Client Service: Ensure the DNS Client service is running:
If stopped, start it with:Get-Service -Name Dnscache | Select-Object Name, StatusStart-Service Dnscache - Flush DNS Cache: Run:
Then repeat the Resolve-DnsName tests.Clear-DnsClientCache - Update WSUS Hostname (if applicable): If WUServer is stale, update it via Group Policy:
- Open the Group Policy Management Editor
- Navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Update
- Edit "Specify intranet Microsoft update service location" and enter the correct WSUS URL
- Force a policy refresh with:
gpupdate /force
- Reset WinHTTP Proxy: If no proxy is needed, reset it:
netsh winhttp reset proxy - Restart Services and Update Components:
Restart-Service Dnscache Restart-Service wuauserv wuauclt.exe /detectnow - Verify via Windows Update: Open Settings > Windows Update and check for updates. Success is indicated by Event ID 19 in the WindowsUpdateClient event log.
- (Optional) Change DNS Servers Temporarily: If internal DNS is problematic, test with public DNS:
Remember to revert after testing.Set-DnsClientServerAddress -InterfaceAlias 'Ethernet' -ServerAddresses ('8.8.8.8','8.8.4.4')
Warning: Modifying the WUServer registry key or Group Policy without proper authorization can break Windows Update for enrolled devices. Always verify with your WSUS administrator before making changes.
Error Code Variants
| Error Code | Description | Distinguishing Feature |
|---|---|---|
0x8024401F |
WU_E_PT_WINHTTP_CONNECTION_REFUSED | TCP connection was refused after successful DNS resolution |
0x80072EFD |
ERROR_INTERNET_NAME_NOT_RESOLVED | Similar to 0x8024402C but occurs in different components (e.g., Internet Explorer) |
0x8024401D |
WU_E_PT_WINHTTP_TIMEOUT | Connection timed out after DNS resolution |
Verification
To confirm the fix:- Check for updates via Settings > Windows Update. Success is indicated by Event ID 19 in the WindowsUpdateClient event log.
- Verify DNS resolution with:
Ensure it returns public IP addresses (e.g., from Microsoft's infrastructure).Resolve-DnsName windowsupdate.microsoft.com - Inspect
C:\Windows\Logs\CBS\CBS.logfor the absence of new0x8024402Centries.
Prevention
To prevent recurrence:- Monitor DNS server health and configuration via Azure Monitor or other tools.
- Implement a maintenance schedule to verify WSUS hostname validity and update policies as needed.
- Ensure all clients have the correct DNS suffix search list configured via Group Policy or DHCP.
- Regularly test WinHTTP proxy configurations and bypass rules for Microsoft Update domains.
TIP: Use the DISM tool to verify component store health:
dism /online /Cleanup-Image /RestoreHealth
This can resolve underlying issues that may contribute to DNS resolution failures.