[Win7SP1 x64] corrupt manifest

[lansalot]

Hi
I have been battling this all day. I am sure that I'm pretty close, but failing at the last hurdle. Maybe I just need to place a manifest in the 'backup' folder for SFC to be happy?

Attached is
sfcfix1 - this was run before changing registry.
changed registry: I have been getting this in the cbs log:

2017-05-22 16:52:07, Info CSI 000006a6 Manifest hash for component [ml:280{140},l:188{94}]"amd64_microsoft-windows-capi2-weakcrypto_31bf3856ad364e35_6.1.7601.19091_none_5e0ace3543c4654c" does not match expected value.
Expected:{l:32 b:9ba48e23c24a9390667a563bc86500e5d07cd777ffe568ae58261a87138ad785}
Found:{l:32 b:0b9c4b62ba620c77aebb3bb958027e5ea9c3c9e0728e53a5e2893836d5c70935}.

So I thought 'ok i will just update the registry key. I therefore renamed the S256H entry, exported and re-imported. The export (post rename to .old) and import files are attached, renamed to .txt Did not reboot before SFC again, if that changes anything.
Then ran SFC which still failed, and gives the logs as per CBS1.zip - this contains the CBS folder contents (minus the large cab files). I believe it contains logs from many attempts throughout the day.

Then ran sfcfix again to get sfxfix2.log

This is on Windows 7 Pro machine installed with a default Fujitsu factory image, and has been in service for around 2 years. The issue we are having at the moment is unable to install a specific set of Windows Updates, namely the Quality Rollups. We have had this issue on another machine at another client's and ended up having to reload from scratch. I would like to know how to fix instead. I am getting Windows Update error 0x80073712 which according to this page means store corruption.

DISM /online /cleanup-image /scanhealth is currently not complaining as best I can tell.

As best I can tell the manifest file it refers to is not corrupt, it opens fine in notepad and looks similar to another PC's version - there is an additional line in the one on this machine. I have attached it for reference, renamed to .txt.

I did have some minor issues with this machine fixed by chkdsk, I can attach this log if you think it relevant.

Assistance and explanations greatly appreciated, I have another machine still to look at which has the same Windows Updates issue, although possibly different error code.

 

[BrianDrab]

Re: corrupt manifest

Hi and welcome to Sysnative. Sorry for the delay. Are you still in need of assistance?

 

[lansalot]

Re: corrupt manifest

Hi
We have not resolved this yet. I am keen to understand how to fix it, as we support a number of computers and this is not the first time we've seen this issue.

Thanks

 

[BrianDrab]

OK, it's ill advised to muck with the S256H value so we are going to set it back and then replace the following files with good copies.

Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-capi2-weakcrypto_31bf3856ad364e35_6.1.7601.23290_none_5e936c9c5ce2e8e6.manifest
 winsxs\manifests\amd64_microsoft-windows-capi2-weakcrypto_31bf3856ad364e35_6.1.7601.19091_none_5e0ace3543c4654c.manifest
 servicing\packages\Package_2_for_KB3123479~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB3123479~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB3123479_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB3123479_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB3123479~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB3123479~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB3123479~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB3123479~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB3123479_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB3123479_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB3123479~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB3123479~31bf3856ad364e35~amd64~~6.1.1.0.cat

So Please start with the following.

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, 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

Step#2 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.