BrianDrab
Emeritus
Believe it or not, you are fixed. The last remaining errors can be ignored. Microsoft is aware of them and will be fixing them but they don't impact the functionality of your machine or Windows Updates. Info on that is below.
https://support.microsoft.com/en-us/kb/3022345
Code:
2015-05-23 17:38:17, Info CSI 00000333 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
Found: {l:32 b:Dk6fUP1SnCTleFraPRQVF4X7qKh8b/NoJA44WgQ6+JE=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-05-23 17:38:17, Info CSI 00000334 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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
2015-05-23 17:38:17, Info CSI 00000335 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
Found: {l:32 b:a6gI0J5yvfGTOqcpiYLkzGXusnwKS2mJUXOwOYSGFFg=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
https://support.microsoft.com/en-us/kb/3022345
Originally Posted by Microsoft
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.