locked
Windows 10 1607 Suddenly can't update RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    An odd one I'm really pulling my hair out with now.

    We have a 2012 R2 WSUS box based on our site. We use it to update our Win7 and Win10 clients.

    Week before last I came to generate new reference build images for Win7 and Win10 with the latest updates inthem(we use ZTI_WindowsUpdate.wsf in MDT) and noticed Win10 was installing between 0 and 20 patches, and the patches it was installing were office ones. The last image I'd done in July installed ~120. Win7 was fine.

    I am usually seening error 0x8024401C in eventviewer and in WindowsUpdate.log (when the powershell script generates readable data!) which I believe is due to not being able to communicate with the WSUS box. Except I can ping the server, connect to IS on it from the clients, and the clients are registering with WSUSs, but then never reporting in a status update.

    I've tried the build multiple times, and have tried installing the September rollup beforehand as a package to see if it helped, but it changed nothing.

    In the end I built a PC from the 1607 DVD and that does the exact same thing.

    Windows 7 can update fine and some other windows 10 kit can also update fine too. Example my laptop can't, but my colleagues can and did just last week.

    I'm seeing a lot of this in the logs -

    2017/10/13 09:59:28.3159176 424   2192  WebServices     WS error: There was an error communicating with the endpoint at 'http://WSUSSVR:8530/ClientWebService/client.asmx'.
    2017/10/13 09:59:28.3159184 424   2192  WebServices     WS error: There was an error receiving the HTTP reply.
    2017/10/13 09:59:28.3159189 424   2192  WebServices     WS error: The operation did not complete within the time allotted.
    2017/10/13 09:59:28.3159201 424   2192  WebServices     WS error: There was an error communicating with the endpoint at 'http://WSUSSVR:8530/ClientWebService/client.asmx'.
    2017/10/13 09:59:28.3159206 424   2192  WebServices     WS error: There was an error receiving the HTTP reply.
    2017/10/13 09:59:28.3159218 424   2192  WebServices     WS error: The operation did not complete within the time allotted.
    2017/10/13 09:59:28.3159227 424   2192  WebServices     WS error: The operation timed out
    2017/10/13 09:59:28.3159244 424   2192  WebServices     Web service call failed with hr = 8024401c.

    But also it seems to be able to query what's available -

    2017/10/13 15:05:20.2255157 636   7392  Misc            Got WSUS Client/Server URL: http://WSUSSVR:8530/ClientWebService/client.asmx""
    2017/10/13 15:05:20.2256582 636   7392  ProtocolTalker  OK to reuse existing configuration
    2017/10/13 15:05:20.2256697 636   7392  ProtocolTalker  Existing cookie is valid, just use it
    2017/10/13 15:05:20.2256727 636   7392  ProtocolTalker  PTInfo: Server requested registration
    2017/10/13 15:05:20.2974478 636   7392  Misc            Got WSUS Reporting URL: http://WSUSSVR:8530/ReportingWebService/ReportingWebService.asmx""
    2017/10/13 15:05:20.2974811 636   7392  WebServices     Auto proxy settings for this web service call.
    2017/10/13 15:12:01.8762894 636   1636  Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2017/10/13 15:12:04.8194553 636   1636  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
    2017/10/13 15:12:04.9353533 636   1636  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 3.
    2017/10/13 15:12:10.4332588 636   1636  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
    2017/10/13 15:12:10.5628268 636   1636  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2017/10/16 07:58:35.9491927 636   1636  Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 0.
    2017/10/16 07:58:36.2790640 636   1636  Agent           Adding timer:
    2017/10/16 07:58:36.2790756 636   1636  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2017-10-17 06:58:34, not idle-only, not network-only
    2017/10/16 07:58:37.5292004 636   7392  DownloadManager PurgeExpiredFiles::Found 0 expired files to delete.
    2017/10/16 07:58:37.5587837 636   1636  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
    2017/10/16 07:58:38.0936514 636   7392  DownloadManager PurgeExpiredUpdates::Found 328 non expired updates.
    2017/10/16 07:58:38.1463366 636   7392  DownloadManager PurgeExpiredUpdates::Found 0 expired updates.

    Am really scratching my head with this one as it's started so suddenly and even affects a DVD build.

    The WSUS server itself has been fully updated.

    We also built a temp box to host WSUS to rule in/out the server and found that was hit an miss too. That was a build including July's updates.

    Any ideas or guidance would really be appreciated!

    Thanks

    Monday, October 16, 2017 11:57 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Looks like this is now sorted - https://community.spiceworks.com/topic/1970827-wsus-on-server-2016-windows-10-1607-client-0x8024401c-error

    Queue Length: 25000 from 10000 (i had to change this 3 time for it to stick)
    Limit Interval (minutes): 15 from 5
    "Service Unavailable" Response: TcpLevel from HttpLevel
    Private Memory Limit (KB): 0 from 18342456 (ours was already 0)

    And finally (which was the extra step for us) "In addition, you can edit the web.config ( C:\Program Files\Update Services\WebServices\ClientWebService\web.config  ) for WSUS
    Stop the IIS and do following changes:

    replace <httpRuntime maxRequestLength="4096" /> with <httpRuntime maxRequestLength="204800" executionTimeout="7200"/> "

    This seems to have sorted it for us.

    I'm intrigued tho and a somewhat baffled. This WSUS box has been in operation for a long time, patching our windows 10 1607 clients and I can't get my head round why it would suddenly and so consistently stop serving them.

    • Marked as answer by warden976 Thursday, October 19, 2017 8:56 AM
    Thursday, October 19, 2017 8:56 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Sir,

    Please check the following article regarding the similar error which caused by the reg/GPO settings:

    http://www.ericcsinger.com/problem-solving-wsus-failing-for-windows-10-with-error-8024401c/

    Also please try to change these IIS application pool settings for 2012 R2 WSUS server:


    Private Memory Limit (KB)
Service Unavailable Response
Limit Interval (minutes)
Queue Length

    https://gal.vin/2017/04/29/wsus-config-tweaks/

    Hope it is useful to you .

    Best Regards,

    Elton

    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 17, 2017 7:07 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Elton,

    Thanks for replying.

    We don't have any of the reg settings or GPOs set as mentioned in the article.

    I change the IIS settings and restarted the services but am still getting the error -

    2017/10/17 09:34:33.5540304 656   168   Agent           WU client version 10.0.14393.1358
    2017/10/17 09:34:33.5542971 656   168   Agent           SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
    2017/10/17 09:34:33.5544281 656   168   Agent           Base directory: C:\windows\SoftwareDistribution
    2017/10/17 09:34:33.5548957 656   168   Agent           Datastore directory: C:\windows\SoftwareDistribution\DataStore\DataStore.edb
    2017/10/17 09:34:33.5737117 656   168   Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2017/10/17 09:34:33.5737292 656   168   Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
    2017/10/17 09:34:33.5742121 656   168   Shared          Network state: Connected
    2017/10/17 09:34:33.5777718 656   168   Misc            LoadHistoryEventFromRegistry completed, hr = 8024000C
    2017/10/17 09:34:33.5784703 656   168   Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2017/10/17 09:34:33.5784758 656   168   Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
    2017/10/17 09:34:33.5784814 656   168   Shared          Power status changed
    2017/10/17 09:34:33.5793774 656   168   Agent           Initializing global settings cache
    2017/10/17 09:34:33.5793778 656   168   Agent           WSUS server: http://WSUSSVR:8530
    2017/10/17 09:34:33.5793782 656   168   Agent           WSUS status server: http://WSUSSVR:8530
    2017/10/17 09:34:33.5793782 656   168   Agent           Alternate Download Server: NULL
    2017/10/17 09:34:33.5793786 656   168   Agent           Fill Empty Content Urls: No
    2017/10/17 09:34:33.5793786 656   168   Agent           Target group: Patch Testing Clients
    2017/10/17 09:34:33.5793791 656   168   Agent           Windows Update access disabled: No
    2017/10/17 09:34:33.5796453 656   8372  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2017-10-18 06:58:34, not idle-only, not network-only
    2017/10/17 09:34:33.5859032 656   168   Agent           Initializing Windows Update Agent
    2017/10/17 09:34:33.5859847 656   168   DownloadManager Download manager restoring 0 downloads
    2017/10/17 09:34:33.5860291 656   168   Agent           CPersistentTimeoutScheduler | GetTimer, returned hr = 0x00000000
    2017/10/17 09:34:33.6041675 656   8008  DownloadManager PurgeExpiredFiles::Found 0 expired files to delete.
    2017/10/17 09:34:33.6156214 656   8008  DownloadManager PurgeExpiredUpdates::Found 326 non expired updates.
    2017/10/17 09:34:33.6705018 656   8372  Agent           * START * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 1]
    2017/10/17 09:34:33.6705090 656   8372  Agent           Added service 00000000-0000-0000-0000-000000000000 to sequential scan list
    2017/10/17 09:34:33.6705555 656   8372  ComApi          Search ClientId = UpdateOrchestrator
    2017/10/17 09:34:33.6733109 656   1988  Agent           * END * Queueing Finding updates [CallerId = UpdateOrchestrator  Id = 1]
    2017/10/17 09:34:33.6752476 656   1988  Agent           * START * Finding updates CallerId = UpdateOrchestrator  Id = 1
    2017/10/17 09:34:33.6752484 656   1988  Agent           Online = Yes; AllowCachedResults = No; Ignore download priority = No
    2017/10/17 09:34:33.6752489 656   1988  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/17 09:34:33.6752510 656   1988  Agent           ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
    2017/10/17 09:34:33.6752514 656   1988  Agent           Search Scope = {Machine}
    2017/10/17 09:34:33.6752544 656   1988  Agent           Caller SID for Applicability: S-1-5-21-3039031127-931851717-1852445250-1411
    2017/10/17 09:34:33.6752548 656   1988  Agent           ProcessDriverDeferrals is set
    2017/10/17 09:34:33.6752553 656   1988  Agent           RegisterService is set
    2017/10/17 09:34:33.6779855 656   8008  DownloadManager PurgeExpiredUpdates::Found 0 expired updates.
    2017/10/17 09:34:33.6785214 656   1988  Misc            Got WSUS Client/Server URL: http://WSUSSVR:8530/ClientWebService/client.asmx""
    2017/10/17 09:34:33.6853992 656   8008  Shared          Effective power state: AC
    2017/10/17 09:34:33.6854010 656   8008  DownloadManager Power state change detected. Source now: AC
    2017/10/17 09:34:34.0246416 656   1988  ProtocolTalker  ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://WSUSSVR:8530/ClientWebService/client.asmx
    2017/10/17 09:34:34.0248426 656   1988  ProtocolTalker  OK to reuse existing configuration
    2017/10/17 09:34:34.0248515 656   1988  ProtocolTalker  Cached cookie has expired or new PID is available
    2017/10/17 09:34:34.0248656 656   1988  Misc            Got WSUS SimpleTargeting URL: http://WSUSSVR:8530""
    2017/10/17 09:34:34.0251122 656   1988  ProtocolTalker  Initializing simple targeting cookie, clientId = eebe37ab-78f6-4755-b41b-2ebd8294d1d6, target group = Patch Testing Clients, DNS name = hcukmc024481a00.zzmentor.eis.hpcds.com
    2017/10/17 09:34:34.0251131 656   1988  ProtocolTalker    Server URL = http://WSUSSVR:8530/SimpleAuthWebService/SimpleAuth.asmx
    2017/10/17 09:34:34.0251873 656   1988  WebServices     Auto proxy settings for this web service call.
    2017/10/17 09:34:34.1180713 656   1988  WebServices     Auto proxy settings for this web service call.
    2017/10/17 09:34:34.1850152 656   1988  ProtocolTalker  PTInfo: Server requested registration
    2017/10/17 09:35:36.9944861 656   1988  WebServices     WS error: There was an error communicating with the endpoint at 'http://WSUSSVR:8530/ClientWebService/client.asmx'.
    2017/10/17 09:35:36.9944870 656   1988  WebServices     WS error: There was an error receiving the HTTP reply.
    2017/10/17 09:35:36.9944874 656   1988  WebServices     WS error: The operation did not complete within the time allotted.
    2017/10/17 09:35:36.9944994 656   1988  WebServices     WS error: The operation timed out
    2017/10/17 09:35:36.9945002 656   1988  WebServices     Web service call failed with hr = 8024401c.
    2017/10/17 09:35:36.9945006 656   1988  WebServices     Current service auth scheme=0.
    2017/10/17 09:35:36.9945011 656   1988  WebServices     Current Proxy auth scheme=0.
    2017/10/17 09:35:38.9993898 656   1988  WebServices     Auto proxy settings for this web service call.
    2017/10/17 09:36:40.9626103 656   1988  WebServices     WS error: There was an error communicating with the endpoint at 'http://WSUSSVR:8530/ClientWebService/client.asmx'.
    2017/10/17 09:36:40.9626133 656   1988  WebServices     WS error: There was an error receiving the HTTP reply.
    2017/10/17 09:36:40.9626150 656   1988  WebServices     WS error: The operation did not complete within the time allotted.
    2017/10/17 09:36:40.9626180 656   1988  WebServices     WS error: There was an error communicating with the endpoint at 'http://WSUSSVR:8530/ClientWebService/client.asmx'.
    2017/10/17 09:36:40.9626201 656   1988  WebServices     WS error: There was an error receiving the HTTP reply.
    2017/10/17 09:36:40.9626227 656   1988  WebServices     WS error: The operation did not complete within the time allotted.
    2017/10/17 09:36:40.9626244 656   1988  WebServices     WS error: The operation timed out
    2017/10/17 09:36:40.9626287 656   1988  WebServices     Web service call failed with hr = 8024401c.
    2017/10/17 09:36:40.9626304 656   1988  WebServices     Current service auth scheme=0.
    2017/10/17 09:36:40.9626312 656   1988  WebServices     Current Proxy auth scheme=0.
    2017/10/17 09:36:42.9707801 656   1988  WebServices     Auto proxy settings for this web service call.
    2017/10/17 09:37:44.9666419 656   1988  WebServices     WS error: There was an error communicating with the endpoint at 'http://WSUSSVR:8530/ClientWebService/client.asmx'.
    2017/10/17 09:37:44.9666449 656   1988  WebServices     WS error: There was an error receiving the HTTP reply.
    2017/10/17 09:37:44.9666470 656   1988  WebServices     WS error: The operation did not complete within the time allotted.
    2017/10/17 09:37:44.9666500 656   1988  WebServices     WS error: There was an error communicating with the endpoint at 'http://WSUSSVR:8530/ClientWebService/client.asmx'.
    2017/10/17 09:37:44.9666521 656   1988  WebServices     WS error: There was an error receiving the HTTP reply.
    2017/10/17 09:37:44.9666543 656   1988  WebServices     WS error: The operation did not complete within the time allotted.
    2017/10/17 09:37:44.9666649 656   1988  WebServices     WS error: There was an error communicating with the endpoint at 'http://WSUSSVR:8530/ClientWebService/client.asmx'.
    2017/10/17 09:37:44.9666688 656   1988  WebServices     WS error: There was an error receiving the HTTP reply.
    2017/10/17 09:37:44.9666718 656   1988  WebServices     WS error: The operation did not complete within the time allotted.
    2017/10/17 09:37:44.9666739 656   1988  WebServices     WS error: The operation timed out
    2017/10/17 09:37:44.9666777 656   1988  WebServices     Web service call failed with hr = 8024401c.
    2017/10/17 09:37:44.9666794 656   1988  WebServices     Current service auth scheme=0.
    2017/10/17 09:37:44.9666807 656   1988  WebServices     Current Proxy auth scheme=0.
    2017/10/17 09:37:44.9667016 656   1988  ProtocolTalker  PTError: 0x8024401c
    2017/10/17 09:37:44.9667046 656   1988  ProtocolTalker  SyncUpdates_WithRecovery failed. 0x8024401c
    2017/10/17 09:37:44.9667306 656   1988  ProtocolTalker  SyncUpdates round trips: 1
    2017/10/17 09:37:44.9667323 656   1988  ProtocolTalker  Sync of Updates 0x8024401c
    2017/10/17 09:37:44.9667844 656   1988  ProtocolTalker  SyncServerUpdatesInternal failed 0x8024401c
    2017/10/17 09:37:44.9742502 656   1988  Agent           Failed to synchronize, error = 0x8024401C
    2017/10/17 09:37:44.9862656 656   1988  Agent           Exit code = 0x8024401C
    2017/10/17 09:37:44.9862660 656   1988  Agent           * END * Finding updates CallerId = UpdateOrchestrator  Id = 1
    2017/10/17 09:37:44.9953582 656   632   ComApi          *RESUMED* Search ClientId = UpdateOrchestrator
    2017/10/17 09:37:44.9960098 656   632   ComApi          Updates found = 0
    2017/10/17 09:37:44.9960102 656   632   ComApi          Exit code = 0x00000000, Result code = 0x8024401C
    2017/10/17 09:37:44.9960106 656   632   ComApi          * END *   Search ClientId = UpdateOrchestrator
    2017/10/17 09:37:44.9964181 656   8372  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C

    Thanks

    Tuesday, October 17, 2017 8:50 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    According to the first log , it seems that you have more than one NICs in that computer , and , configured IPv6 , right ?

    To get the clear log , please try to disable other useless NICs and IPv6 address .

     

    Also please try to open URLs (to see if you can open that website successfully) :

    http://WSUSSVR:8530/SimpleAuthWebService/SimpleAuth.asmx
    http://WSUSSVR:8530/ClientWebService/client.asmx

    Any further information please feel  free to let us know .

    (In addition , If it is possible , please try to manually download and install a monthly CU such as august CU , then try to get updates from WSUS again)

    Best Regards,

    Elton

    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 Elton_Ji Wednesday, October 18, 2017 5:22 AM
    Wednesday, October 18, 2017 5:18 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Elton,

    The PC I got the logs from that time was my own laptop which does have 2 nics, but was only connected with the wireless adapter. The other affected machines have 1 or 2 nics.

    I can get to both sites from the PCs.

    Unfortunately now on the 1607 disc built PC I'm now getting "no format information found" :( when I run get-windowsupdatelog. On this machine yesterday (and the WSUS server) I disabled IPv6 and also killed the firewall on both. Neither change helped.

    1601/01/01 00:00:00.0000000 708   3996                  Unknown( 14): GUID=3905367d-5739-34f2-739b-cf9a482c3e56 (No Format Information found).
    1601/01/01 00:00:00.0000000 708   3996                  Unknown( 187): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).
    1601/01/01 00:00:00.0000000 708   3996                  Unknown( 188): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).
    1601/01/01 00:00:00.0000000 708   3996                  Unknown( 16): GUID=bc21bb5e-eb28-3f99-1073-acecfea6cb82 (No Format Information found).
    1601/01/01 00:00:00.0000000 708   3996                  Unknown( 16): GUID=bc21bb5e-eb28-3f99-1073-acecfea6cb82 (No Format Information found).
    1601/01/01 00:00:00.0000000 708   3996                  Unknown( 119): GUID=2fc03aa6-a1fa-3d0c-ba09-b8539ec28a26 (No Format Information found).

    WRT installing an update, I did that and went for the September one, but it made no difference. I even tried adding it to the MDT build too, but that didn't help. I will manually install it tho on this 1607 box.

    We are currently on for the time being 1607, but I installed a fresh 1703 build this morning from disc and that updates with the same reg settings and from the same WSUS box? (disc built 1607 left, disc built 1703 right)


    • Edited by warden976 Wednesday, October 18, 2017 10:28 AM
    Wednesday, October 18, 2017 10:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Looks like this is now sorted - https://community.spiceworks.com/topic/1970827-wsus-on-server-2016-windows-10-1607-client-0x8024401c-error

    Queue Length: 25000 from 10000 (i had to change this 3 time for it to stick)
    Limit Interval (minutes): 15 from 5
    "Service Unavailable" Response: TcpLevel from HttpLevel
    Private Memory Limit (KB): 0 from 18342456 (ours was already 0)

    And finally (which was the extra step for us) "In addition, you can edit the web.config ( C:\Program Files\Update Services\WebServices\ClientWebService\web.config  ) for WSUS
    Stop the IIS and do following changes:

    replace <httpRuntime maxRequestLength="4096" /> with <httpRuntime maxRequestLength="204800" executionTimeout="7200"/> "

    This seems to have sorted it for us.

    I'm intrigued tho and a somewhat baffled. This WSUS box has been in operation for a long time, patching our windows 10 1607 clients and I can't get my head round why it would suddenly and so consistently stop serving them.

    • Marked as answer by warden976 Thursday, October 19, 2017 8:56 AM
    Thursday, October 19, 2017 8:56 AM