We are experiencing this issue with a number of Windows 10 machines, both 1703 and 1607.
They are all showing the same error:
* START * Finding updates CallerId = UpdateOrchestrator Id = 11
Online = Yes; Interactive = Yes; AllowCachedResults = No; Ignore download priority = No
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""
ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
Search Scope = {Machine}
Caller SID for Applicability: S-1-5-21-1615105449-1528263825-1960982893-210032
ProcessDriverDeferrals is set
Got WSUS Client/Server URL: http://[FQDN]:8530/ClientWebService/client.asmx""
Skipping printer driver 3 due to incomplete info or mismatched environment - HWID[(null)] Provider[(null)] MfgName[(null)] Name[WebEx Document Loader] pEnvironment[Windows x64] LocalPrintServerEnv[Windows x64]
Skipping printer driver 6 due to incomplete info or mismatched environment - HWID[microsoftmicrosoft_musd] Provider[Microsoft] MfgName[Microsoft] Name[Microsoft enhanced Point and Print compatibility driver] pEnvironment[Windows NT x86] LocalPrintServerEnv[Windows x64]
ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://[FQDN]:8530/ClientWebService/client.asmx
OK to reuse existing configuration
Existing cookie is valid, just use it
PTInfo: Server requested registration
WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 159; does use network; is at background priority
Auto proxy settings for this web service call.
WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 159) stopped; does use network; is at background priority
WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 160; does use network; is at background priority
WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 160) stopped; does use network; is at background priority
SyncUpdates round trips: 2
ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://[FQDN]:8530/ClientWebService/client.asmx
OK to reuse existing configuration
Existing cookie is valid, just use it
PTInfo: Server requested registration
WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 161; does use network; is at background priority
WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 161) stopped; does use network; is at background priority
*FAILED* [80248007] Method failed [SlsDatastoreLookup:797]
Retrieving SLS response from server...
Making request with URL HTTPS://sls.update.microsoft.com/SLS/{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}/x64/10.0.16299.0/0?CH=480&L=en-US;cs-CZ;de-DE;es-ES;fr-FR;hu-HU;it-IT;ja-JP;ko-KR;pl-PL;pt-BR;pt-PT;ru-RU;sv-SE;tr-TR&P=&PT=0x4&WUA=10.0.16299.15&MK=Dell+Inc.&MD=Precision+Tower+5810
SLS Response is Error response type. Attempting to extract the HRESULT in the payload...
Succeeded in extracting the HRESULT from the payload => 0x80240042
*FAILED* [80245004] Method failed [MetadataIntegrity::SignatureVerifier::GetFragmentSigningConfig:793]
*FAILED* [80245004] GetFragmentSigningConfig (Using default enforcement mode: Audit)
*FAILED* [80245004] Method failed [MetadataIntegrity::SignatureVerifier::GetFragmentSigningConfigAndUpdateEnforcementPolicy:745]
Policy-driven service enabled. Using Ignore Policy.
SyncExtendedUpdateInfo - 0 bad out of 0 metadata signatures checked using Audit enforcement mode.
Found 0 updates and 98 categories in search; evaluated appl. rules of 3605 out of 5934 deployed entities
* END * Finding updates CallerId = UpdateOrchestrator Id = 11
WU operation (CSearchCall::Init ID 11, operation # 158) stopped; does use network; is not at background priority
Can anyone suggest anything?
restarting the WU client service and clearing the SoftwareDist folder has made no difference.
Note that CCM is not involved here, aside from asking the WUAU clt to scan. This is a client or WSUS issue.
Thanks
