none
Some windows 10 cannot get windows update from Windows 2012 R2 WSUS

    Question

  • Our client PC all get windows update from WSUS server (server 2012 R2 Standard), recently, some of windows 10 clients (build 1511 and 1607) can not get update from WSUS server, the windows update log as below.

    2016/12/23 15:07:54.7134302 496   7452  ComApi          * START *   SLS Discovery
    2016/12/23 15:07:54.7143422 496   7452  ComApi          *QUEUED* SLS Discovery
    2016/12/23 15:07:54.7146990 496   6324  ComApi          *RESUMED* Discovery
    2016/12/23 15:07:54.7147004 496   6324  ComApi          Exit code = 0x00000000, Result code = 0x8024500C
    2016/12/23 15:07:54.7147007 496   6324  Api             * END *   Discovery ClientId
    2016/12/23 15:07:54.7156135 496   7452  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C
    2016/12/23 15:07:54.7163071 496   7452  ComApi          Unable to get SLS chunk. (hr=8024500C)
    2016/12/23 15:07:54.7167583 496   644   ComApi          * START *   SLS Discovery
    2016/12/23 15:07:54.7176633 496   644   ComApi          *QUEUED* SLS Discovery
    2016/12/23 15:07:54.7179790 496   6324  ComApi          *RESUMED* Discovery
    2016/12/23 15:07:54.7179800 496   6324  ComApi          Exit code = 0x00000000, Result code = 0x8024500C
    2016/12/23 15:07:54.7179807 496   6324  Api             * END *   Discovery ClientId
    2016/12/23 15:07:54.7188874 496   644   ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C
    2016/12/23 15:07:54.7196413 496   644   ComApi          Unable to get SLS chunk. (hr=8024500C)
    2016/12/23 15:07:56.3733373 496   644   ComApi          * START *   SLS Discovery
    2016/12/23 15:07:56.3743629 496   644   ComApi          *QUEUED* SLS Discovery
    2016/12/23 15:07:56.3747522 496   2816  ComApi          *RESUMED* Discovery
    2016/12/23 15:07:56.3747536 496   2816  ComApi          Exit code = 0x00000000, Result code = 0x8024500C
    2016/12/23 15:07:56.3747540 496   2816  Api             * END *   Discovery ClientId
    2016/12/23 15:07:56.3756748 496   644   ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C
    2016/12/23 15:07:56.3763218 496   644   ComApi          Unable to get SLS chunk. (hr=8024500C)
    2016/12/23 15:07:56.3767383 496   644   ComApi          * START *   SLS Discovery
    2016/12/23 15:07:56.3776312 496   644   ComApi          *QUEUED* SLS Discovery
    2016/12/23 15:07:56.3779236 496   7452  ComApi          *RESUMED* Discovery
    2016/12/23 15:07:56.3779250 496   7452  ComApi          Exit code = 0x00000000, Result code = 0x8024500C
    2016/12/23 15:07:56.3779253 496   7452  Api             * END *   Discovery ClientId
    2016/12/23 15:07:56.3788717 496   644   ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C
    2016/12/23 15:07:56.3795682 496   644   ComApi          Unable to get SLS chunk. (hr=8024500C)
    2016/12/23 15:07:58.1980323 496   6324  ComApi          * START *   SLS Discovery
    2016/12/23 15:07:58.1988360 496   6324  ComApi          *QUEUED* SLS Discovery
    2016/12/23 15:07:58.1992048 496   2816  ComApi          *RESUMED* Discovery
    2016/12/23 15:07:58.1992062 496   2816  ComApi          Exit code = 0x00000000, Result code = 0x8024500C
    2016/12/23 15:07:58.1992069 496   2816  Api             * END *   Discovery ClientId
    2016/12/23 15:07:58.2000875 496   6324  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C
    2016/12/23 15:07:58.2007726 496   6324  ComApi          Unable to get SLS chunk. (hr=8024500C)

    Tuesday, January 17, 2017 9:28 AM

All replies

  • Hi YuKaYuen,

    Please check if the windows 10 clients install the monthly rollup update, unpatched windows 10 have issues update from WSUS server.

    You may install the latest monthly rollup update for windows 10 manually, or as a test, you may install pervious monthly rollup for windows 10, then check if the win10 could detect and install later monthly rollup from WSUS server:

    https://support.microsoft.com/en-us/help/4000825/windows-10-update-history

    Best Regards,

    Anne


    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 18, 2017 3:36 AM
    Moderator
  • Hi,

    Have you got any progress with the issue? Welcome to feedback.

    Best Regards,

    Anne


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

    Friday, January 27, 2017 8:00 AM
    Moderator
  • still got problem, do you have other solution?

    Thanks

    Thursday, March 09, 2017 4:44 AM
  • Hi Yuka.

    I have absolutely same problem in this week.

    Have you solved this problem?

    If you've solve, and if you have time , please teach me the solution...

    Regards

    Sunday, June 18, 2017 2:02 PM
  • Check this page out - https://community.spiceworks.com/topic/1970827-wsus-on-server-2016-windows-10-1607-client-0x8024401c-error

    Helped me out immensely!

    Monday, September 04, 2017 8:17 AM
  • If the clients are Win10 1607 RTM - there's a known issue with 1607's RTM where it doesn't communicate back with WSUS. It was fixed in the September 2016 cumulative update, so you have to manually install a CU past Sept. 2016 and then 1607 will start to communicate back with WSUS. You can use whatever tools at your disposal to install it, including PDQ Deploy, SCCM, PSEXEC, or even manually.

    If your Windows 10 are not in this above state, please try my Cleanup script as it usually fixes these problems.

    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.

    If after running my script you're still having issues, another thing you can try on the affected client is run the following script on 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


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

    Tuesday, September 05, 2017 2:03 AM