How view CBS.log

[Walter Donavan]

Vista Basic. Dell Vostro 220.

It tells me I do not have access. I am the administrator and only user.

* Background: I ran sfc /scannow because my system, brand new, often refuses
to run pgms or carry out commands (doing nothing when told). Sometimes it
says a file is missing. Sometimes it just ignores the command.

* sfc /scannow told me I had some corrupted files and to examine CBS.log.
But Vista won't let me examine it. I managed to TYPE it in Command Mode, but
it went by so quickly I couldn't see it. It is also very big.

* I am an inch away from using the Dell utility that restores the computer
to its original state--but of course I'd lose all my installations and
tweaking.

What can I do?

Thanks for your help.

Walter

 

[zachd [MSFT]]

Run "cmd.exe" *as an administrator*. In that window, type "notepad
%systemroot%\logs\cbs\cbs.log". Or copy cbs.log to elsewhere and then open
it...

 

[Walter Donavan]

Thank you zachd.

The latter did not work for me, but I will try the former, which I
understand.

I have saved your response in my Tech Notes section of Documents.

 

[Walter Donavan]

zachd,

Using your technique, I was able to open CBS.log, but I couldn't interpret
it. It is also huge (2+MB .txt file).

Any suggestions as to how to intepret it? (E.g. how to search for errors,
what to do when I find them?)

 

[zachd [MSFT]]

What you could do is copy the existing file, rename the old one to
cbs.old.log in that elevated cmd.exe prompt, run sfc /scannow and see what's
new there. Or copy the existing one to cbs.old.log , run sfc /scannow and
windiff the two after that completes.

I don't know if there's any great interpretation mechanisms other than going
through the file. But your errors would be towards the bottom. Possibly
search for "error"?

 

[Darrell Gorter[MSFT]]

Hello,
Use this article to get the relevant SFC information out of the cbs.log file
928228 How to analyze the log file entries that the Microsoft Windows
Resource Checker (SFC.exe) program generates in Windows Vista
http://support.microsoft.com/default.aspx?scid=kb;EN-US;928228



Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
| >Reply-To: "zachd [MSFT]" <[email protected]>
| >From: "zachd [MSFT]" <[email protected]>
| >References: <[email protected]>
<[email protected]>
<[email protected]>
| >In-Reply-To: <[email protected]>
| >Subject: Re: How view CBS.log
| >Date: Tue, 27 Jan 2009 17:19:10 -0800
| >Lines: 25
| >Message-ID: <[email protected]>
| >MIME-Version: 1.0
| >Content-Type: text/plain;
| > format=flowed;
| > charset="iso-8859-1";
| > reply-type=response
| >Content-Transfer-Encoding: 7bit
| >X-Priority: 3
| >X-MSMail-Priority: Normal
| >X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
| >X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
| >X-MS-CommunityGroup-PostID: {7FFCFAC5-39CC-4ADE-AC3B-FEF740497720}
| >X-MS-CommunityGroup-ThreadID: FB9A01CA-CD2B-41D1-A412-12B28321AA67
| >X-MS-CommunityGroup-ParentID: 09116E6C-B6C9-4689-8661-1339AD56A19C
| >Newsgroups: microsoft.public.windows.vista.general
| >Path: TK2MSFTNGHUB02.phx.gbl
| >Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.general:381111
| >NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
| >X-Tomcat-NG: microsoft.public.windows.vista.general
| >
| >
| >What you could do is copy the existing file, rename the old one to
| >cbs.old.log in that elevated cmd.exe prompt, run sfc /scannow and see
what's
| >new there. Or copy the existing one to cbs.old.log , run sfc /scannow
and
| >windiff the two after that completes.
| >
| >I don't know if there's any great interpretation mechanisms other than
going
| >through the file. But your errors would be towards the bottom.
Possibly
| >search for "error"?
| >
| >--
| >Speaking for myself only.
| >See http://zachd.com/pss/pss.html for some helpful WMP info.
| >This posting is provided "AS IS" with no warranties, and confers no
rights.
| >--
| >| >> zachd,
| >>
| >> Using your technique, I was able to open CBS.log, but I couldn't
interpret
| >> it. It is also huge (2+MB .txt file).
| >>
| >> Any suggestions as to how to intepret it? (E.g. how to search for
errors,
| >> what to do when I find them?)
| >
| >