[SOLVED] About "Automatic SFC Corruption repair (SFCFix.exe) " and KB3022345

[Acrobaze]

Hi,

I had some problems with the installation of this update : KB3022345.

Well known.

So, I did the solution posted here :
The Tech Cookbook – Windows 8 update (KB3022345) causing corrupt files

Immediately, a "sfc/ scannow" gave me a perfect result. And the same thing with :
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /RestorehealthDISM.exe /Online /Cleanup-image /startcomponentcleanup

So, I thougt that the problem was fixed.

A couple of days later, I re-did a "sfc/ scannow" and the problem went back. Exactly the same as at the beginning. :

000004be [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17807, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

So, I think (but perhaps I mistake) that your fix correct the files in Windows (WinSxS) but that the update reinstall its own corrupted files when it runs.

I read many messages saying that after an immediatly done sfc/ sannow, the problem seemed solved. But noone posted a couple of days later to confirm that everything was ok.

And it's not. The same problem comes back.

At this point : to make sure, I uninstalled this KB3022345. And after many use and reboots, made "sfc /scannow". The report is always clean, no problem or corrupted files.

I do'nt think that my computer is the only one in the world. So, it is important that Microsoft knows that this update is not well done.

Regards, and thank you in advance for your answers, even if my English is not perfect. :smile9:

 

[Acrobaze]

Here are the logs.

 

[BrianDrab]

Hi Acrobaze - Welcome to Sysnative.

We've been collecting information on this update to provide to Microsoft to get a resolution. Would you mind zipping and posting your C:\Windows\WindowsUpdate.log

Thank you.

 

[Acrobaze]

Hi BrianDrab,

Now, there is not any problem.

I followed these steps :
1- I uninstalled KB3045999 via Windows Update with NO REBOOT.
2 -I installed KB3022345 via Windows Update (as it was hidden in Windows update and can be thus reinstalled.).
3- Rebbot.
4- Then re-installed KB3045999 and reboot.
5 -fc /scannow said "errors" and the CBS log is always (still) in the same errors "telemetry" et .json".
6- I applied then
The Tech Cookbook – Windows 8 update (KB3022345) causing corrupt files
7-sfc /scannow then clean and Dism /Online /Cleanup-Image /CheckHealth clean too.

To make sure, I rebooted and re-did SFC and DISM. Allways clean.

Since the beginning of this problem, many updates installed (Windows, Office Pro and etc) without any problem.

So, as I see that you are very busy and that at this moment, the problem looks as solved. I'd want only thank you for the expertise.

Regards

NB : But Microsoft proposes always this day an update with defects.

 

[BrianDrab]

Thanks for the update. Take care.

 

[Acrobaze]

Hi,

The same error came back. :huh:


The windowsupdate.log file is too heavy to be uploaded.

 

[Acrobaze]

I unistalled this famous KB3022345 and everything came back clean.

What a mess !

 

[BrianDrab]

As long as the corruption isn't affecting you from getting Windows Updates or causing any other undesirable issues we may just have to live with it until Microsoft resolves. You can keep it uninstalled or install it and just deal with the corruption.

 

[Acrobaze]

Yes, I saw that Microsoft proposed an explanation here :

https://support.microsoft.com/en-us/kb/3022345/fr

Saying :

Lorsqu'un utilisateur expérimenté exécute l'outil Vérificateur des fichiers système (sfc.exe), les fichiers sont involontairement signalés comme étant endommagé. Il n'y a aucun impact ou la corruption sur un périphérique qui exécute cette mise à jour, et ce problème sera corrigé dans une mise à jour ultérieure du service.


Translatable in many languages, if needed.

In fact, the problem comes from : Diagnostics Tracking Service "DiagTrack"


This service, when running re-installs the "corrupted files" (in fact, not corrupted, just a hash question).