locked
Problems with Windows Server 2016 downloading updates from WSUS (error 0x8024401c) RRS feed

  • Question

  • Hi all.

    In an large enterprise environment we're experiencing problems with the newly deployed Win server 2016.

    Those are deplyed in a VMWare installation using a template.

    After the new machines are deployed we run sysprep on everyone of them. And that works fine for all of the previous versions of windows server.

    Starting with win server 2016 we have problems pulling updates from our corporate WSUS (win2012r2 - wsus6.3.9600.18694).

    The client replies with error 0x8024401c and on the WSUS side is shown as "not yet reported" 0% updated...

    I've been searching technet and all sorts of knowledge bases but still havn't been able to solve the problem yet.

    Can anybody help ?


    • Edited by vdb1965 Friday, November 10, 2017 3:04 PM
    Friday, November 10, 2017 2:53 PM

All replies

  • Hello vdb1965,

    Could you please go through the WSUS logs and let us know what do you see happening in the logs for your newly deployed Windows Server 2016.

    For WSUS server logs you could refer below on WSUS server.
    C:\Program Files\Update Services\Logfiles 
    and the Application Event Log

    On your newly deployed Windows Server 2016 you could refer below logs.
    C:\Windows\WindowsUpdate.log
    C:\Windows\SoftwareDistribution\ReportingEvents.log
    and the Application Event Log

    Hope this helps.

    Regards,
    Apps4rent_Anantesh
    Friday, November 10, 2017 4:04 PM
  • Hello,

    Please try Adamj Clean-WSUS script:

    http://community.spiceworks.com/scripts/show/2998-adamj-clean-wsus

    Regards,

    Yan Li


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

    Monday, November 13, 2017 6:21 AM
  • Hi, thanks for your kind reply.

    Incredibly the problem seem to have solved itself. Checking again this morning I found the server had updated and WSUS marks it as 99% updated.

    I don't know what had happened but I will get back to you as soon as I will have to deploy a new 2016 server and in case that won't work on WSUS again.

    Cheers.

    Monday, November 13, 2017 3:44 PM
  • Hello,

    Just checking in to see any update about this post. 

    If everything works, would you please mark helpful reply as answer?


    Regards,

    Yan Li


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

    Friday, November 24, 2017 2:52 AM
  • For reference,  I had this problem with a new WSUS build on Server 2016 (CU 2018-08), and tried all the solutions out there, eventually this was the one that worked...

    Via IIS Manager, set the Wsuspool application pool, advanced settings to:

    Queue Length = 25000

    Service Unavailable Response Type = TcpLevel

    Private Memory Limit (KB) = 8000000

    Virtual Memory Limit (KB) = 0

    The last two were the key ones for me.

    Hope this helps someone with my pain!!!!

    • Proposed as answer by Jajodu Sunday, October 7, 2018 6:43 PM
    Tuesday, August 28, 2018 12:52 PM