Windows 7 update (KB3022345) causing corrupt files

[NoelDP]

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..

 

[TedPacheco]

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.

 

[maxseven]

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)????

 

[Sky Ranch]

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.

 

[TedPacheco]

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.

 

[Seffrid]

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

 

[Seffrid]

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

 

[Sky Ranch]

Well, only one optional (KB3054476) today - May 2015 update for stream.sys driver-based applications in Windows 7 or Windows Server 2008 R2.

 

[ownedandout]

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.

 

[kado897]

Me too.

 

[Sky Ranch]

Yes, the misbehaving files have returned and the only way around this was to uninstall KB3022345.

 

[kado897]

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

 

[maxseven]

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!?

 

[Gacrux]

I have reported in another thread about those hideous inexplicable massive file system corruption after running WU days ago, now I know what was happening. At least for me things came back to normal.

 

[johnlkerry]

KB3022345 sfc file corruption report.
Google search indicates the problem is the KB3022345 update itself, now at version 6 or more and still not working correctly.
The sfc /scannow corrupted files report is an error which results from the bad KB update... Simply remove the KB and wait for MicroSoft to "get it right".

 

[carwiz]

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.

　

 

[NoelDP]

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!

 

[carwiz]

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.

 

[kado897]

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

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

 

[carwiz]

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?