locked
Windows 10 Clients not reporting on Server 2012 R2 WSUS RRS feed

  • Question

  • Hello Community,

    I know this question has been asked a million times, but I have not found a solution in all my attempts following everyone else's listed fixes.

    Problem:  I have (3) windows 10 clients that refuse to update from a new WSUS installation on server 2012R2.

    -The three clients are (1) creators edition, and (2) anniversary edition machines.

    -They also work perfectly with my existing Server 2012 WSUS installation.

    WSUS server (Server 2012R2)

    -I have confirmed that KB3095113 and KB3159706 are installed.

    -I have followed the manual steps for 3159706 (running the post install /servicing and installing HTTP activiation)

    -The WSUS server will update itself and another server 2012R2.  WSUS appears to be working for non-windows10 machines.

    -I currently have firewall disabled

    -I have confirmed that I can access 'http://c3-carm-sec.<FQDN>:8530/ClientWebService/client.asmx' and that it displays the XML files on the windows 10 machine that is having problems.

    -I have used Adamj's CLean-WSUS script to perform some maintenance tasks as others have suggested it magically fixed their issues.

    -I am using an external database (SUSDB lives on a SQL server).  This is also the case with the correctly functioning server 2012 WSUS installation.  They are not the same name since you can't do that.

    -I have installed windows server 2012R2 a few times and WSUS a few more times thinking it might have been a corrupted installation, nothing has worked

    -There is no AV software installed until this is resolved.

    Windows 10 Clients (both Aniv. and Creators)

    -They work perfectly with my existing Server 2012 WSUS installation

    -I have tried the suggested client reset tasks (stopping service, clearing out software distribution folder, removing SUSID from registry, etc)

    -They both currently say 'not yet reported' under status

    -I'll include the windows update log for then in a second post

    -Client error is 0x8024401c

    I am out of ideas and need further troubleshooting guidance.  If they work perfect on the other WSUS installation, I don't see how the clients are the issue.  I can't seem to get the 2012R2 to work correctly.



    • Edited by Cory Candia Saturday, October 7, 2017 12:56 AM
    Saturday, October 7, 2017 12:49 AM

All replies

  • Here's the client log:

    --------------------------------------------

    2017/10/06 20:24:51.4568010 1064  11996 Agent           * START * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 33]
    2017/10/06 20:24:51.4568075 1064  11996 Agent           Removing service 00000000-0000-0000-0000-000000000000 from sequential scan list
    2017/10/06 20:24:51.4568104 1064  11996 Agent           Added service 00000000-0000-0000-0000-000000000000 to sequential scan list
    1600/12/31 19:00:00.0000000 1064  11996                 Unknown( 12): GUID=eb73583d-5481-33b4-202d-9bb270eddffa (No Format Information found).
    2017/10/06 20:24:51.4688015 1064  1176  Agent           * END * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 33]
    2017/10/06 20:24:51.4806210 1064  1176  Agent           * START * Finding updates CallerId = UpdateOrchestrator  Id = 33
    2017/10/06 20:24:51.4806221 1064  1176  Agent           Online = Yes; AllowCachedResults = No; Ignore download priority = No
    2017/10/06 20:24:51.4806225 1064  1176  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""
    2017/10/06 20:24:51.4806257 1064  1176  Agent           ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
    2017/10/06 20:24:51.4806261 1064  1176  Agent           Search Scope = {Machine}
    2017/10/06 20:24:51.4806293 1064  1176  Agent           Caller SID for Applicability: S-1-5-21-1767476182-2949951987-4135003533-1112
    2017/10/06 20:24:51.4806297 1064  1176  Agent           ProcessDriverDeferrals is set
    2017/10/06 20:24:51.4806297 1064  1176  Agent           RegisterService is set
    2017/10/06 20:24:51.4994796 1064  1176  Misc            Got WSUS Client/Server URL: http://c3-carm-sec.<FQDN>:8530/ClientWebService/client.asmx""
    2017/10/06 20:24:51.9373818 1064  1176  ProtocolTalker  ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://c3-carm-sec.<FQDN>:8530/ClientWebService/client.asmx
    2017/10/06 20:24:51.9375520 1064  1176  ProtocolTalker  OK to reuse existing configuration
    2017/10/06 20:24:51.9375567 1064  1176  ProtocolTalker  Cached cookie has expired or new PID is available
    2017/10/06 20:24:51.9375690 1064  1176  Misc            Got WSUS SimpleTargeting URL: http://c3-carm-sec.<FQDN>:8530""
    2017/10/06 20:24:51.9377749 1064  1176  ProtocolTalker  Initializing simple targeting cookie, clientId = 8055b8a1-6b14-4a0d-a42b-400b688bb7ce, target group = Clients, DNS name = carmel-ws1.<FQDN>
    2017/10/06 20:24:51.9377757 1064  1176  ProtocolTalker    Server URL = http://c3-carm-sec.<FQDN>:8530/SimpleAuthWebService/SimpleAuth.asmx
    2017/10/06 20:24:51.9377901 1064  1176  WebServices     Auto proxy settings for this web service call.
    2017/10/06 20:24:51.9731424 1064  1176  WebServices     Auto proxy settings for this web service call.
    2017/10/06 20:24:51.9994660 1064  1176  WebServices     WS error: The body of the received message contained a fault.
    2017/10/06 20:24:51.9994678 1064  1176  WebServices     WS error: Fault occurred
    2017/10/06 20:24:51.9994693 1064  1176  WebServices     WS Error code: Client
    2017/10/06 20:24:51.9994844 1064  1176  WebServices     WS error: <detail><ErrorCode>ConfigChanged</ErrorCode><Message></Message><ID>e7079672-1975-4398-a89a-1e34f784eaeb</ID><Method>http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"</Method></detail>"
    2017/10/06 20:24:53.9999611 1064  1176  WebServices     Auto proxy settings for this web service call.
    2017/10/06 20:24:54.0214485 1064  1176  WebServices     WS error: The body of the received message contained a fault.
    2017/10/06 20:24:54.0214496 1064  1176  WebServices     WS error: The body of the received message contained a fault.
    2017/10/06 20:24:54.0214518 1064  1176  WebServices     WS error: Fault occurred
    2017/10/06 20:24:54.0214532 1064  1176  WebServices     WS Error code: Client
    2017/10/06 20:24:54.0214724 1064  1176  WebServices     WS error: <detail><ErrorCode>ConfigChanged</ErrorCode><Message></Message><ID>99aacf47-0723-47d7-803e-ca933b99d732</ID><Method>http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"</Method></detail>"
    2017/10/06 20:24:56.0222269 1064  1176  WebServices     Auto proxy settings for this web service call.
    2017/10/06 20:24:56.0424337 1064  1176  WebServices     WS error: The body of the received message contained a fault.
    2017/10/06 20:24:56.0424348 1064  1176  WebServices     WS error: The body of the received message contained a fault.
    2017/10/06 20:24:56.0424355 1064  1176  WebServices     WS error: The body of the received message contained a fault.
    2017/10/06 20:24:56.0424373 1064  1176  WebServices     WS error: Fault occurred
    2017/10/06 20:24:56.0424391 1064  1176  WebServices     WS Error code: Client
    2017/10/06 20:24:56.0424536 1064  1176  WebServices     WS error: <detail><ErrorCode>ConfigChanged</ErrorCode><Message></Message><ID>2d90cb1c-fa7b-47f8-8913-e8cdff94b0db</ID><Method>http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"</Method></detail>"
    2017/10/06 20:24:56.0424828 1064  1176  ProtocolTalker  PT: Calling GetConfig on server
    2017/10/06 20:24:56.0466866 1064  1176  ProtocolTalker  Cached cookie has expired or new PID is available
    2017/10/06 20:24:56.0466960 1064  1176  Misc            Got WSUS SimpleTargeting URL: http://c3-carm-sec.<FQDN>:8530""
    2017/10/06 20:24:56.0469312 1064  1176  ProtocolTalker  Initializing simple targeting cookie, clientId = 8055b8a1-6b14-4a0d-a42b-400b688bb7ce, target group = Clients, DNS name = carmel-ws1.<FQDN>
    2017/10/06 20:24:56.0469320 1064  1176  ProtocolTalker    Server URL = http://c3-carm-sec.<FQDN>:8530/SimpleAuthWebService/SimpleAuth.asmx
    2017/10/06 20:24:56.0469439 1064  1176  WebServices     Auto proxy settings for this web service call.
    2017/10/06 20:24:56.0804124 1064  1176  ProtocolTalker  PTInfo: Server requested registration
    2017/10/06 20:24:56.1036665 1064  1176  ProtocolTalker  PTInfo: Calling RegisterComputer
    2017/10/06 20:24:56.1156031 1064  1176  ProtocolTalker  PTInfo: Server requested registration
    2017/10/06 20:25:59.9401000 1064  1176  WebServices     WS error: There was an error communicating with the endpoint at 'http://c3-carm-sec.<FQDN>:8530/ClientWebService/client.asmx'.
    2017/10/06 20:25:59.9401007 1064  1176  WebServices     WS error: There was an error receiving the HTTP reply.
    2017/10/06 20:25:59.9401010 1064  1176  WebServices     WS error: The operation did not complete within the time allotted.
    2017/10/06 20:25:59.9401018 1064  1176  WebServices     WS error: The body of the received message contained a fault.
    2017/10/06 20:25:59.9401025 1064  1176  WebServices     WS error: The body of the received message contained a fault.
    2017/10/06 20:25:59.9401032 1064  1176  WebServices     WS error: The body of the received message contained a fault.
    2017/10/06 20:25:59.9401155 1064  1176  WebServices     WS error: The operation timed out
    2017/10/06 20:25:59.9401173 1064  1176  WebServices     Web service call failed with hr = 8024401c.
    2017/10/06 20:25:59.9401173 1064  1176  WebServices     Current service auth scheme=0.
    2017/10/06 20:25:59.9401177 1064  1176  WebServices     Current Proxy auth scheme=0.
    2017/10/06 20:26:01.9411248 1064  1176  WebServices     Auto proxy settings for this web service call.
    2017/10/06 20:27:03.9406156 1064  1176  WebServices     WS error: There was an error communicating with the endpoint at 'http://c3-carm-sec.<FQDN>:8530/ClientWebService/client.asmx'.
    2017/10/06 20:27:03.9406163 1064  1176  WebServices     WS error: There was an error receiving the HTTP reply.
    2017/10/06 20:27:03.9406167 1064  1176  WebServices     WS error: The operation did not complete within the time allotted.
    2017/10/06 20:27:03.9406178 1064  1176  WebServices     WS error: There was an error communicating with the endpoint at 'http://c3-carm-sec.<FQDN>:8530/ClientWebService/client.asmx'.
    2017/10/06 20:27:03.9406200 1064  1176  WebServices     WS error: There was an error receiving the HTTP reply.
    2017/10/06 20:27:03.9406207 1064  1176  WebServices     WS error: The operation did not complete within the time allotted.
    2017/10/06 20:27:03.9406214 1064  1176  WebServices     WS error: The body of the received message contained a fault.
    2017/10/06 20:27:03.9406221 1064  1176  WebServices     WS error: The body of the received message contained a fault.
    2017/10/06 20:27:03.9406225 1064  1176  WebServices     WS error: The body of the received message contained a fault.
    2017/10/06 20:27:03.9406232 1064  1176  WebServices     WS error: The operation timed out
    2017/10/06 20:27:03.9406247 1064  1176  WebServices     Web service call failed with hr = 8024401c.
    2017/10/06 20:27:03.9406250 1064  1176  WebServices     Current service auth scheme=0.
    2017/10/06 20:27:03.9406250 1064  1176  WebServices     Current Proxy auth scheme=0.
    2017/10/06 20:27:05.9415787 1064  1176  WebServices     Auto proxy settings for this web service call.
    2017/10/06 20:28:07.9403287 1064  1176  WebServices     WS error: There was an error communicating with the endpoint at 'http://c3-carm-sec.<FQDN>:8530/ClientWebService/client.asmx'.
    2017/10/06 20:28:07.9403294 1064  1176  WebServices     WS error: There was an error receiving the HTTP reply.
    2017/10/06 20:28:07.9403298 1064  1176  WebServices     WS error: The operation did not complete within the time allotted.
    2017/10/06 20:28:07.9403305 1064  1176  WebServices     WS error: There was an error communicating with the endpoint at 'http://c3-carm-sec.<FQDN>:8530/ClientWebService/client.asmx'.
    2017/10/06 20:28:07.9403316 1064  1176  WebServices     WS error: There was an error receiving the HTTP reply.
    2017/10/06 20:28:07.9403320 1064  1176  WebServices     WS error: The operation did not complete within the time allotted.
    2017/10/06 20:28:07.9403330 1064  1176  WebServices     WS error: There was an error communicating with the endpoint at 'http://c3-carm-sec.<FQDN>:8530/ClientWebService/client.asmx'.
    2017/10/06 20:28:07.9403334 1064  1176  WebServices     WS error: There was an error receiving the HTTP reply.
    2017/10/06 20:28:07.9403341 1064  1176  WebServices     WS error: The operation did not complete within the time allotted.
    2017/10/06 20:28:07.9403348 1064  1176  WebServices     WS error: The body of the received message contained a fault.
    2017/10/06 20:28:07.9403352 1064  1176  WebServices     WS error: The body of the received message contained a fault.
    2017/10/06 20:28:07.9403363 1064  1176  WebServices     WS error: The body of the received message contained a fault.
    2017/10/06 20:28:07.9403367 1064  1176  WebServices     WS error: The operation timed out
    2017/10/06 20:28:07.9403385 1064  1176  WebServices     Web service call failed with hr = 8024401c.
    2017/10/06 20:28:07.9403385 1064  1176  WebServices     Current service auth scheme=0.
    2017/10/06 20:28:07.9403388 1064  1176  WebServices     Current Proxy auth scheme=0.
    2017/10/06 20:28:07.9403464 1064  1176  ProtocolTalker  PTError: 0x8024401c
    2017/10/06 20:28:07.9403464 1064  1176  ProtocolTalker  SyncUpdates_WithRecovery failed. 0x8024401c
    2017/10/06 20:28:07.9403547 1064  1176  ProtocolTalker  SyncUpdates round trips: 1
    2017/10/06 20:28:07.9403554 1064  1176  ProtocolTalker  Sync of Updates 0x8024401c
    2017/10/06 20:28:07.9403652 1064  1176  ProtocolTalker  SyncServerUpdatesInternal failed 0x8024401c
    2017/10/06 20:28:07.9531626 1064  1176  Agent           Failed to synchronize, error = 0x8024401C
    2017/10/06 20:28:08.0088499 1064  1176  Agent           Exit code = 0x8024401C
    2017/10/06 20:28:08.0088506 1064  1176  Agent           * END * Finding updates CallerId = UpdateOrchestrator  Id = 33
    1600/12/31 19:00:00.0000000 1064  4352                  Unknown( 16): GUID=eb73583d-5481-33b4-202d-9bb270eddffa (No Format Information found).
    1600/12/31 19:00:00.0000000 1064  4352                  Unknown( 17): GUID=eb73583d-5481-33b4-202d-9bb270eddffa (No Format Information found).
    1600/12/31 19:00:00.0000000 1064  4352                  Unknown( 19): GUID=eb73583d-5481-33b4-202d-9bb270eddffa (No Format Information found).
    1600/12/31 19:00:00.0000000 1064  4352                  Unknown( 20): GUID=eb73583d-5481-33b4-202d-9bb270eddffa (No Format Information found).
    1600/12/31 19:00:00.0000000 1064  11996                 Unknown( 10): GUID=fe1b6309-dedb-392e-308c-ec757efded1a (No Format Information found).

    ----------------------------------

    I don't understand the communication error.  As stated above, I can get the client to view the XML files, there is no firewall blocking communication.

    Saturday, October 7, 2017 12:53 AM
  • Am 07.10.2017 schrieb SFC RedFox:

    -Client error is 0x8024401c

    Since January is a 3rd entry in GPO for WSUS:

    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
    UpdateServiceUrlAlternate
    http://YourWSUS:8530
    Set the 3rd entry, make sure the new entry is in the registry from the
    client and restart the Service WUAUSERV. Try again.

    Winfried


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

    Saturday, October 7, 2017 10:22 AM
  • Set the intranet update service for detecting updates: http://c3-carm-sec:8530 
    Set the intranet statistics server: http://c3-carm-sec:8530 
    Set the alternate download server: http://c3-carm-sec.<FQDN>:8530 
    
    Download files with no Url in the metadata if alternate download server is set. Enabled 
    

    Here's current GPO setting.  I've previously used FQDN in all positions, but changed it to host:port in this testing.

    After gpupdate, confirming changes taken with resultant policy and registry, still error remains.  

    Monday, October 9, 2017 12:41 PM
  • Am 09.10.2017 schrieb SFC RedFox:

    After gpupdate, confirming changes taken with resultant policy and registry, still error remains.  

    Did you restart the whole systems? And delete
    %windir%\Softwaredistribution at this clients. Restart and try again.
    Winfried


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

    Monday, October 9, 2017 4:11 PM
  • Hello SFC,

    The error means that the server timed out for the request.

    This issue has been introduced in the following blog article, and it's mainly driven by the Windows 10 1607 updates. These updates have large metadata payloads for the dependent (child) packages because they roll up a large number of binaries. For large metadata packages and many simultaneous requests, it can take longer than ASP.NET’s default timeout time.

    You can adopt the solutions in the article to fix this issue.

    https://blogs.technet.microsoft.com/askcore/2017/08/18/high-cpuhigh-memory-in-wsus-following-update-tuesdays/

    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.

    Tuesday, October 10, 2017 9:32 AM
  • As for my script - a) are you using the latest 3.1? Try re-downloading it and re-running -FirstRun.

    b) Are you sure the script ran successfully? on the log, do you see numbers beside each of the line items (they can be and most likely will be 0's) of the server cleanup wizard output (not just the last 2)?

    If not, re-run -FirstRun. Also look for errors in the logs.

    I'd be surprised if my script didn't fix your issue (along with the below).

    If my script ran successfully, run the following on the affected client machines from an Admin 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

    Friday, October 13, 2017 3:45 AM