Solved Windows 7 update (KB3022345) causing corrupt files with a twist

[yaddidimean]

I have gone through every process of removal to fix this to no avail

this is the result of SFCFix.txt

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-06-20 18:35:20.267
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.




AutoAnalysis::
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\utc.app.json
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18869_none_fde7d5f71db043ad\telemetry.ASM-WindowsDefault.json


SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 2
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-06-20 18:56:56.170
----------------------EOF-----------------------



I have uninstalled the windows update (KB3022345) which also didn't fix the issue. I'm not seeing any issues affecting performance to my knowledge, but would like to not have corrupted files lol. Thanks for time.

A little backround about the system, it was previously a HP prebuilt machine hpe-180t. It was originally an intel processor/chipset, and the new stuff is AMD. I updated everything but the hard drive and did not reformat it. Updated all drivers to work for current rig, so I'm wondering if it was an update optimized for my previous build and when I switched the hardware it caused problems. I have no idea honestly, it just seemed like such a quick fix for everyone else and I cannot find a fix for the life of me after hours of searching. Usually I can fix the problems through my own research, but this is the first problem I could not and warranted a forum post. Thanks again for your time.

 

[NoelDP]

Pleasefollow the WindowsUpdate Posting Instructions and postthe requested data



If thefile is too large (8MB compressed), remove the older CBSPersist cab files untilthe final file is below the limit - you can always post them separately afterzipping them. (the forum doesn't allow the upload of bare CAB files, for anumber of reasons)



Pleasealso post the C:\Windows\windowsudpate.log file

 

[yaddidimean]

Here is the cbs.log

 

[NoelDP]

That file appears to be corrupt?
please try recreating it, and post the new version.

 

[yaddidimean]

That file appears to be corrupt?
please try recreating it, and post the new version.

It's actually a .rar i just tried changing it, guess it didnt work, heres a zip

 

[NoelDP]

The only error in the SFC is this...

 Line 100018: 2015-06-26 01:31:56, Info                  CSI    000006b3 [SR] Repairing 1 components
 Line 100019: 2015-06-26 01:31:56, Info                  CSI    000006b4 [SR] Beginning Verify and Repair transaction
 Line 100022: 2015-06-26 01:31:56, Info                  CSI    000006b6 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, 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 100025: 2015-06-26 01:31:56, Info                  CSI    000006b8 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, 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

According to MS, this can be ignored.
If you want to get rid of it and wait until MS fix the problem (eventually) - uninstall KB3068708 then do a check for updates, and Hide the update when it re-appears. This will prevent it installing until MS either revise it, or produce a new version.

 

[yaddidimean]

Thanks +rep

 

[NoelDP]

You're welcome - and thanks for the rep!