sfc /scannow found corrupt files but was unable to fix them

aussiepride · 23 Jun 2015

AddRAM said:

Did you remove both updates if you have them ?

Once again.

Uninstalling both of those worked! Thanks for your help!

LaurieD227 · 24 Jun 2015

I found the same problem when I ran SFC /SCANNOW.

When I went searching for information on this, I found the following information in the Microsoft article about KB3068708:

"The included service uses SSL (TCP Port 443) to download manifests and upload data to Microsoft when data is available for upload. The service uses the following DNS endpoints:

vortex-win.data.microsoft.com
settings-win.data.microsoft.com

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 actual corruption on a device that is running this update, and this issue will be fixed in a later service update."

Here's the link:
https://support.microsoft.com/en-us/kb/3068708

Of course, each of us is free to go ahead and uninstall the two updates discussed in earlier posts if we don't want to wait for the issue to be fixed

LaurieD227 · 28 Jun 2015

One other interesting thing - I have an older Win7 Pro machine that has the KB3068708 and KB3022345 updates installed, and those SFC /SCANNOW results come back with no errors.

Hmmm .....

GokAy · 28 Jun 2015

Did you run sfcfix earlier for KB3022345 on that Win7 Pro machine? I used to have KB3022345 (later uninstalled but fixed with SFCFix), and now have KB3068708, no corruptions also.

Layback Bear · 28 Jun 2015

I remove both of those KB's and when they came back in Windows 7 Updated I hid them.
Then ran sfc /scannow a couple of times with reboots between and problem was solved.

Done it on my Pro and Home Premium systems.

KB3022345
KB3068708,

LaurieD227 · 28 Jun 2015

Nope, I didn't run SFC for the KB3022345 install as far as I recall. I wasn't having any issues on that machine (an old Dell D630) back in May when I installed KB3022345. This past weekend, I installed KB3068708 along with some other updates, and had no issues.

After I found the issue on my ProStar Win7 Pro, I got curious, so I checked the D630 - yep, both updates were there - and ran SFC /SCANNOW - nope, no false corruption findings, just a clean bill of health.

If I had to guess, I'd think it may be tied to a combination of other characteristics of the two machines - maybe software, maybe hardware - where something about the newer set up triggers the false corrupt reading. The D630 is a 32-bit machine and the other one is 64-bit but I have no idea if that contributes to the fact that one has the problem and the other does not.

Regardless, I have uninstalled both KB3022345 and KB3068708 from my ProStar, and its SFC results are now clean. I may choose to experiment with re-installing one or both to see if I once again get the error. If I do that, I'll probably try your technique of running sfc after installing KB3022345 to see if that shows clean before installing KB3068708.

If I do run these experiments, I'll let you know what happens.

LaurieD227 · 28 Jun 2015

I found a little bit more information on this whole situation.

--KB3022345 was released in multiple versions, so perhaps my D630 has a version that doesn't have the problem.
--KB3022345 is no longer offered; instead, people are referred to KB3068708
--There's no clear explanation of what either of these updates do, but other folks seem to think they pertain to the upcoming Windows 10 release

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

Microsoft confirms patch KB 3022345 breaks SFC /scannow | InfoWorld

The Tech Cookbook – Windows 7 update (KB3022345) causing corrupt files

Based on my additional reading, I think I'm going to just hide the KB3068708 Update for now instead of installing it. I want to wait and see if Microsoft issues a fix for it that works, and I'd really like to know what it does.