It's simply a case of how fragile the HD is. If it's fragile enough ANY access could trigger failure. SFC touches tens of thousands of files, so stands more chance than most things of doing so. The other main potential triggers would be a full AV scan, and CHKDSK..
I came late in this thread, but I just wanted to say tip of the hat and Kudo to Ehasanov for opening this thread. I knew it was a Windows update that was responsible for the corrupt files found after running sfc /scannow, but I could not tell which update. I spent almost 4 to 5 days trying to find a solution to that nagging problem until today.
:)
Yikes this is why I too was glad to find this problem when I did--had I found it instead down-the-road I'd have fiddled with the problem as you TP.
I just checked another computer that needed another round of updates and sure enough sfc fails and now I have to try SFCFix again.
HOW ON EARTH can MS rationalize leaving this turd in place given some folks are spending a lot of time & effort to fix sfc /scannow woes (and don't enjoy the comfort of sevenforums.com)????
I suspect 80% of Windows users are probably unaware of this issue and would only find out if they had serious corruption problems unrelated to this specific update. Probably be wise for MS to offer an easy fix sooner than later as to prevent any unnecessary grief or confusion for the average Windows user who practices the set-and-forget maintenance philosophy.
Rumor has it that some of the updates that Microsoft is throwing at us right now are in preparation of the big event, that is, the release of Win 10 probably late this summer. Some definitely have bugs and it seems so far Microsoft is not paying much attention to that. In the meantime, all the users out there who are using Windows seem to be paying the price.
Four to five days to find the solution to a problem caused by Microsoft is productivity time lost and that's a lot. That doesn't square off with good practice.
KB3045171 is also giving problems, it would seem, along with KB3057110 (the latter hasn't been offered to me).
Microsoft font driver updates KB 3057110 and 3045171 cause Windows 7 PCs to crash | InfoWorld
Also, KB3020369 has now been identified as the May update that causes computers to hang on installation.
Microsoft fingers KB 3020369 as culprit in Stage 3 of 3 reboot hangs | InfoWorld
Well, only one optional (KB3054476) today - May 2015 update for stream.sys driver-based applications in Windows 7 or Windows Server 2008 R2.
Last edited by Sky Ranch; 19 May 2015 at 19:24.
Is anyone have the same issue again after installing the latest Windows updates?
It seemed to be fixed after running but SFCFix but now the issue has returned.
Regards.
Quote