sfc /scannow file replacement log? (in XP, not Vista)

[Bill in Co.]

Can someone please tell me where a LOG file of the actual files that are
being replaced or updated is? I know Event Viewer will indicate that some
files were replaced as an event, but I want to know specifically which dll
files (or whatever) are being replaced in case there are some problems with
some specific programs and I need to restore the previous version. As I
recall (but I may be recalling incorrectly), Event Viewer will not have that
information, much less be able to save it in a log.

 

[Nonny]

Can someone please tell me where a LOG file of the actual files that are
being replaced or updated is? I know Event Viewer will indicate that some
files were replaced as an event, but I want to know specifically which dll
files (or whatever) are being replaced in case there are some problems with
some specific programs and I need to restore the previous version. As I
recall (but I may be recalling incorrectly), Event Viewer will not have that
information, much less be able to save it in a log.

If you do sfc /?, you will see no option for log file <hint>

 

[Bill in Co.]

If you do sfc /?, you will see no option for log file <hint>

But that doesn't *necessarily* mean one isn't created, or (more likely) that
that information isn't being written somewhere. Although at this point,
I'm not even betting on that. Which is pretty sad. (I think that is
one thing they did fix in Vista, from what I recall reading).

 

[Nonny]

But that doesn't *necessarily* mean one isn't created, or (more likely) that
that information isn't being written somewhere.

I don't know why anyone bothers to answer your questions. You never
seem to accept the answers.

 

[Bill in Co.]

I don't know why anyone bothers to answer your questions. You never
seem to accept the answers.

Because I have not yet got a *definitive* answer (i.e., not speculative).

 

[Nonny]

Because I have not yet got a *definitive* answer (i.e., not speculative).

When you exhaust everything you know how to do and still can't find
the log, then you will know that my answer was definitive.

 

[Nonny]

Because I have not yet got a *definitive* answer (i.e., not speculative).

I see (via a Google Groups search) that you asked essentially the same
question 3 months ago and you got no "definitive" answer then either.

So why ask it again?

 

[Bill in Co.]

I see (via a Google Groups search) that you asked essentially the same
question 3 months ago and you got no "definitive" answer then either.

So why ask it again?

Because somebody may know the answer. And I have some patience and
perseverance. (old school values, pretty much gone with the wind, I know,
I know).

 

[Bill in Co.]

When you exhaust everything you know how to do and still can't find
the log, then you will know that my answer was definitive.

"Exhaust everything I know, end of story"? I don't know about you, but I
keep learning (or try to), so that will never happen, grasshopper.

 

[Nonny]

Because somebody may know the answer. And I have some patience and
perseverance. (old school values, pretty much gone with the wind, I know,
I know).

Know how to use XP's search using wildcards?

Should be a simple task to run the System File Checker and then to run
a simple search of your system disk for "*.log".

THAT should be provide you with a "definitive" answer.

Of course, then you'd probably wonder if maybe the checker used a
different file suffix other than ".log".

 

[Bill in Co.]

Know how to use XP's search using wildcards?

Should be a simple task to run the System File Checker and then to run
a simple search of your system disk for "*.log".

THAT should be provide you with a "definitive" answer.

Of course, then you'd probably wonder if maybe the checker used a
different file suffix other than ".log".

Actually, it does in Vista, from what I recall reading. (So, so much for
assumptions).

 

[Nonny]

Actually, it does in Vista, from what I recall reading. (So, so much for
assumptions).

Nope. In Vista it's a standard log file.