I have been having problems installing the following Windows 7 (64 bit) updates in the past month:
Update KB3061518 - 5/12/15
Update KB3063858 - 6/9/15
Windows 7 Update error returns 80073712.
I have run sfc /scannow and the scan does not detect corrupt files. See attached scan file, which contains results before and after the attempted update.
I would appreciate some guidance on further troubleshooting.
Thanks.
Pleasefollow the WindowsUpdate Posting Instructions and postthe requested data
If thefile is too large (8MB compressed), remove the older CBSPersist cab files untilthe final file is below the limit - you can always post them separately afterzipping them. (the forum doesn't allow the upload of bare CAB files, for anumber of reasons)
Pleasealso post the C:\Windows\windowsudpate.log file
Hi Noel,
I have completed all the steps requested. See attached files.
Thanks.
You have a number of registry problems.
Do you have System Restore points available as far back as the start of May? if so, I would suggest using them, and then running the data-gathering exercise again.Code:Checking Packages (f) CBS Registry Error 0x80070002 Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514 failed to get CurrentState (f) CBS Registry Error 0x80070002 Microsoft-Windows-GroupPolicy-ClientTools-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514 failed to get Visibility Checking Component Store (f) CSI Payload File Missing 0x00000000 powercfg.exe x86_microsoft-windows-p..nfiguration-cmdline_31bf3856ad364e35_6.1.7600.16385_none_09320e5ae212b9d9 (f) CSI Missing Identity 0x00000000 appid cf188e4f6a8..7aef7b7fb39_31bf3856ad364e35_6.1.7601.18741_14d6ee8e3fa2616b (f) CSI Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_717cd316e33ca2f6 HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 db3812601a1..e3a875c39e1_31bf3856ad364e35_6.1.7601.22948_e6ea7771c9e927b4 HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 59a45f66a46..35f8b642cc5_31bf3856ad364e35_6.1.7601.18741_ed4431e62f1473e1 HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 933aeb16137..3f4990b165a_31bf3856ad364e35_6.1.7601.18741_780ad933ad30fca6 HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 microsoft-w..anguagepack_31bf3856ad364e35_7.1.7601.16492_2b2514f236be925f HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 358048f3aa8..bfc8e1e644d_31bf3856ad364e35_6.1.7601.22948_7affb5a728c8530c HKLM\Components\CanonicalData\Deployments (f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-crypt32-dll_31bf3856ad364e35_6.1.7601.18741_none_b97243acf48e6cd8 Summary: Seconds executed: 1255 Found 11 errors CSI Missing Deployment Key Total count: 6 CSI Missing Identity Total count: 1 CSI Payload File Missing Total count: 1 CBS Registry Error Total count: 2 CSI Missing Winning Component Key Total count: 1
Hi Noel,
I check my computer and I cannot find any restore points from critical installs older than a couple of days. Any other suggestions on how to fix these registry problems?
Thanks.
Let's see if another tool can help...
Please download SFCFix from here... http://www.sysnative.com/niemiro/apps/SFCFix.exe and save it to your desktop (we'll need it later anyhow, I think)
Once saved, double-click on it and accept the warnings. It'll run, and create a file SFCFix.log on the desktop -please upload it to your reply.
OK - let's go at it another way, then....
I need to have a look at your COMPONENTS registry hive
Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.
Quote