CBS.log file: Getting a usable txt file and interpreting the file

[gogreen]

First, what does "CBS" mean in cbs.log?

Does the cbs.log file show only errors? I create a cbs.log file a lot, so if there are errors, I'd like to correct them. However, my computer seems to be working just fine. sfc /scannow shows everything is OK.

I've tried findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > c:\test.txt to create a text file so that I can read the cbs.log file, but this command creates the test.txt file with 0 bytes, and I know the cbs.log file is at least 1,000 bytes.

So, 1) how do I get a workable copy of my cbs.log file, and 2) how does one interpret its meaning?

Thanks.

 

[Ztruker]

You don't have any [SR] flagged entries in the cbs.log file.

To look at it, from a Command Prompt, enter:

notepad %windir%\logs\cbs\cbs.log

If you use Ctrl+F you can search for things, like [SR].

I believe System File Checker (SFC) adds the [SR] entries. If you haven't run it then they won't be there.

 

[gogreen]

Thank you , Ztruker. Now I have the txt file, but it's a jumble to me. Can you point me to a tutorial on how to interpret the file entries? Or is it best just to Google some and see what I get?

Thanks again.

 

[Ztruker]

Google interpret cbs.log or analyze cbs.log.

First hit I got was this: How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program generates in Windows Vista