Here's the errors from the SFC log...
Code:
Line 4640: 2015-05-26 18:21:06, Info CSI 00000353 [SR] Repairing 1 components
Line 4641: 2015-05-26 18:21:06, Info CSI 00000354 [SR] Beginning Verify and Repair transaction
Line 4644: 2015-05-26 18:21:06, Info CSI 00000356 [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
Line 4647: 2015-05-26 18:21:06, Info CSI 00000358 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.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
These are due to the KB3022345 update - and the latest advice from MS is to ignore them, as they are the result of a logic error rather than a real problem. (MS forgot to add the flags that tell SFC to ignore the files!)
You can either ignore them, or uninstall the update and hide it - when MS fix the problem (as promised!) then the new version of the update will appear.
How is the system behaving now?