Useless Leftover Files In Windows XP

[Jupiter Jones [MVP]]

Free should not "heighten my suspicions".
If free does that to you, there is far to much quality free stuff you are
avoiding and possibly to much money you pay simply because it costs $.
There is not necessarily a correlation between $ and quality in software.

Whether something is safe enough for you is only for you to determine.
You asked a question and got a good answer.
You need to judge the suitability for your purposes yourself.

--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar
http://www.dts-l.org

Hmmmmmm...

Safe?

Somehow I'm quite suspicious of a piece of software that calls itself
"Crap Cleaner" and purports to be able to do the very sensitive job of
cleaning useless files off the HD without disturbing useful files.

The fact it is FREE and only 528 KB tends to heighten my suspicions.

If this software is so great why isn't it selling like hotcakes?

DSH

 

[D. Spencer Hines]

Fair Enough.

Thank You.

Do we have some other comments from MVP's and other folks who have used
"Crap Cleaner" and who endorse it?

We can call that _How To Answer Questions The Smart Way_.

P.S. I touch my Registry frequently -- and carefully -- with excellent
results.

But that doesn't mean I necessarily want something called "Crap Cleaner" to
do it automatically.

DSH

 

[D. Spencer Hines]

More to the point...

What has been your experience in using "Crap Cleaner"?

DSH

 

[Shenan Stanley]

P.S. I touch my Registry frequently -- and carefully -- with
excellent results.

But that doesn't mean I necessarily want something called "Crap
Cleaner" to do it automatically.

So you do - that's fair.. But would you consider yourself a "user" or a
"power user" of your workstation? (Not security levels - and if that is the
first thing you thought of, you fall into the second category for sure.)

In other words - do you usually research and solve your own issues or do you
take it elsewhere and could care less about any explanation (if any) given
about the problems found and how to prevent them.

For a regular user - Crap Cleaner is a wonderful tool - and the only one I
would dare recommend to a "user" and even junior "power users". And it
doesn't do it "automatically". It scans - by you pressing a button - shows
you all of the problems it finds and you have the option of checking what
you wish to remove.

Automatic? No. Foolproof? Nothing is. Better than Joe user going into
the registry and randomly deleting things? Definitely.
It also does the file scan for the TMP and log and such files - and allows
the same flexibility of deletion as it does with the registry.
It is well maintained and

As for who else recommends it:

http://groups.google.com/groups?q=ccleaner
( Results 1 - 10 of 5,630 for ccleaner )

Other mentions:
http://groups.google.com/groups?q="crap+cleaner"
( Results 1 - 10 of 600 for "crap cleaner" )

Don't get me wrong - it is not the "only game in town" - but it has proven
itself. =)

 

[D. Spencer Hines]

O.K.

Fair Enough.

I've deleted what you posted NOT because I disagree with it -- but simply in
order to keep this brief and focused.

I normally fix my own problems and am the administrator for all systems I
touch -- so I guess I'm a Cautious, Realistic, Innovative Power User,
[CRIPU] who knows his limitations.

I downloaded "Crap Cleaner" and installed it.

Here's an issue:

If I just want CC to clean Cookies in IE it says it wants to permanently
delete those upgrade log files we were talking about, such as:

C:\WINDOWS\KB873339.log 5.11KB
C:\WINDOWS\KB883939.log 10.38KB
C:\WINDOWS\KB885250.log 4.55KB
C:\WINDOWS\KB885835.log 5.42KB
C:\WINDOWS\KB885836.log 10.54KB
C:\WINDOWS\KB885855.log 6.39KB
C:\WINDOWS\KB886185.log 6.86KB
C:\WINDOWS\KB887472.log 5.23KB
C:\WINDOWS\KB887742.log 11.63KB
C:\WINDOWS\KB887797.log 9.51KB
C:\WINDOWS\KB888113.log 5.24KB
C:\WINDOWS\KB888302.log 11.01KB
C:\WINDOWS\KB888310.log 3.55KB
C:\WINDOWS\KB890046.log 15.79KB
C:\WINDOWS\KB890175.log 4.87KB
C:\WINDOWS\KB890859.log 16.50KB
C:\WINDOWS\KB891781.log 5.19KB
C:\WINDOWS\KB892627.log 2.62KB
C:\WINDOWS\KB893056.log 3.31KB
C:\WINDOWS\KB893066.log 12.53KB
C:\WINDOWS\KB893756.log 15.75KB
C:\WINDOWS\KB893803v2.log 9.03KB
C:\WINDOWS\KB894391.log 17.73KB
C:\WINDOWS\KB896344.log 9.07KB
C:\WINDOWS\KB896358.log 14.93KB
C:\WINDOWS\KB896422.log 5.30KB
C:\WINDOWS\KB896423.log 11.02KB
C:\WINDOWS\KB896424.log 28.93KB
C:\WINDOWS\KB896428.log 12.68KB
C:\WINDOWS\KB896688.log 23.19KB
C:\WINDOWS\KB898458.log 5.32KB
C:\WINDOWS\KB898461.log 8.52KB
C:\WINDOWS\KB899587.log 16.13KB
C:\WINDOWS\KB899589.log 21.36KB
C:\WINDOWS\KB899591.log 15.64KB
C:\WINDOWS\KB900725.log 29.68KB
C:\WINDOWS\KB900930.log 14.33KB
C:\WINDOWS\KB901017.log 21.37KB
C:\WINDOWS\KB901214.log 8.76KB
C:\WINDOWS\KB902400.log 25.24KB
C:\WINDOWS\KB904706.log 21.79KB
C:\WINDOWS\KB905414.log 20.88KB
C:\WINDOWS\KB905749.log 27.17KB
C:\WINDOWS\KB905915.log 16.96KB
C:\WINDOWS\KB908519.log 9.91KB
C:\WINDOWS\KB910437.log 7.09KB
C:\WINDOWS\KB912919.log 9.54KB

But I thought we were told to delete these only AFTER making sure we NEVER
wanted to UNINSTALL ANY of these Microsoft UPDATES and had already
uninstalled the matching UNINSTALL files, of the form:

C:\WINDOWS\$NtUninstallKB885836$...

So, CC seems to be bollixed, clumsy and overly aggressive...

N'est-ce pas?

DSH

news:O%[email protected]...

 

[Shenan Stanley]

Fair Enough.

I've deleted what you posted NOT because I disagree with it -- but
simply in order to keep this brief and focused.

I normally fix my own problems and am the administrator for all
systems I touch -- so I guess I'm a Cautious, Realistic, Innovative
Power User, [CRIPU] who knows his limitations.

I downloaded "Crap Cleaner" and installed it.

Here's an issue:

If I just want CC to clean Cookies in IE it says it wants to
permanently delete those upgrade log files we were talking about,
such as:
C:\WINDOWS\KB873339.log 5.11KB

But I thought we were told to delete these only AFTER making sure
we NEVER wanted to UNINSTALL ANY of these Microsoft UPDATES and had
already uninstalled the matching UNINSTALL files, of the form:

C:\WINDOWS\$NtUninstallKB885836$...

No - you only want to delete these DIRECTORIES when you are sure you no
longer need to worry about uninstalling these patches. The log files -
delete them at will.

So, CC seems to be bollixed, clumsy and overly aggressive...

N'est-ce pas?

Actually - the log files serve no purpose I know of in the uninstall..
The $NtUninstallKB######$ directories are what matters.
Delete your log files as you see fit.

On the 5 systems I just used it on - I checked only "cookies" under the
Internet Explorer category and unchecked everything else under both tabs (as
you seemed to imply you did) and analyzed. It came up with IE cookies and
no mention of the log files you quoted as it found on your system. I cannot
say it did not do that on your system- but on the 5 different systems I just
ran it on - I verified that the log files still existed in the System
directory, analyzed with only cookies selected and failed to repeat your
results even once.

Did you uncheck everything but the Internet Explorer --> Cookies under both
tabs of the Cleaner settings?

So I was not able to replicate your results and I believe you have
misunderstood the need for the KB######.log files vs. the
$NtUninstallKB######$ directories in an uninstall process. =)

I never said you didn't have to pay attention to the tool and the settings
when you used it - but nothing you would have deleted with the settings you
claimed to have used here - would have affected your ability to uninstall
the hotfixes/patches - even if you didn't uncheck everything and had the
KB######.log files listed.

Again - I am reminded of something my grandfather used to say about tools
and those who choose to use them. =)

 

[D. Spencer Hines]

D. Spencer Hines wrote:


No - you only want to delete these DIRECTORIES when you are sure you no
longer need to worry about uninstalling these patches. The log files -
delete them at will.

There may be some disagreement on that point.

My understanding, from previous posts in this thread, is that if one of the
updates turned out to be flawed -- and perhaps corrupting other programs --
the LOG file could be most helpful in determining what went wrong and should
therefore remain on the system until the SA is SURE the upgrade is CLEAN and
will NOT be uninstalled.

Actually - the log files serve no purpose I know of in the uninstall..
The $NtUninstallKB######$ directories are what matters.
Delete your log files as you see fit.

Vide supra.

[Uncalled for snide remark about grandfathers deleted as not worthy of being
dignified by an answer.]

 

[Shenan Stanley]

[Uncalled for snide remark about grandfathers deleted as not worthy
of being dignified by an answer.]

As if you knew what my grandfather said.

In short - those who aren't willing to try something (use it properly) -
won't.

As your point seemed to be to discredit its worthiness from the very
beginning - you fall nicely into said category. You went in with the
attitude of "This is crap because it is small in size and freeware. How
could it possibly do what I want?" and not the interested attitude of
someone trying to fix an issue with their system as guided by someone who's
advice they had chosen to follow.

The difference in attitude may (subliminally) cause you to find fault where
there is none. Where someone who used it to help cleanup their PC because
of advice and diligently used the tool as per the advice (their interest
making them examine the options closely) will have a completely different
point of view. =)

 

[Shenan Stanley]

There may be some disagreement on that point.

My understanding, from previous posts in this thread, is that if
one of the updates turned out to be flawed -- and perhaps
corrupting other programs -- the LOG file could be most helpful in
determining what went wrong and should therefore remain on the
system until the SA is SURE the upgrade is CLEAN and will NOT be
uninstalled.

It would only be useful for advanced users. The immediate fix for someone
thinking they are having trouble with a patch is to remove the last set of
patches and install each patch one at a time - waiting after each one and
before installing the next one for any issues.

If they finally track down which patch caused them issues - then they will
indeed have the log at that point..

Someone troubleshooting problems with patches does not take the time (after
realizing it was a patch causing the problem and doing the uninstall of the
patches, seeing everything works, installing them one at a time again until
finding the culprit) in the middle of it to use Crap Cleaner and remove
their log files anyway. And each time it is installed - that log file is
created.

Otherwise - if you are not having trouble - these logs are not needed.

[Uncalled for snide remark about grandfathers deleted as not worthy
of being dignified by an answer.]

Responded separately.

 

[D. Spencer Hines]

Fair Enough.

The Really Sound & Smart thing to do then seems to be to leave the Uninstall
Files & Logs [in C:/WINDOWS] and the Shortcuts in Add/Remove Programs of
Control Panel until the next SP -- SP3 in this case -- will remove them for
you.

They don't take up a lot of space.

THAT way one has SOME assurances [hopefully] that Microsoft has ascertained
that ALL the previous updates are IN the new SP3 or have been superseded --
and nothing has been left as an orphan to corrupt.

The SP's ARE cumulative -- n'est-ce pas?

That is, SP3 will also contain everything required from SP1 and SP2?

DSH

 

[D. Spencer Hines]

D. Spencer Hines wrote:

It would only be useful for advanced users...

I made it quite clear I was talking about the System Administrator [SA] --
an advanced user.

Additional Irrelevant, Pontificatory Gibberish Deleted.

Exitus Acta Probat.

DSH

 

[Shenan Stanley]

Fair Enough.

The Really Sound & Smart thing to do then seems to be to leave the
Uninstall Files & Logs [in C:/WINDOWS] and the Shortcuts in
Add/Remove Programs of Control Panel until the next SP -- SP3 in
this case -- will remove them for you.

They don't take up a lot of space.

THAT way one has SOME assurances [hopefully] that Microsoft has
ascertained that ALL the previous updates are IN the new SP3 or
have been superseded -- and nothing has been left as an orphan to
corrupt.
The SP's ARE cumulative -- n'est-ce pas?

That is, SP3 will also contain everything required from SP1 and SP2?

Yes - that is indeed the smart thing to do.

I really have no interest (except on woefully underpowered/undersized
machines) at removing the log or un-install directories of the Windows
patches. Yeah - there are a thousand web pages on what is/is not safe to
remove *if* you know you will not have to unsintall the patches to free up
disk space..

I am still of the attitude that if you have to remove those files to gains
space on your machine (very little space in relative terms these days) - you
have other issues. And if you are freeing up the space - it is likely to
use it up with something less valuable than your fallback from
incompatabilities. So you end up with a net gain of nothing (although you
might install that extra 200-600MB of music for that new game you got) and a
possible loss of some stability (or ability to troubleshoot and return to a
stable point.)

And yes - Service Packs are cumulative. They contain all critical patches
(including previous service packs) up until the month before they are
released in most cases. So Service Pack 3 will replace Service Pack 2 and
the 39+ (more likely by the time there is a SP3) fixes since SP2. As a
matter of fact - I don't see SP3 being much more than a roll-up. I would
bet SP2 was the "big change" and because Vista is getting closer to that
release date by the day - SP3 will have very little in the way of
improvements over just having SP2 and all the patches released after it. Of
course - that is PURE speculation.

SP3 would(will) remove whatever it includes when it is installed and leave
whatever it does not supercede.

 

[D. Spencer Hines]

Now, to the more important issue of Temporary Files.

http://personal-computer-tutor.com/deletingtempfiles.htm

What do qualified folks think of Linda's Gambit?

DSH

 

[Shenan Stanley]

C:\WINDOWS\KB873339.log 5.11KB
<snipped for brevity>

But I thought we were told to delete these only AFTER making sure
we NEVER wanted to UNINSTALL ANY of these Microsoft UPDATES and
had already uninstalled the matching UNINSTALL files, of the form:

C:\WINDOWS\$NtUninstallKB885836$..

No - you only want to delete these DIRECTORIES when you are sure
you no longer need to worry about uninstalling these patches. The
log files - delete them at will.

There may be some disagreement on that point.

My understanding, from previous posts in this thread, is that if
one of the updates turned out to be flawed -- and perhaps
corrupting other programs -- the LOG file could be most helpful in
determining what went wrong and should therefore remain on the
system until the SA is SURE the upgrade is CLEAN and will NOT be
uninstalled.

It would only be useful for advanced users...

I made it quite clear I was talking about the System Administrator [SA] --
an advanced user.

Additional Irrelevant, Pontificatory Gibberish Deleted.

Actually..

The owner of the system is the "System Administrator". Not necessarily an
advanced user.
My grandmother is the system administrator of her system - because she lives
far enough away and only has dial-up - that there is no one else.
She is by far NOT an advanced user. I have many other relatives and friends
and aquaintances who are the system administrators of their systems (by
ownership and location if nothing else) and they would be less than advanced
users as well.

Therefore - your assumption that being a "System Administrator" (SA) implied
"advanced user" is a flawed one. Either that or you greatly over-estimated
your clarity on that one. =)

 

[D. Spencer Hines]

Fair Enough.

I say again:

I don't have space or power problems on my system.

That has never been my motivation.

The system is brand-new and quite powerful -- a Dell XPS System.

I just want to eliminate ash and trash.

TEMP files are the issue now.

DSH

D. Spencer Hines wrote:

Fair Enough.

The Really Sound & Smart thing to do then seems to be to leave the
Uninstall Files & Logs [in C:/WINDOWS] and the Shortcuts in
Add/Remove Programs of Control Panel until the next SP -- SP3 in
this case -- will remove them for you.

They don't take up a lot of space.

THAT way one has SOME assurances [hopefully] that Microsoft has
ascertained that ALL the previous updates are IN the new SP3 or
have been superseded -- and nothing has been left as an orphan to
corrupt.
The SP's ARE cumulative -- n'est-ce pas?

That is, SP3 will also contain everything required from SP1 and SP2?

Yes - that is indeed the smart thing to do.

I really have no interest (except on woefully underpowered/undersized
machines) at removing the log or un-install directories of the Windows
patches. Yeah - there are a thousand web pages on what is/is not safe to
remove *if* you know you will not have to unsintall the patches to free up
disk space..

I am still of the attitude that if you have to remove those files to gains
space on your machine (very little space in relative terms these days) -
you have other issues. And if you are freeing up the space - it is likely
to use it up with something less valuable than your fallback from
incompatabilities. So you end up with a net gain of nothing (although you
might install that extra 200-600MB of music for that new game you got) and
a possible loss of some stability (or ability to troubleshoot and return
to a stable point.)

And yes - Service Packs are cumulative. They contain all critical patches
(including previous service packs) up until the month before they are
released in most cases. So Service Pack 3 will replace Service Pack 2 and
the 39+ (more likely by the time there is a SP3) fixes since SP2. As a
matter of fact - I don't see SP3 being much more than a roll-up. I would
bet SP2 was the "big change" and because Vista is getting closer to that
release date by the day - SP3 will have very little in the way of
improvements over just having SP2 and all the patches released after it.
Of course - that is PURE speculation.

SP3 would(will) remove whatever it includes when it is installed and leave
whatever it does not supercede.

 

[D. Spencer Hines]

Grandmothers should not be taught to suck eggs -- or Grandfathers to chop
wood -- but some pogues will try to do so.

'Nuff Said.

DSH

Lux et Veritas et Libertas

 

[Jupiter Jones [MVP]]

I have no opinion since I have never used it.