Windows 7: How to open Windows cbs.log files ?

After running scannow in boot/cmd mode...I received an error message saying some files were repaired...they are listed in cbs.logs

When I try to open cbs.logs...I get the error reported in attached jpg.

How or what do I change in permissions to allow me to open the file...I have administrator status on this one user Win 7 Pro 32bit machine ?

Thanks...TRinAZ

Hello TRinAZ,

Normally your would copy the C:\Windows\Logs\CBS\CBS.log file to your desktop, then open it in notepad to view it.

However, you could use OPTION THREE in the tutorial below to make it a lot easier to only view the SFC result details from within the CBS.log.

SFC /SCANNOW Command - System File Checker

Hope this helps,
Shawn

I love it Brink. I always wanted to know how to do that.

Thanks as always...still have two issues tho...

1) When I open command prompt as administrator and paste the link - findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt - I get the sfcdetails.txt file but it's empty..?..have tried the process three times but still get empty file ?

and 2) The original boot disk cmd run of sfc gave me the warning that a couple files couldn't be repaired...but when I open the cbs.log file on the desktop...I have no idea what I am looking for ?

What key words should I use to search the attached cbs.log to find out what how many files and which ones need to be manually repaired ?

Thanks...TRinAZ

TRinAZ,

Since you only ran SFC at boot, there would be no entiries made into the CBS.log. That's all.

Run the SFC command from a elevated command prompt inside Windows 7 first, then create a new sfcdetails.txt report.

OK...ran from desktop and now have the file...but...when I open the cbs.log file on the desktop...I have no idea what I am looking for ?

What key words should I use to search the attached cbs.log to find out what and/or how many files were repaired and which ones need to be manually repaired ?

You could use OPTION THREE in the tutorial below to make it a lot easier to only view the SFC result details from within the CBS.log to see what files were not able to be repaired.

SFC /SCANNOW Command - System File Checker

If you like upload the sfcdetails.txt file, and I'll be happy to take a look at it.

Unfortuantely...the new scan shows no error/fixes. The only file I have now is the original cbs.log previously uploaded at:
http://www.sevenforums.com/attachmen...-files-cbs.log

I know there were some files repaired and I think some that said they couldn't be repaired...

If the cbs.log is too large to mess with...I'll understand

Thanks

Trinaz,

There are not any SFC results (SR) in your cbs.log file above. Looks like there was nothing that needed to be fixed.