[SOLVED] CBS.LOG Corrupted

[abcas2]

• I received an error when using SFC /Scannow

Error message:
​

Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log %WinDir%\Logs\CBS\CBS.log.

​

• I tried using Dism /Online /Cleanup-Image /RestoreHealth but there is an error (see attachment below)

​

• Then I followed this:

• Boot your PC from the installation disk
• On the next screen, hold down SHIFT key and press F10, a command prompt should be displayed.
• Type: diskpart <ENTER> then type list volume <ENTER> and take a note of the drive letter of your System Reserved & Windows OS. Type: Exit
• Type: sfc /scannow /offbootdir=c:\ /offwindir=d:\windows where c: is the system reserved d: is your Windows OS drive

but it gives an error of "Windows Resource Protection could not start the repair services"

​

• I run Run SFCFix

Result:​

[INDENT=2]SFCFix version 2.4.5.0 by niemiro.

[/INDENT]
[INDENT=2]Start time: 2015-06-19 17:23:16.836
[/INDENT]
[INDENT=2]Microsoft Windows 8.1 Update 3 - amd64
[/INDENT]
[INDENT=2]Not using a script file.
[/INDENT]

[INDENT=2]AutoAnalysis::
[/INDENT]
[INDENT=2]SUMMARY: No corruptions were detected.
[/INDENT]
[INDENT=2]AutoAnalysis:: directive completed successfully.
[/INDENT]

[INDENT=2]Successfully processed all directives.
[/INDENT]
[INDENT=2]SFCFix version 2.4.5.0 by niemiro has completed.
[/INDENT]
[INDENT=2]Currently storing 0 datablocks.
[/INDENT]
[INDENT=2]Finish time: 2015-06-19 17:23:33.761
[/INDENT]
[INDENT=2]----------------------EOF-----------------------
[/INDENT]

• CBS.txt attachment below

View attachment cbs.txt
​

 

[BrianDrab]

Hi and welcome to Sysnative. The errors that you have are a known issue that Microsoft is working on. It doesn't impact the operation of your machine. They can be safely ignored. More info on this follow.

2015-06-19 17:30:11, Info                  CSI    0000000b Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17807_none_910ac2c6daa01c43\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
  Found: {l:32 b:hxHfXj427JxbVLpmOJKBMMwJ3nfvwV57qrOPwblWU6s=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-06-19 17:30:11, Info                  CSI    0000000c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17807_none_910ac2c6daa01c43\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
  Found: {l:32 b:rX0CB3J2u+8b88W40OtkWxE6DLvV/cFEMvqhqqbQIlI=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}

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.

 

[abcas2]

Hello Brian. Thanks for the reply, I really appreciate it.

I see, I hope they will be able to fix it soon.

I got another question but I am not sure if it still belong to the right thread.
Last week, I contact Microsoft support to help me with a problem I had with my machine. It seems that the automatic maintenance is bugged since it froze my system everytime it automatically start or I manually start it. During the session, she checked if I still have remaining updates for Windows and run the elevated sfc /scannow, which started this thread. Sadly, They require me to purchase the premium support before we could continue, which I declined.

My steps in trying to fix the issue:

1. The first time it happened, I decided to reformat my computer hoping it will fix the issue. After installing everything.. it worked but after a few months it came back and I don't know what might have cause it. I have a hunch that it might be a bug from one of the Windows update since there was no major programs I installed.

2. I deleted the automatic maintenance in the Schedule tasked to prevent it from doing it in the first place.

Recently I experience random freeze, which I never had before... not sure if it is related.

Thanks for all the help. :)

 

[BrianDrab]

Since I work Windows Update issues and am not an expert on hardware/software issues I suggest that you post a thread in our Windows 8 forum. They are much more knowledgeable when it comes to these types of things.