WSUS update failed with error code 0x8024401c
I have an WSUS error code 0x8024401c on server 2016 Std.
My 2016 Servers machines are configured with ABB Security - Windows Update Service GPO as shown in 2PAA120528_A_800xA_Symphony Plus_System_Hardening_Group_Policies_Overview.
They are updated from Customer's WSUS server.
So, why Windows Update is failed with this error code 0x8024401c?
Could you help me ?
What does error 0x8024401c mean?
•Windows error code 0x8024401C stands for WU_E_PT_HTTP_STATUS_REQUEST_TIMEOUT.
•This is equivalent to HTTP status 408 (request timed out).
•Because no data has been received since the request, the server has disconnected.
Which systems are affected?
Computers running the Windows 10 Anniversary Update will no longer be able to connect to the update server and will show error 0x8024401c:
•After installing updates KB4034658 and KB4034661, the error occurs.
•If multiple Windows 10 clients then retrieve the updates from the server at the same time, the xml records (metadata) exchange update information on the server result in high CPU and RAM usage.
•Often the calculation takes too long and the connection is therefore terminated with error 0x8024401c.
Microsoft has already included the bug as known in the KB4034658 cumulative update:
WSUS servers will exhibit increased CPU, memory, and network utilization when Windows Update clients perform their first scan after installing KB4034658.
An associated Technet blog entry describes the symptoms as follows:
•High CPU on your WSUS server - 70-100% CPU in w3wp.exe hosting WsusPool
•High memory in the w3wp.exe process hosting the WsusPool – customers have reported memory usage approach 24GB
•Constant recycling of the W3wp.exe hosting the WsusPool (identifiable by the PID changing)
•Clients fail to scan with 8024401c (timeout) errors in the WindowsUpdate.log
•Mostly 500 errors for the /ClientWebService/Client.asmx requests in the IIS logs
According to Microsoft, this is especially true for updates to Windows 10 Anniversary Update such as KB4022715, KB4022723, or KB4025339. These have extensive metadata that leads to the long calculation mentioned above.
So far, it will help if you uninstall and block appropriate updates. In the technet post mentioned, Microsoft advises the following:
•Configure IIS to stop recycling the App Pool
•Limit the number of inbound connections to WSUS
•Increase the ASP.NET timeout
Otherwise, just wait for Microsoft to correct the bug soon.
It should be noted that updates for Windows 10 version 1703 clients (Creators Update) can still be delivered because there are currently few packages available. It is therefore very likely that the problem will also occur later for version 1703 if there are several cumulative updates.