none
0x80248007 and 0x8024401c error installing 2018-02 Cumulative Update for Win10 1607 (KB4074590) RRS feed

  • Question

  • We've recently experienced a rash of these errors on client laptops attempting to install the Feb Cumulative update for Windows 10 1607 (KB4074590).  

    Reviewing the WindowsUpdateLog file I see many occurances of the following:

    2018/03/06 12:07:25.4363242 848   11592 WebServices     WS error: There was an error communicating with the endpoint at 'http://wsus-u.domainname.com:8530/ClientWebService/client.asmx'.
    2018/03/06 12:07:25.4363261 848   11592 WebServices     WS error: There was an error receiving the HTTP reply.
    2018/03/06 12:07:25.4363272 848   11592 WebServices     WS error: The operation did not complete within the time allotted.
    2018/03/06 12:07:25.4363552 848   11592 WebServices     WS error: The operation timed out
    2018/03/06 12:07:25.4363574 848   11592 WebServices     Web service call failed with hr = 8024401c.
    2018/03/06 12:07:25.4363586 848   11592 WebServices     Current service auth scheme=0.
    2018/03/06 12:07:25.4363589 848   11592 WebServices     Current Proxy auth scheme=0.
    2018/03/06 12:07:27.4378591 848   11592 WebServices     Auto proxy settings for this web service call.
    2018/03/06 12:08:29.4352847 848   11592 WebServices     WS error: There was an error communicating with the endpoint at 'http://wsus-u.domainname.com:8530/ClientWebService/client.asmx'. 

    Hank Vare

    Tuesday, March 6, 2018 5:16 PM

All replies

  • 0x80248007 = The information requested is not in the data store.

    0x8024401c = Same as HTTP status 408 - the server timed out waiting for the request.

    What's the OS version and your WSUS version?

    Is there any firewall between the WSUS server and client?


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, March 7, 2018 8:11 AM
    Moderator
  • WSUS OS and version: Windows Server 2012 R2 Standard, 6.3.9600.18324

    There is not a firewall issue here as the majority of the clients have no issue communicating with WSUS and are not reporting errors. Seems only the clients running Win10 1607 are the ones having this issue. The client machines have the Windows Firewall enabled however they have always had it enabled with no WSUS communication issues in the past. As a test I turned the Windows Firewall off on one client laptop which made no difference -- the machine continues to give the 0x8024401c error when clicking "Check for updates".


    Hank Vare

    Wednesday, March 7, 2018 4:02 PM
  • Additionally when running the Server Cleanup Wizard it errors out:

    Server Wizard process runs for about 30 mins then errors out:

    The WSUS administration console was unable to connect to the WSUS Server Database.
    Verify that SQL server is running on the WSUS Server. If the problem persists, try restarting SQL.

    We are using WID db, not an external SQL server.


    Hank Vare

    Wednesday, March 7, 2018 9:52 PM
  • Am 07.03.2018 schrieb techrep43:

    Additionally when running the Server Cleanup Wizard it errors out:

    Server Wizard process runs for about 30 mins then errors out:

    Try this solution:
    https://social.technet.microsoft.com/Forums/ie/en-US/7b12f8b2-d0e6-4f63-a98a-019356183c29/getting-past-wsus-cleanup-wizard-time-out-removing-unnecessary-updates?forum=winserverwsus
    You have to go a long way to fix it.

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Thursday, March 8, 2018 6:02 AM
  • I'm not overly concerned about the Server Cleanup error as I have plenty of space on the C: drive, and this particular server will not be around for that much longer anyway. My primary concern at this point is getting the 4 or 5 (out of 80) clients giving this error to start talking to the WSUS server again.

    Hank Vare

    Thursday, March 8, 2018 6:20 PM