locked
Single 2016 Server not updating RRS feed

  • Question

  • Hello,

    We have a 2016 WSUS server deployed.

    We have one server 2016 server that will not update. All other 2016 and 2012R2 servers update.

    Error we get from this server for any update is;

    There were problems installing some updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help:

     - Error 0x80244019

    Any help would be great.

    Thanks

    Matt


    Monday, January 1, 2018 9:50 AM

All replies

  • Am 01.01.2018 schrieb matty15206:

    Error we get from this server for any update is;

    There were problems installing some updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help:

     - Error 0x80244019

    Open a admin Commandline:

    net stop wuauserv
    rd /s /q %windir%\softwaredistribution
    net start wuauserv
    
    wuauclt /resetauthorization /detectnow
    

    Wait 10 Minutes and then try again search for Windows Updates.

    Winfried


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

    Monday, January 1, 2018 10:21 AM
  • Tried the above but still getting Error 0x80244019.

    Matt

    

    Monday, January 1, 2018 3:29 PM
  • First, can you install an update MANUALLY on the server (downloaded from the Windows Catalog and then installed)?

    It really sounds like something that my WSUS Automated Maintenance system will fix. It fixes these types of issues and errors with 1 or more systems failing to install/report to WSUS. It also makes your life easier - see the information below.

    Please have a look at the WSUS Automated Maintenance (WAM) system. It is an automated maintenance system for WSUS, the last system you'll ever need to maintain WSUS!

    https://community.spiceworks.com/scripts/show/2998-wsus-automated-maintenance-formerly-adamj-clean-wsus

    What it does:

    1. Add WSUS Index Optimization to the database to increase the speed of many database operations in WSUS by approximately 1000-1500 times faster.
    2. Remove all Drivers from the WSUS Database (Default; Optional).
    3. Shrink your WSUSContent folder's size by declining multiple types of updates including by default any superseded updates, preview updates, expired updates, Itanium updates, and beta updates. Optional extras: Language Packs, IE7, IE8, IE9, IE10, Embedded, NonEnglishUpdates, ComputerUpdates32bit, WinXP.
    4. Remove declined updates from the WSUS Database.
    5. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
    6. Compress Update Revisions.
    7. Remove Obsolete Updates.
    8. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
    9. Application Pool Memory Configuration to display the current private memory limit and easily set it to any configurable amount including 0 for unlimited. This is a manual execution only.
    10. Checks to see if you have a dirty database, and if you do, fixes it. This is primarily for Server 2012 WSUS, and is a manual execution only.
    11. Run the Recommended SQL database Maintenance script on the actual SQL database.
    12. Run the Server Cleanup Wizard.

    It will email the report out to you or save it to a file, or both.

    Although the script is lengthy, it has been made to be super easy to setup and use so don't over think it. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment (email settings only if you are accepting all the defaults), simply run:

    .\Clean-WSUS.ps1 -FirstRun

    If you wish to view or increase the Application Pool Memory Configuration, or run the Dirty Database Check, you must run it with the required switch. See Get-Help .\Clean-WSUS.ps1 -Examples

    If you're having trouble, there's also a -HelpMe option that will create a log so you can send it to me for support.


    If my script alone doesn't fix it, then run the following script on an affected client from an Administrative command prompt:

    net stop bits
    net stop wuauserv
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f
    reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIDValidation /f
    rd /s /q "C:\WINDOWS\SoftwareDistribution"
    net start bits
    net start wuauserv
    wuauclt /resetauthorization /detectnow
    PowerShell.exe (New-Object -ComObject Microsoft.Update.AutoUpdate).DetectNow()

    The combination of these 2 things should fix your issue. If for some strange reason that it does not, run a gpresult /h gpo.htm and post the output so we can see what GPOs are hitting your client that may be causing the issues.


    Adam Marshall, MCSE: Security
    http://www.adamj.org
    Microsoft MVP - Windows and Devices for IT

    Monday, January 1, 2018 5:59 PM
  • Am 01.01.2018 schrieb matty15206:

    Tried the above but still getting Error 0x80244019.

    Show us the WSUS-Entry from this Server who will not update. Did you
    see the Server in WSUS.MSC?

    Winfried


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

    Tuesday, January 2, 2018 5:23 PM
  • Hi,

    Is that server in a different network environment ?

    I mean , is there any firewall or proxy between that server and WSUS server .

    Also please check the proxy setting on that 2016 server :

    netsh winhttp show proxy

    Best Regards,

    Elton


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

    Wednesday, January 3, 2018 2:30 AM
  • You should to set the same port in IIS on GPO or registry. 
    Friday, June 7, 2019 1:10 PM
  • my friend, my english is bad.... but i can try:

    i my case, the solution was setting port. see that: 

    --


    unfortunately I have no right to post links and images


    Sunday, March 1, 2020 6:58 PM