[SOLVED] Windows 7 - Multiple failures to install KB3197868 + SFC errors

J

jonUK76

Member
Joined
Nov 23, 2016
Posts
6
Hello,

For as long as I can recall this W7 installation has shown unfixable SFC errors, which don't appear to have caused any ill effect. Several months ago, something strange happened where Windows spontaneously decided it had not been activated, but I re-activated and apart from a few issues with other software also needing re-activation at that time, I carried on and all seemed well... Recently though, a new important update has come through (KB3197868) which will not install, and therefore I'd like to get to the bottom of these problems.

Capture.PNG

The error code is 80073712 which I understand indicates some serious corruption with the component store?

I have so far tried the following:

1) Ran SFC several times... and carried out full chkdsk
2) Ran Windows Update Fixit
3) Ran Windows System Update Readiness Tool
4) Attempted manual installation of KB3197868 from the update catalog (fails)
5) Ran Tweaking.com "Windows Repair AIO" - choosing the fix Windows Updates option
6) Ran SFC Fix

Note: The CBS folder (as opposed to just the log) is larger than I can attach to a post, so I will link to it on my OneDrive. I also attach a link to a zip of the COMPONENTS file.

https://1drv.ms/u/s!AjyFRnqOVSEbmGQqjLSfvtZXw3gd - link to CBS.zip

https://1drv.ms/u/s!AjyFRnqOVSEbmGOHYy63IY0XvDQa - link to components.zip

I am at the stage where previously I'd have chosen just to re-install Windows, but as I have various specialized music software that is locked to this installation, and de-authorizing it is something of a hassle, I'd like to avoid that if possible...

Thank you very much in advance for any help you can give :)
 

Attachments

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.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip 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 - put [CODE][/CODE] tags around the log to break up the text.
View attachment SFCFix.zip

Windows Update Manifest Replacement

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. Please download the attached file, Packs.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing the folder Manifests
  5. Open the Manifests folder and copy the files into the following folder

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

  6. Run the System Update Readiness Tool (SURT) again.
  7. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

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

View attachment packs.zip
 
Hello and thanks for your help.

I have run both items, and here are the logs:

SFCFix

Code: 
SFCFix version 3.0.0.0 by niemiro.Start time: 2016-11-30 01:22:07.407
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Jon\Desktop\SFCFix.zip [0]


RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396.


Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c.
Successfully deleted registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396.


Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_a338d8ea2df29efb with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_499a1b14d5902dfc with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_914751ebea0c5702 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_56aba0211ca246c2 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_policy.14.0.avast.vc140.mfc_fcc99ee6193ebbca_14.0.24210.0_none_962753dde6e08635 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc140.crt_fcc99ee6193ebbca_14.0.24210.0_none_9e58d6f8311e6fc8 with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_1d37a43bbfe1dc9c with error code ERROR_FILE_NOT_FOUND.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_avast.vc110.crt_2036b14a11e83e4a_11.0.60610.1_none_d58a6d64ab65b396 with error code ERROR_FILE_NOT_FOUND.
RegistryScript:: directive failed to complete successfully.








Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2016-11-30 01:22:08.748
Script hash: HK5AvMkKnmBwbvx017UMKhXi8Qru+LgbtfSd5wwkBDA=
----------------------EOF-----------------------


And contents of CheckSUR.log

Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-11-30 01:27


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f)    CSI Manifest Failed Catalog Check    0x00000000    winsxs\Manifests\amd64_microsoft-windows-uianimation_31bf3856ad364e35_7.1.7601.16492_none_dabb204d1164d720.manifest    amd64_microsoft-windows-uianimation_31bf3856ad364e35_7.1.7601.16492_none_dabb204d1164d720    
(fix)    CSI Manifest Failed Catalog Check    CSI File Replaced    File: amd64_microsoft-windows-uianimation_31bf3856ad364e35_7.1.7601.16492_none_dabb204d1164d720.manifest From: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab


Summary:
Seconds executed: 628
 Found 1 errors
 Fixed 1 errors
  CSI Manifest Failed Catalog Check Total count: 1
  Fixed: CSI Manifest Failed Catalog Check.  Total count: 1
 
Just to confirm, I unhid the update KB3197868 after running this fix, and let it install. It completed successfully! I also ran SFC and that now shows no errors. So it appears the issues have been solved :) Thanks once again.
 
Glad to help!

I'll mark the thread solved. Please post back if you encounter any problems and I will continue to assist you.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top