So typically when it comes to individual machines failing patches I get all grumpy and just tell the first touch guys to PXE image the pig. My theory is that if there is something wrong enough that a machine won't patch there is usually 5 other things wrong that will get ugly later on down the road.
In this case most patches installed, but 4 were failing. Odd, SCCM is obviously working, and the system had just been imaged a week ago. Permissions were set right so I don't 'think' anyone got to tinkering with the box. What the heck.
So first I tried out normal WMI and SCCM Repair proceedures. No change. Looked through the event logs, nothing stood out. Went through the execmgr log and I see if failed with a 0x80073712 code.
Never seen that before. To my best friend Google: "What is 0x80073712"? Which is also how you probably got here.
To fix, use the System Update Readiness Tool and perhaps SFC.exe /scannow
NOTE: The above also mentions error codes 800706BE and 8024200D
For some more background, 0x80073712 [ERROR_SXS_COMPONENT_STORE_CORRUPT] means that there are some inconsistencies or corruption in the winsxs folder. For information on winsxs see here: http://www.winvistaclub.com/f16.html
Along the way I can up with the following tips but didn't use them:
net stop wuauserv
ren SoftwareDistribution SoftwareDistribution.old
net start wuauserv
Download update manually, and attempt to install form download.
How to reset Window Update: http://support.microsoft.com/kb/971058
Example of my WindowsUpdate.log
2013-02-25 09:45:03:332 7276 6a4 Handler CBS package identity: Package_for_KB2753842~31bf3856ad364e35~amd64~~22.214.171.124
2013-02-25 09:45:03:351 7276 6a4 Handler Installing self-contained with source=C:\Windows\SoftwareDistribution\Download\908a0e5d76fa13f541dce8ccd1e16264\windows6.1-kb2753842-v2-x64.cab, workingdir=C:\Windows\SoftwareDistribution\Download\908a0e5d76fa13f541dce8ccd1e16264\inst
2013-02-25 09:45:07:190 7276 40c Handler FATAL: CBS called Error with 0x80073712,
2013-02-25 09:45:07:880 7276 6a4 Handler FATAL: Completed install of CBS update with type=0, requiresReboot=0, installerError=1, hr=0x80073712
Example of CBS.log
Well, when it finally worked it overwrote my CBS.log, so I don't have an example... But this is where I connected the 0x80073712 with the verbiage ERROR_SXS_COMPONENT_STORE_CORRUPT.
Post a Comment