SFC cannot fix corrupted files in Windows 7 -- Windows Update for May 2015?

Anonymous
2015-05-14T15:47:58+00:00

I believe we have a system wide problem!  No, I am not kidding.  I routinely run SFC on computers and it almost always returns a report of no problems or not often but sometimes reports that it found problems and fixed them.  Rarely, it reports corruption found and not fixed.  In those instances the only way I know to fix this in Windows 7 is to re-build the OS.

 In the past several days I have run SFC on 5 different computers all running Windows 7, but in different places, used by different people. 

All report SFC found corrupted files and was unable to fix them.

I do not know if there is corruption, if SFC is itself incorrect, let alone how to fix this.  There is suspicion that the May 2015 patches may have caused this.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

84 answers

Sort by: Newest
  1. Anonymous
    2015-05-22T18:04:22+00:00

    Thanks Susan....any thoughts about what happened when I made the adjustment noted in my previous (May 20th) post...there did seem to be some interaction between 3022345 and 3035583.

    (and for info I have checked my event-viewer logs and they are error-free.) - Ric.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-05-22T17:55:26+00:00

    https://support2.microsoft.com/default.aspx?scid=kb;en-us;3022345

    KB3022345 does NOT cause file corruption.

    Summary

    This update enables the Diagnostics Tracking Service in Windows 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1), and Windows Server 2008 R2 SP1. This tracking service collects data about functional issues in Windows.

    This update contains the following two manifests that are occasionally updated by the Diagnostic Tracking Service:

    • telemetry.ASM-WindowsDefault.json
    • utc.app.json

    The two files are marked as static files in the update. When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted. There is no impact or corruption on a device that is running this update, and this issue will be fixed in a later service update.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-05-20T21:55:54+00:00

    I would be interested to see your Event Viewer System and Application logs.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-05-20T18:23:35+00:00

    I look after about 160 client Windows computers -- virtually all Windows 7 today.  I have been doing this for 13 years now.

    On patch Tuesday, they get an email at about 1pm EST telling them that if they are using their computers today, they should immediately close all applications, start Windows Update, click Check for updates.  Then simply click Install. 

    They are to never open either category.  Never check mark anything.  Never even open the Optional link.

    Bottom line:  Only the updates categorized as "Important" get installed.  Even if there is one in the Important category and UNCHECKED, it is not installed.

    I use remote control software and manage to log into each computer at least once per year.  When I do that one part of my routine is to examine these un-installed updates and install, hide or do nothing with them. 

    Up until recently, Microsoft has been pretty good about this categorization.  Lately, with updates like KB3022345 and KB3035583, they have crossed the line.  These updates (and there are likely more) are not Important to their computers or the people themselves.  They are important to Microsoft in meeting its goals. 

    I am currently re-thinking my policies.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-05-20T18:05:24+00:00

    I was helping my neighbor who has a Dell laptop with Window 7 Home Premium 64 bit when I ran across this thread.  Her system was rebooting after installing updates during reboot ... stage 3 update @ 35% then it would restart .... continuously! I ran recovery, took care of the KB3022345 issue and got a clean SFC run.  I then proceeded to install updates one by one until I got down to KB3020369, KB3020370, and KB3045645 and thought "what the heck" and let all three go at once. Well, once again the updates applied on restart got into the Stage 3 @ 35%, shutdown loop.  After spending 18 hours trying to fix this issue I decided to heck with it. I ran recovery, hid those three updates and it works fine.  I told her to NOT install any updates until she checked with me.

    I have several Windows 7 systems that I help people with and am going to turn off updates on all of them.  I will tell them to only call me when they have a particular problem and then I will look at the updates to find out what can fix it.  Not really the way I want to go but this is getting upsetting.  I am not a windows expert but have been programming computers for 50 years and have never run into this before......I'm glad I retired and may just have to refuse to helping people with these things. 

    I personally have several Windows 7 and Windows 8 computers at home and spend most of my computer time running updates ... Windows, Firefox, Java, Adobe, etc.  Linux is beginning to look more and more attractive.  I also have a Windows 8.1 phone after putting up with the debacle that is called Android.  Microsoft's attempt to remake itself into a marketing/advertising company for cash flow and take control of my devices via the Microsoft Store is making Blackberry look pretty good too.

    Was this answer helpful?

    0 comments No comments