utc.app.json and telemetry.ASM-WindowsDefault.json files

[gmyner]

tried this fix from a posting in tech cookbook
1.Download SFCFix.exe (by niemiro) and save this to your Desktop.
2.Download SFCFix.zip from one of the below links, and save this to your
Desktop. Ensure that this file is named SFCFix.zip – do not rename it.
3.If you have a x64 machine download this version: SFCFix (x64 fix)
4.If you have a x86 machine download this version: SFCFix (x86 fix)
5.Save any open documents and close all open windows.
6.On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
7.Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
8.SFCFix will now process the script.
9.Upon completion, a file should be created on your Desktop: SFCFix.txt.
10.The results should return as Fixed:
SFC /SCANNOW
1.Right click on the button
2.Click on Command prompt (Admin) => Press Yes on the prompt
3.Inside the Command Prompt windows copy and paste the following command
SFC /SCANNOW
It does not fix the issue and I was directed to this forum. I still have have two corrupt files
utc.app.json and telemetry.ASM-WindowsDefault.json
This is a windows 8.1 pro laptop, it boots fine but the reboot to repair
hard drive corruption won't go away. The main issue that concerns me it
that it won't perform a system restore becaue of the corruption on my
drive c: My drive c: is a curcial 240gm ssd msata. attached is the CBS logfile. thanks

 

[DuchessOfKvetch]

Same here, it would appear that the fixes are customized for situations just slightly different. I'm also on an 8.1 laptop, so maybe the original fix was for Win 8.0?

I tried to manually change the folder name inside SFXFix.zip, but that just confused SFC more (I get decompression errors inside CBS.log instead now).

The results of just running SFCFix by itself gives this output:

---------------------------------------------------------------------------------------------------------------------------------------------------------------
SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-06-15 00:01:39.134
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.
---------------------------------------------------------------------------------------------------------------------------------------------------------------

Looks like I have exactly the same winsxs folder as the above guy, too, after looking at his cbs.log.... the one that ends in ".17842_none_90da81a4dac50d54" instead of ".17747_none_90df8130dac08ee0".

 

[DuchessOfKvetch]

Eh, there are lots of threads here about these damned corrupt telemetry files.

I think that the fix floating around for a while was before Microsoft finally made a statement about them, saying they were "False positives" essentially, and to wait for a fix.

See: https://www.sysnative.com/forums/windows-update/14656-cbs-corrupt-files-log.html

I suspect that the admins here are tired of seeing all the reports of the same series of bugged files, so for now I am letting it be, I think... I just won't trust Windows 10 to be that clean either for a month.

Of course I have other issues with Windows Update itself not working, also due to those damned Windows 10 updates I think, but that is another issue.

 

[gmyner]

Waiting if fine except if you need to do a system restore, it won't let you restore a corrupt drive. Thanks for the input.

 

[Deaf Dave]

Waiting if fine except if you need to do a system restore, it won't let you restore a corrupt drive. Thanks for the input.

Hi,
I am a new member to Sysnative so please bear with me. I am also not that tech savy. Having said that, what brought me here is that these two and their corresponding corrupted MS updates (KB3022345 and KB3068708 may not allow a clone of your hard drive either. I always clone my hard drive before MS patch Tuesdays. last month I did my clone on 5-11-15 successfully.The next day I did the patches. When I tried to do my clone this month, the clone failed due to the VSS being unable to read a file. Three times the clone failed for the same reason. I now suspect these MS corrupt updates to have been the cause. I'm trying to solve these problems and another just cropped up, my primary PC will not boot because the drive is not recognized. So, I'm using my backup PC to try to solve all these problems. and, I can't afford to wait.. Thank you for taking the time to read my reply. Dave

 

[Ufuomanefe Akortha]

You can try to fix the corruption by performing the following steps:
1. Open an elevated command prompt
2. Type "cd /D %windir%" (without the quotation marks) at the prompt
3. Then type this command "icacls * /T /Q /C /RESET" (once again without the quotation marks) at the prompt. You will see a lot of "access denied" messages while this command executes - that is perfectly normal
4. Wait for the command to be executed completely, then run the sfc /scannow and/or the SFCFix tool again. There should be no more corruptions found, and if there are, run "chkdsk /r" (once again without the quotation marks) at an elevated command prompt. You will be presented with something like this message:

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.


C:\Windows\system32>chkdsk /r
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)


Hit the "y" key and restart windows and wait for chkdsk to attempt repairs and then when windows boots run sfc /scannow again... you should be rid of the corruption.

Hope this helps.

Ps. An elevated command prompt is simply running command prompt as an administrator.