Registry cleaners - EasyCleaner

[Alias~-]

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


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.

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

Alias

 

[Pez D Spencer]

i use RegClean which is a microsoft product that microsoft doesn't
distribute anymore.

i also use Windows Install Clean Up which can dislodge stuff from the
resistry that's causing problems with software installation.

both are microsoft products and free.

as for commercial products -- like the pc tools version, which i think
is called registry mechanic -- they kinda remind me of ad-aware in the
way they list ever last little think that might possibly be a problem,
but usually isn't.

 

[Detlev Dreyer]

i use RegClean which is a microsoft product that microsoft doesn't
distribute anymore.

That's no good idea and bad advice if meant as recommendation:
"Errors that the RegClean utility finds after you install Microsoft
Office" http://support.microsoft.com/?kbid=299958

i also use Windows Install Clean Up which can dislodge stuff from the
resistry that's causing problems with software installation.

Correct, this tool has proven to be useful. However, its scope is
limited to software being installed by the Windows Installer. In
addition, this tool is not really a registry cleaner. It has an
impact on the %SystemRoot%\Installer folder as well.

 

[Bruce Chambers]

i use RegClean which is a microsoft product that microsoft doesn't
distribute anymore.

It's not distributed or good reason; it's likely to do more harm than
good, and that on the OS for which it was designed, which most
definitely wasn't WinXP.


--

Bruce Chambers

Help us help you:



They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -Benjamin Franklin

Many people would rather die than think; in fact, most do. -Bertrand Russell

 

[Pez D Spencer]

That's no good idea and bad advice if meant as recommendation:
"Errors that the RegClean utility finds after you install Microsoft
Office"

it wasn't a recommendation. the knowledge base article you're
referring to explains problems that may occur if you run regclean after
you install office but before you run office for the first time.

 

[Detlev Dreyer]

it wasn't a recommendation. the knowledge base article you're
referring to explains problems that may occur if you run regclean after
you install office but before you run office for the first time.

Not really. Note that "Installed on First Use" is a Windows Installer
option (state) during setup that applies to the components of a program.
Therefore, the problems may occur at any time when the program needs one
of these (optional) components. When selecting a standard installation,
many or most of the components have this state and running "RegClean"
the other day will affect all these components except those having the
"Local" state (installed on the hard disk). Another good example for
problems caused by a registry cleaner and showing up at a later date.

 

[Pez D Spencer]

Not really. Note that "Installed on First Use" is a Windows Installer
option (state) during setup that applies to the components of a program.
Therefore, the problems may occur at any time when the program needs one
of these (optional) components. When selecting a standard installation,
many or most of the components have this state and running "RegClean"
the other day will affect all these components except those having the
"Local" state (installed on the hard disk). Another good example for
problems caused by a registry cleaner and showing up at a later date.

thanks for the tip.

if i start having problems, i'll just go ahead and reinstall word
2002...which is the only piece of office i use. oddly, though, word
2002 isn't on the list of incompatibles.

 

[Detlev Dreyer]

thanks for the tip.

You're welcome. BTW, these problems are not limited to Microsoft Office:

| This issue occurs for any Microsoft Windows Installer product on which
| the program's installation state is set to Installed on First Use.

oddly, though, word 2002 isn't on the list of incompatibles.

Good catch! I already noticed and I was close to advise the MSKB content
manager to add this application to the list. However, one of my systems
came with a preinstalled Word XP (= Word 2002) and AFAIR all components
had the "Local" state before installing the entire Office XP package on
top. Therefore, I'm not sure at all if Word XP (stand-alone) allows for
"Installed on First Use" components anyway.