The only significant error in the SFC is this...
Code:
Line 3580: 2015-05-28 17:42:11, Info CSI 00000336 [SR] Repairing 1 components
Line 3581: 2015-05-28 17:42:11, Info CSI 00000337 [SR] Beginning Verify and Repair transaction
Line 3584: 2015-05-28 17:42:11, Info CSI 00000339 [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 3587: 2015-05-28 17:42:11, Info CSI 0000033b [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
This is the result of the KB3022345 problem - which MS deny being a problem
MS have updated their advice on the SFC issue.
It seems that this is an error in the 'logic' rather than an actual problem.
There is no point in attempting to correct the apparent errors, since they will reappear as soon as another diagnostic is run (possibly without user intervention!).
Therefore, as far as these errors are concerned the current options are
- ignore the errors, and wait for MS to release the promised update to correct the SFC detections
- uninstall KB3022345 and hide the offered update until its either updated or replaced.
Take your pick!
There are no other errors in the SFC scan that need attention.
CheckSUR is clear
As to your problem updating...
Open an Elevated Command Prompt, and run the following commands
Code:
REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
Code:
REG DELETE HKLM\COMPONENTS /V PendingRequired
.
then reboot, and try Windows Update again.