Validating signature wuident cab 0x80096001

Rated 3.94/5 based on 728 customer reviews

The other problem could be an issue with the software distribution folder on the server. Windows 2003: There are 4 updates that aren't downloading, all Windows security updates for Windows 2003: 2698365 (x64 and x32); 2509553, 2536276, and 2638806 (x64 only).

I just now noticed, looking back at my WSUS console, that these are very old updates, but they must have just showed up in the downloads over the last month (I do Windows updates on these servers once a month).

7) Since the customer may have a large number of machines with problematic State registry values, I suggested that they look into using Group Policy Preferences to change the registry value.

See the following articles for information: Information about new Group Policy preferences in Windows Server 2008 Group Policy Preferences Overview Best regards, Watson Wang Microsoft Partner Support Community Technical Support Engineer Microsoft Global Partner Services --------------------------------------------------------------------------------------- This posting is provided "AS IS" with no warranties, and confers no rights.

They're NOT showing as having been superseded in the console. Point the server to MS, for check updates to see whether this update is still reflected as needed.

And they are on the list of needed updates for these servers. one option you could download the update from MS at

validating signature wuident cab 0x80096001-32

These servers are set by group policy to detect and download updates but not to install them automatically.2015-03-30 :8 AU AU setting next detection timeout to 2015-03-30 2015-03-30 :8 AU Successfully wrote event for AU health state:0 2015-03-30 :8 AU Successfully wrote event for AU health state:0 2015-03-30 :772 928 220c Report REPORT EVENT: 2015-03-30 :764-0400 1 147 101 0 0 Automatic Updates Success Software Synchronization Windows Update Client successfully detected 1 updates.2015-03-30 :772 928 220c Report REPORT EVENT: 2015-03-30 :764-0400 1 156 101 0 0 Automatic Updates Success Pre-Deployment Check Reporting client status.1) Reviewed files from a repro and found the following entries of note: Running on 'Microsoft Windows 7 Professional ' (6.1.7601). No registry lookup for command line parameters is required. COM 1/28/2014 PM CCMFIRSTCERT: 1 1/28/2014 PM Config file: C:\windows\ccmsetup\Mobile Client 1/28/2014 PM Retry time: 10 minute(s) 1/28/2014 PM MSI log file: C:\windows\ccmsetup\Logs\log 1/28/2014 PM MSI properties: INSTALL="ALL" SMSSITECODE="AA1" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" FSP="SDSCCMDPPRD01. 1/28/2014 PM Found local location ' 1/28/2014 PM Found local location ' 1/28/2014 PM Discovered 2 local DP locations. Product Type = 18 1/28/2014 PM Ccmsetup command line: "C:\windows\ccmsetup\ccmsetup.exe" /runservice /config: Mobile 1/28/2014 PM Command line parameters for ccmsetup have been specified. COM" CCMFIRSTCERT="1" 1/28/2014 PM Source List: 1/28/2014 PM \XXXX\SMSClient 1/28/2014 PM \XXXX\SMSClient 1/28/2014 PM MPs: 1/28/2014 PM XXXX 1/28/2014 PM No version of the client is currently detected.

Leave a Reply