Home › Windows Update › 0x8024402C

Windows Update · 0x8024402C · Windows 10 / Windows 11

Windows Update Error 0x8024402C - DNS Resolution Failure

The error occurs due to failed DNS resolution of Microsoft Update servers. Fix by resolving DNS issues, updating WSUS settings, or clearing cache.

Error Details

FactValueSourceNote
Error Code0x8024402C (WU_E_PT_WINHTTP_NAME_NOT_RESOLVED)Windows Update Log and CBS LogIndicates DNS resolution failure for Microsoft Update servers.
Affected OS BuildsWindows 10 / Windows 11Microsoft DocumentationApplies to all relevant builds of Windows 10 and 11.
Registry KeyHKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WUServerRegistry EditorCheck if WUServer points to a resolvable hostname.
Relevant URLswindowsupdate.microsoft.com, update.microsoft.com, delivery.mp.microsoft.comWindows Update Client LogsHostnames that must resolve for updates to proceed.
Log Signature'0x8024402C' and 'WINHTTP_CALLBACK_STATUS_NAME_NOT_RESOLVED'WindowsUpdate.log and CBS.logSearch logs for these strings to confirm the issue.

Log Files to Check

What This Error Actually Means

The error code 0x8024402C (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: This issue occurs before any TCP connection is attempted, meaning the problem lies in DNS resolution rather than network connectivity or server availability.

Affected Versions and Scope

This error affects: It does not affect:

Where To Look First: Logs and Event IDs

The error can be identified in the following logs:
  1. C:\Users\%USERNAME%\Desktop\WindowsUpdate.log: Generated by running Get-WindowsUpdateLog in an elevated PowerShell session. Search for '0x8024402C' and 'WINHTTP_CALLBACK_STATUS_NAME_NOT_RESOLVED'.
  2. C:\Windows\Logs\CBS\CBS.log: Search for '0x8024402C' if the error was triggered during a DISM operation.
  3. 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 the 0x8024402C result 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:

2. Incorrect WinHTTP Proxy Configuration

A proxy is configured via netsh winhttp show proxy that cannot resolve external hostnames. This could include:

3. Misconfigured WSUS Policy

The Windows Update client is configured to use an internal WSUS server via the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\WUServer registry key, but:

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 via ipconfig /all.

Fix Procedure

  1. Test DNS Resolution: Open PowerShell and run:
    Resolve-DnsName -Name windowsupdate.microsoft.com -Type A
    Resolve-DnsName -Name delivery.mp.microsoft.com -Type A
    If these commands fail with 0x0000232B RCODE_NAME_ERROR, proceed to step 2.
  2. Check WinHTTP Proxy Settings: Run:
    netsh winhttp show proxy
    If a proxy is configured, test resolution through it or add bypass rules:
    netsh winhttp set proxy proxy-server=':' bypass-list='*.microsoft.com;*.windowsupdate.com'
  3. Verify WSUS Configuration: Check the WUServer registry key:
    Get-ItemProperty 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate' | Select-Object WUServer
    If WUServer points to an internal hostname, verify it resolves with:
    Resolve-DnsName 
  4. Check DNS Client Service: Ensure the DNS Client service is running:
    Get-Service -Name Dnscache | Select-Object Name, Status
    If stopped, start it with:
    Start-Service Dnscache
  5. Flush DNS Cache: Run:
    Clear-DnsClientCache
    Then repeat the Resolve-DnsName tests.
  6. 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
  7. Reset WinHTTP Proxy: If no proxy is needed, reset it:
    netsh winhttp reset proxy
  8. Restart Services and Update Components:
    Restart-Service Dnscache
    Restart-Service wuauserv
    wuauclt.exe /detectnow
  9. Verify via Windows Update: Open Settings > Windows Update and check for updates. Success is indicated by Event ID 19 in the WindowsUpdateClient event log.
  10. (Optional) Change DNS Servers Temporarily: If internal DNS is problematic, test with public DNS:
    Set-DnsClientServerAddress -InterfaceAlias 'Ethernet' -ServerAddresses ('8.8.8.8','8.8.4.4')
    Remember to revert after testing.
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:
  1. Check for updates via Settings > Windows Update. Success is indicated by Event ID 19 in the WindowsUpdateClient event log.
  2. Verify DNS resolution with:
    Resolve-DnsName windowsupdate.microsoft.com
    Ensure it returns public IP addresses (e.g., from Microsoft's infrastructure).
  3. Inspect C:\Windows\Logs\CBS\CBS.log for the absence of new 0x8024402C entries.

Prevention

To prevent recurrence:
  1. Monitor DNS server health and configuration via Azure Monitor or other tools.
  2. Implement a maintenance schedule to verify WSUS hostname validity and update policies as needed.
  3. Ensure all clients have the correct DNS suffix search list configured via Group Policy or DHCP.
  4. 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.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.