[SOLVED] SFCFix

[Eli]

Ola, estou precisando de ajuda com esse relátorio do SFCFix
Agradeço desde já


SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-07-27 10:07:58.228
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 3 datablocks.
Finish time: 2015-07-27 10:27:21.222
----------------------EOF-----------------------

Muito obrigado

 

[Aura]

Hi Eli :)

This is an English-speaking forum, so if you want to receive assistance for your issue, you'll have to post in English, alright? :) This being said, the two files reported as corrupted are false positives. SFC reports them as corrupted when they aren't. Microsoft is aware of the issue and said that they'll address that issue in a future update. For more information, read the 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.