Share via

Windows 10 Client SCCM doesn't process to update

Question

Friday, July 19, 2019 5:58 AM

Hello everybody, 

Sorry for my english, i'm french.. 

I have a problem with different sites of my SCCM infrastructure. My Windows 10 Client do not update from SUP replica. 

I verified the synchro between primary SUP and replica and it's ok. 

I have one GPO applied on my client : To forbidden the client to download update on Internet

My Configuration Manager Client is ok (i Can access to software center and download some soft, i can run all the actions)

You can see the WindowsUpdate.log : 

2019/07/18 14:34:00.8363747 5172  8172  ComApi          *FAILED* [8024500C] Method failed [CSLSClientProxy::GetSLSDataChunk:254]
2019/07/18 14:34:00.8367994 7304  4732  ComApi          *FAILED* [8024500C] Method failed [CSLSClientProxy::GetSLSDataChunk:254]
2019/07/18 14:34:00.8368006 5172  1776  ComApi          *FAILED* [8024500C] Method failed [CSLSClientProxy::GetSLSDataChunk:254]
2019/07/18 14:34:00.8372421 4916  7996  DownloadManager Received power state change notification: Old: <unknown>; New: AC.
2019/07/18 14:34:00.8372491 4916  7996  DownloadManager Power state changed from <unknown> to AC.
2019/07/18 14:34:00.8373730 5172  1776  ComApi          * START *   SLS Discovery
2019/07/18 14:34:00.8399960 4916  4708  IdleTimer       WU operation (CDiscoveryCall::Init ID 4) started; operation # 18; does use network; is not at background priority
2019/07/18 14:34:00.8402202 5172  1776  ComApi          *QUEUED* SLS Discovery
2019/07/18 14:34:00.8406042 4916  3064  IdleTimer       WU operation (CDiscoveryCall::Init ID 4, operation # 18) stopped; does use network; is not at background priority
2019/07/18 14:34:00.8488165 7304  4732  ComApi          * START *   Federated Search ClientId = Update;ScanForUpdatesForUser (cV: zw/o+uI56Uydct1Z.0.3.1.1.0)
2019/07/18 14:34:00.8505573 4916  4708  IdleTimer       WU operation (SR.Update;ScanForUpdatesForUser ID 5) started; operation # 21; does use network; is not at background priority
2019/07/18 14:34:00.8509514 4916  4360  Agent           *FAILED* [80240007] Method failed [CAgentServiceManager::GetTargetedServiceMapping:3010]
2019/07/18 14:34:00.8509735 4916  4360  Agent           *FAILED* [80248014] GetServiceObject couldn't find service '855E8A7C-ECB4-4CA3-B045-1DFA50104289'.
2019/07/18 14:34:00.8509796 4916  4360  Agent           *FAILED* [80248014] Method failed [CAgentServiceManager::GetServiceObject:1967]
2019/07/18 14:34:00.8509831 4916  4360  Agent           Processing auto/pending service registrations and recovery.
2019/07/18 14:34:00.8515391 4916  4360  Misc            *FAILED* [8024500C] Method failed [CSLSEndpointProvider::GetWUClientData:2028]
2019/07/18 14:34:00.8515562 4916  4360  Misc            *FAILED* [8024500C] Method failed [CSLSEndpointProvider::GetSecondaryServicesEnabledState:1535]
2019/07/18 14:34:00.8515712 4916  4360  Agent           *FAILED* [8024500C] Method failed [CAgentServiceManager::DetectAndToggleServiceState:2896]
2019/07/18 14:34:00.8515809 4916  4360  Agent           *FAILED* [8024500C] Failed to resolve federated serviceId 855E8A7C-ECB4-4CA3-B045-1DFA50104289
2019/07/18 14:34:00.8515979 4916  4360  Agent           *FAILED* [8024500C] Failed to execute service registration call {0AEC6F1B-0B67-4BD0-9CA6-4B8C9213B9F1} (cV: zw/o+uI56Uydct1Z.0.3.1.1.0.1)
2019/07/18 14:34:00.8516400 4916  4360  IdleTimer       WU operation (SR.Update;ScanForUpdatesForUser ID 5, operation # 21) stopped; does use network; is not at background priority
2019/07/18 14:34:00.8627775 5172  2052  ComApi          *RESUMED* Discovery
2019/07/18 14:34:00.8627832 7304  2976  ComApi          * END *   Federated Search failed to process service registration, hr=0x8024500C (cV = zw/o+uI56Uydct1Z.0.3.1.1.0)
2019/07/18 14:34:00.8627886 5172  2052  ComApi          Exit code = 0x00000000, Result code = 0x8024500C
2019/07/18 14:34:00.8627925 5172  2052  Api             * END *   Discovery ClientId
2019/07/18 14:34:00.8663996 5172  1776  ComApi          *FAILED* [8024500C] Method failed [CSLSClientProxy::GetSLSDataChunk:254]
2019/07/18 14:38:02.1789985 7956  4664  ComApi          * START *   SLS Discovery
2019/07/18 14:38:02.1832018 4916  7864  IdleTimer       WU operation (CDiscoveryCall::Init ID 6) started; operation # 28; does use network; is not at background priority
2019/07/18 14:38:02.1836128 7956  4664  ComApi          *QUEUED* SLS Discovery
2019/07/18 14:38:02.1842212 4916  3064  IdleTimer       WU operation (CDiscoveryCall::Init ID 6, operation # 28) stopped; does use network; is not at background priority
2019/07/18 14:38:02.1995063 7956  4492  ComApi          *RESUMED* Discovery
2019/07/18 14:38:02.1995332 7956  4492  ComApi          Exit code = 0x00000000, Result code = 0x8024500C
2019/07/18 14:38:02.1995358 7956  4492  Api             * END *   Discovery ClientId
2019/07/18 14:38:02.2027272 7956  4664  ComApi          *FAILED* [8024500C] Method failed [CSLSClientProxy::GetSLSDataChunk:254]
2019/07/18 14:38:02.2051444 7956  4664  ComApi          * START *   SLS Discovery
2019/07/18 14:38:02.2066346 4916  7864  IdleTimer       WU operation (CDiscoveryCall::Init ID 7) started; operation # 33; does use network; is not at background priority
2019/07/18 14:38:02.2068408 7956  4664  ComApi          *QUEUED* SLS Discovery
2019/07/18 14:38:02.2076662 4916  3064  IdleTimer       WU operation (CDiscoveryCall::Init ID 7, operation # 33) stopped; does use network; is not at background priority
2019/07/18 14:38:02.2151030 7956  4492  ComApi          *RESUMED* Discovery
2019/07/18 14:38:02.2151096 7956  4492  ComApi          Exit code = 0x00000000, Result code = 0x8024500C
2019/07/18 14:38:02.2151121 7956  4492  Api             * END *   Discovery ClientId
2019/07/18 14:38:02.2180550 7956  4664  ComApi          *FAILED* [8024500C] Method failed [CSLSClientProxy::GetSLSDataChunk:254]
2019/07/18 14:44:01.1637172 1872  4664  ComApi          * START *   Federated Search ClientId = Antivirus Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24) (cV: YA4AuGfKWkatWtBt.1.0)
2019/07/18 14:44:01.1654441 4916  7864  IdleTimer       WU operation (SR.Antivirus Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24) ID 8) started; operation # 41; does use network; is not at background priority
2019/07/18 14:44:01.1655922 4916  4360  Agent           *FAILED* [80240007] Method failed [CAgentServiceManager::GetTargetedServiceMapping:3010]
2019/07/18 14:44:01.1656264 4916  4360  IdleTimer       WU operation (SR.Antivirus Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24) ID 8, operation # 41) stopped; does use network; is not at background priority
2019/07/18 14:44:01.1700835 1872  7956  ComApi          Federated Search: Starting search against 1 service(s) (cV = YA4AuGfKWkatWtBt.1.0)
2019/07/18 14:44:01.1702749 1872  7956  ComApi          * START *   Search ClientId = Antivirus Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24), ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7, Flags: 0X10010 (cV = YA4AuGfKWkatWtBt.1.0.0)
2019/07/18 14:44:01.1723306 4916  7864  IdleTimer       WU operation (CSearchCall::Init ID 9) started; operation # 44; does use network; is not at background priority
2019/07/18 14:44:01.1724498 4916  7864  Reporter        OS Product Type = 0x00000079
2019/07/18 14:44:01.2039260 4916  7864  Agent           * START * Queueing Finding updates [CallerId = Antivirus Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24)  Id = 9]
2019/07/18 14:44:01.2039450 4916  7864  Agent           Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is not in sequential scan list
2019/07/18 14:44:01.2039551 4916  7864  Agent           Added service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 to sequential scan list
2019/07/18 14:44:01.2044612 4916  6664  Agent           Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is in sequential scan list
2019/07/18 14:44:01.2058405 4916  9012  Agent           * END * Queueing Finding updates [CallerId = Antivirus Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24)  Id = 9]
2019/07/18 14:44:01.2067547 4916  9012  Agent           * START * Finding updates CallerId = Antivirus Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24)  Id = 9 (cV = YA4AuGfKWkatWtBt.1.0.0.2)
2019/07/18 14:44:01.2067610 4916  9012  Agent           Online = Yes; Interactive = Yes; AllowCachedResults = No; Ignore download priority = No
2019/07/18 14:44:01.2067675 4916  9012  Agent           Criteria = (IsInstalled = 0 and IsHidden = 0 and CategoryIDs contains '8c3fcc84-7410-4a95-8b89-a166a0190486' and CategoryIDs contains 'e0789628-ce08-4437-be74-2495b842f43b' and Type = 'Software')""
2019/07/18 14:44:01.2067747 4916  9012  Agent           ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2019/07/18 14:44:01.2067768 4916  9012  Agent           Search Scope = {Machine}
2019/07/18 14:44:01.2067829 4916  9012  Agent           Caller SID for Applicability: S-1-5-18
2019/07/18 14:44:01.2725773 4916  9012  Misc            Got WSUS Client/Server URL: https://DLS-DP.mou-source.college.local:8531/ClientWebService/client.asmx""
2019/07/18 14:44:01.3354126 4916  9012  ProtocolTalker  ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = https://DLS-DP.mou-source.college.local:8531/ClientWebService/client.asmx
2019/07/18 14:44:01.3354166 4916  9012  ProtocolTalker  OK to reuse existing configuration
2019/07/18 14:44:01.3354351 4916  9012  ProtocolTalker  Cached cookie has expired or new PID is available
2019/07/18 14:44:01.3354726 4916  9012  Misc            Got WSUS SimpleTargeting URL: https://DLS-DP.mou-source.college.local:8531""
2019/07/18 14:44:01.3372296 4916  9012  IdleTimer       WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie) started; operation # 45; does use network; is at background priority
2019/07/18 14:44:01.3372401 4916  9012  ProtocolTalker  Initializing simple targeting cookie, clientId = 7ab4aea8-2a74-4730-9e60-1c3234866b60, target group = , DNS name = e-dls-test.mou-source.college.local
2019/07/18 14:44:01.3372442 4916  9012  ProtocolTalker    Server URL = https://DLS-DP.mou-source.college.local:8531/SimpleAuthWebService/SimpleAuth.asmx
2019/07/18 14:44:01.3372958 4916  9012  WebServices     Auto proxy settings for this web service call.
2019/07/18 14:44:01.3961683 4916  9012  IdleTimer       WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie, operation # 45) stopped; does use network; is at background priority
2019/07/18 14:44:01.3969810 4916  9012  IdleTimer       WU operation (CAgentProtocolTalker::GetCookie_WithRecovery) started; operation # 46; does use network; is at background priority
2019/07/18 14:44:01.3970487 4916  9012  WebServices     Auto proxy settings for this web service call.
2019/07/18 14:44:01.4262781 4916  9012  IdleTimer       WU operation (CAgentProtocolTalker::GetCookie_WithRecovery, operation # 46) stopped; does use network; is at background priority
2019/07/18 14:44:01.4263307 4916  9012  ProtocolTalker  PTInfo: Server requested registration
2019/07/18 14:44:01.4478149 4916  9012  IdleTimer       WU operation (CAgentProtocolTalker::StartCategoryScan_WithRecovery) started; operation # 47; does use network; is at background priority
2019/07/18 14:44:01.4530051 4916  9012  IdleTimer       WU operation (CAgentProtocolTalker::StartCategoryScan_WithRecovery, operation # 47) stopped; does use network; is at background priority
2019/07/18 14:48:01.8021908 4916  9012  ProtocolTalker  ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = https://DLS-DP.mou-source.college.local:8531/ClientWebService/client.asmx
2019/07/18 14:48:01.8022117 4916  9012  ProtocolTalker  OK to reuse existing configuration
2019/07/18 14:48:01.8022219 4916  9012  ProtocolTalker  Existing cookie is valid, just use it
2019/07/18 14:48:01.8022265 4916  9012  ProtocolTalker  PTInfo: Server requested registration
2019/07/18 14:48:02.9813640 4916  9012  IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 48; does use network; is at background priority
2019/07/18 14:48:03.6355207 4916  9012  IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 48) stopped; does use network; is at background priority
2019/07/18 14:48:04.0704768 4916  9012  Metadata        Policy-driven service enabled. Using Ignore Policy.

Then the ScanAgent.log : 

ScanJob({DD3BDFE8-6D51-4C9B-BEE9-52F7DDEB7305}): CScanJob::OnScanComplete -Scan Failed with Error=0x80244007 ScanAgent 17/07/2019 19:01:14 5432 (0x1538)
ScanJob({DD3BDFE8-6D51-4C9B-BEE9-52F7DDEB7305}): CScanJobManager::OnScanComplete- failed at CScanJob::OnScanComplete with error=0x80244007 ScanAgent 17/07/2019 19:01:14 5432 (0x1538)
ScanJob({DD3BDFE8-6D51-4C9B-BEE9-52F7DDEB7305}): CScanJobManager::OnScanComplete -ScanJob is completed. ScanAgent 17/07/2019 19:01:14 5432 (0x1538)
ScanJob({DD3BDFE8-6D51-4C9B-BEE9-52F7DDEB7305}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients... ScanAgent 17/07/2019 19:01:14 5432 (0x1538)

    • -Evaluating Update Status... ScanAgent 17/07/2019 19:01:14 6568 (0x19A8)
    • Calling back to client on Scan request complete... ScanAgent 17/07/2019 19:01:14 6568 (0x19A8)
      No CatScan history exists ScanAgent 17/07/2019 19:01:21 6568 (0x19A8)
      Sources are not current ScanAgent 17/07/2019 19:01:21 6568 (0x19A8)
      ScanJob({5C13BF25-E828-4A69-807B-3981FF46B670}): CScanJob::OnScanComplete -Scan Failed with Error=0x80244007 ScanAgent 17/07/2019 19:01:21 5432 (0x1538)
      ScanJob({5C13BF25-E828-4A69-807B-3981FF46B670}): CScanJobManager::OnScanComplete- failed at CScanJob::OnScanComplete with error=0x80244007 ScanAgent 17/07/2019 19:01:22 5432 (0x1538)
      ScanJob({5C13BF25-E828-4A69-807B-3981FF46B670}): CScanJobManager::OnScanComplete -ScanJob is completed. ScanAgent 17/07/2019 19:01:22 5432 (0x1538)
      ScanJob({5C13BF25-E828-4A69-807B-3981FF46B670}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients... ScanAgent 17/07/2019 19:01:22 5432 (0x1538)
    • -Evaluating Update Status... ScanAgent 17/07/2019 19:01:22 8228 (0x2024)
    • Calling back to client on Scan request complete... ScanAgent 17/07/2019 19:01:22 8228 (0x2024)
      ScanJob({7A83130A-0335-4BCC-A4BE-F99633F3C790}): CScanJob::OnScanComplete -Scan Failed with Error=0x80244007 ScanAgent 17/07/2019 19:01:28 8228 (0x2024)
      ScanJob({7A83130A-0335-4BCC-A4BE-F99633F3C790}): CScanJobManager::OnScanComplete- failed at CScanJob::OnScanComplete with error=0x80244007 ScanAgent 17/07/2019 19:01:28 8228 (0x2024)
      ScanJob({7A83130A-0335-4BCC-A4BE-F99633F3C790}): CScanJobManager::OnScanComplete -ScanJob is completed. ScanAgent 17/07/2019 19:01:28 8228 (0x2024)
      ScanJob({7A83130A-0335-4BCC-A4BE-F99633F3C790}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients... ScanAgent 17/07/2019 19:01:28 8228 (0x2024)
    • -Evaluating Update Status... ScanAgent 17/07/2019 19:01:28 6568 (0x19A8)
    • Calling back to client on Scan request complete... ScanAgent 17/07/2019 19:01:28 6568 (0x19A8)
      *****Policy Change notification received for ToolUniqueID={8C5EF564-175C-4F97-99A4-28D586010453} ScanAgent 17/07/2019 21:12:42 3112 (0x0C28)
      *****ScanByUpdates request received with ForceReScan=0, ScanOptions=0x00000008,  WSUSLocationTimeout = 604800 ScanAgent 17/07/2019 22:09:00 6568 (0x19A8)
    • -Evaluating Update Status... ScanAgent 17/07/2019 22:09:00 6568 (0x19A8)
      Found CategoryID of :8c3fcc84-7410-4a95-8b89-a166a0190486 for Update:564cef9e-33bb-4a89-a53e-c4331b6d7516 ScanAgent 17/07/2019 22:09:00 6568 (0x19A8)
      CScanAgent::ScanByUpdates - Found UpdateClassification e0789628-ce08-4437-be74-2495b842f43b for Update:564cef9e-33bb-4a89-a53e-c4331b6d7516 ScanAgent 17/07/2019 22:09:00 6568 (0x19A8)
      Found CategoryID of :8c3fcc84-7410-4a95-8b89-a166a0190486 for Update:a31a271f-d897-4a7f-b021-d3739a17bd15 ScanAgent 17/07/2019 22:09:00 6568 (0x19A8)
      CScanAgent::ScanByUpdates - Found UpdateClassification e0789628-ce08-4437-be74-2495b842f43b for Update:a31a271f-d897-4a7f-b021-d3739a17bd15 ScanAgent 17/07/2019 22:09:00 6568 (0x19A8)
      Found CategoryID of :8c3fcc84-7410-4a95-8b89-a166a0190486 for Update:c01d654d-44cf-4a71-b31f-8402d5b54166 ScanAgent 17/07/2019 22:09:00 6568 (0x19A8)
      CScanAgent::ScanByUpdates - Found UpdateClassification e0789628-ce08-4437-be74-2495b842f43b for Update:c01d654d-44cf-4a71-b31f-8402d5b54166 ScanAgent 17/07/2019 22:09:00 6568 (0x19A8)
      Found CategoryID of :8c3fcc84-7410-4a95-8b89-a166a0190486 for Update:e6b69756-e842-40d1-aa4e-835764be98cf ScanAgent 17/07/2019 22:09:00 6568 (0x19A8)
      CScanAgent::ScanByUpdates - Found UpdateClassification e0789628-ce08-4437-be74-2495b842f43b for Update:e6b69756-e842-40d1-aa4e-835764be98cf ScanAgent 17/07/2019 22:09:00 6568 (0x19A8)
      Sources are not current ScanAgent 17/07/2019 22:09:00 6568 (0x19A8)
      ScanJob({1906AE72-8EB9-4A67-96EA-2D7A75DA2E4E}): - - - - - -Locations requested for ScanJobID={1906AE72-8EB9-4A67-96EA-2D7A75DA2E4E} (LocationRequestID={3B80DE94-183D-4668-BDCC-489B7DC65786}), will process the scan request once locations are available. ScanAgent 17/07/2019 22:09:00 6568 (0x19A8)
      *****WSUSLocationUpdate received for location request guid={3B80DE94-183D-4668-BDCC-489B7DC65786} ScanAgent 17/07/2019 22:28:52 7080 (0x1BA8)
      CScanJobMgr::UpdateSUPLocationList- Original WUA location count is 0, new location count is 1, WUA locations updated. ScanAgent 17/07/2019 22:28:53 7080 (0x1BA8)
      No CatScan history exists ScanAgent 17/07/2019 22:28:53 5752 (0x1678)
      Sources are not current ScanAgent 17/07/2019 22:28:53 5752 (0x1678)
      ScanJob({1906AE72-8EB9-4A67-96EA-2D7A75DA2E4E}): CScanJob::Execute- Requesting scan with CategoryIDs=8C3FCC84-7410-4A95-8B89-A166A0190486,8C3FCC84-7410-4A95-8B89-A166A0190486,8C3FCC84-7410-4A95-8B89-A166A0190486,8C3FCC84-7410-4A95-8B89-A166A0190486 ScanAgent 17/07/2019 22:28:53 5752 (0x1678)
      ScanJob({1906AE72-8EB9-4A67-96EA-2D7A75DA2E4E}): CScanJob::OnScanComplete -Scan Failed with Error=0x80240436 ScanAgent 17/07/2019 22:41:39 5752 (0x1678)
      ScanJob({1906AE72-8EB9-4A67-96EA-2D7A75DA2E4E}): CScanJobManager::OnScanComplete- failed at CScanJob::OnScanComplete with error=0x80240436 ScanAgent 17/07/2019 22:41:39 5752 (0x1678)
      ScanJob({1906AE72-8EB9-4A67-96EA-2D7A75DA2E4E}): CScanJobManager::OnScanComplete -ScanJob is completed. ScanAgent 17/07/2019 22:41:39 5752 (0x1678)
      ScanJob({1906AE72-8EB9-4A67-96EA-2D7A75DA2E4E}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients... ScanAgent 17/07/2019 22:41:39 5752 (0x1678)

The WUAHandler.log : 

OnSearchComplete - Failed to end search job. Error = 0x80244007. WUAHandler 17/07/2019 19:01:14 6568 (0x19A8)
Scan failed with error = 0x80244007. WUAHandler 17/07/2019 19:01:14 6568 (0x19A8)
Its a WSUS Update Source type ({8C5EF564-175C-4F97-99A4-28D586010453}), adding it. WUAHandler 17/07/2019 19:01:14 8228 (0x2024)
Device is not MDM enrolled yet. All workloads are managed by SCCM. WUAHandler 17/07/2019 19:01:14 5596 (0x15DC)
SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. Windows Update for Business is not enabled through ConfigMgr WUAHandler 17/07/2019 19:01:14 5596 (0x15DC)
Existing WUA Managed server was already set (https://DLS-DP.mou-source.college.local:8531), skipping Group Policy registration. WUAHandler 17/07/2019 19:01:14 8228 (0x2024)
Added Update Source ({8C5EF564-175C-4F97-99A4-28D586010453}) of content type: 2 WUAHandler 17/07/2019 19:01:14 8228 (0x2024)
Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 17/07/2019 19:01:14 8228 (0x2024)
Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 17/07/2019 19:01:14 8228 (0x2024)
Async searching of updates using WUAgent started. WUAHandler 17/07/2019 19:01:14 8228 (0x2024)
Async searching completed. WUAHandler 17/07/2019 19:01:21 9128 (0x23A8)
OnSearchComplete - Failed to end search job. Error = 0x80244007. WUAHandler 17/07/2019 19:01:21 8228 (0x2024)
Scan failed with error = 0x80244007. WUAHandler 17/07/2019 19:01:21 8228 (0x2024)
Its a WSUS Update Source type ({8C5EF564-175C-4F97-99A4-28D586010453}), adding it. WUAHandler 17/07/2019 19:01:21 6568 (0x19A8)
Device is not MDM enrolled yet. All workloads are managed by SCCM. WUAHandler 17/07/2019 19:01:21 6828 (0x1AAC)
SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. Windows Update for Business is not enabled through ConfigMgr WUAHandler 17/07/2019 19:01:21 6828 (0x1AAC)
Existing WUA Managed server was already set (https://DLS-DP.mou-source.college.local:8531), skipping Group Policy registration. WUAHandler 17/07/2019 19:01:22 6568 (0x19A8)
Added Update Source ({8C5EF564-175C-4F97-99A4-28D586010453}) of content type: 2 WUAHandler 17/07/2019 19:01:22 6568 (0x19A8)
Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 17/07/2019 19:01:22 6568 (0x19A8)
Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 17/07/2019 19:01:22 6568 (0x19A8)
Async searching of updates using WUAgent started. WUAHandler 17/07/2019 19:01:22 6568 (0x19A8)
Async searching completed. WUAHandler 17/07/2019 19:01:28 7388 (0x1CDC)
OnSearchComplete - Failed to end search job. Error = 0x80244007. WUAHandler 17/07/2019 19:01:28 6568 (0x19A8)
Scan failed with error = 0x80244007. WUAHandler 17/07/2019 19:01:28 6568 (0x19A8)
Its a WSUS Update Source type ({8C5EF564-175C-4F97-99A4-28D586010453}), adding it. WUAHandler 17/07/2019 22:28:53 5752 (0x1678)
Device is not MDM enrolled yet. All workloads are managed by SCCM. WUAHandler 17/07/2019 22:28:53 4380 (0x111C)
SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. Windows Update for Business is not enabled through ConfigMgr WUAHandler 17/07/2019 22:28:53 4380 (0x111C)
Existing WUA Managed server was already set (https://DLS-DP.mou-source.college.local:8531), skipping Group Policy registration. WUAHandler 17/07/2019 22:28:53 5752 (0x1678)
Added Update Source ({8C5EF564-175C-4F97-99A4-28D586010453}) of content type: 2 WUAHandler 17/07/2019 22:28:53 5752 (0x1678)
Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 17/07/2019 22:28:53 5752 (0x1678)
Search Criteria is ((DeploymentAction=* AND Type='Software' AND CategoryIDs contains '8C3FCC84-7410-4A95-8B89-A166A0190486')) WUAHandler 17/07/2019 22:28:53 5752 (0x1678)
Async searching of updates using WUAgent started. WUAHandler 17/07/2019 22:28:53 5752 (0x1678)
Async searching completed. WUAHandler 17/07/2019 22:41:39 8624 (0x21B0)

And on my SUP Replica i have the SoftwareDistribution.log : 

2019-07-19 05:29:20.912 UTC Info w3wp.115 ThreadEntry ThreadPoolWorkQueue.Dispatch
2019-07-19 05:29:20.912 UTC Warning w3wp.115 SoapUtilities.CreateException ThrowException: actor = https://dls-dp.mou-source.college.local:8531/ClientWebService/client.asmx, ID=3cb9d6f6-ed6e-4a2f-8510-43a8ff3aa4bb, ErrorCode=InvalidParameters, Message=parameters.OtherCachedUpdateIDs, Client=e01eb659-3f1a-4c92-8e23-9c88733c902e
2019-07-19 05:29:23.041 UTC Info w3wp.122 ThreadEntry ThreadPoolWorkQueue.Dispatch
2019-07-19 05:29:23.041 UTC Warning w3wp.122 SoapUtilities.CreateException ThrowException: actor = https://dls-dp.mou-source.college.local:8531/ClientWebService/client.asmx, ID=1cf8342a-1508-4408-8c6a-9556bc0e9c71, ErrorCode=InvalidParameters, Message=parameters.OtherCachedUpdateIDs, Client=e01eb659-3f1a-4c92-8e23-9c88733c902e
2019-07-19 05:29:25.159 UTC Info w3wp.118 ThreadEntry ThreadPoolWorkQueue.Dispatch
2019-07-19 05:29:25.159 UTC Warning w3wp.118 SoapUtilities.CreateException ThrowException: actor = https://dls-dp.mou-source.college.local:8531/ClientWebService/client.asmx, ID=b68c98ff-f80b-49fc-ac85-30d360b3247f, ErrorCode=InvalidParameters, Message=parameters.OtherCachedUpdateIDs, Client=e01eb659-3f1a-4c92-8e23-9c88733c902e
2019-07-19 05:31:47.521 UTC Info w3wp.54 ThreadEntry ThreadHelper.ThreadStart
2019-07-19 05:31:47.521 UTC Info w3wp.54 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2019-07-19 05:31:47.521 UTC Info w3wp.54 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
2019-07-19 05:31:47.537 UTC Info w3wp.54 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange
2019-07-19 05:31:47.521 UTC Info w3wp.122 ThreadEntry PipelineRuntime.ProcessRequestNotification
2019-07-19 05:31:47.537 UTC Info w3wp.122 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
2019-07-19 05:31:47.537 UTC Info w3wp.54 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange
2019-07-19 05:31:47.537 UTC Info w3wp.54 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: LanguageChange, EventInfo: LanguageChange
2019-07-19 05:38:18.562 UTC Error WsusService.9 HmtWebServices.CheckServerSyncWebService ServerSync WebService WebException:System.Net.WebException: La demande a ..chou.. avec l'..tat HTTP 403 : Forbidden.
   .. System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   .. System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   .. Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.Ping(Int32 pingLevel)
   .. Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckServerSyncWebService(EventLoggingType type, HealthEventLogger logger)
   .. Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckServerSyncWebService(EventLoggingType type, HealthEventLogger logger)
   .. Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringTasks.ExecuteSubtask(HealthMonitoringSubtask subtask, EventLoggingType type, HealthEventLogger logger)
   .. Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.Execute(EventLoggingType type)
   .. Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringTasks.Execute(EventLoggingType type)
   .. Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringThreadManager.Execute(Boolean waitIfNecessary, EventLoggingType loggingType)
   .. Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringThreadManager.PeriodicTask()
   .. Microsoft.UpdateServices.Internal.HealthMonitoring.PeriodicTaskExecuter.ThreadStart()
   .. System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   .. System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   .. System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   .. System.Threading.ThreadHelper.ThreadStart()
2019-07-19 05:38:18.562 UTC Error WsusService.9 HmtWebServices.CheckClientWebService Client WebService WebException:System.Net.WebException: La demande a ..chou.. avec l'..tat HTTP 403 : Forbidden.
   .. System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   .. System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   .. Microsoft.UpdateServices.Internal.ClientWebService.Client.Ping(Int32 pingLevel)
   .. Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckClientWebService(EventLoggingType type, HealthEventLogger logger)
   .. Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckClientWebService(EventLoggingType type, HealthEventLogger logger)
   .. Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringTasks.ExecuteSubtask(HealthMonitoringSubtask subtask, EventLoggingType type, HealthEventLogger logger)
   .. Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.Execute(EventLoggingType type)
   .. Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringTasks.Execute(EventLoggingType type)
   .. Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringThreadManager.Execute(Boolean waitIfNecessary, EventLoggingType loggingType)
   .. Microsoft.UpdateServices.Internal.HealthMonitoring.HealthMonitoringThreadManager.PeriodicTask()
   .. Microsoft.UpdateServices.Internal.HealthMonitoring.PeriodicTaskExecuter.ThreadStart()
   .. System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   .. System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   .. System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   .. System.Threading.ThreadHelper.ThreadStart()
2019-07-19 05:38:18.562 UTC Error WsusService.9 HmtWebServices.CheckSimpleAuthWebService SimpleAuth WebService WebException:System.Net.WebException: La demande a ..chou.. avec l'..tat HTTP 403 : Forbidden.

Finally the WindowsUpdate.log on my SUP : 

2019-07-19 07:40:52:255 472 f04 Agent ***********  Agent: Initializing global settings cache  ***********
2019-07-19 07:40:52:255 472 f04 Agent   * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2019-07-19 07:40:52:255 472 f04 Agent   * WSUS server: https://dls-wsus.mou-source.college.local:8531/
2019-07-19 07:40:52:255 472 f04 Agent   * WSUS status server: https://dls-wsus.mou-source.college.local:8531/
2019-07-19 07:40:52:255 472 f04 Agent   * Target group: DLS-SRV
2019-07-19 07:40:52:255 472 f04 Agent   * Windows Update access disabled: No
2019-07-19 07:40:52:255 472 f04 Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
2019-07-19 07:40:52:333 472 f04 WuTask WuTaskManager delay initialize completed successfully..
2019-07-19 07:40:52:333 472 f04 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-07-19 07:54:07, not idle-only, not network-only
2019-07-19 07:40:52:333 472 f04 AU     Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2019-07-19 19:06:09, not idle-only, not network-only
2019-07-19 07:40:52:333 472 f04 AU     Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2019-07-19 19:06:09, not idle-only, not network-only
2019-07-19 07:40:52:349 472 f04 Report CWERReporter::Init succeeded
2019-07-19 07:40:52:349 472 f04 Agent ***********  Agent: Initializing Windows Update Agent  ***********
2019-07-19 07:40:52:349 472 f04 DnldMgr Download manager restoring 0 downloads
2019-07-19 07:40:52:349 472 f04 AU ###########  AU: Initializing Automatic Updates  ###########
2019-07-19 07:40:52:349 472 f04 AU AIR Mode is disabled
2019-07-19 07:40:52:349 472 f04 AU   # Policy Driven Provider: https://dls-wsus.mou-source.college.local:8531/
2019-07-19 07:40:52:349 472 f04 AU   # Detection frequency: 22
2019-07-19 07:40:52:349 472 f04 AU   # Target group: DLS-SRV
2019-07-19 07:40:52:349 472 f04 AU   # Approval type: Scheduled (Policy)
2019-07-19 07:40:52:349 472 f04 AU   # Auto-install minor updates: Yes (User preference)
2019-07-19 07:40:52:349 472 f04 AU   # Will interact with non-admins (Non-admins are elevated (User preference))
2019-07-19 07:40:52:349 472 f04 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
2019-07-19 07:40:52:349 472 f04 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-07-19 07:40:52:365 472 f04 AU AU finished delayed initialization
2019-07-19 07:40:52:365 472 f04 AU Currently AUX is enabled - so not show any WU Upgrade notifications.
2019-07-19 07:40:52:365 472 f04 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-07-19 07:40:52:365 472 f04 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2019-07-19 07:40:52:365 472 1918 DnldMgr Asking handlers to reconcile their sandboxes
2019-07-19 07:51:20:113 472 1770 AU Earliest future timer found: 
2019-07-19 07:51:20:113 472 1770 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-07-19 07:54:07, not idle-only, not network-only
2019-07-19 07:51:21:128 472 f04 AU ###########  AU: Uninitializing Automatic Updates  ###########
2019-07-19 07:51:21:144 472 f04 WuTask Uninit WU Task Manager
2019-07-19 07:51:21:191 472 f04 AU Earliest future timer found: 
2019-07-19 07:51:21:191 472 f04 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-07-19 07:54:07, not idle-only, not network-only
2019-07-19 07:51:21:206 472 f04 AU Earliest future timer found: 
2019-07-19 07:51:21:206 472 f04 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2019-07-19 07:54:07, not idle-only, not network-only
2019-07-19 07:51:21:253 472 f04 Service *********
2019-07-19 07:51:21:253 472 f04 Service **  END  **  Service: Service exit [Exit code = 0x240001]
2019-07-19 07:51:21:253 472 f04 Service *************

Thanks for your help, 

Quentin

All replies (10)

Friday, July 19, 2019 6:44 AM

check this thread https://social.technet.microsoft.com/Forums/en-US/51b7603a-eff9-4521-9cc9-3adae0d17983/windows-updates-through-wsus-sccm-and-windows-81-pterror-0x80244007?forum=configmanagersecurity

Friday, July 19, 2019 7:59 AM

I already double the cache and i get the same error

Thanks

Quentin

Friday, July 19, 2019 8:09 AM

Have you tried reset windows update agent any one of the machine

https://gallery.technet.microsoft.com/reset-windows-update-agent-d824badc

Friday, July 19, 2019 8:15 AM

Yes no changes

Quentin

Friday, July 19, 2019 8:19 AM

I have this message in ScanAgent.log : Sources are current, but Invalid. TTL is also invalid. 

This appear when it found update classification (and i suppose update to do)

Quentin

Friday, July 19, 2019 9:14 AM

Hi Quentin,

Can you try with the following steps: 

https://ugetfix.com/ask/how-to-fix-windows-update-error-0x80244007/

Regards,

SAAD Youssef

______

Please remember to mark the replies as answer if they help, thank you.

Monday, July 22, 2019 5:36 AM

Hi Youssef,

I tested the steps this week-end and no changes .. 

I found a new log on client : SoftwareDistribution.log :

{2BF12512-B601-4CF6-A551-5B0BA38F7B36} 2019-07-20 14:50:20:204+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10893.0.0.3.0
{F35FE717-A313-482E-813E-581D861B3C22} 2019-07-20 14:50:25:110+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10894.0.0.3.0
{B3DF48B4-A8AE-4BFC-B298-43169DF3B2D0} 2019-07-20 14:50:30:438+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10895.0.0.3.0
{B5ED2079-1D6E-4F0E-B004-27105EA31A2E} 2019-07-20 14:50:35:235+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10896.0.0.3.0
{BA0389A1-0AFA-48C5-ACB2-8BF6D6618388} 2019-07-20 14:50:40:476+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10897.0.0.3.0
{C43BF464-B7D9-4453-A2B0-CEB5A9E82B86} 2019-07-20 14:50:45:648+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10898.0.0.3.0
{C3C55701-B0B4-4D14-B6D8-4447309273FC} 2019-07-20 14:50:50:679+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10899.0.0.3.0
{E6126C72-192A-49CA-BE67-98474B88E41D} 2019-07-20 14:50:54:945+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10900.0.0.3.0
{8A1DF540-76F3-443B-810F-7F00BE7235D9} 2019-07-20 14:51:00:101+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10901.0.0.3.0
{59691AF3-54AE-434B-B110-073B91F27A19} 2019-07-20 14:51:05:023+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10902.0.0.3.0
{F827E7BE-96EF-4A42-996B-682257E4BB39} 2019-07-20 14:51:09:758+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10903.0.0.3.0
{4320CCFB-FCBB-4307-B119-EC04F168C823} 2019-07-20 14:51:14:383+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10904.0.0.3.0
{EEA5D68B-6C0A-4D63-8539-E2FC1F509F7C} 2019-07-20 14:51:18:961+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10905.0.0.3.0
{ECA2F297-F44C-4F92-8977-9F6C6F2D0792} 2019-07-20 14:51:23:872+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10906.0.0.3.0
{D3420FB9-1842-4136-A827-B479ADFE162E} 2019-07-20 14:51:28:492+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10907.0.0.3.0
{9391FFBB-A27F-4D83-8F52-CC5B1740D4CA} 2019-07-20 14:51:33:827+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10908.0.0.3.0
{E4184FB0-DCED-45F2-803E-A5F47B75FCD9} 2019-07-20 14:51:38:874+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10909.0.0.3.0
{355CB8B3-474C-4898-A8D2-EAA16457C466} 2019-07-20 14:51:43:835+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10910.0.0.3.0
{923976AA-1385-4FA8-92F3-89DB9AD42322} 2019-07-20 14:51:48:976+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10911.0.0.3.0
{828F6C81-7B10-4CFF-A978-CCD66DDB3AE0} 2019-07-20 14:51:53:835+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10912.0.0.3.0
{1813242E-E92C-4004-B0E3-EBD220CE6368} 2019-07-20 14:51:58:391+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10913.0.0.3.0
{4402A4FE-81C5-44BD-B046-0D7E5B717704} 2019-07-20 14:52:03:344+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10914.0.0.3.0
{1D88C774-752C-4654-97FF-9CBCF57924F8} 2019-07-20 14:52:08:336+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10915.0.0.3.0
{0CB5D89B-46FB-4B5E-AE0C-74220A707AEC} 2019-07-20 14:52:13:029+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10916.0.0.3.0
{486CD7AB-5F74-4543-8B18-655D1E220BC7} 2019-07-20 14:52:17:617+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10917.0.0.3.0
{8BE3B5AE-D4A9-4CC5-85D5-6143FE82F87B} 2019-07-20 14:52:22:601+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10918.0.0.3.0
{34D6C38E-436B-4579-95C9-96F698ABAF67} 2019-07-20 14:52:27:523+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10919.0.0.3.0
{5E060599-5784-4906-A42D-19A74C14CF39} 2019-07-20 14:52:32:054+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10920.0.0.3.0
{8EE35D36-408B-44E7-8544-D506247231CC} 2019-07-20 14:52:36:930+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10921.0.0.3.0
{8012DC9F-61DC-486F-9C88-69F3321F7A5D} 2019-07-20 14:52:41:320+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10922.0.0.3.0
{DE4DE289-C456-425C-990B-266D32D2B7EF} 2019-07-20 14:52:46:054+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. Xd5+AgeHEES13c/I.10923.0.0.3.0
{7B325916-CD58-4011-A354-E9414C9D7585} 2019-07-20 23:32:33:817+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80240436 Antivirus Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24) Failure Software Synchronization Windows Update Client failed to detect with error 0x80240436. lyr59u4jAk6AmHgw.1.0.0.3.0
{CC0E69B8-9EC3-4FBA-ACA0-DFEC878CB571} 2019-07-21 02:03:54:420+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80240436 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80240436. Xd5+AgeHEES13c/I.10924.0.0.3.0
{7109FA12-FE3A-4F80-B126-D22FED8F2A03} 2019-07-21 07:38:11:666+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 UpdateOrchestrator Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007. /8kjtlU2vUKcJFaW.1.1.0.0.3.0
{FD446D97-B38A-404A-8E2F-31F2C8A47A64} 2019-07-21 11:31:09:654+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80240436 Antivirus Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24) Failure Software Synchronization Windows Update Client failed to detect with error 0x80240436. RPM/lms+q0uAM2vc.1.0.0.3.0
{BF453145-FD9F-4113-8FC1-94B494718DB5} 2019-07-21 21:15:02:295+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80240436 CcmExec Failure Software Synchronization Windows Update Client failed to detect with error 0x80240436. Xd5+AgeHEES13c/I.10925.0.0.3.0
{1C4EB55D-2D5A-44C6-8F0D-A762153D75A9} 2019-07-21 23:31:01:351+0200 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80240436 Antivirus Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24) Failure Software Synchronization Windows Update Client failed to detect with error 0x80240436. oEKspT6rWEm0jxIr.1.0.0.3.0

Regards, 

Quentin

Monday, July 22, 2019 6:38 AM

Still i can see the same error, try this

0x80244007 = Same as SOAPCLIENT_SOAPFAULT - SOAP client failed because there was a SOAP fault for reasons of WU_E_PT_SOAP_* error codes.

Please try to open the registry, and then go to : HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate

And then look for Target Group key, export it first (just a backup) then delete it.

Now, restart your computer and check Windows Updates.

https://social.technet.microsoft.com/Forums/en-US/05129498-19ab-4f0a-bf6d-d0995de50b54/clients-cant-update-from-wsus-server-error-0x80244007?forum=winserverwsus

Monday, July 22, 2019 8:53 AM

Hi, 

I checked on my client and there is not regedit key as Target Group, 

I think this key is present when the WSUS is in standalone mode (not integrated to SCCM) 

Thanks, 

Quentin

Monday, July 22, 2019 9:22 AM

Hi Quentin,

On the client, check if the information about your Software Update Point is configured correctly in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\

Check the two following keys:

  • WUServer
  • WUStatusServer

It must be contains the link of your Software Update Point with the port.

Regards,

SAAD Youssef

  • Last updated on