Windows 7 update (KB3022345) causing corrupt files

Hi Go The Power,

Just curious what SFCFix exactly does to stop the error? Does it replace the files with the ones before the update?

Regards,
Robert

ownedandout said:

Hi Go The Power,

Just curious what SFCFix exactly does to stop the error? Does it replace the files with the ones before the update?

Regards,
Robert

SFCFix.exe works with another file, SFCFix (x64 fix) or SFCFix (x86 fix). The latter files have the 2 JSON files which replace the corrupted files. See my previous post for more instructions.

I don't think it will be necessary to use the above fix. Eventually, Microsoft will become aware of the problem and create another fix in their Windows Update. To speed this up, perhaps someone should notify Microsoft and let them know about the problem they created.

Urthboundmisfit said:

Go The Power said:

I have just taken a look at the files within the Windows 7 version of this update and those two files have the same SHA256-Base64 hash as the ones from the Windows 8 version. This is why SFCFix was able to track down and repair these files for you.

At the time when I wrote this article I was not aware it was also causing issues on Windows 7 machines.

Could you please zip up the entire CBS folder and upload this OneDrive/Dropbox then share the link back here? I would like to be able to update my article to include a Windows 7 fix.

Thanks

Hello GTP, I have the same corrupt files after installing KB3022345; CBS.zip uploaded to OneDrive:
https://onedrive.live.com/redir?resi...2abebf5%211444

sfcdetails.txt

Thanks for that, I have now created a specific fix for Windows 7:
The Tech Cookbook – Windows 7 update (KB3022345) causing corrupt files

ownedandout said:

Hi Go The Power,

Just curious what SFCFix exactly does to stop the error? Does it replace the files with the ones before the update?

Regards,
Robert

Hi Robert,

SFCFix can basically go one of two ways, if a corrupt file is found inside the CBS log SFCFix will search your computer for a suitable replacement. SFCFix will do this by checking the SHA256 algorithm of each file on your computer. But if SFCFix can not find a suitable replacement then a fix zip file needs to be made, inside the zip fix will contain the non corrupt version of these files. SFCFix will then remove the corrupt version and replace it with the non corrupt version.

The thing is Windows Updates are no released corrupt, the files inside the KBxxxx.msu have had a sanity check to make sure they are correct, in actual fact the installer will not run if a corrupt file is inside the WU file. If you ever look inside a Windows Update MSU file you will see a file called _manifest_.cix.xml, this file contains all the SHA1 hashes of the file, this is used to make sure no files are corrupt or tampered.

Now something must be going wrong after the files have been installed onto these users computers, as if they were corrupt inside the update the install would not of processed. I wish I could tell you how this is happening, but I have not been able to trigger it my self.

Hi Go The Power,

Thanks for the explanation, much appreciated!

Kind Regards,
Robert

I just mistakenly installed KB 3022345 on Win7 X64 SP1.... long story short I thought I would try Go The Power's fix first out of curiosity and yes it works like charm, well it did on my system anyway...

you must change these corrupted files with good files manually . you can do it with another computer

Another Win 7 x64 SP1 user reporting in. SFC would show the 2 files as corrupt. A re-run of SFC after the fix returned no corruptions.

I would like to ask though: The CBS.log file after the first run of SFC was 252MB big and it was a pain to load in Notepad. Was that normal? After the fix and re-run, file size dropped to 700kB.

GokAy said:

Another Win 7 x64 SP1 user reporting in. SFC would show the 2 files as corrupt. A re-run of SFC after the fix returned no corruptions.

I would like to ask though: The CBS.log file after the first run of SFC was 252MB big and it was a pain to load in Notepad. Was that normal? After the fix and re-run, file size dropped to 700kB.

I do not know if that is normal or not but I can say mine was around about that size and then dropped down also afterwards... Maybe worth a mention I went on to uninstall that update anyway even after the fix (like I said I was just curious to try the fix) and re-checked SFC /SCANNOW and did a CHKDSK /F also and everything is ok... the uninstall removed the service successfully also by the looks of things.

It is normal, the CBS log is set to a certain limit, once it reaches that limit it will be renamed to CBSPersist_{Date}.log