The data provided by the CBS.log is massive - 5.4MB of text is a years worth of reading. Has anybody figured out a way to quickly identify the corrupted files ?? I have read this Microsoft page, but that does not really help.
Here's the most common text to search for (from the KB article that you referenced):
Repairing corrupted file
Cannot repair member file
Repaired file
Personally, when I search, I search for the term "repair" (without the quotes).
Also, I search from the bottom up, checking dates as I go (so I only have to review the latest sessions).
Thanks for the answer. I am not sure how you search for those terms. I pasted the Notepad content into a Word file and tried to search the text from there. But the terms you mention did not yield any results.
Example:
Hello Wolfgang,
You might be able to use what I did in OPTION TWO of the SFC tutorial below to search for specific items (within the quotes in the code) in the CBS.log, and have it placed neatly in a separate file.
SFC /SCANNOW Command - System File Checker
Hope this helps,
Shawn
Thanks Shawn. But my problem is not to open the CBS.log. It is just too much data to sift thru. The OPTION TWO did not really do anything for me. It says:
Oh well, it was worth a try.
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt
You might see if any of the other FINDSTR command switches may allow you to sort through the CBS.log easier.
Last edited by Brink; 03 Jun 2012 at 13:22.
Hmm, success. With that part of the command ( findstr /c:"[SR]" %windir%\logs\cbs\cbs.log ) it shows me all the files it repaired and the ones it could not repair. And that is a manageable amount of data. I pasted into a Word file and then it is easy to read. Thanks again Shawn.
PS: Amazing though how many files (95 in total) it had to repair - on a system that is only 2 months old. Since there were many gadgets, I suspect that my Vista sidebar is going to be on the blink next time I reboot. But that is easy to fix.
So now I just made a little generic summary for those that want to just see the repaired and non-repaired files in the CBS.log - just in case somebody is looking for the solution in this thread:
With the command findstr /c:"[SR]" %windir%\logs\cbs\cbs.log (in elevated Command Prompt) it shows all the files it repaired and the ones it could not repair. And that is a manageable amount of data. Paste that into a Notepad, Word or Wordpad file and then it is easy to read.
Quote