Validating signature for c windows softwaredistribution selfupdate default wuident cab

Posted by / 11-Jun-2017 03:41

Validating signature for c windows softwaredistribution selfupdate default wuident cab

What I've checked so far: 2015-01-06 :715 12 1508 Setup Checking for agent Self Update 2015-01-06 :808 12 1508 Setup Client version: Core: 7.6.7600.320 Aux: 7.6.7600.320 2015-01-06 :824 12 1508 Misc Validating signature for C:\Windows\Software Distribution\Self Update\with dw Prov Flags 0x00000080: 2015-01-06 :840 12 1508 Misc Microsoft signed: NA 2015-01-06 :840 12 1508 Misc WARNING: Cab does not contain correct inner CAB file.2015-01-06 :840 12 1508 Misc Validating signature for C:\Windows\Software Distribution\Self Update\with dw Prov Flags 0x00000080: 2015-01-06 :855 12 1508 Misc Microsoft signed: NA 2015-01-06 :855 12 1508 Setup Wuident for the managed service is valid but not quorum-signed. 2015-01-06 :855 12 1508 Setup Skipping Self Update check based on the /SKIP directive in wuident 2015-01-06 :855 12 1508 Setup Self Update check completed. 2015-01-06 :462 12 1508 PT PT: Synchronizing server updates 2015-01-06 :462 12 1508 PT Service Id = , Server URL = Web Service/2015-01-06 :571 12 1508 PT WARNING: Cached cookie has expired or new PID is available 2015-01-06 :571 12 1508 PT Initializing simple targeting cookie, client Id = 0c4aed4f-6c60-46a0-b29b-f2080ea315c1, target group = , DNS name = wsus-server 2015-01-06 :571 12 1508 PT Server URL = Auth Web Service/Simple 2015-01-06 :844 12 1508 Agent * Found 0 updates and 76 categories in search; evaluated appl.I installed this fix on the WSUS Server and restart the it.At the clients stop the “Windows Update” Service This website uses cookies to improve your experience and to serv personalized advertising by google adsense.Click Start, click Run, type regedit in the Open box, and then click OK.Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Current Version\Windows Update In the details pane of Registry Editor, delete the following registry entries: Ping ID Account Domain Sid Sus Client Id Sus Client IDValidation Note Windows Update Agent 3.0 adds the Sus Client IDValidation value. The other registry entries exist in both Windows Update Agent 2.0 and in Windows Update Agent 3.0. At the command prompt, type net start wuauserv, and then press ENTER.By using this website, you consent to the use of cookies for personalized content and advertising.For more information about cookies, please see our Privacy Policy, but you can opt-out if you wish.

The computer runs Windows Update fine while its not joined to the domain.I'm having trouble getting updates to download to my computer. My test computer is listed on the computer list in the wsus console.2016-02-16 :649 1004 d50 AU ############# 2016-02-16 :649 1004 d50 AU ## START ## AU: Search for updates 2016-02-16 :649 1004 d50 AU ######### 2016-02-16 :649 1004 d50 AU ## RESUMED ## AU: Search for updates [Call Id = ] 2016-02-16 :553 1004 f00 AU # WARNING: Search callback failed, result = 0x80244010 2016-02-16 :553 1004 f00 AU # WARNING: Failed to find updates with error code 80244010 2016-02-16 :553 1004 f00 AU ######### 2016-02-16 :553 1004 f00 AU ## END ## AU: Search for updates [Call Id = ] 2016-02-16 :553 1004 f00 AU ############# 2016-02-16 :553 1004 f00 AU Successfully wrote event for AU health state:0 2016-02-16 :553 1004 f00 AU AU setting next detection timeout to 2016-02-16 2016-02-16 :553 1004 f00 AU Setting AU scheduled install time to 2016-02-17 2016-02-16 :553 1004 f00 AU Successfully wrote event for AU health state:0 2016-02-16 :553 1004 f00 AU Successfully wrote event for AU health state:0 2016-02-16 :553 1004 ac0 Report REPORT EVENT: 2016-02-16 :553-0800 1 148 101 0 80244010 Automatic Updates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244010.rules of 699 out of 1392 deployed entities 2015-01-06 :844 12 1508 Agent ********* 2015-01-06 :844 12 1508 Agent ** END ** Agent: Finding updates [Caller Id = Automatic Updates] 2015-01-06 :844 12 1508 Agent ************* 2015-01-06 :859 12 16b4 AU ## RESUMED ## AU: Search for updates [Call Id = ] 2015-01-06 :859 12 16b4 AU # 0 updates detected 2015-01-06 :875 12 16b4 AU ######### 2015-01-06 :875 12 16b4 AU ## END ## AU: Search for updates [Call Id = ] 2015-01-06 :875 12 16b4 AU ############# 2015-01-06 :875 12 16b4 AU Successfully wrote event for AU health state:0 2015-01-06 :875 12 16b4 AU Featured notifications is disabled.2015-01-06 :875 12 16b4 AU AU setting next detection timeout to 2015-01-06 2015-01-06 :875 12 16b4 AU Setting AU scheduled install time to 2015-01-11 2015-01-06 :875 12 16b4 AU Successfully wrote event for AU health state:0 2015-01-06 :875 12 16b4 AU Successfully wrote event for AU health state:0 2015-01-06 :851 12 1508 Report REPORT EVENT: 2015-01-06 :844 0100 1 147 101 0 0 Automatic Updates Success Software Synchronization Windows Update Client successfully detected 0 updates.

validating signature for c windows softwaredistribution selfupdate default wuident cab-9validating signature for c windows softwaredistribution selfupdate default wuident cab-41validating signature for c windows softwaredistribution selfupdate default wuident cab-12

At the clients I checked the Windows Update Logfile C:\Windows\Windows and found many errors like these: It means that the the Clients does no longer trust the WSUS Server due to an invalid signature of the WSUS Client update package.