Can't update, all have code 80073712

Code: 
2015-06-23 16:38:59, Error                 CSI    0000165a@2015/6/23:21:38:59.835 (F) d:\win7sp1_gdr\base\wcp\componentstore\storelayout.cpp(11690): Store corruption detected in function ComponentStore::CRawStoreLayout::CheckFamilyIndexForDeadWinnerComponent expression: (null)
  MissingWinningComponentKey on resource [86]"x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.18779_none_5fa9ce6b500a61f6"[gle=0x80004005]

Step#1 - SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.



  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please



Step#2 - Attempt Install
 1. Assuming kb3068708 is still one of the updates showing that needs to be installed (please verify),
2. Go ahead and attempt to install this update.
3. If it fails, please zip up the following logs and send my way.

C:\Windows\Logs\CBS\CBS.log

If any of them are too large to attach to the forum (larger than around 7Mb), you may upload to SendSpace and just provide the link.
Items for your next post
1. SFCFix.txt
2. CBS.log
 

Attachments

Code: 
SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-06-24 10:12:31.642
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at D:\Users\Roberts\Downloads\SFCScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_none_781e00248a39d4df\v!6.1.7601.18779.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.18779_none_5fa9ce6b500a61f6.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\d1ac5e2821b407c6b32fbb628201261cda3634d16b75a4973f9b62a618a95199.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8550536b684..0bf70ce607d_31bf3856ad364e35_6.1.7601.18779_ff883b225abce8f2.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_none_781e00248a39d4df\v!6.1.7601.18779.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_none_781e00248a39d4df\v!6.1.7601.18779.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.18779_none_5fa9ce6b500a61f6.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\d1ac5e2821b407c6b32fbb628201261cda3634d16b75a4973f9b62a618a95199.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8550536b684..0bf70ce607d_31bf3856ad364e35_6.1.7601.18779_ff883b225abce8f2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_none_781e00248a39d4df\v!6.1.7601.18779.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 49 datablocks.
Finish time: 2015-06-24 10:12:32.380
Script hash: ekjjgztR2Kbyhqtgl3f5yYzTiEr1tX54rx/Du5zg+GU=
----------------------EOF-----------------------

https://www.sendspace.com/file/7ejlv3
 
Code: 
2015-06-24 10:15:33, Error                 CSI    000017b9@2015/6/24:15:15:33.527 (F) d:\win7sp1_gdr\base\wcp\componentstore\storelayout.cpp(11690): Store corruption detected in function ComponentStore::CRawStoreLayout::CheckFamilyIndexForDeadWinnerComponent expression: (null)
  MissingWinningComponentKey on resource [95]"wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.18779_none_8a5509bda06f5d45"[gle=0x80004005]

Step#1 - SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please

Step#2 - Attempt Install
 1. Assuming kb3068708 is still one of the updates showing that needs to be installed (please verify),
2. Go ahead and attempt to install this update.
3. If it fails, please zip up the following logs and send my way.

C:\Windows\Logs\CBS\CBS.log

If any of them are too large to attach to the forum (larger than around 7Mb), you may upload to SendSpace and just provide the link.
Items for your next post
1. SFCFix.txt
2. CBS.log
 

Attachments

Code: 
SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-06-25 08:47:00.992
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at D:\Users\Roberts\Downloads\SFCScript(1).txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\d1ac5e2821b407c6b32fbb628201261cda3634d16b75a4973f9b62a618a95199.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8550536b684..0bf70ce607d_31bf3856ad364e35_6.1.7601.18779_ff883b225abce8f2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_none_d9449137c13ad562\v!6.1.7601.18779.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.18779_none_8a5509bda06f5d45.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\d1ac5e2821b407c6b32fbb628201261cda3634d16b75a4973f9b62a618a95199.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8550536b684..0bf70ce607d_31bf3856ad364e35_6.1.7601.18779_ff883b225abce8f2.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_none_d9449137c13ad562\v!6.1.7601.18779.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_none_d9449137c13ad562\v!6.1.7601.18779.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.18779_none_8a5509bda06f5d45.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Catalogs\d1ac5e2821b407c6b32fbb628201261cda3634d16b75a4973f9b62a618a95199.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8550536b684..0bf70ce607d_31bf3856ad364e35_6.1.7601.18779_ff883b225abce8f2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_none_d9449137c13ad562\v!6.1.7601.18779.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 51 datablocks.
Finish time: 2015-06-25 08:47:03.061
Script hash: ZMmRbYgMrFn27wzPHVfj7MFC2Nk8xiuLCr13rOGkHWw=
----------------------EOF-----------------------

https://www.sendspace.com/file/e1swwe
 
Code: 
2015-06-25 08:50:48, Error                 CSI    00001918@2015/6/25:13:50:48.547 (F) d:\win7sp1_gdr\base\wcp\componentstore\storelayout.cpp(11690): Store corruption detected in function ComponentStore::CRawStoreLayout::CheckFamilyIndexForDeadWinnerComponent expression: (null)
  MissingWinningComponentKey on resource [86]"wow64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.18409_none_fc484db2a13f5426"[gle=0x80004005]

Step#1 - SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.



  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please


Step#2 - Attempt Install
 1. Assuming kb3068708 is still one of the updates showing that needs to be installed (please verify),
2. Go ahead and attempt to install this update.
3. If it fails, please zip up the following logs and send my way.

C:\Windows\Logs\CBS\CBS.log

If any of them are too large to attach to the forum (larger than around 7Mb), you may upload to SendSpace and just provide the link.
Items for your next post
1. SFCFix.txt
2. CBS.log
 

Attachments

Code: 
SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-06-26 06:33:42.759
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at D:\Users\Roberts\Downloads\SFCScript(2).txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\578c218ab96..51d38575fb2_31bf3856ad364e35_6.1.7601.18409_811fb736c5399f9f.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6c357d43a56..22066fdfc62_31bf3856ad364e35_6.1.7601.18409_76089b5dff1ee546.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\wow64_microsoft-windows-kernel32_31bf3856ad364e35_none_c321ed781672c19d\v!6.1.7601.18409.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.18409_none_fc484db2a13f5426.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\578c218ab96..51d38575fb2_31bf3856ad364e35_6.1.7601.18409_811fb736c5399f9f.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6c357d43a56..22066fdfc62_31bf3856ad364e35_6.1.7601.18409_76089b5dff1ee546.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\wow64_microsoft-windows-kernel32_31bf3856ad364e35_none_c321ed781672c19d\v!6.1.7601.18409.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\wow64_microsoft-windows-kernel32_31bf3856ad364e35_none_c321ed781672c19d\v!6.1.7601.18409.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-kernel32_31bf3856ad364e35_6.1.7601.18409_none_fc484db2a13f5426.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\578c218ab96..51d38575fb2_31bf3856ad364e35_6.1.7601.18409_811fb736c5399f9f.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6c357d43a56..22066fdfc62_31bf3856ad364e35_6.1.7601.18409_76089b5dff1ee546.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\wow64_microsoft-windows-kernel32_31bf3856ad364e35_none_c321ed781672c19d\v!6.1.7601.18409.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 53 datablocks.
Finish time: 2015-06-26 06:33:44.827
Script hash: JNkdxq7Ls/4JCX/QHcR01D9vOFyOZ25DHOVwNS8yQ24=
----------------------EOF-----------------------

https://www.sendspace.com/file/7tl67r
 
Darn. I was really hoping that we would get somewhere but it looks like we are at the end of the road. We could continue this for weeks and still not be done.

really, really want to find a solution that isn't a complete wipe and reinstall. All I can get here is DSL, which gives me a maximum download speed of 180 kb per second... and I would have to download more than a terabyte to replace what I would lose. One doesn't have to do the math to understand what a nightmare that would be.
Click to expand...

I tried everything I possibly could because of your desire not to wipe and re-install. But we are at the end of the road. The only options I see are to try a repair install or do a complete wipe/reload. Yes you would have to obtain a Windows 7 DVD with SP1 on it in order to do so. Not sure if you have any friends, co-workers, family that may have one you can borrow. But this may not even work. The next step would be a wipe and load. You should copy your data off to an external backup drive before doing so obviously.

The last option would be to ensure that you reserved your free Windows 10 upgrade. Then when it comes out next month you could wipe/load at that time using the media.

I'm very sorry we couldn't do more. Let me know what your intentions are.
 
One other notion has occurred to me last night, but I don't know if it would be useful.

Sometime last year, I upgraded my hard drive. When I did so, I used the program from the manufacturer to just basically copy the old hard drive onto the new, larger one, and I still have the old drive. Now, in a sense, that is the same hard drive, but it would be quite a b it out of date. My question would be, were I to plug it in and boot into it, do a registry backup on it, and then copy the backup of the hive that is damaged here onto a usb drive to use in a registry restore on this one. My question would be, would it be too out of date to avoid something rather similar to what I already have going on here?

My other question would be, do you think it would be possible to, instead of using updates, use the beta Windows 10 install and try to repair the things that are keeping it from working? Or would we run into the same thing as with the updates, with just an endless string of errors?
 
Sometime last year, I upgraded my hard drive. When I did so, I used the program from the manufacturer to just basically copy the old hard drive onto the new, larger one, and I still have the old drive. Now, in a sense, that is the same hard drive, but it would be quite a b it out of date. My question would be, were I to plug it in and boot into it, do a registry backup on it, and then copy the backup of the hive that is damaged here onto a usb drive to use in a registry restore on this one. My question would be, would it be too out of date to avoid something rather similar to what I already have going on here?
Click to expand...

This would likely put your machine in to a much worse state if it's not too current. I've heard of people doing this successfully but it was in a corporate environment where there were identical images, etc.


My other question would be, do you think it would be possible to, instead of using updates, use the beta Windows 10 install and try to repair the things that are keeping it from working? Or would we run into the same thing as with the updates, with just an endless string of errors?
Click to expand...

I don't think this would work. I've never tried though so can't be sure but I would think that the repair has to happen with the original OS. Installing a new OS on top of a "damaged" OS doesn't see like a good idea.
 
I guess my one other question before I start trying to figure out what to do from the tough options: in a similar vein to the Windows 10 question, we have the uninstalling SP1 errors. My disc can see that SP1 is there and thus won't allow me to do a repair install, but when I try to uninstall SP1 Windows seems to think it isn't installed. Would that, too, lead to the endless errors?
 
I guess my one other question before I start trying to figure out what to do from the tough options: in a similar vein to the Windows 10 question, we have the uninstalling SP1 errors. My disc can see that SP1 is there and thus won't allow me to do a repair install, but when I try to uninstall SP1 Windows seems to think it isn't installed. Would that, too, lead to the endless errors?
Click to expand...

Sorry, I'm not sure what the question is. Would what lead to endless errors?
 
Oh. Were we to try to fix the errors that lead to SP1 failing to uninstall rather than the ones that lead to updates failing to install, would that lead to a similar string of endless errors? Or is that even possible?
 
Got it. Unfortunately I feel we would be met with the same issues. Is there anyone that you can borrow a DVD from that has SP1 on it?
 
Doubtful, but I'm going to spend a couple of days asking around before I come to any other decisions. Maybe I'll get lucky.

Thanks for everything here, bud. I'll pop back once I know where I've landed and let you know.
 
It took some doing, but I did finally manage to get my hands on a disc that included SP1. The repair install has finished, and I'm now in the process of installing the 90 Windows Updates it found thus far afterwards.

Thanks again for all you did here, man. It was serious yeoman's work.
 
You must log in or register to reply here.
Back
Top