Windows 7 update (KB3022345) causing corrupt files

Yes. I should have done that in the first place. It's about time MS got their fingers out and fixed it.

Good grief! Same here, the sfc /scannow corruption has returned, for no reason that I can see other than there WERE a passel of updates I allowed since running SFCFix.

The irony of this crummy update is that it's about the Diagnostic Tracking Service (which AFAICT I do not use)! Way to go Microsoft!



p.s. I too uninstalled the update and another sfc shows as good. Dunno what about the interim updates un-did the SFCFix!?

According to MS, it is NOT corrupt files but an error in reporting logic. When the two files are updated, they get reported as corrupt even though they are not. If the Diagnostic Tracking Service runs after you apply some mystical fix, the false error will return. Don't do anything and wait for the update or remove the KB. Those are you two choices. Stop running "fixes" for the wrong problem.

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.

　

Interesting -so MS screwed the pooch again, but can't be assed to do anything about it!

The point is that an SFC is not an 'Advanced user tool' it's a basic tool which is recommended in many KB's for basic users - and it should run clean at all times.

When it doesn't run clean is when it becomes an advanced user's tool - and when it lies, then it's no user's tool!

I think SFC is doing what it's supposed to do. The two JSON files are considered system files that are being updated and not handled correctly in implementation. I'm not knowledgeable on exactly how SFC works but it's probably a Winsxs situation similar to drivers. (Except the two JSON files are scripts.) When MS works out how to generate the scripts on the fly, maintain security then get them accepted by SFC, they'll issue a patch.

I wouldn't make a big deal about it. Personally, I think it was a bad choice to use JSON files in this method. But, who am I.

Added:
Hey, it took MS several months to get IE-11 working.

carwiz said:

Hey, it took MS several months to get IE-11 working.

True but IE11 is a complex program this is just lazy testing.

kado897 said:

carwiz said:

Hey, it took MS several months to get IE-11 working.

True but IE11 is a complex program this is just lazy testing.

And Windows isn't complex?