2 corrupted files SFCFix couldn't fix

[TomWin8]

sfc /scannow is reporting two corrupt files that it cannot fix, nor can be fixed by:

Dism /Online /Cleanup-Image /RestoreHealth

I've generated a fresh CBS.LOG by running sfc /scannow and then running the current version of SFCFix; it generates the following SFCFix.TXT file:

SFCFix version 120.105.65535.0 by niemiro.
Start time: 2015-08-14 15:36:48.774
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 120.105.65535.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2015-08-14 15:43:28.005
----------------------EOF-----------------------

Is there a fix for this? (I'm getting the same results on my other computers; this one is a Toshiba, the others are a Lenovo and an Acer, each with Windows 8.1 Pro)

Many thanks,
Tom

 

[Aura]

Hi TomWin8 :)

My name is Aura and I'll be assisting you with your issue. Follow the instructions below please.

System File Checker (SFC)
Follow the instructions below to run a SFC scan on your system and to provide the CBS log in your next reply;

• On Windows Vista & 7, click on the Windows Start Menu, then enter cmd in the search box, right-click on the cmd icon and select
  
  Run as Administrator
• On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin);
• On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
• Enter the command below and press on Enter;
  

  sfc /scannow

  Note: There's a space between "sfc" and "/scannow";
• Once the scan is complete, enter the command below and press on Enter
  

  copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

• A file called cbs.txt will have appeared on your Desktop. Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;

Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the SFC scan is completed, it won't contains the information from the scan anymore. So archive it and upload it as soon as you can.

SFCFix - Fix Time

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to download and execute a SFCFix fix, and provide the log.

• Download SFCFix and move the executable on your Desktop;
• Download the attached SFCFix.zip and move the archive to your Desktop;
  Note: Make sure that the file is named SFCFix.zip, do not rename it.
• Save any work you have open, and close every programs;
• Drag the SFCFix.zip archive file over the SFCFix.exe executable and release it;
  
  
• SFCFix will launch, let it complete;
• Once done, a file will appear on your Desktop, called SFCFix.txt;
• Open the file, then copy and paste its content in your next reply;

SFCFix.zip

Your next reply should contain:

Download link to the cbs.txt file;
Copy/pasted SFCFix log;

 

[TomWin8]

Many thanks! I've followed the instructions; here is the cbs.txt file on my DropBox:

https://www.dropbox.com/s/uk9ucs9a7lddtlz/cbs.txt?dl=0

And here is the text of the SFCFix log:
-------------------------------------------

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-08-15 09:51:09.677
Microsoft Windows 8.1 Update 3 - amd64
Using .zip script file at C:\Users\Tom\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.asm-windowsdefault.json
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json


Successfully copied file C:\Users\Tom\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.asm-windowsdefault.json to C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.asm-windowsdefault.json.
Successfully copied file C:\Users\Tom\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json to C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json.


Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.asm-windowsdefault.json
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\telemetry.asm-windowsdefault.json
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17842_none_90da81a4dac50d54\utc.app.json
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2015-08-15 09:51:10.067
Script hash: 5zeE71QxanwyheQYWFfDoaFFqbDWmGU+AU9nkQ8r3lA=
----------------------EOF-----------------------

 

[Aura]

Alright, we'll run SFC again to see if the changes were accepted.

System File Checker (SFC)
Follow the instructions below to run a SFC scan on your system and to provide the CBS log in your next reply;

• On Windows Vista & 7, click on the Windows Start Menu, then enter cmd in the search box, right-click on the cmd icon and select
  
  Run as Administrator
• On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin);
• On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
• Enter the command below and press on Enter;
  

  sfc /scannow

  Note: There's a space between "sfc" and "/scannow";
• Once the scan is complete, enter the command below and press on Enter
  

  copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

• A file called cbs.txt will have appeared on your Desktop. Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;

Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the SFC scan is completed, it won't contains the information from the scan anymore. So archive it and upload it as soon as you can.

 

[TomWin8]

Sadly, I don't think so... at the end of the repeated "sfc /scannow" routine it reported that 2 items could still not be fixed.

Here, however, is a DropBox link to the cbs.txt file:

https://www.dropbox.com/s/uk9ucs9a7lddtlz/cbs.txt?dl=0

With luck, it will indicate what isn't working (or perhaps it did work).

Many thanks,
Tom
P.S. You'll see it appended the results from the second scan to the first, so both are in there, with the earlier one first.

 

[Aura]

This is normal, don't worry. We still have one fix to apply.

SFCFix - Fix Time

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to download and execute a SFCFix fix, and provide the log.

• Download SFCFix and move the executable on your Desktop;
• Download the attached SFCFixScript.txt and move the file to your Desktop;
  Note: Make sure that the file is named SFCFixScript.txt, do not rename it.
• Save any work you have open, and close every programs;
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it;
• SFCFix will launch, let it complete;
• Once done, a file will appear on your Desktop, called SFCFix.txt;
• Open the file, then copy and paste its content in your next reply;

SFCFixScript.txt

 

[TomWin8]

Fantastic! That worked! I have two other machines configured identically (both Windows 8.1 update 3, both with all current updates, etc.) I had run "sfc /scannow" and "SFCFix" on them, and the resulting SFCFix files were identical, with the relevant text as here:

AutoAnalysis::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.

I'd like to resolve this on the other two machines. Is the 2nd script you sent (SFCFixScript.txt) the only script that needs to be used on the other machines, or would I have to use the ZIP file (SFCFix.zip) *first* and then run the 2nd script?

Many thanks,
Tom

 

[Aura]

First, you use the SFCFix.zip I provided. Once done, you launch a SFC and if it says there's still files that cannot be fixed, you use the SFCFixScript.txt and then launch SFC one last time. Simple as that :)

 

[TomWin8]

Sadly, it didn't work. I just finished processing SFCFix with the ZIP file and the TXT file you sent me on one of the other computers (a Toshiba, the first one where we had success was a Lenovo), and ran "sfc /scannow" after each processing to see if there were still problems. After processing the ZIP file, problems were reported by "sfc /scannow", and after processing the TXT file, problems were still reported by "sfc /scannow".

I've uploaded a new cbs.txt file showing the results of the new scans here:

https://www.dropbox.com/s/uk9ucs9a7lddtlz/cbs.txt?dl=0

Please let me know what I should do next.

Many thanks,
Tom

 

[Aura]

You can leave these be. They are in the "Temp" folder of WinSxS, we cannot replace them. They'll eventually be deleted. However, they do not cause any harm to the system. In the first place, SFC falsely reports utc.app.json and telemetry.ASM-WindowsDefault.json as corrupt. Microsoft is aware of this issue and said that they'll fix it in a later update.

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

This update contains the following two manifests 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 that is running this update, and this issue will be fixed in a later service update.