locked
WSUS doesn't deliver 1709 update to machines RRS feed

  • Question

  • Hi all,

    This week I started approving Windows 10 1709 update to some of my machines.

    They all start downloading, but some stop with error 0x80d0200, and on other machines it just keeps on saying downloading updates, but the uploading never stops. When you manually update the machine, it works fine...

    Doing some research on google resulted in finding simular problems, but I haven't seen a solution.

    Do you know one?

    Thursday, November 16, 2017 4:34 PM

All replies

  • If you are going to deploy upgrades from Windows 10 to Windows 10 latest streams there are 3 things you need to do.

    1. In Products/Classifications, make sure to check the Upgrades box or Windows 10 will not be available to deploy.
    2. You also will need to add a MIME type for *.esd as application/octet-stream at the top level in IIS.
    3. Install KB3159706 which should come as a regular Windows update on the WSUS 2012 or 2012 R2 Server. Then you need to perform the extra manual steps that are documented here: https://support.microsoft.com/en-us/kb/3159706. Make sure you do ALL OF THE STEPS, including the ones for SSL, even if you do not use SSL currently.

    If all of these are in place, you may have a dirty WSUS database which is caused by downloading the Windows upgrades before installing (and configuring) KB3159706.

    To fix this, download my script and run .\Clean-WSUS.ps1 -DirtyDatabaseCheck

    My script will check to see if your database is dirty, and if it is, it will clean it out and fix it.

    Have a peek at my Adamj Clean-WSUS script. It is the last WSUS Script you will ever need!

    http://community.spiceworks.com/scripts/show/2998-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.


    Adam Marshall, MCSE: Security
    http://www.adamj.org

    Thursday, November 16, 2017 6:33 PM
  • Hello,

    Would you please look into the Windowsupdate.log to get more details about the error?

    You may try steps below to solve the issue:

    1. Stopping the Windows Updates service.
    2. Deleting the Windows\SoftwareDistribution folder.
    3. Restarting the Windows Updates service.

    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.


    • Edited by Yan Li_ Friday, November 17, 2017 7:06 AM
    • Proposed as answer by Yan Li_ Tuesday, November 21, 2017 7:50 AM
    Friday, November 17, 2017 7:05 AM