How to analyse the CBS.log

I open the log file in Notepad, then use the "Find" function to search for the terms.

usasma said:

I open the log file in Notepad, then use the "Find" function to search for the terms.

You said that earlier, but I could not make it work. I therefore (with the help of Shawn), went this route: https://www.sevenforums.com/general-d...g-useable.html

Shawn's method is probably better than mine. He's spent a lot more time on this than I have.

I can confirm that the SFC had messed up my tweaked Vista sidebar. Actually, all the 95 files that it "fixed" or tried to fix were from the sidebar. It was funny though - although the sidebar was gone, it still acted like a Vista sidebar. My gadgets were there and they stayed "on top". The gadgets were only bigger than in the sidebar, but that is probably because I run with a changed screen resolution (poor eyesight).
But then before I moved my Sidebar and Sidebar(2) folders around, i needed to stop the sidebar from running. But killing it in task manager did not do the trick - I wonder why. Maybe I had caught an older cached instance. i had to use the Process Explorer to kill it. Which only shows: The more you learn, the less you know - at least it feels like that.

Brink said:

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

I was getting some BSOD after a video driver update. This technique saved me a lot of time.

Jane1002 said:

When I typed the command, it said "findstr" not recognised command. My OS is win7
Pls help if there is another way I can see what files need to be repaired. Many thx

findstr is a regular cmd command. No idea why ot would not work on your system.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>findstr /?
Searches for strings in files.
FINDSTR [/B] [/E] [/L] [/R] [/S] [/I] [/X] [/V] [/N] [/M] [/O] [/P] [/F:file]
[/C:string] [/G:file] [/D:dir list] [/A:color attributes] [/OFF[LINE]]
strings [[drive:][path]filename[ ...]]
/B Matches pattern if at the beginning of a line.
/E Matches pattern if at the end of a line.
/L Uses search strings literally.
/R Uses search strings as regular expressions.
/S Searches for matching files in the current directory and all
subdirectories.
/I Specifies that the search is not to be case-sensitive.
/X Prints lines that match exactly.
/V Prints only lines that do not contain a match.
/N Prints the line number before each line that matches.
/M Prints only the filename if a file contains a match.
/O Prints character offset before each matching line.
/P Skip files with non-printable characters.
/OFF[LINE] Do not skip files with offline attribute set.
/A:attr Specifies color attribute with two hex digits. See "color /?"
/F:file Reads file list from the specified file(/ stands for console).
/C:string Uses specified string as a literal search string.
/G:file Gets search strings from the specified file(/ stands for console).
/D:dir Search a semicolon delimited list of directories
strings Text to be searched for.
[drive:][path]filename
Specifies a file or files to search.
Use spaces to separate multiple search strings unless the argument is prefixed
with /C. For example, 'FINDSTR "hello there" x.y' searches for "hello" or
"there" in file x.y. 'FINDSTR /C:"hello there" x.y' searches for
"hello there" in file x.y.
Regular expression quick reference:
. Wildcard: any character
* Repeat: zero or more occurrences of previous character or class
^ Line position: beginning of line
$ Line position: end of line
[class] Character class: any one character in set
[^class] Inverse class: any one character not in set
[x-y] Range: any characters within the specified range
\x Escape: literal use of metacharacter x
\<xyz Word position: beginning of word
xyz\> Word position: end of word
For full information on FINDSTR regular expressions refer to the online Command
Reference.
C:\Windows\system32>

Try elevated cmd