C
cquirke (MVP Windows shell/user)
Guest
Re: Best Registry Cleaner for vista
On Sun, 8 Jul 2007 22:28:58 -0500, OzBoy
>Bit lost here, thought the poster asked for a registry cleaner not
>whether they work or not and especially not for the flaming that went
>on. Only been coming here for a couple of weeks and was very surprised
>by the contents of this post. Thought the idea was to help people????
>Confused.
What is being <ahem> "robustly debated" here, is whether there's any
point in registry cleaners at all, or more accuratrely, whether the
expected gains outweigh the risks.
Firstly; just how much performance impact does registry bloat have?
It may have been an issue in the Win95 days, especially when there
were 16-bit size limits on some registry structures, but now?
Secondly; are registry cleaners safe? The track record casts doubts
here, as often the OS or its apps have evolved to create registry
items that appear to be redundent, and are thus inappropriately
"cleaned", by registry cleaners.
The latter is one reason why a cleaner from MS may be on interest; at
least it will (or should) stay in synch with the way the evolving OS
changes the nature of registry usage.
Then again, the contents of the registry are defined not by the OS or
registry, but by the apps that create and use their keys.
You see this with file association issues and filespec parameters;
some apps require these to be "in quotes" to prevent spaces within the
filespec from being mistaken for an end-of-parameter delimiter, and
others will not work if these quotes are added.
For example, some graphic apps won't "find" target files unless "%1"
is used instead of %1, while others won't work with "%1".
Ambiguities in the way things are specified may cause some registry
entries to appear redundant, e.g. when matching...
%Variable%\Some Path
%Variable%\SomePa~1
"C:\Program Files\Some Path"
C:\Progra~1\SomePa~1"
....and there may be linkage hide-and-seek where the linkage path
passes through an app's private config files.
My own opinion, FWIW, is that registry cleaners are not worth the
bother. I've yet to see a recent system sped up by "cleaning the
registry", and I have seen hard-to-fix problems that follow them.
I do see stability etc. issues related to registry "leftovers", but
have managed these manually; I would not trust a registry cleaner to
automate this process, and the primary fix is not to do dumb-ass
things that spawn such problems (e.g. deleting application subtrees
instead of uninstalling apps, running sware directly off removable
disks, and various malware-related botch-ups).
>-------------------- ----- ---- --- -- - - - -
Tip Of The Day:
To disable the 'Tip of the Day' feature...
>-------------------- ----- ---- --- -- - - - -
On Sun, 8 Jul 2007 22:28:58 -0500, OzBoy
>Bit lost here, thought the poster asked for a registry cleaner not
>whether they work or not and especially not for the flaming that went
>on. Only been coming here for a couple of weeks and was very surprised
>by the contents of this post. Thought the idea was to help people????
>Confused.
What is being <ahem> "robustly debated" here, is whether there's any
point in registry cleaners at all, or more accuratrely, whether the
expected gains outweigh the risks.
Firstly; just how much performance impact does registry bloat have?
It may have been an issue in the Win95 days, especially when there
were 16-bit size limits on some registry structures, but now?
Secondly; are registry cleaners safe? The track record casts doubts
here, as often the OS or its apps have evolved to create registry
items that appear to be redundent, and are thus inappropriately
"cleaned", by registry cleaners.
The latter is one reason why a cleaner from MS may be on interest; at
least it will (or should) stay in synch with the way the evolving OS
changes the nature of registry usage.
Then again, the contents of the registry are defined not by the OS or
registry, but by the apps that create and use their keys.
You see this with file association issues and filespec parameters;
some apps require these to be "in quotes" to prevent spaces within the
filespec from being mistaken for an end-of-parameter delimiter, and
others will not work if these quotes are added.
For example, some graphic apps won't "find" target files unless "%1"
is used instead of %1, while others won't work with "%1".
Ambiguities in the way things are specified may cause some registry
entries to appear redundant, e.g. when matching...
%Variable%\Some Path
%Variable%\SomePa~1
"C:\Program Files\Some Path"
C:\Progra~1\SomePa~1"
....and there may be linkage hide-and-seek where the linkage path
passes through an app's private config files.
My own opinion, FWIW, is that registry cleaners are not worth the
bother. I've yet to see a recent system sped up by "cleaning the
registry", and I have seen hard-to-fix problems that follow them.
I do see stability etc. issues related to registry "leftovers", but
have managed these manually; I would not trust a registry cleaner to
automate this process, and the primary fix is not to do dumb-ass
things that spawn such problems (e.g. deleting application subtrees
instead of uninstalling apps, running sware directly off removable
disks, and various malware-related botch-ups).
>-------------------- ----- ---- --- -- - - - -
Tip Of The Day:
To disable the 'Tip of the Day' feature...
>-------------------- ----- ---- --- -- - - - -