Windows 7 update (KB3022345) causing corrupt files

Page 4 of 8 FirstFirst ... 23456 ... LastLast

  1. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #31

    Yeah - there are actually a number of triggers for the 'archiving' to the Persist files.
    1) file size (can be over-ridden by the system)
    2) Time: generally, it will archive after 10 days
    3) System action: SFC can trigger archiving if the existing file is of a given size or age.
    4) others!
      My Computer


  2. Posts : 6
    8.1 (x64)
       #32

    Anyone who has had this issue can you please upload the Windows Update log for me? Trying to find a trend.

    Windows Update Log

    1. Click on the Start button -> Inside the search box copy and paste the following command
    2. cmd /c copy %windir%\WindowsUpdate.log "%userprofile%\Desktop\WindowsUpdate.txt"
    3. Please go to your desktop and attach WindowsUpdate.txt to your next post
      My Computer


  3. Posts : 10,455
    Microsoft Windows 7 Home Premium 64-bit Service Pack 1
       #33

    Go The Power said:
    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

    Attachment 358753
    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.
    Thanks for the link. Just spotted the problem with my weekly sfc today.
      My Computer


  4. Posts : 20,583
    Win-7-Pro64bit 7-H-Prem-64bit
       #34

    Go The Power said:
    Anyone who has had this issue can you please upload the Windows Update log for me? Trying to find a trend.

    Windows Update Log

    1. Click on the Start button -> Inside the search box copy and paste the following command
    2. cmd /c copy %windir%\WindowsUpdate.log "%userprofile%\Desktop\WindowsUpdate.txt"
    3. Please go to your desktop and attach WindowsUpdate.txt to your next post
    Probably would be better to strip the color out of the text first
      My Computer


  5. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #35

    kado897 said:
    Thanks for the link. Just spotted the problem with my weekly sfc today.
    WHY? - the only time you should ever need to run SFC is when you suspect problems!
    I run SFC /SCANNOW maybe once every 3-4 months, simply because I have every update installed since release (and don't use DiskClean) and need to ensure that the licks are kosher.
      My Computer


  6. Posts : 10,455
    Microsoft Windows 7 Home Premium 64-bit Service Pack 1
       #36

    NoelDP said:
    kado897 said:
    Thanks for the link. Just spotted the problem with my weekly sfc today.
    WHY? - the only time you should ever need to run SFC is when you suspect problems!
    I run SFC /SCANNOW maybe once every 3-4 months, simply because I have every update installed since release (and don't use DiskClean) and need to ensure that the licks are kosher.
    I had a problem some time ago with corruption caused by a beta version of IE and didn't pick it up for months. By the time I picked it up I had run out of RPs and had to go to an old image. Recovery was no fun. Since then I have a timer set up to run it every Saturday afternoon before my weekly image.
      My Computer


  7. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #37

    Fair enough, then
      My Computer


  8. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #38

    Noel does running sfc /scannow hurt anything?

    I run it often. After a large Windows 7 Update or if and when I have been tinkering.
      My Computer


  9. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #39

    The only reason that SFC may hurt anything is the same one that affects CHKDSK - if the HD is failing, then it may trigger a total collapse.
      My Computer


  10. NoN
    Posts : 4,166
    Windows 7 Professional SP1 - x64 [Non-UEFI Boot]
       #40

    NoelDP said:
    The only reason that SFC may hurt anything is the same one that affects CHKDSK - if the HD is failing, then it may trigger a total collapse.
    Good to know.

    I knew i couldn't finish a defrag on a disk that have errors/bad sectors, but wasn't that aware Sfc could bump onto one bad sector during checking integrity, which didn't happenned on the disk i couldn't defrag.

    Does it could lead a total collapse during Sfc /Scannow when on Desktop session or more at boot?
      My Computer


 
Page 4 of 8 FirstFirst ... 23456 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:49.
Find Us