SFC.exe - How seriously should I take this report?

Hello guys,

Thanks so much for all the great input, obviously special mention to 'UsernameIssues' for being the pathfinder in this whole thread. Everyone here who's posted is about to get some rep, and I think I might just have the solution.

There was a windows update released only a few days ago (for me I installed it yesterday). Here is the link to the update:

https://support.microsoft.com/en-us/kb/3068708

Here is my evidence that is has solved the issue (at least for me):

1) I ran system file checker after installing the problem update in a windows update wave that 'UsernameIssues' made us aware of earlier in this thread.

2) The SFC report stated at the end that 'Windows found corrupt files and could not fix some of them'.

3) I ran a natural windows update only yesterday which included the referenced KB (see above hyperlink)

4) The hyperlink is promoted by microsoft as being an update to the 'broken' update that 'UsernameIssues' made us aware of earlier in the thread.

5) I ran SFC from elevated command prompt, and this time the report at the end showed the correct message when there are no corrupt files 'windows found no problems' or something similar.

Try running windows update today guys, making sure that the KB listed above ^^ is included (it should be by default). Try running SFC again and let me know if you get the same results.

Thanks again everyone, and keep the thread rolling for those who are still working this issue out.

Kind Regards,
Eldar

I removed KB3022345 and KB3068708, then ran SFC with good results. I then manually reinstalled KB3068708 and ran SFC and got the corrupted files that can't be fixed indication. So, I removed KB3068708 again and everything was good with SFC. I've hidden the KB3068708 update so that it won't get reinstalled, but I noticed that KB3022345 doesn't reappear after it's been removed from the system.

I guess KB3022345 was pulled from Windows Update, I don't have it installed or hidden and neither does it being offered any more.

tjg79 said:

I removed KB3022345 and KB3068708, then ran SFC with good results. I then manually reinstalled KB3068708 and ran SFC and got the corrupted files that can't be fixed indication. So, I removed KB3068708 again and everything was good with SFC. I've hidden the KB3068708 update so that it won't get reinstalled, but I noticed that KB3022345 doesn't reappear after it's been removed from the system.

I agree with your logic that if when KB3022345 & KB3068708 are uninstalled, and then SFC found no corrupt files, then your system is not at fault, but the updates are.

The updates I would assume aren't that important, as the original KB3022345, was an 'optional' update, and the fix for it KB3068708 was 'recommended' (I would assume only recommended because it was a fix update for the original 'optional' one).

I think you are fine to leave the updates uninstalled and hidden.

and hello again GoKay :) How's it going?

GokAy said:

I guess KB3022345 was pulled from Windows Update, I don't have it installed or hidden and neither does it being offered any more.

I think they have removed it from win update as well. I have no evidence to back this, as I already have that update installed, but it makes sense to me, that they would remove it to stop others from accidentally installing it, and ignoring the update that fixes it.

After I removed both problematic updates, KB3022345 and KB3068708, and confirmed everything was good with SFC, I got three more updates to install: KB3045999, KB3063858, and KB2882822. I installed the three new updates and then checked View Update History and I saw that KB3068708 appeared to be installed even though I had hidden this update, because of the SFC issue. I just confirmed everything is good with SFC /Scannow results. I suspect one of these new updates is a subsequent fix for the SFC indications.

Now I'm going to unhide KB3068708 and see if it still wants to be installed even though it appears to already be installed.

microsoft update always bugs me like that. the way it finds more updates instead of just getting the lot in one go. overall, i think we can chalk this one up to #microsoftfail. now lets hope they dont make windows a yearly subscription service :/

Layback Bear said:

I have removed and then hid KB3022345 without any problems.
SFC / SCANNOW works as it should.

out of curiosity, did you have the original issue with SFC reporting 'windows found corrupt files'?

just did a quick check when the sfc fix was released, and it was the 8th June, so would make sense that when you re-installed windows 4 days ago, that update would have been installed on your system before you hit sfc.exe.