WSUS problems w/ Windows 10 clients RRS feed

  • Question

  • I had a handful of machines that weren't checking regularly. I decided to remove them from WSUS and let WSUS rediscover them but now they are saying "not yet reported". I checked the event log and they all say: Windows Update failed to check for updates with error 0x80240439.

    Anyone know what that error means? Also, I don't think I've seen a successful install of 1703 through WSUS. I'm running WSUS on Server 2012 R2. 

    Thursday, August 31, 2017 12:06 AM

All replies

  • Hello,

    Firstly, please make sure you have installed KB3095113 and KB3159706 on the WSUS server. The two patches must be installed if you deploy and manage windows 10 updates with WSUS on Windows Server 2012 R2.

    In addition, you can try to increase the values of the following parameters in web.config file. The file is located at: C:\Program Files\Update Services\WebServices\ClientWebService

    • maxReceivedMessageSize
    • maxBufferSize

    You should stop the wsus service before you modify the parameter settings.

    Best regards,

    Andy Liu

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

    Thursday, August 31, 2017 6:49 AM
  • Yeah i have those installed. Windows 10 updates has been working for some clients for awhile. What should those values in ClientWebService be changed to? What does that error mean that some clients are receiving? 
    Thursday, August 31, 2017 1:54 PM
  • My script will fix your issue.

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


    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

    Saturday, September 2, 2017 1:20 AM
  • Hello,

    The error indicates that the WSUS server is too busy to handle the requests from client PC.

    By default, the value for the parameters mentioned above is 1M(1048576). You can increase it to a larger one, such as 20 ~ 200M(Please written in byte). 

    Best regards,

    Andy Liu 

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

    Wednesday, September 6, 2017 8:15 AM
  • You can use my script mentioned above to do this for you too.

    .\Clean-WSUS.ps1 -SetApplicationPoolMemory 4096
    (for 4GB)

    .\Clean-WSUS.ps1 -SetApplicationPoolMemory 2048
    (for 2GB)

    .\Clean-WSUS.ps1 -SetApplicationPoolMemory 0
    (0 for Unlimited)

    Adam Marshall, MCSE: Security

    Wednesday, September 6, 2017 1:23 PM