Re: CCleaner use on Registry ??
"Jose" <jose_ease@yahoo.com> wrote in message
news:9e6c65fd-d8ec-4a97-a89e-fbe35514fc30@r5g2000yqb.googlegroups.com...
On Jan 15, 7:48 pm, Desmond <Desmond.44v...@no.email.invalid> wrote:
> Registry Cleaners - can and often do, stop the system from restarting.
>
> They can remove system files as well as other files.
> Best leave cleaning the registry alone.
>
> Why not to use a reg cleaner..http://www.edbott.com/weblog/?p=643
Can anyone tell me any registry cleaner I can run that will delete
system files or other files without my knowledge/consent that will
leave my system unbootable when it is done?
Can anyone provide an example (not a rumor) of any Windows function
that works and then after a registry cleaner, the function does not
work anymore? I need the function and the registry cleaner that
breaks it.
Can anyone provide an example (not a rumor) of how running a registry
cleaner will make my system worse than before I started (timings are
good).
I'm not saying these things are not, but I have never experienced it
and would like to.
===============
I use CCleaner at home and have never had a problem with any portion of it.
Of course, I read what it says it is going to do, and act accordingly. I
don't blindly let it have its way with my system.
But I used to use it at work before I retired, and the registry cleaning
part of it could (and did) do some damage to network-run apps. For example
(from personal experience, not rumor or word of mouth), our AS400 system,
MacPac, was run from a server with only a small part of the interface
installed locally. If the registry cleaner was allowed to delete keys with
"broken" links (network drives), "Unused file extension", or "Missing shared
DLL", then the program had to be reinstalled locally. Of course, that was
not done without "my consent", but it did leave the program unusable. I have
never had it leave a system unbootable, though.
I think in a home environment, registry cleaners and the like are less
likely to do any harm than in a network environment. I've used a few since
the early Win95 days, and have never rendered a system unbootable/unusable,
be it at home or at work, but I have seen a very few problems like the
example I gave, but only where network mapped drives or programs are in
play.
--
SC Tom