How to Fix Windows Update Error 0x8024401c

Windows Update error 0x8024401c is a network timeout, not a generic installation failure. Microsoft maps the code to WU_E_PT_HTTP_STATUS_REQUEST_TIMEOUT, the Windows Update equivalent of HTTP 408. In practical terms, Windows sent an update request but did not get a usable response in time.

Start with the network and proxy checks below, then reset Windows Update components only if the simpler fixes do not work. The instructions apply mainly to Windows 11 and still help on supported or managed Windows 10 installations.

What causes Windows Update error 0x8024401c?

Because 0x8024401c is a request-timeout code, the most relevant causes are an unstable connection, a VPN or proxy that is not working correctly, a filtered work or school network, or an overloaded or unreachable update source. On managed PCs, the update source may be an organization's WSUS server rather than Microsoft's public service.

Microsoft also documents that Windows Update uses WinHTTP for network communication, so an incorrect system-level proxy can break update checks even when a web browser still works. See Microsoft's Windows Update networking error reference and Windows Update network troubleshooting guidance.

1. Run the Windows Update troubleshooter and retry on a clean connection

Restart the PC and your router first, then try Windows Update again. If possible, temporarily disconnect a VPN and test a different network, such as a trusted mobile hotspot. A successful update on another connection strongly points to the original network, proxy, or firewall path.

On Windows 11, open Settings > System > Troubleshoot > Other troubleshooters, then select Run next to Windows Update. Microsoft also directs current Windows users to the automated troubleshooter in the Get Help app. Follow any recommended fixes, restart, and check for updates again. The official steps are on Microsoft's Windows Update Troubleshooter page.

2. Check the WinHTTP proxy before resetting anything

Open Command Prompt as administrator and run:

netsh winhttp show proxy

If this is a personal PC and the result shows an unexpected static proxy, you can return WinHTTP to direct access with:

netsh winhttp reset proxy

Do not reset the proxy on a work or school PC unless your administrator tells you to. Corporate devices may require a proxy or automatic configuration to reach Windows Update or WSUS. Microsoft documents the command behavior in the netsh winhttp reference.

3. Reset the Windows Update cache and services

If the network path looks normal but the error keeps returning, reset the core Windows Update components. Open Command Prompt as administrator and run these commands one line at a time:

net stop wuauserv
net stop bits
net stop cryptSvc
ren %windir%\SoftwareDistribution SoftwareDistribution.old
ren %windir%\System32\catroot2 catroot2.old
net start cryptSvc
net start bits
net start wuauserv

Restart the PC after the commands finish, then open Windows Update and select Check for updates. Microsoft includes the same core reset approach in its Windows Update troubleshooting resources.

4. Repair Windows system files

Corruption in the Windows component store can keep update components from working correctly. In an elevated Command Prompt, run DISM first:

DISM.exe /Online /Cleanup-Image /RestoreHealth

When DISM finishes, run:

sfc /scannow

Restart Windows and try the update again. If DISM cannot obtain repair files on a managed device, your administrator may need to provide a matching repair source. Microsoft explains this process in its Windows Update corruption repair guidance.

If 0x8024401c still appears

Try the update later and compare results on another trusted network. If several devices on the same organization network fail with the same timeout, stop changing local registry or Group Policy settings and ask the administrator to check the WSUS or proxy path. Random registry edits, disabling core network services, or leaving the firewall turned off are not appropriate fixes for an HTTP 408 update timeout.

If you are on Windows 10, remember that Microsoft ended free Windows 10 support on October 14, 2025. Standard Windows 10 PCs no longer receive free security fixes, although some editions and eligible managed or extended-support scenarios have different servicing rules. Microsoft's current guidance is available on its Windows 10 end-of-support page.

For most home PCs, the best order is: troubleshooter and network test, WinHTTP proxy check, Windows Update component reset, then DISM and SFC. That sequence targets the timeout itself without relying on obsolete registry hacks or risky service changes.