[SOLVED] SFCFix log warnings about utc.app.json

[Jed]

After installing MS patch Tuesday Winupdates today I ran SFC to check for any corruptions.
I do not have KB2952664 or KB3035583 installed.

Corruptions appear to be related to utc.app.json so I ran SFCFix.exe.

After rebooting my laptop the utc.app.json corruptions reappeared despite using SFCFix.

SFC & SFCFix logs attached.

How can I fix the utc.app.json corruptions permanently as it appears from the SFCFix log warning that there is an issue?

Also is there an easy way of clearing the (growing) cbs.log?

 

[Jed]

Any chance of a SFCFix script to fix the utc.app.json corruptions permanently?

Also is there an easy way of clearing my (growing) cbs.log?

 

[BrianDrab]

Hi and welcome to Sysnative. The errors that you have are a known issue and Microsoft is working on a fix. They don't cause any Windows Update issues so you can safely ignore them. More info on this is below. Also, Windows manages the CBS logs. Periodically they get archived off automatically.

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

Originally Posted by Microsoft
This update enables the Diagnostics Tracking Service in Windows 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1), and Windows Server 2008 R2 SP1. This tracking service collects data about functional issues in Windows.

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 corruption on a device that is running this update, and this issue will be fixed in a later service update.

 

[Jed]

Thanks Brian. I appreciate that these corruptions do not cause any Windows Update issues. I do not have any Win update issues.

Can you please explain the Warning message in the SFXFixJED log (utc.app.json was not backed up as that would replace the current backup) & if it can be permanently fixed with a script.
Reason I ask is that my other Toshiba laptop with an identical software environment does not have recurring (after a reboot) utc.app.json corruptions (after running SFCFix).

Also is there any way to force the archiving of the cbs.log?
What is the periodicity criterion for "Periodically they get archived off automatically"?
My cbs.log is already too large for me to regularly review.
Getting rid of the utc.app.json corruptions will reduce the need to look at cbs.log after running sfc /scannow & getting corruption warnings.

FYI I run sfc regularly as part of this complex issue https://www.sysnative.com/forums/wi...em-restore-points-manually-automatically.html

 

[BrianDrab]

Can you please explain the Warning message in the SFXFixJED log (utc.app.json was not backed up as that would replace the current backup) & if it can be permanently fixed with a script.
Reason I ask is that my other Toshiba laptop with an identical software environment does not have recurring (after a reboot) utc.app.json corruptions (after running SFCFix).

SFCFix always makes a backup of items it touches. You will see a folder on your hard drive C:\SFCFix with all the logs, script list & backups. The message means that there is already a file in the backup location and that it won't overwrite it. It's a safeguard. So the message can safely be ignored. This folder can be removed once you are done using the tool. There is currently no way to permanently get rid of the errors until Microsoft fixes. You may be able to uninstall the update and keep it hidden though.

Also is there any way to force the archiving of the cbs.log?
What is the periodicity criterion for "Periodically they get archived off automatically"?
My cbs.log is already too large for me to regularly review.
Getting rid of the utc.app.json corruptions will reduce the need to look at cbs.log after running sfc /scannow & getting corruption warnings.

I do not know of any way to change the behavior of the CBS persisting. Windows should automatically manage this. Once the log gets to be about 100 MB, windows should compress the file into a .cab file and then start a new one.

 

[Jed]

Thanks Brian for this info.