Windows 8.1 update KB3022345 causing SFC integrity violations

[windows8mypc]

It's official, many users are reporting problems with this OPTIONAL Microsoft update. ( KB3022345) The lucky ones are only having problems with it failing to install, however the unlucky ones have no problem getting it to install and then causing SFC file integrity violations. I have been able to repair this as verified by a clean bill of health from SFC, however it comes back after some period of time. I'm not sure what causes it to re-appear (Possibly a computer reboot?) but the final solution is to uninstall the update and Do NOT re-install it.

Below are the two files that consistently become corrupt;

CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\utc.app.json
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\telemetry.ASM-WindowsDefault.json

If you are showing integrity violations related to the above mentioned files I recommend uninstalling the optional Windows update KB3022345.

Regards.

 

[Go The Power]

I have helped about ~15 people with this update over the past few days.

It appears to be happening with x86 and x64 machine. From a x86 machine the following files will show as corrupt:

Hashes for file member \SystemRoot\WinSxS\[COLOR="#FF0000"]x86_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_34c0e5ad22631daa[/COLOR]\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]”telemetry.ASM-WindowsDefault.json” :
Found: {l:32 b:Qz+6AyEHylwXB/Zp4JJIIOTViV567gZDYlfmxHLVQ4w=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}

Hashes for file member \SystemRoot\WinSxS\[COLOR="#FF0000"]x86_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_34c0e5ad22631daa[/COLOR]\utc.app.json do not match actual file [l:24{12}]”utc.app.json” :
Found: {l:32 b:4t5Yv0Q+Af1zoZNsJ8sl2qR+YiAT1ol6TJlyCeYAXlU=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}

But these are the exact same files in the x64 update.

 

[kpost]

Just found out MS know about these corruptions and says on https://support.microsoft.com/en-us/kb/3022345 :

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.

Wasted I don't know how many hours trying to figure this thing out, but as a result I did run into this forum, so not all was wasted.