Solved SFC runs, finds errors, but does not create CBS.log file

greetings all

I have a similar problem (as it relates to cbs logs) as the OP of this thread:

SFC runs, finds errors, but does not create CBS.log file - Vista Forums

I read through the whole page, however I am not yet technologically advanced enough to understand what a "repair" environment is, nor how I accomplish that.

and post #5 may as well be chinese....I don't understand what 'set' means. "Set" what/where/how?

is there any chance I could get step-by-step instructions to accomplish that?

btw, in the past, I have accessed, copied and interpreted cbs logs, but now my beast doesn't create them and I have no idea why. CHKDSK ran clean today.

any help anyone can give would be greatly appreciated.

TIA
Boots

What #5 means is you enter (or copy and paste)

set WINDOWS_TRACING_LOGFILE=C:\TEMP\CBS.log

before you run the sfc /scannow command in the Command Prompt window.

That is supposed to redirect the output to c:\temp\cbs.log instead of c:\windows\logs\cbs\cbs.log.

Didn't work for me when I just tried it but give it a try, can't hurt.

I can't find any reference anywhere to WINDOWS_TRACING_LOGFILE so I'm skeptical it works, but you never know.

This command should bring up the cbs.log

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log

I found the solution; thanks for your suggestions folks

Boots