[SOLVED] SFC CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client errors

Jeffs

New member
Joined
Jul 24, 2015
Posts
2
I was having some slow startup issues and decided to look into the logs. After finding a few errors I tried SFC /scannow and it returned errors. In searching I found this site and thus, I am hoping someone here can help me.

I have already tried the following:
SFC /scannow
Checkdsk (found errors but fixed them on my boot SSD).
I attached the CBS.zip file as recomended but had to remove one log file (CbsPersist_2015724014343.log from it as it was too long to include. If needed I can attach that separately.
SFCFix (which returned the following text)

One odd point. The files that appear corrupt relate to AMD64 but I am, in fact, using an Intel processor. Not sure if that matters/helps.

Thanks,
Jeff

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-07-24 09:48:53.325
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.




AutoAnalysis::
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\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-07-24 10:22:49.987
----------------------EOF-----------------------
 
Hi Jeffs :)

These files (utc.app.json and telemetry.ASM-WindowsDefault.json) are falsely reported as corrupt by SFC. Microsoft is aware of this situation and they said that this issue will be fixed in a later update. These files aren't corrupt and they won't affect anything on your system. You can leave it be without any consequences. For more information, see the Microsoft Article below.

https://support.microsoft.com/en-us/kb/3022345

This update contains the following files 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 actual corruption on a device running this update, and a later service update will resolve this issue.

Therefore, these files aren't responsible for your current issues.
 
No problem Jeffs, you're welcome :)
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top