Registry cleaners - EasyCleaner

[Smirnoff]

I notice that there seems to be a shift in opinion re the use of registry
cleaners.
Most posters now warn against their use.
I have used EasyCleaner by ToniArts for about 5 years on various machines
without trouble.
It's always "un-doable" should problems occur (which they haven't).
The only thing I avoid is the Duplicate File option (don't know enough about
that).
Does anybody else still use/recommend this program?

 

[Detlev Dreyer]

I have used EasyCleaner by ToniArts for about 5 years on various machines
without trouble.
...
Does anybody else still use/recommend this program?

I do not recommend any of these tools since there is no benefit vs. high
risk to render applications or the entire system useless. When removing
registry entries, they are marked as deleted - however, they still exist.
There is no difference if the registry contains orphaned entries (before
"cleaning") or slack space (after "cleaning") instead. There are tools
around (eg. NTREGOPT) compressing the registry by removing the slack
space, however, when running WinXP on adequate hardware, there will be
no mensurable performance increase either.

 

[=?ISO-8859-1?Q?Ga=EBtan?=]

Smirnoff a écrit :

I notice that there seems to be a shift in opinion re the use of registry
cleaners.
Most posters now warn against their use.
I have used EasyCleaner by ToniArts for about 5 years on various machines
without trouble.
It's always "un-doable" should problems occur (which they haven't).
The only thing I avoid is the Duplicate File option (don't know enough about
that).
Does anybody else still use/recommend this program?

I have been using it since Win 98 ( more than your 5 years ) without any
problem at all. I still use it weekly for deleting crap registry
entries. No problems, and my pc runs fine and quick.

 

[Alias~-]

I do not recommend any of these tools since there is no benefit vs. high
risk to render applications or the entire system useless. When removing
registry entries, they are marked as deleted - however, they still exist.
There is no difference if the registry contains orphaned entries (before
"cleaning") or slack space (after "cleaning") instead. There are tools
around (eg. NTREGOPT) compressing the registry by removing the slack
space, however, when running WinXP on adequate hardware, there will be
no mensurable performance increase either.

Depends on the tool and how you use it. I use SystemSuite that gives
registry scan results in a color coded list, green, safe to remove,
yellow, maybe safe to remove and red, you better know what you're doing.
Systemsuite provides a way to make a floppy to restore your system if
removing an entry makes the computer unbootable and you can restore any
entries with the program itself if it does boot.

I have had SystemSuite since 2001 and have never, ever, had a problem
with it and I have deleted thousands of registry entries with it on many
machines using 98/Me/W2K and XP. After installing XP SP2, you will find
hundreds of entries. The same is true for Office and Office updates.
Maybe you want a clogged computer but I don't.

Alias

 

[Detlev Dreyer]

Depends on the tool and how you use it. I use SystemSuite that gives
registry scan results in a color coded list, green, safe to remove,
yellow, maybe safe to remove and red, you better know what you're doing.
Systemsuite provides a way to make a floppy to restore your system if
removing an entry makes the computer unbootable and you can restore
any entries with the program itself if it does boot.

That's the point. If the system doesn't start anymore after "cleaning"
the registry, the cause is rather clear and what a lucky guy if his tool
allows for system restore while Windows cannot be accessed. In cases
when cleaning the registry "successfully", the majority of the resulting
problems will show up at a later date and the user will never ever come
to the conclusion that this problem has been caused by the registry
cleaner. Even in the remote case that he does, using an out-dated "Undo"
file may mess up the registry furthermore.

I have had SystemSuite since 2001 and have never, ever, had a problem
with it and I have deleted thousands of registry entries with it on
many machines using 98/Me/W2K and XP.

Well, you never had a problem showing up instantly (see above). A good
example has been the EasyCleaner prior to version 2.0 IIRC, destroying
the function of WinMe's and WinXP's Help&Support Center. Never-ending
postings at that time complaining about that problem and absolutely no
user capability to detect the relation to that useless and harmful tool.

Maybe you want a clogged computer but I don't.

LOL! Note that the registry is not a sequential database. Turning
orphaned registry entries into slack space cannot really speed up your
system unless you strongly believe in it (placebo effect).

 

[Alias~-]

That's the point. If the system doesn't start anymore after "cleaning"
the registry, the cause is rather clear and what a lucky guy if his tool
allows for system restore while Windows cannot be accessed. In cases
when cleaning the registry "successfully", the majority of the resulting
problems will show up at a later date and the user will never ever come
to the conclusion that this problem has been caused by the registry
cleaner. Even in the remote case that he does, using an out-dated "Undo"
file may mess up the registry furthermore.
Baloney.


Well, you never had a problem showing up instantly (see above). A good
example has been the EasyCleaner prior to version 2.0 IIRC, destroying
the function of WinMe's and WinXP's Help&Support Center. Never-ending
postings at that time complaining about that problem and absolutely no
user capability to detect the relation to that useless and harmful tool.

Like I said, I have never had a problem using SystemSuite for five
years. I was talking about SystemSuite, not EasyCleaner.

LOL! Note that the registry is not a sequential database. Turning
orphaned registry entries into slack space cannot really speed up your
system unless you strongly believe in it (placebo effect).

No, my stop watch is my witness, not some belief.

Alias

 

[Detlev Dreyer]

Baloney.

Nope. There is no user running all installed applications and checking
all Windows functions (eg. the Help&Support Center) on a daily base.
When starting an application being damaged by his "Cleaner", this may
happen some days or even weeks after running that tool. In the meantime,
other things have been changed in addition (system settings, software/
hardware installations, system updates) and there is no way to find the
actual culprit. What is so hard to understand?

 

[DatabaseBen]

the criterian for dup files, are exact filename, date, time
size type. The only difference would be their folders.

Deleting regular files that are dups won't be the problem.
However, if they are executiables files/programs what have been dup'd, then
you should manually intervene and check their validity. Again,
if these executaibles are duplicated, it is likely that they are
the same files but found in different folders...

Then the next question after you
clean out the duplicates, is to find out if there is a
cause in the background that is duplicating them.
Like the old LaRue virus for spreadsheets that
replicated spreadsheets by the thousands in the background,
you may have a similar problem installed as well.

Back to dup's. I would refrain from using a registry cleaner
to automatically clean them out at first. But I would suggest
to use this type of automation later and after you manually
clean out your system beforehand. Try using a specialty software
for finding and listing dup files/folders first. Then clean them out
manually.

there are lots of cleaner avail
and if you use any of them be sure
they are of current code;
an old registry cleaner may not recognize the
new stuff...And some malicious softwares are
disguised as cleaners too. So do some research in this area...

I use several cleaners and edit my registry
whenver I d-m well please and my systems
run like a rolls royce....Each cleaner has a different
criterian as to what is not a proper registry entry. And
some simply remove all the blank spaces only.

It's your system, its a free market and
you are entitled to do and use whatever you
think is best. Remember to always have
a little insurance, like a current restore point, etc...

There will always be those with the
haves who want to control the have nots....
!To deny you of the truth....... (blah blah....).....

Good luck with your quest for knowledge....

 

[Alias~-]

Nope. There is no user running all installed applications and checking
all Windows functions (eg. the Help&Support Center) on a daily base.
When starting an application being damaged by his "Cleaner", this may
happen some days or even weeks after running that tool. In the meantime,
other things have been changed in addition (system settings, software/
hardware installations, system updates) and there is no way to find the
actual culprit. What is so hard to understand?

You've never run SystemSuite's registry fixer, have you? Had you done
this, you would know what you're talking about but you haven't, so
you're just blowing ill informed hot air. When SystemSuite shows the
scan's results, it also shows the path and registry key. Soooo, if later
you're having a problem with something, you can go to SystemSuite's undo
feature, find the culprit and restore it. That said, in over five years
I have never had to do that on countless machines.

You have a theory and an opinion that is not based on SystemSuite.

I have actual experience on many machines.

Alias

 

[Ken Blake, MVP]

I notice that there seems to be a shift in opinion re the use of
registry cleaners.
Most posters now warn against their use.
I have used EasyCleaner by ToniArts for about 5 years on various
machines without trouble.
It's always "un-doable" should problems occur (which they haven't).
The only thing I avoid is the Duplicate File option (don't know
enough about that).
Does anybody else still use/recommend this program?

I'm not sure that there's been any shift of opinion, but I always recommend
against the routine use of registry cleaners. Routine cleaning of the
registry isn't needed and is dangerous. Leave the registry alone and don't
use a registry cleaner. Despite what many people think, and what vendors of
registry cleaning software try to convince you of, having unused registry
entries doesn't really hurt you.


The risk of a serious problem caused by a registry cleaner erroneously
removing an entry you need is far greater than any potential benefit it may
have.



Of course, not every time someone uses s registry cleaner does a problem
develop. You can often get away with it. But the risk is always there, and
the benefit is non-existent. If you've used such a program for five years
without trouble, consider yourself lucky,

 

[Detlev Dreyer]

You've never run SystemSuite's registry fixer, have you?

No. However, I've tested most of the well-known registry cleaners. I was
analyzing their Undo files in order to find the applications, concerned
by the "cleaning" process. All of them were removing essential entries,
even when orphaned. The latter applies to software, setting default path
and filenames for log files (anti-virus, firewall etc.). Since these
files do not exist yet right after the installation, all of them removed
these entries, winding up with malfunctions of the software.

You have a theory and an opinion that is not based on SystemSuite.
Correct.

I have actual experience on many machines.

When testing your cleaner as I was testing many others, you will find
out that it makes the same basic mistakes as the other cleaners, most
likely.

 

[Alias~-]

No. However, I've tested most of the well-known registry cleaners. I was
analyzing their Undo files in order to find the applications, concerned
by the "cleaning" process. All of them were removing essential entries,
even when orphaned. The latter applies to software, setting default path
and filenames for log files (anti-virus, firewall etc.). Since these
files do not exist yet right after the installation, all of them removed
these entries, winding up with malfunctions of the software.


When testing your cleaner as I was testing many others, you will find
out that it makes the same basic mistakes as the other cleaners, most
likely.

Get back to me when you have some empirical experience with SystemSuite
and have used their Registry Fixer. You can buy it at
http://www.v-com.com/ What you are saying is like testing Linux and
saying Windows is not good because you tested Linux.

Alias

 

[Detlev Dreyer]

Get back to me when you have some empirical experience with SystemSuite
and have used their Registry Fixer. You can buy it at
http://www.v-com.com/ What you are saying is like testing Linux and
saying Windows is not good because you tested Linux.

ROFL! http://www.v-com.com/product/SystemSuite_Features.html#fix

| RegistryFixer searches the registry for invalid links and invalid
| entries and offers to repair or remove them.

The same crap as all the other "fixers" and "cleaners"! Dream on, boy.

 

[R. McCarty]

I've studied the Registry for years. To this day, it takes hours to manually
resolve/remove Keys,Values and Class Identifiers that are associated to
each other and a parent application. I've tested many different "Cleaners"
and haven't found a single one that I could recommend as safe/effective.

 

[Alias~-]

ROFL! http://www.v-com.com/product/SystemSuite_Features.html#fix

| RegistryFixer searches the registry for invalid links and invalid
| entries and offers to repair or remove them.

The same crap as all the other "fixers" and "cleaners"! Dream on, boy.

When you've tested it, let me know. In the meantime, you're just blowing
hot air. Mind you, I am referring to the manual reg. fixer, not the
automated one which I wouldn't use or recommend. This product was
originally developed by OnTrack.

Alias

 

[Detlev Dreyer]

I've studied the Registry for years. To this day, it takes hours to
manually resolve/remove Keys,Values and Class Identifiers that are
associated to each other and a parent application. I've tested many
different "Cleaners" and haven't found a single one that I could
recommend as safe/effective.

ACK, same here. In addition, many applications (eg. Netscape) replaced
the removed registry entries when testing. The user, running a registry
cleaner from time to time does not even notice that many of the removed
entries have been already removed last time. He enjoys frequently the
placebo of "thousands" of removed entries instead. Under the bottom
line, this funny game results in an significant increase regarding the
amount of slack space, winding up with more fragmented registry files.
These tools are simply counter-productive, useless and dangerous.

 

[Alias~-]

ACK, same here. In addition, many applications (eg. Netscape) replaced
the removed registry entries when testing. The user, running a registry
cleaner from time to time does not even notice that many of the removed
entries have been already removed last time. He enjoys frequently the
placebo of "thousands" of removed entries instead. Under the bottom
line, this funny game results in an significant increase regarding the
amount of slack space, winding up with more fragmented registry files.
These tools are simply counter-productive, useless and dangerous.

SystemSuite comes with a registry defragger too. Interesting how you
talk about something you've never experienced and paint all programs
with the same brush.

Alias

 

[Detlev Dreyer]

SystemSuite comes with a registry defragger too. Interesting how you
talk about something you've never experienced and paint all programs
with the same brush.

Note that registry defragger != registry compressor (eg. NTREGOPT)

Only a registry compressor can remove the slack space created by
registry cleaners. As for *defragging* the registry files, your
"SystemSuite" is wasted money. There is free software around,
defragging registry files as well as other system files:
http://www.sysinternals.com/Utilities/PageDefrag.html

 

[Alias~-]

Note that registry defragger != registry compressor (eg. NTREGOPT)

Only a registry compressor can remove the slack space created by
registry cleaners. As for *defragging* the registry files, your
"SystemSuite" is wasted money. There is free software around,
defragging registry files as well as other system files:
http://www.sysinternals.com/Utilities/PageDefrag.html

Again, sigh, when and if you test SystemSuite, get back to me. In the
meantime, STFU.

I have an AMD 800 with 512 RAM and when I installed Windows, SP2, Office
and all the updates, the computer booted in a minute and a 40 seconds.
After doing a registry fix and registry defrag, it booted in 53 seconds.
Those are facts. All you've provided is hot air based on what you
*think* SystemSuite is and it is getting old really fast.

Alias

 

[Detlev Dreyer]

I have an AMD 800 with 512 RAM and when I installed Windows, SP2,
Office and all the updates, the computer booted in a minute and a 40
seconds.

That's not unusual since the system is severly fragmented after such
installations.

After doing a registry fix and registry defrag, it booted in
53 seconds.

Well, when having the idea to defrag the registry files, you had the
idea to defrag the rest of the system as well. When doing this, it's
not unusual to achieve such results. You were turning several screws
at the same time and it's nothing but a joke when stating that the
improvement results from a registry cleaner (topic of this thread).
All of my systems (SP2, Office, all updates) boot in less than a minute
w/o using any registry cleaner/fixer and while testing these tools,
there was no improvement at all in terms of speed. The case is closed.