WSUS - a diva... :)

Michael Sabo 21 Reputation points

My WSUS worked several month. At once the last client update time was no more updated. What was the problem??

The first thing I wanted to know was if the reason was on the client or server side. Because of this, I had the server reverted to the last image before clients have send the last life signs. After the restore, I updated everything again. Also ESET Mail Security. After all updates had been carried out, the clients reported still to the server. Shortly afterwards, however, there was no communication again and the clients reported the error 0x8024401c.

Unfortunatelly it is very hard to find out whats the problem. :/
The only warning I found in event log is WAS / 5013.
How would you proceed?


Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
9,550 questions
{count} votes

4 answers

Sort by: Most helpful
  1. Adam J. Marshall 6,181 Reputation points MVP


    Are you performing the proper WSUS maintenance including but not limited to running the Server Cleanup Wizard (SCW), declining superseded updates, running the SQL Indexing script, etc.?

    I would recommend reading the whole 8 part series along with other guides on my site.

    0 comments No comments

  2. Michael Sabo 21 Reputation points

    Thanks for your quick response.
    I already found the first link myself. But if communication has already worked in the past, it cannot be a wrong configuration.
    E.g. the command http://server.domain.local:8530/ClientWebService/client.asmx works great at client side.
    Before restoring the image I already tried to reinstall (and completly removed WSUS DB Folder). But with no success.
    Is there possible to activate verbose logs or something else? What could the reason for warning 5013? Should this be an error, not a warning?

    0 comments No comments

  3. Adam J. Marshall 6,181 Reputation points MVP

    Did you run the client side script on every affected client (after deleting it from the WSUS MMC Console)?

  4. Rita Hu -MSFT 9,441 Reputation points

    @Michael Sabo
    I want to share the error code for your reference:
    0x8024401C -2145107940 WU_E_PT_HTTP_STATUS_REQUEST_TIMEOUT Same as HTTP status 408 - the server timed out waiting for the request.

    Open the IE browser on one of the client and print the below URL to test the connection between WSUS server and the client. The URL should resemble the following URL:


    In additionm, we could review registry value on the client:

    Reference picture:

    Here is a Office Doucment for your reference.

    looking for your feedback and have a great weekend.


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.