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:
