locked
Windows 10 1709 Clients No Longer report Status WSUS 2012 R2 RRS feed

  • Question

  • Hi guys - All of my Windows 10 1709 clients (fully updated) have stopped reporting their status to WSUS running on 2012 R2.

    It appears that this started happening for me on the 3rd January.  All other client OS's and Server OS's are reporting status without issue.

    Steps I've attempted so far.

    1. Ran Windows Update troubleshooter (The machines can all receive updates from Microsoft update servers)

    2. wuauclt /reportnow (No change)

    3. Telnet to ports 8530 and 8531 are successful from all Windows 10 clients.

    4. Server cleanup performed on WSUS (no change)

    5. Forward and reverse DNS lookups are all fine from the Windows 10 clients to the WSUS server.

    Here's the logs from the clients.

    2018/01/10 16:59:16.5569761 3624  5620  WebServices     WS error: There was an error communicating with the endpoint at 'http://andromeda.apollo.local:8530/ReportingWebService/ReportingWebService.asmx'.
    2018/01/10 16:59:16.5569774 3624  5620  WebServices     WS error: The operation timed out
    2018/01/10 16:59:16.5569815 3624  5620  WebServices     WS error: Server was unable to process request. ---> Object reference not set to an instance of an object.
    2018/01/10 16:59:16.5569844 3624  5620  WebServices     WS Error code: Server
    2018/01/10 16:59:16.5570045 3624  5620  WebServices     WS error: <detail/>
    2018/01/10 16:59:16.5575165 3624  5620  IdleTimer       WU operation (CLegacyEventUploader::HandleEvents, operation # 1071) stopped; does use network; is at background priority
    2018/01/10 17:06:11.8244134 3624  5620  Misc            Got WSUS Client/Server URL: http://andromeda.apollo.local:8530/ClientWebService/client.asmx""
    2018/01/10 17:06:11.8415981 3624  5620  ProtocolTalker  OK to reuse existing configuration
    2018/01/10 17:06:11.8416035 3624  5620  ProtocolTalker  Existing cookie is valid, just use it
    2018/01/10 17:06:11.8416055 3624  5620  ProtocolTalker  PTInfo: Server requested registration
    2018/01/10 17:06:11.8966714 3624  5620  Misc            Got WSUS Reporting URL: http://andromeda.apollo.local:8530/ReportingWebService/ReportingWebService.asmx""
    2018/01/10 17:06:11.8966841 3624  5620  IdleTimer       WU operation (CLegacyEventUploader::HandleEvents) started; operation # 1072; does use network; is at background priority
    2018/01/10 17:06:11.8969229 3624  5620  WebServices     Auto proxy settings for this web service call.
    2018/01/10 17:06:38.8547668 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547688 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547705 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547721 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547738 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547750 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547799 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547820 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547836 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547853 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547865 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547882 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547898 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547914 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547931 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547947 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547964 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547980 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8547997 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8548013 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8548034 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8548050 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:38.8548079 3624  5620  WebServices     WS error: There was an error communicating with the endpoint at 'http://andromeda.apollo.local:8530/ReportingWebService/ReportingWebService.asmx'.
    2018/01/10 17:06:38.8548091 3624  5620  WebServices     WS error: The operation timed out
    2018/01/10 17:06:38.8548132 3624  5620  WebServices     WS error: Server was unable to process request. ---> Object reference not set to an instance of an object.
    2018/01/10 17:06:38.8548161 3624  5620  WebServices     WS Error code: Server
    2018/01/10 17:06:38.8548379 3624  5620  WebServices     WS error: <detail/>
    2018/01/10 17:06:40.8551609 3624  5620  WebServices     Auto proxy settings for this web service call.
    2018/01/10 17:06:40.8846397 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846418 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846430 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846447 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846459 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846476 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846517 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846537 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846632 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846648 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846665 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846681 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846693 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846710 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846726 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846743 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846759 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846776 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846792 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846808 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846829 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846845 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:40.8846874 3624  5620  WebServices     WS error: There was an error communicating with the endpoint at 'http://andromeda.apollo.local:8530/ReportingWebService/ReportingWebService.asmx'.
    2018/01/10 17:06:40.8846886 3624  5620  WebServices     WS error: The operation timed out
    2018/01/10 17:06:40.8846932 3624  5620  WebServices     WS error: Server was unable to process request. ---> Object reference not set to an instance of an object.
    2018/01/10 17:06:40.8846960 3624  5620  WebServices     WS Error code: Server
    2018/01/10 17:06:40.8847166 3624  5620  WebServices     WS error: <detail/>
    2018/01/10 17:06:42.8850605 3624  5620  WebServices     Auto proxy settings for this web service call.
    2018/01/10 17:06:42.9168866 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9168887 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9168903 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9168916 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9168932 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9168945 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9168986 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9169006 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9169101 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9169117 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9169134 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9169150 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9169162 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9169179 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9169195 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9169212 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9169228 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9169245 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9169261 3624  5620  WebServices     WS error: The body of the received message contained a fault.
    2018/01/10 17:06:42.9169277 3624  5620  WebServices     WS error: The body of the received message contained a fault.

    If I navigate to the reporting services URL from any Windows 10 client I get 

    Server Error in '/ReportingWebService' Application.
    Runtime Error
    Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. 
    
    Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
    
    
    <!-- Web.Config Configuration File -->
    
    <configuration>
        <system.web>
            <customErrors mode="Off"/>
        </system.web>
    </configuration>
    
    Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
    
    
    <!-- Web.Config Configuration File -->
    
    <configuration>
        <system.web>
            <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
        </system.web>
    </configuration>

    This issue appears to be related to an update that has applied recently, presumably for Windows 10 1709.

    Any ideas?

    Many thanks





    • Edited by Misan Wednesday, January 10, 2018 5:16 PM
    Wednesday, January 10, 2018 5:13 PM

Answers

  • WAM along with a client side script of:

    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()

    which does exactly what you did (deleting the SoftwareDistribution directory) along with a few other things fixes most WSUS issues.


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

    • Marked as answer by Misan Saturday, January 13, 2018 2:30 PM
    Thursday, January 11, 2018 2:49 PM
  • Also, many forget about KB3159706 and it's post-install instructions that have to be followed for WSUS to work after installing the patch. Make sure to perform ALL the instructions including the ones for SSL, even if you're not using SSL right now.

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

    Hi Adam, many thanks for the response.  I covered this quite some time ago when Windows 10 was first released. Like I said, this has only just started happening since the 3rd January 2018 for Windows 10 1709 clients.

    I'll try running through your client side script and see if this clears things up for my Windows 10 clients.

    Many thanks

    • Marked as answer by Misan Friday, January 12, 2018 7:08 AM
    Thursday, January 11, 2018 8:45 PM

All replies

  • Quick update - I've also ran the excellent WSUS script from Adamj.  This hasn't helped the issue however.
    Wednesday, January 10, 2018 7:18 PM
  • Hi,  I am having similar issues to you.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/e7e0445a-2c19-405b-9f2a-bd7455200a95/clients-connecting-to-wsus-but-no-longer-reporting?forum=winserverwsus

    Steve

    Thursday, January 11, 2018 9:57 AM
  • I've managed to get a client reporting in by:

    Stopping the windows update service

    Deleting the whole C:\Windows\SoftwareDistribution\ directory

    Starting the windows update service.

    I previously just tried deleting C:\Windows\SoftwareDistribution\DataStore\ and C:\Windows\SoftwareDistribution\Downloads\ this had no effect.

    Thursday, January 11, 2018 11:22 AM
  • The same here, posted a note in that thread.
    Thursday, January 11, 2018 2:38 PM
  • WAM along with a client side script of:

    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()

    which does exactly what you did (deleting the SoftwareDistribution directory) along with a few other things fixes most WSUS issues.


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

    • Marked as answer by Misan Saturday, January 13, 2018 2:30 PM
    Thursday, January 11, 2018 2:49 PM
  • Also, many forget about KB3159706 and it's post-install instructions that have to be followed for WSUS to work after installing the patch. Make sure to perform ALL the instructions including the ones for SSL, even if you're not using SSL right now.

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

    Thursday, January 11, 2018 2:52 PM
  • Also, many forget about KB3159706 and it's post-install instructions that have to be followed for WSUS to work after installing the patch. Make sure to perform ALL the instructions including the ones for SSL, even if you're not using SSL right now.

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

    Hi Adam, many thanks for the response.  I covered this quite some time ago when Windows 10 was first released. Like I said, this has only just started happening since the 3rd January 2018 for Windows 10 1709 clients.

    I'll try running through your client side script and see if this clears things up for my Windows 10 clients.

    Many thanks

    • Marked as answer by Misan Friday, January 12, 2018 7:08 AM
    Thursday, January 11, 2018 8:45 PM
  • Your client side script worked a treat - Windows 10 1709 reporting status again. Also have your WSUS script running every month to keep the server ticking over nicely.

    Excellent work on both of these Adamj - very much appreciated.


    Saturday, January 13, 2018 2:30 PM
  • deleting the software distribution folder on the client side did it for me. i have used this before but forgot. Thanks for the reminder. the client is again reporting successfully. 
    Friday, February 23, 2018 2:44 PM
  • 2018.03.16 17:43:10.5669671 5112  4164  Agent           * START * Finding updates CallerId = UpdateOrchestrator  Id = 6
    2018.03.16 17:43:10.5669700 5112  4164  Agent           Online = Yes; Interactive = No; AllowCachedResults = No; Ignore download priority = No
    2018.03.16 17:43:10.5669745 5112  4164  Agent           Criteria = IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1""
    2018.03.16 17:43:10.5669788 5112  4164  Agent           ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2018.03.16 17:43:10.5669799 5112  4164  Agent           Search Scope = {Machine}
    2018.03.16 17:43:10.5669848 5112  4164  Agent           Caller SID for Applicability: S-1-5-21-2405232527-3037331580-1253703611-1885
    2018.03.16 17:43:10.5669859 5112  4164  Agent           ProcessDriverDeferrals is set
    2018.03.16 17:43:10.5670730 5112  4164  Agent           *FAILED* [8024043D] GetIsInventoryRequired
    2018.03.16 17:43:10.5674248 5112  4164  Agent           Blocking Windows content for WUfB
    2018.03.16 17:43:10.5913432 5112  4164  Misc            Got WSUS Client/Server URL: http://192.168.0.132:8530/ClientWebService/client.asmx""
    2018.03.16 17:43:10.6077847 5112  4164  Driver          Skipping printer driver 4 due to incomplete info or mismatched environment - HWID[microsoftmicrosoft_musd] Provider[Microsoft] MfgName[Microsoft] Name[Microsoft enhanced Point and Print compatibility driver] pEnvironment[Windows NT x86] LocalPrintServerEnv[Windows x64]
    2018.03.16 17:43:10.6760445 5112  4164  ProtocolTalker  ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.0.132:8530/ClientWebService/client.asmx
    2018.03.16 17:43:10.6761560 5112  4164  ProtocolTalker  PT: Calling GetConfig on server
    2018.03.16 17:43:10.6761637 5112  4164  IdleTimer       WU operation (CAgentProtocolTalker::GetConfig_WithRecovery) started; operation # 25; does use network; is at background priority
    2018.03.16 17:43:10.6761833 5112  4164  WebServices     Auto proxy settings for this web service call.
    2018.03.16 17:43:10.6816802 5112  4164  IdleTimer       WU operation (CAgentProtocolTalker::GetConfig_WithRecovery, operation # 25) stopped; does use network; is at background priority
    2018.03.16 17:43:10.6821413 5112  4164  ProtocolTalker  Cached cookie has expired or new PID is available
    2018.03.16 17:43:10.6821632 5112  4164  Misc            Got WSUS SimpleTargeting URL: http://192.168.0.132:8530""
    2018.03.16 17:43:10.6823111 5112  4164  IdleTimer       WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie) started; operation # 26; does use network; is at background priority
    2018.03.16 17:43:10.6823137 5112  4164  ProtocolTalker  Initializing simple targeting cookie, clientId = fb256e27-20ae-4c5a-b8b9-0575f8fd49e9, target group = , DNS name = pc180.akhisar.bel.tr
    2018.03.16 17:43:10.6823148 5112  4164  ProtocolTalker    Server URL = http://192.168.0.132:8530/SimpleAuthWebService/SimpleAuth.asmx
    2018.03.16 17:43:10.6823268 5112  4164  WebServices     Auto proxy settings for this web service call.
    2018.03.16 17:43:10.6893924 5112  4164  IdleTimer       WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie, operation # 26) stopped; does use network; is at background priority
    2018.03.16 17:43:10.6895579 5112  4164  IdleTimer       WU operation (CAgentProtocolTalker::GetCookie_WithRecovery) started; operation # 27; does use network; is at background priority
    2018.03.16 17:43:10.6945496 5112  4164  IdleTimer       WU operation (CAgentProtocolTalker::GetCookie_WithRecovery, operation # 27) stopped; does use network; is at background priority
    2018.03.16 17:43:10.6945582 5112  4164  ProtocolTalker  PTInfo: Server requested registration
    2018.03.16 17:43:10.7015922 5112  4164  ProtocolTalker  PTInfo: Calling RegisterComputer
    2018.03.16 17:43:10.7015996 5112  4164  IdleTimer       WU operation (CAgentProtocolTalker::RegisterComputer_WithRecovery) started; operation # 28; does use network; is at background priority
    2018.03.16 17:43:10.7072515 5112  4164  IdleTimer       WU operation (CAgentProtocolTalker::RegisterComputer_WithRecovery, operation # 28) stopped; does use network; is at background priority
    2018.03.16 17:43:10.7078673 5112  4164  IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 29; does use network; is at background priority
    2018.03.16 17:43:11.2731313 5112  4164  IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 29) stopped; does use network; is at background priority
    2018.03.16 17:43:26.4986936 5112  4176  Misc            *FAILED* [80072EE2] Send request
    2018.03.16 17:43:26.4987269 5112  4176  Misc            *FAILED* [80072EE2] Library download error. Will retry. Retry Counter:0
    2018.03.16 17:45:26.4893852 5112  4176  Misc            *FAILED* [80072EE2] Send request
    2018.03.16 17:45:26.4894108 5112  4176  Misc            *FAILED* [80072EE2] WinHttp: SendRequestToServerForFileInformation (retrying with default proxy)
    2018.03.16 17:47:26.4979444 5112  4176  Misc            *FAILED* [80072EE2] Send request
    2018.03.16 17:47:26.4979757 5112  4176  Misc            *FAILED* [80072EE2] Library download error. Will retry. Retry Counter:1
    2018.03.16 17:49:26.4917094 5112  4176  Misc            *FAILED* [80072EE2] Send request
    2018.03.16 17:49:26.4917344 5112  4176  Misc            *FAILED* [80072EE2] WinHttp: SendRequestToServerForFileInformation (retrying with default proxy)
    2018.03.16 17:51:30.4897808 5112  4176  Misc            *FAILED* [80072EE2] Send request
    2018.03.16 17:51:30.4898110 5112  4176  Misc            *FAILED* [80072EE2] Library download error. Will retry. Retry Counter:2
    2018.03.16 17:53:34.5000481 5112  4176  Misc            *FAILED* [80072EE2] Send request
    2018.03.16 17:53:34.5000737 5112  4176  Misc            *FAILED* [80072EE2] WinHttp: SendRequestToServerForFileInformation (retrying with default proxy)
    2018.03.16 17:55:34.4967656 5112  4176  Misc            *FAILED* [80072EE2] Send request
    2018.03.16 17:55:34.4967964 5112  4176  SLS             *FAILED* [80072EE2] GetDownloadedOnWeakSSLCert
    2018.03.16 17:55:34.4970151 5112  4176  SLS             *FAILED* [80072EE2] Method failed [CSLSClient::GetResponse:525]
    2018.03.16 17:55:34.4970737 5112  4176  IdleTimer       WU operation (CDiscoveryCall::Init ID 2, operation # 7) stopped; does use network; is not at background priority
    2018.03.16 17:55:34.5120440 6400  2492  ComApi          *RESUMED* Discovery
    2018.03.16 17:55:34.5120665 6400  2492  ComApi          Exit code = 0x00000000, Result code = 0x80072EE2
    2018.03.16 17:55:34.5120702 6400  2492  Api             * END *   Discovery ClientId
    2018.03.16 17:55:34.5161460 6400  4016  ComApi          *FAILED* [80072EE2] Method failed [CSLSClientProxy::GetSLSDataChunk:247]
    2018.03.16 17:55:34.5187802 6400  4016  ComApi          * START *   SLS Discovery
    2018.03.16 17:55:34.5206152 5112  4752  IdleTimer       WU operation (CDiscoveryCall::Init ID 7) started; operation # 34; does use network; is not at background priority
    2018.03.16 17:55:34.5207890 6400  4016  ComApi          *QUEUED* SLS Discovery
    2018.03.16 17:55:34.5380056 5112  4164  SLS             *FAILED* [80248007] Method failed [SlsDatastoreLookup:797]
    2018.03.16 17:55:34.5380175 5112  4164  SLS             Retrieving SLS response from server...
    2018.03.16 17:55:34.5388632 5112  4164  SLS             Making request with URL HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/10.0.16299.0/0?CH=181&L=tr-TR&P=&PT=0x4&WUA=10.0.16299.15&MK=System+manufacturer&MD=System+Product+Name
    2018.03.16 17:57:38.4920729 5112  4164  Misc            *FAILED* [80072EE2] Send request
    2018.03.16 17:57:38.4921010 5112  4164  Misc            *FAILED* [80072EE2] WinHttp: SendRequestToServerForFileInformation (retrying with default proxy)
    2018.03.16 17:59:38.4944170 5112  4164  Misc            *FAILED* [80072EE2] Send request
    2018.03.16 17:59:38.4944486 5112  4164  Misc            *FAILED* [80072EE2] Library download error. Will retry. Retry Counter:0
    2018.03.16 18:01:03.6521065 5668  6220  AppAU 

    client Windows 10 1709 error  Not yet reported ?

    • Edited by akkayahmed Friday, March 16, 2018 3:06 PM
    Friday, March 16, 2018 3:04 PM
  • akkayahmed, are you using WSUS Automated Maintenance?


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

    Friday, March 16, 2018 3:39 PM
  • akkayahmed, are you using WSUS Automated Maintenance?


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

    No.

    Friday, March 16, 2018 4:16 PM
  • akkayahmed, are you using WSUS Automated Maintenance?


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

    No.

    Then I suggest you should.

    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.


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


    Friday, March 16, 2018 4:27 PM
  • How is your post help to resolve the problem?

    Can you garantee that after anybody use your suggested script, the "client Windows 10 1709 error"  will be resolved immediately? ..or if not, then why you wrote your post? 




    • Edited by Trier23 Wednesday, April 11, 2018 1:23 PM
    Wednesday, April 11, 2018 1:12 PM
  • How is your post help to resolve the problem?

    Can you garantee that after anybody use your suggested script, the "client Windows 10 1709 error"  will be resolved immediately? ..or if not, then why you wrote your post? 




    Can you guarantee you won't get hit by a bus today? No. There's no guarantees as there are too many variables. All I can offer is it fixes 'most' issues.

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

    Wednesday, April 11, 2018 2:24 PM
  • Hi Adam - I just noticed we were having this issue when I checked some info on the WSUS service today.

    I am running your WAM script, but I want to clarify where this other script, you posted above, is being run - on server or client? 

    Thanks

    Friday, May 4, 2018 8:47 PM
  • Hi Adam - I just noticed we were having this issue when I checked some info on the WSUS service today.

    I am running your WAM script, but I want to clarify where this other script, you posted above, is being run - on server or client? 

    Thanks


    Client side script = run on any affected client. Could be the server itself or any other Windows Server, or it could be a windows desktop client like Windows 10 or Windows 7 etc.

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

    Friday, May 4, 2018 9:48 PM
  • This worked for me. Thanks adamj


    • Edited by Ladee Tuesday, July 17, 2018 8:07 AM
    Tuesday, July 17, 2018 8:06 AM
  • I found a simple issue... you must specify the port 8530 in your GPO, not just the server name.  My Server 2012 clients were reporting fine, but my Win 10 began dropping off.  I edited the GPO to point to http://Server:8530 for detecting and status, and the clients showed back up.
    Wednesday, May 1, 2019 6:03 PM
  • The problem for me is it says this update is not applicable to my computer (Windows Server 2012 R2) When i try to run updates on the Server it says it is fully up to date.
    Tuesday, June 18, 2019 7:38 PM
  • The problem for me is it says this update is not applicable to my computer (Windows Server 2012 R2) When i try to run updates on the Server it says it is fully up to date.

    Are the updates that are needed approved in WSUS? Part 6 of my 8 part blog series on How to Setup, Manage, and Maintain WSUS explains the approvals process.

    https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-6-selecting-your-test-systems-the-approvals-process/

    Feel free to read the whole series and other guides on my site.


    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Wednesday, June 19, 2019 1:01 AM
  • thanks for your answer it is work for me. i also config "delivery option" on my client

    گر صبر کنی، زقوره حلوا سازی

    Thursday, October 17, 2019 8:37 PM