none
WSUS problem - Machines timing out to reach server (0x8024401c) RRS feed

  • Question

  • Hi,

    Since last week our domain machines are getting time out to reach the WSUS server (Version 3.2.7600.226, Windows Server 2008 SP2 fully patched).

    Machines already patched contact WSUS normally.

    Tried this morning after rebooting the server with a Virtual Machine (all physical machine are getting the same error, fresh installations of the latest Windows 10 ISO available 1607 build 14393.0). This is the error:

    The machine appears on WSUS but with no report:

    Tried opening http://srv-ad02/ClientWebService/client.asmx on the browser and got this:

    Here is the WindowsUpdate.log:

    2016/12/09 08:17:55.5320185 808   2356  Shared          * START * Service startup
    2016/12/09 08:17:58.1362643 808   2356  Agent           WU client version 10.0.14393.0
    2016/12/09 08:17:58.1365191 808   2356  Agent           SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
    2016/12/09 08:17:58.1366005 808   2356  Agent           Base directory: C:\Windows\SoftwareDistribution
    2016/12/09 08:17:58.1373778 808   2356  Agent           Datastore directory: C:\Windows\SoftwareDistribution\DataStore\DataStore.edb
    2016/12/09 08:17:59.0805618 808   2356  DataStore       Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 added
    2016/12/09 08:17:59.0978707 808   2356  DataStore       Service 9482F4B4-E343-43B6-B170-9A65BC822C77 added
    2016/12/09 08:17:59.1060866 808   2356  DataStore       Data store successfully created
    2016/12/09 08:17:59.1629132 808   2356  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2016/12/09 08:17:59.1629322 808   2356  Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2016/12/09 08:17:59.1635234 808   2356  Shared          Network state: Connected
    2016/12/09 08:17:59.3679245 808   2356  Misc            LoadHistoryEventFromRegistry completed, hr = 8024000C
    2016/12/09 08:17:59.3784513 808   2356  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2016/12/09 08:17:59.3784562 808   2356  Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2016/12/09 08:17:59.3784612 808   2356  Shared          Power status changed
    2016/12/09 08:17:59.4357064 808   2356  Agent           Initializing Windows Update Agent
    2016/12/09 08:17:59.4386182 808   1892  Agent           Initializing global settings cache
    2016/12/09 08:17:59.4386188 808   1892  Agent           WSUS server: NULL
    2016/12/09 08:17:59.4386188 808   1892  Agent           WSUS status server: NULL
    2016/12/09 08:17:59.4386194 808   1892  Agent           Target group: (Unassigned Computers)
    2016/12/09 08:17:59.4386194 808   1892  Agent           Windows Update access disabled: No
    2016/12/09 08:17:59.4386975 808   2356  DownloadManager Download manager restoring 0 downloads
    2016/12/09 08:17:59.4611954 808   2356  Agent           CPersistentTimeoutScheduler | GetTimer, returned hr = 0x80248007
    2016/12/09 08:17:59.4612191 808   2356  Agent           CPersistentTimeoutEvent | Resubscribe, no existing/cached timer for Id=29A863E7-8609-4D1E-B7CD-5668F857F1DB.
    2016/12/09 08:17:59.4612250 808   2356  Agent           Adding timer:
    2016/12/09 08:17:59.4612315 808   2356  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2016-12-10 10:17:59, not idle-only, not network-only
    2016/12/09 08:17:59.4681931 808   2612  DownloadManager PurgeExpiredFiles::Found 0 expired files to delete.
    2016/12/09 08:17:59.4682270 808   2612  DownloadManager PurgeExpiredUpdates::Found 0 non expired updates.
    2016/12/09 08:17:59.4682313 808   2612  DownloadManager PurgeExpiredUpdates::Found 0 expired updates.
    2016/12/09 08:17:59.4781999 808   2612  Shared          Effective power state: AC
    2016/12/09 08:17:59.4782005 808   2612  DownloadManager Power state change detected. Source now: AC
    2016/12/09 08:18:00.4106294 304   1052  ComApi          * START *   SLS Discovery
    2016/12/09 08:18:00.4276665 304   1052  ComApi          *QUEUED* SLS Discovery
    1600/12/31 22:00:00.0000000 808   2648                  Unknown( 38): GUID=adf11b8c-baac-3d44-1059-4f8c843b025a (No Format Information found).
    2016/12/09 08:18:00.4540476 808   2648  SLS             Retrieving SLS response from server...
    2016/12/09 08:18:00.4540529 808   2648  Misc            Failed to get proxy settings token, not impersonating user. hr=800703f0
    2016/12/09 08:18:00.4546158 808   2648  SLS             Making request with URL HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/10.0.14393.0/0?CH=651&L=pt-BR&P=&PT=0x30&WUA=10.0.14393.0
    2016/12/09 08:18:00.4616141 808   2648  Misc            StatusCode for transaction returned from WinHttpQueryHeaders is 403
    2016/12/09 08:18:00.4616215 808   2648  Misc            WinHttp: SendRequestToServerForFileInformation failed with 0x80072ef3; retrying with default proxy.
    2016/12/09 08:18:01.9179650 808   2648  Misc            Validating signature for C:\Windows\SoftwareDistribution\SLS\9482F4B4-E343-43B6-B170-9A65BC822C77\sls.cab with dwProvFlags 0x00000080:
    2016/12/09 08:18:01.9256998 808   2648  Misc             Microsoft signed: NA
    2016/12/09 08:18:01.9257732 808   2648  Misc             Infrastructure signed: Yes
    2016/12/09 08:18:01.9279907 808   2648  Misc            Validating signature for C:\Windows\SoftwareDistribution\SLS\9482F4B4-E343-43B6-B170-9A65BC822C77\TMPF464.tmp with dwProvFlags 0x00000080:
    2016/12/09 08:18:01.9326968 808   2648  Misc             Microsoft signed: NA
    2016/12/09 08:18:01.9327621 808   2648  Misc             Infrastructure signed: Yes
    1600/12/31 22:00:00.0000000 808   2648                  Unknown( 38): GUID=adf11b8c-baac-3d44-1059-4f8c843b025a (No Format Information found).
    2016/12/09 08:18:01.9351296 808   2648  SLS             Retrieving SLS response from server...
    2016/12/09 08:18:01.9351312 808   2648  Misc            Failed to get proxy settings token, not impersonating user. hr=800703f0
    2016/12/09 08:18:01.9354503 808   2648  SLS             Making request with URL HTTPS://sls.update.microsoft.com/SLS/{855E8A7C-ECB4-4CA3-B045-1DFA50104289}/x64/10.0.14393.0/0?CH=651&L=pt-BR&P=&PT=0x30&WUA=10.0.14393.0
    2016/12/09 08:18:01.9413432 808   2648  Misc            StatusCode for transaction returned from WinHttpQueryHeaders is 403
    2016/12/09 08:18:01.9413503 808   2648  Misc            WinHttp: SendRequestToServerForFileInformation failed with 0x80072ef3; retrying with default proxy.
    2016/12/09 08:18:03.4162365 808   2648  Misc            Validating signature for C:\Windows\SoftwareDistribution\SLS\855E8A7C-ECB4-4CA3-B045-1DFA50104289\sls.cab with dwProvFlags 0x00000080:
    2016/12/09 08:18:03.4401291 808   2648  Misc             Microsoft signed: NA
    2016/12/09 08:18:03.4403409 808   2648  Misc             Infrastructure signed: Yes
    2016/12/09 08:18:03.4478150 808   2648  Misc            Validating signature for C:\Windows\SoftwareDistribution\SLS\855E8A7C-ECB4-4CA3-B045-1DFA50104289\TMPFA51.tmp with dwProvFlags 0x00000080:
    2016/12/09 08:18:03.4546643 808   2648  Misc             Microsoft signed: NA
    2016/12/09 08:18:03.4547480 808   2648  Misc             Infrastructure signed: Yes
    2016/12/09 08:18:03.8610691 304   1472  ComApi          *RESUMED* Discovery
    2016/12/09 08:18:03.8613201 304   1472  Api             * END *   Discovery ClientId
    2016/12/09 08:18:03.8948584 304   1052  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C
    2016/12/09 08:18:03.9075262 304   1052  ComApi          * START *   SLS Discovery
    2016/12/09 08:18:03.9111163 304   1052  ComApi          *QUEUED* SLS Discovery
    2016/12/09 08:18:03.9243733 304   1472  ComApi          *RESUMED* Discovery
    2016/12/09 08:18:03.9245101 304   1472  Api             * END *   Discovery ClientId
    2016/12/09 08:18:03.9261579 304   1052  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C
    2016/12/09 08:18:12.0489625 808   1892  Agent           Created new random SusClientId c55f4b6a-6fbb-408a-8b27-f553c8278a5e. Old Id: none.
    2016/12/09 08:18:12.5521496 808   1892  Agent           * START * Queueing Finding updates [CallerId = OOBE ZDP  Id = 1]
    2016/12/09 08:18:12.5521540 808   1892  Agent           Added service 00000000-0000-0000-0000-000000000000 to sequential scan list
    2016/12/09 08:18:12.5540525 1016  1040  ComApi          Search ClientId = OOBE ZDP
    2016/12/09 08:18:12.5570479 808   2860  Agent           * END * Queueing Finding updates [CallerId = OOBE ZDP  Id = 1]
    2016/12/09 08:18:12.5590017 808   2860  Agent           * START * Finding updates CallerId = OOBE ZDP  Id = 1
    2016/12/09 08:18:12.5590023 808   2860  Agent           Online = Yes; AllowCachedResults = No; Ignore download priority = No
    2016/12/09 08:18:12.5590030 808   2860  Agent           Criteria = IsInstalled = 0 AND DeploymentAction = 'Installation' AND CategoryIDs contains 'DD78B8A1-0B20-45C1-ADD6-4DA72E9364CF'""
    2016/12/09 08:18:12.5590048 808   2860  Agent           ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
    2016/12/09 08:18:12.5590051 808   2860  Agent           Search Scope = {Machine}
    2016/12/09 08:18:12.5590064 808   2860  Agent           Caller SID for Applicability: S-1-5-18
    2016/12/09 08:18:12.5590067 808   2860  Agent           RegisterService is set
    2016/12/09 08:18:12.5628929 808   2860  Misc            Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir Client/Server URL: https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx""
    2016/12/09 08:18:15.1339046 808   2860  ProtocolTalker  PT: Calling GetConfig on server
    2016/12/09 08:18:15.1462017 808   2860  WebServices     Auto proxy settings for this web service call.
    2016/12/09 08:18:15.2056757 808   2860  WebServices     WS error: Houve um erro na comunicação com o ponto de extremidade em 'https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx'.
    2016/12/09 08:18:15.2056766 808   2860  WebServices     WS error: O servidor retornou o código de status HTTP '403 (0x193)' com o texto 'Forbidden'.
    2016/12/09 08:18:15.2056769 808   2860  WebServices     WS error: O servidor compreendeu a solicitação, mas não pode atendê-la.
    2016/12/09 08:18:15.2056772 808   2860  WebServices     WS error: A operação não pôde ser concluída porque o canal foi cancelado.
    2016/12/09 08:18:15.2142496 808   2860  WebServices     Web service call failed with hr = 80244017.
    2016/12/09 08:18:15.2142502 808   2860  WebServices     Current service auth scheme=0.
    2016/12/09 08:18:15.2142505 808   2860  WebServices     Current Proxy auth scheme=0.
    2016/12/09 08:18:15.2142564 808   2860  ProtocolTalker  PTError: 0x80244017
    2016/12/09 08:18:15.2142574 808   2860  ProtocolTalker  GetConfig_WithRecovery failed 0x80244017
    2016/12/09 08:18:15.2142580 808   2860  ProtocolTalker  StartCategoryScan failed  0x80244017
    2016/12/09 08:18:15.2620310 808   2860  Agent           Exit code = 0x80244017
    2016/12/09 08:18:15.2620320 808   2860  Agent           * END * Finding updates CallerId = OOBE ZDP  Id = 1
    2016/12/09 08:18:15.2676319 1016  1108  ComApi          *RESUMED* Search ClientId = OOBE ZDP
    2016/12/09 08:18:15.2682623 1016  1108  ComApi          Updates found = 0
    2016/12/09 08:18:15.2682629 1016  1108  ComApi          Exit code = 0x00000000, Result code = 0x80244017
    2016/12/09 08:18:15.2682633 1016  1108  ComApi          * END *   Search ClientId = OOBE ZDP
    2016/12/09 08:18:15.3067946 1016  1040  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C

    Another log file ReportingEvents.log:

    {06524194-C72E-4719-BD26-DCEFA6471B03} 2016-12-09 08:18:15:252-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244017 OOBE ZDP Failure Software Synchronization Windows Update Client failed to detect with error 0x80244017.
    {F3BE3858-0419-45A7-A760-C97F6634E5A9} 2016-12-09 08:23:36:741-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244017 Device Driver Retrieval Client Failure Software Synchronization Windows Update Client failed to detect with error 0x80244017.
    {D62C8EE8-A092-4B85-A8DC-45E87D2612BC} 2016-12-09 08:26:24:554-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244017 Device Driver Retrieval Client Failure Software Synchronization Windows Update Client failed to detect with error 0x80244017.
    {7D4BBB27-B498-4041-9AEF-2B7A8C376D24} 2016-12-09 08:30:56:984-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244017 Device Driver Retrieval Client Failure Software Synchronization Windows Update Client failed to detect with error 0x80244017.
    {F7E17E09-ABD8-4523-9404-12309945CC61} 2016-12-09 08:42:18:390-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244017 TrustedInstaller FOD Failure Software Synchronization Windows Update Client failed to detect with error 0x80244017.
    {634ED6ED-D755-47D8-987B-881B8C909AD7} 2016-12-09 08:45:41:325-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244017 Device Driver Retrieval Client Failure Software Synchronization Windows Update Client failed to detect with error 0x80244017.
    {7299B290-F2BF-4764-83D7-28182A795608} 2016-12-09 08:50:21:278-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.
    {2DD39B82-6237-43F9-B035-F0E2A2531951} 2016-12-09 08:54:37:498-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.
    {3751DEC2-1458-4378-9BD4-C9C3AA501C11} 2016-12-09 09:00:38:248-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.
    {707D7D21-E52B-4607-ACC6-5E7D70F7A2BA} 2016-12-09 09:04:22:247-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.
    {A95F896A-A357-40B6-AD13-A011C3CEDD4A} 2016-12-09 09:04:22:591-0200 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 0 updates.
    {82AA2F98-B352-49F8-9EEE-AB5713E8C64C} 2016-12-09 09:07:46:216-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.
    {0BF58FA2-8BE2-4CE0-BA2E-E06B4BBA2840} 2016-12-09 09:07:46:513-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80248014 Update;taskhostw Failure Software Synchronization Windows Update Client failed to detect with error 0x80248014.
    {2CFC1DC4-62D3-4DE6-837F-CA7D5781D490} 2016-12-09 09:09:47:685-0200 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 0 updates.
    {AE1AC183-DB92-42F8-A2D6-70BA4DDC952E} 2016-12-09 09:20:48:935-0200 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Success Software Synchronization Windows Update Client successfully detected 0 updates.
    {C0E47BEC-4F18-4A87-A919-54C3BC7554E4} 2016-12-09 09:41:42:248-0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 8024401c UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x8024401c.


    • Edited by Vandrey Trindade Friday, December 9, 2016 3:54 PM Added WSUS version
    Friday, December 9, 2016 11:49 AM

Answers

  • Same problem here, i have a w2k8r2 wsus running. W7,W2k8r2 and W2k12 clients updates normal, but with all W10 clients i always get the 0x8024401c connection lost error. I checked some W10 clients, nothing to find what can be fixed. The error comes during end of Nov to now, maybe with the upload of cumulative update kb320184 last week to wsus. Before i had no problems with my W10 clients. I blow up the iss pool mem for wsus, i repaired local .net on wsus. 0x8024401c Still there.

    Then i read something about the asp 1309 error in appeventlog and i changed the execution timeout for asp from 110sec to 300sec on iis wsus site ... and now W10 clients get their updates :)



    • Edited by Clemenca Wednesday, December 14, 2016 3:58 PM
    • Marked as answer by Vandrey Trindade Thursday, December 15, 2016 12:18 PM
    Wednesday, December 14, 2016 11:58 AM

All replies

  • Hi Vandrey Trindade,

    The version of your WSUS server is old now. For WSUS 3.0:

    WSUS 3.0 (SP2): Build 3.2.7600.226
    WSUS 3.0 (SP2) + KB2720211: Build 3.2.7600.251
    WSUS 3.0 (SP2) + KB2734608: Build 3.2.7600.256
    WSUS 3.0 (SP2) + KB2828185: Build 3.2.7600.262
    WSUS 3.0 (SP2) + KB2938066: Build 3.2.7600.274

    So, if you still on WSUS 3.0, please install KB2938066 to upgrade your WSUS server.

    While, if the WSUS server have win10 clients, then, you'd upgrade your WSUS server to 4.0, install on server 2012(R2) or server 2016, since, WSUS 3.0 only support minimal win10 updates:

    https://blogs.technet.microsoft.com/wsus/2016/01/22/for-those-on-wsus-3-0-sp2-or-sbs-2011/

    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.

    Monday, December 12, 2016 2:17 AM
    Moderator
  • Anne He,

    Sorry but I disagree on that.

    First, I already read that article, and as it says:

    "Because WSUS 3.0 SP2 is already in extended support (receiving no support at all after January 2020)"

    Second, I can't deploy the Windows 10 features, like Anniversary Update, but security patches I can.

    I'm using it since Windows 10 release and had no problems at all with it. Machines already patched receive updates normally (last week I installed the KB3201845 patch deployed by WSUS). Only fresh install machines are having this problem.

    Monday, December 12, 2016 10:23 AM
  • Was going to create a new thread on this, but then i see this topic at the top of the list, so i will chime in. My situation is a bit different. I use WSUS 4 (new installation on WS2012R2 - VM). I have replaced our old WSUS 3 with it and all machines have successfully switched to it (Win7/WS2008/WS2008R2/WS2012/WS2012R2). Now i have one new laptop with Win10 (fresh install of 1607 build) and it can't check for updates. Reports 0x8024401c or (f at the end). More so, it completely bogs down WSUS server when checking for updates (1 machine!). In the event log i get ASP.NET errors about httprequest timing out. I have already tried to add more CPU and RAM to this VM, but it only helped a bit with the load.

    I know there is a hotfix for WSUS 4 for it to understand feature updates. I haven't installed it before doing first synchronization. Although i haven't checked Upgrades classification as i only need security updates. So maybe i'm not affected by this. I have since installed this hotfix and WSUS now shows that machine as "Windows (Version 10.0)" (was showing Windows Vista before). Still "Not reported yet" status. Haven't tried to update that machine from the internet first yet.

    I have found information that httprequest time out might be related to IIS not having enough resources. Win10 cumulative updates are of 1.5 GB size or even more, so maybe IIS can't handle them. Maybe it needs to give Application pool more usable memory. Although this worked before for Vandrey. Unless recent increase in cumulative size caused this issue. My Win10 is just week old, so maybe this issue is new one.

    Monday, December 12, 2016 10:36 AM
  • That's the article i have found on IIS resources issues https://blogs.technet.microsoft.com/configmgrdogs/2016/11/02/windows-update-error-80072ee2-wsus/
    Monday, December 12, 2016 10:41 AM
  • wrootw,

    Thanks! It's hard to search for solutions when using old versions. Everyone says to "upgrade and all will work ok". But I can't upgrade my servers for a reason. I'm the IT guy, not the boss lol

    I'll take a look on the link you sent.

    Monday, December 12, 2016 10:47 AM
  • Well, i have tried to change default value of Private Memory 1843200 in Recycling section of WsusPool (Advanced settings) to 3072000. Rebooted the server. No effect. That's just blind guessing. I haven't found any other setting related to memory (over than virtual memory field, but it is 0 by default). So, unless someone suggests how to increase memory for application pool or at least confirms that's the case here.

    I'm going to update that machine from Internet to test the theory that it only fails for fresh install.

    Monday, December 12, 2016 11:41 AM
  • Have tried to update it from Internet (including the infamous KB3201845). Still no luck with checking from WSUS.
    Monday, December 12, 2016 12:50 PM
  • wrootw,

    I've checked my machine Windows Update log.

    Last friday when I installed the latest W10 cumulative pack:

    2016/12/09 14:48:50.5615014 1164  2592  ComApi          *RESUMED* Search ClientId = UpdateOrchestrator
    2016/12/09 14:48:50.6811735 1164  2592  ComApi          Updates found = 1
    2016/12/09 14:48:50.6811741 1164  2592  ComApi          Reboot required
    2016/12/09 14:48:50.6811747 1164  2592  ComApi          * END *   Search ClientId = UpdateOrchestrator
    2016/12/09 14:48:50.6872160 1164  9388  ComApi          ISusInternal:: DisconnectCall failed, hr=8024000C
    2016/12/09 14:49:19.5784331 1164  4836  ComApi          * START *   Commit   ClientId = UpdateOrchestrator
    1600/12/31 22:00:00.0000000 1164  4836                  Unknown( 242): GUID=fde1d6c9-915b-3206-4ef5-31d14b23d758 (No Format Information found).
    1600/12/31 22:00:00.0000000 1076  7968                  Unknown( 69): GUID=e26dfe10-35bf-3106-db9d-9a51a6a0981f (No Format Information found).
    1600/12/31 22:00:00.0000000 1076  7968                  Unknown( 72): GUID=e26dfe10-35bf-3106-db9d-9a51a6a0981f (No Format Information found).
    1600/12/31 22:00:00.0000000 1076  7968                  Unknown( 75): GUID=e26dfe10-35bf-3106-db9d-9a51a6a0981f (No Format Information found).
    1600/12/31 22:00:00.0000000 1164  4836                  Unknown( 288): GUID=0defb9f2-be29-3d72-4390-6806b45a584c (No Format Information found).
    2016/12/09 14:49:19.6323425 1164  4836  ComApi          * END *   Commit   hr=0x00000000

    (Just a part of the log file)

    What's all those 1600/12/31 entries?

    Monday, December 12, 2016 1:04 PM
  • wrootw,

    What is your server hardware specifications?

    Mine is 12 GB of RAM and 4 CPUs, will try to add more processors and more RAM to it...

    Monday, December 12, 2016 1:19 PM
  • My log has such entries:

    1601-01-01 02:00:00.0000000 84    5528                  Unknown( 230): GUID=8ce98bfa-21f0-385f-839a-1073774029ac (No Format Information found).
    1601-01-01 02:00:00.0000000 84    5528                  Unknown( 240): GUID=8ce98bfa-21f0-385f-839a-1073774029ac (No Format Information found).
    1601-01-01 02:00:00.0000000 84    5528                  Unknown( 241): GUID=8ce98bfa-21f0-385f-839a-1073774029ac (No Format Information found).

    Monday, December 12, 2016 1:36 PM
  • Mine is Hyper-V VM machine with 2 virtual CPUs and 6 GB RAM currently (on a physical Xeon 5110). It was 1 CPU and just 3 GB before and it was enough for 200+ machines.
    Monday, December 12, 2016 1:38 PM
  • Mine is ESXi 5.5 machine. 4 virtual CPUs and 12 GB RAM (on a physical PowerEdge 2950).

    It does not seem to be RAM the problem....

    Monday, December 12, 2016 1:40 PM
  • I'm going to try Experess Files as described in this article (though i'm not sure this applies to security updates) https://technet.microsoft.com/en-us/itpro/windows/manage/waas-manage-updates-wsus?f=255&MSPPError=-2147217396

    And then maybe Download from Microsoft Update option. Not ideal, but maybe not a huge deal in our case.

    Monday, December 12, 2016 1:52 PM
  • What classifications do you have enabled in WSUS? I only have Critical Updates, Security Updates, Service Packs and Update Rollups. I do not have Upgrades enabled.
    Monday, December 12, 2016 1:59 PM
  • wrootw,

    Mine is using "Synchronize from Microsoft Update" (since it's the only WSUS I have), and all classifications except "Drivers".

    Your WSUS is new?

    Mine was working two weeks ago.

    Funny thing that one guy that works with me told me: One machine we were testing, gave this time out error then when I rebooted the server it got updates. Now all machines (fresh install only) are getting time out errors.

    Monday, December 12, 2016 3:23 PM
  • wrootw,

    I was checking my WSUS server event viewer and found this error:

    Event code: 3001
    Event message: The request has been aborted.
    Event time: 12/12/2016 12:50:48 PM
    Event time (UTC): 12/12/2016 2:50:48 PM
    Event ID: d801fd6c72524c898d9ab2ac63c66e0f
    Event sequence: 13311
    Event occurrence: 10
    Event detail code: 0
     
    Application information:
        Application domain: /LM/W3SVC/1/ROOT/ClientWebService-1-131260041497943423
        Trust level: Full
        Application Virtual Path: /ClientWebService
        Application Path: C:\Program Files\Update Services\WebServices\ClientWebService\
        Machine name: SRV-AD02
     
    Process information:
        Process ID: 12512
        Process name: w3wp.exe
        Account name: NT AUTHORITY\NETWORK SERVICE
     
    Exception information:
        Exception type: HttpException
        Exception message: Request timed out.
     
    Request information:
        Request URL: http://srv-ad02/ClientWebService/client.asmx
        Request path: /ClientWebService/client.asmx
        User host address: 192.168.40.54
        User: 
        Is authenticated: False
        Authentication Type: 
        Thread account name: NT AUTHORITY\NETWORK SERVICE
     
    Thread information:
        Thread ID: 85
        Thread account name: NT AUTHORITY\NETWORK SERVICE
        Is impersonating: False
        Stack trace: 
      
    Custom event details:

    Monday, December 12, 2016 3:56 PM
  • wrootw,

    New update: Tried a Windows 7 machine and it gives me the same event viewer error. Not a Windows 10 problem.

    Monday, December 12, 2016 4:16 PM
  • wrootw,

    I get the same event viewer error on the server when trying to access this address from my computer:

    http://srv-ad02/ClientWebService/client.asmx

    Can anyone help with this?

    Monday, December 12, 2016 4:40 PM
  • Changed the web.config file, set customErrors to "Off". This is the result when I try to open that path on the browser now:

    Server Error in '/ClientWebService' Application.

    Request format is unrecognized.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.InvalidOperationException: Request format is unrecognized.

    Source Error:
    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:
    [InvalidOperationException: Request format is unrecognized.]
       System.Web.Services.Protocols.WebServiceHandlerFactory.CoreGetHandler(Type type, HttpContext context, HttpRequest request, HttpResponse response) +401258
       System.Web.Services.Protocols.WebServiceHandlerFactory.GetHandler(HttpContext context, String verb, String url, String filePath) +281
       System.Web.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +425
       System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +263
    

    Monday, December 12, 2016 5:41 PM
  • Yes, my WSUS is the new installation of WSUS 4 on WS2012R2. Installed and configured a few weeks ago, connected one WS2012 server to it and it was working fine, then i have moved all my other machines to it and it was working fine. Only that one new Win10 machine can't check updates. Windows 7 machines are fine. I have just installed updates and refreshed the status on a few of them today. So, for me this IS a Win10 issue, it seems.

    I'm getting the same event like you do when Win10 machine tries to check for updates. It time outs. It looks like WSUS is not able to response quickly enough.

    Enabling Express files was not a good idea. It started downloading additional files for every update already in the database (thousands of updates, 200+ GB of data..). We can't have terabytes dedicated just to store update files. I'm going to rebuild my WSUS from a scratch tomorrow and i will install both patches mentioned in that article before picking any classifications or products or doing sync. Will see if that changes anything.

    I have only installed KB3095113 previously. But maybe you still need this one too KB3159706

    The second one requires additional manual operations after the installation.

    So maybe WSUS would be able to decode Win10 updates. But i'm still puzzled, as it seems it was working for you and then stopped. I suspect that won't help me anyway. As we will need to prepare new laptops soon, i feel i will just install Win7 on them and won't bother anymore :D

    Monday, December 12, 2016 7:48 PM
  • Try installing kb3172605 on a machine that isn't getting updates and report back.
    Monday, December 12, 2016 9:10 PM
  • WSUS-Luis, i know this update and i'm already using it for a month or so. It helps speed up WU check whether using WSUS or not (using it at home with Win7 also). But that's it. It just makes checks faster. And there is no such update for Win10. Maybe it will help fix Win7 machines for Vandrey. My Win7 are checking fine with WSUS.
    Tuesday, December 13, 2016 4:17 AM
  • wrootw,

    Today I rebooted the server and added 2 more CPUs.

    Same event viewer error.

    All clients (tried Windows 7, 10) generate the same event.

    Even from the server itself I can't open that URL...

    Maybe an update broke ASP.NET for me?


    Tuesday, December 13, 2016 12:17 PM
  • I'm in the process of rebuilding my server. WSUS role uninstall botched whole server for some reason.. So it is clean install of WS2012R2 and i will not update it for now (except for needed patches). So, will see if that's some .NET update causing that.
    Tuesday, December 13, 2016 12:20 PM
  • Progress so far: i have rebuilt my WS2012R2 server and installed WSUS, then installed KB3095113 (downloaded from MS site) and KB3159706 (this is only available via WU as optional update, so i have not connected this server to WSUS yet and checked for updates from MS servers, have not installed any other update except for this one optional update). Then made additional changes described on KB3159706 page (one cmd command and additional feature install, not using SSL, so less to do). Then i have done initial WSUS configuration, but only selected Windows 7 and Security Updates, haven't done initial synchronization. In WSUS i already found all my network PCs connected with correct status. Then i have launched Win10 laptop and did Check updates. It went very fast and without an error (1 second maybe). No load on the server (probably because there are no huge Win10 updates stored on it yet). Win10 PC appeared in WSUS with no status. Doing additional checks was not producing any errors (just showed "Up to date" message). But the status hasn't updated. Well, that's usual for WU agent to not update its status to WSUS when you are doing check for updates. It usually does it on its own schedule. But then i have ran "wuauclt /reportnow" command on Win10 and it has updated its status in WSUS correctly.

    So now i'm going to finalize things step by step (enabling firewall on the server, installing updates, antivirus, etc.) and watch if it gets broken at some point.

    Wednesday, December 14, 2016 8:57 AM
  • wrootw,

    Nice!

    I found two more events, now on IIS:

    I don't understand nothing about IIS... if someone can help...

    I checked the WID memory and is configured to 2GB maximum... it is alright?

    Wednesday, December 14, 2016 11:41 AM
  • Same problem here, i have a w2k8r2 wsus running. W7,W2k8r2 and W2k12 clients updates normal, but with all W10 clients i always get the 0x8024401c connection lost error. I checked some W10 clients, nothing to find what can be fixed. The error comes during end of Nov to now, maybe with the upload of cumulative update kb320184 last week to wsus. Before i had no problems with my W10 clients. I blow up the iss pool mem for wsus, i repaired local .net on wsus. 0x8024401c Still there.

    Then i read something about the asp 1309 error in appeventlog and i changed the execution timeout for asp from 110sec to 300sec on iis wsus site ... and now W10 clients get their updates :)



    • Edited by Clemenca Wednesday, December 14, 2016 3:58 PM
    • Marked as answer by Vandrey Trindade Thursday, December 15, 2016 12:18 PM
    Wednesday, December 14, 2016 11:58 AM
  • Back with the same problem. All i did is enabling Windows 10 product (just Windows 10, not other Windows 10 products (LTSB, with drivers and other stuff) and synchronizing again. It's interesting that while just synchronizing CPU was climbing to 100% sometimes. But it stayed around 70 on average. Then i have tried checking for updates in Win10 and it gave me the same 0x8024401c error and the server was bogged down with 100% (even 10 minutes after client showed the error). So it seems that's one of the latest updates released for Win10 which is driving WSUS or rather IIS nuts. I doubt MS will react fast on that, unless it also affects SCCM..
    Wednesday, December 14, 2016 2:28 PM
  • Thinking maybe this SCOM crash after October 2016 CU update is related https://blogs.technet.microsoft.com/germanageability/2016/10/17/october-2016-windows-patch-kb3192392-might-cause-scom-2012r2-console-to-crash/
    Wednesday, December 14, 2016 2:49 PM
  • Clemenca,

    Can you post the steps to change that setting?

    PS: Found that tip also https://www.404techsupport.com/2016/03/iis-wsus-private-memory/
    Wednesday, December 14, 2016 4:05 PM
  • wrootw,

    It started at the end of November here too.

    Funny that only us are having this problem it seems...

    Wednesday, December 14, 2016 4:06 PM
  • go to iismanager- site of wsus - configurationeditor - system.web/httpRuntime - executiontimeout 5min -  webservice restart via services
    Wednesday, December 14, 2016 11:27 PM
  • hmmm...good question, all w2k8r2 wsus should run in this problem with default executiontimeout ...
    Wednesday, December 14, 2016 11:29 PM
  • Thanks, Clemenca!

    In case someone runs into same problem with WSUS 4 on WS2012R2: i have opened IIS Manager and right-clicked Sites > WSUS Administration site. Went into Advanced settings, expanded Limits section and increased Connection Time-out from 180 to 320. Rebooted the server. When doing updates check from Win10 machine it was faster than before and the load on the server was very brief. Win10 reported status and found updates on WSUS correctly. I suspect i might need to bump that limit even more in the future once more updates for Windows 10 come out and the total size of download files increases.

    Thursday, December 15, 2016 8:16 AM
  • Yes i also think that in the future the limit need to be bump up again depends on the size of the updates, also my wsus is runing quicker than before
    • Edited by Clemenca Thursday, December 15, 2016 9:24 AM
    Thursday, December 15, 2016 9:03 AM
  • Clemenca,

    Sorry, but I can't find that "Configuration editor" (IIS 6 here).

    Changed the connection time-out to 320 and rebooted the server and no joy for me.


    Thursday, December 15, 2016 10:14 AM
  • i just only have iis 7 here, i think you finde it under sitepropertis/asp in iis6


    Thursday, December 15, 2016 10:40 AM
  • Clemenca,

    I'm trying this line on the web.config file (system.web session):

    <httpRuntime maxRequestLength="204800" executionTimeout="7200"/>


    Can you send me how your file is configured? That line only...
    Thursday, December 15, 2016 10:42 AM
  • Clemenca and wrootw,

    It seems to be working again now.

    Will try this configuration until next week to see how the server behaves.

    Thanks for all your attention!

    Thursday, December 15, 2016 12:18 PM
  • Well, i hope it will work for you. It stopped working for me. I have already tried 640 limit, but it's the same. The more updates i enable, the worse it gets. I have wasted too much time on this already. So for now a few laptops will be updating from MS servers and in future we will have to think about Intune or something else.
    Friday, December 16, 2016 8:57 AM
  • wrootw,

    Sorry! Do you want me to unmark this post keep it as not resolved?

    Let me tell you the changes I made:

    First I changed that setting to 0 (Unlimited): https://www.404techsupport.com/2016/03/iis-wsus-private-memory/

    Then I went to IIS and set the connection time-out to 320

    And the last thing, I changed the web.config file (under C:\Program Files\Update Services\WebServices\clientwebservices).

    Changed this line:

        <httpRuntime maxRequestLength="600" />

    For this line:

        <httpRuntime maxRequestLength="204800" executionTimeout="7200"/>

    And rebooted the server.

    Let us know if you still have problems.


    Friday, December 16, 2016 10:38 AM
  • If this works for you, you can leave the thread as solved.

    I have added WsusPool and we.config changes and first time the check was fine. But it was with Win10 which i have already updated from Internet. But when i try to check from fresh 1607 machine it behaves the same (huge load on the server and error on the client). Unless that's some update for Win10 which fixes this situation and that's why it works for updated machine.. Will have to monitor it.

    Friday, December 16, 2016 12:32 PM
  • Hi,

    Are you able to give the exact instructions on how to do this?
    I tried adjusting Configure > Limits (In IIS - WSUS Administation Website) to 300 and even 360, but still did not work.

    Thanks.

    Tuesday, June 20, 2017 1:54 AM
  • Well, i hate to advertise my own blog here, but i don't want to paste whole article here. There are more options to change than that single one and also a few pre-requisites even before you try to do Win10 updates via WSUS. So read this http://www.wroot.lt/wp/technology/wsus-woes-with-windows-10-en/

    And then for the Creators Update http://www.wroot.lt/wp/technology/wsus-updating-windows-10-to-creators-update-en/

    Tuesday, June 20, 2017 3:53 AM
  • After 9 months, Microsoft released a patch to this problem:

    https://www.microsoft.com/en-us/download/details.aspx?id=55793

    Tuesday, August 29, 2017 4:23 PM
  • Thanks for letting know. Maybe this will make fresh 1607 install not to fail. I won't be installing the fix as it currently works fine for me. But will note it if i ever need to rebuild the WSUS server.
    Tuesday, August 29, 2017 5:03 PM
  • All my Windows 10 1607 and Server 2016 1607 had error 0x8024401c.
    Some IIS Application Pool tuning tips didn't help.
    Adamj's Clean-WSUS PowerShell 3 script running on WSUS Srv solved the problem:
    http://community.spiceworks.com/scripts/show/2998-adamj-clean-wsus
    https://community.spiceworks.com/topic/1970827-wsus-on-server-2016-windows-10-1607-client-0x8024401c-error
    Thursday, October 19, 2017 8:50 AM
  • All my Windows 10 1607 and Server 2016 1607 had error 0x8024401c.
    Some IIS Application Pool tuning tips didn't help.
    Adamj's Clean-WSUS PowerShell 3 script running on WSUS Srv solved the problem:
    http://community.spiceworks.com/scripts/show/2998-adamj-clean-wsus
    https://community.spiceworks.com/topic/1970827-wsus-on-server-2016-windows-10-1607-client-0x8024401c-error

    Thank you for mentioning my script :)

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

    Friday, October 20, 2017 3:34 AM