Windows 7 Update error 80073712 on Updates KB3061518, KB3063858

[looromach]

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.

 

[NoelDP]

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

 

[looromach]

Hi Noel,

I have completed all the steps requested. See attached files.

Thanks.

 

[NoelDP]

You have a number of registry problems.

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

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.

 

[looromach]

Thanks, Noel. I will double check and get back to you.

 

[looromach]

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.

 

[NoelDP]

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.

 

[looromach]

Thanks. Please see attached scan results. Thanks.

 

[NoelDP]

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.

 

[looromach]

https://onedrive.live.com/redir?resid=24AE5B01DB879F2F!111&authkey=!AKpFA68VCE-RX0U&ithint=file,

 

[NoelDP]

I've uploaded a file - jmnaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it to your desktop.

Right-click on the file and select Extract All, andsave to the default destination (which should be a folder on the desktop)

Create a new System Restore point
Open an Elevated Command Prompt, and run the followingcommands.

[B]IF EXIST C:\Windows\System32\config\COMPONENTS.OLD1  DEL C:\Windows\System32\config\COMPONENTS.OLD1[/B]
[B]REN C:\Windows\System32\config\COMPONENTS  COMPONENTS.OLD1[/B]
[B]COPY  "%userprofile%\desktop\wfire\COMPONENTS"   C:\Windows\System32\config[/B]
 
[COLOR=black][FONT=Segoe UI].[/FONT][/COLOR]

If you get an error with any command, STOP THERE - do not reboot! - post for instructions.

Assuming all commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.

 

[looromach]

Hi Noel,

Can you check these commands again? I highlight the items in question.

Thanks

*IF EXIST C:\Windows\System32\config\COMPONENTS.OLD1DEL C:\Windows\System32\config\COMPONENTS.OLD1*
*REN C:\Windows\System32\config\COMPONENTSCOMPONENTS.OLD1* *COPY"%userprofile%\desktop\wfire\COMPONENTS" C:\Windows\System32\config*

 

[NoelDP]

I amended the post within a couple of minutes of posting it - but obviously not before the email went out (the forum and my One-Note archive tend to argue sporadically - it annoys the heck out of me!)

Check the revised post #11 in the forum

 

[looromach]

Same files still corrupted. See attached scan results. Also include links to the old components file and the new one I downloaded. Are they the same?

https://onedrive.live.com/redir?resid=24AE5B01DB879F2F!112&authkey=!AIGekmW7WwooXuA&ithint=file,OLD1

https://onedrive.live.com/redir?resid=24AE5B01DB879F2F!113&authkey=!AAgD8l3xyDbhvb0&ithint=file,

 

[NoelDP]

You will get the same result from SFCFix until you run the CheckSUR tool - please post the new CheckSUR.log file.

 

[looromach]

Hi Noel,

I'm still working on this. I noticed that after I ran the system readiness update (SRU), the number of corrupted SRU files went down from 11 to 6. However, when I re-ran the sfc /scannow after the SRU, the number of corrupted files in the CBS log increased significantly, and I was not able to repair them. Is this expected?

Anyway, I had to restored system and start again. Will send the results when I am done.

Thanks.

 

[looromach]

Meant SUR in the previous post, not SRU.

 

[looromach]

Hi Noel,

Please find attached the checkSUR.log file. I also include the scan fix log.

Here's the link to the latest component file if you want to take a look at it.

https://onedrive.live.com/redir?resid=24AE5B01DB879F2F!118&authkey=!AGflRhyZXPT4hvI&ithint=file,zip

Let me know where to go from here.

Thanks.

 

[NoelDP]

CheckSUR shows these errors remaining now...

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 Missing Deployment Key 0x00000000 win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_717cd316e33ca2f6 HKLM\Components\CanonicalData\Deployments 
(f) CSI C Mark Deployment Missing 0x00000000 c!1d4ffe5d024..93ab13df945_31bf3856ad364e35_6.1.7601.18741_3eb0a94f17ca3e3f amd64_microsoft-windows-crypt32-dll_31bf3856ad364e35_6.1.7601.18741_none_b97243acf48e6cd8

I'll work on these when I can get to them.

 

[NoelDP]

I've uploaded a file - jmnab.zip - to my OneDrive at Noel's OneDrive
Please download and save it to your desktop.

Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)

Create a new System Restore point
Open an Elevated Command Prompt, and run the following commands.

[B]IF EXIST C:\Windows\System32\config\COMPONENTS.OLD1  DEL C:\Windows\System32\config\COMPONENTS.OLD1[/B]
[B]REN C:\Windows\System32\config\COMPONENTS  COMPONENTS.OLD1[/B]
[B]COPY  "%userprofile%\desktop\jmnab\COMPONENTS"   C:\Windows\System32\config[/B]
 
[COLOR=black][FONT=Segoe UI].[/FONT][/COLOR]

If you get an error with any command, STOP THERE - do not reboot! - post for instructions.

Assuming all commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.