philo said:
....
Yes I have read his words.
Years ago when I was using Win98 I did use a registry cleaner from
time to time...and I never noticed any improvement in
performance...however once in a while it caused a problem.
OK. Win98x is apples and oranges, but I guess I see your point.
Depending on whether one insists on carrying forth win98 "stuff", it can
create confusion for them and cause them to assume things in XP et al
that aren't necessarily so. But I suspect you know all that from
previous posts or yours that I've read.
....
but since I've since moved on to Win2k and XP never again ran into the
the problem of partial uninstallations.
I don't either on my own machines with the exception of the sandbox
laptop; there, anything goes becasuse it's an easily restored "learning"
machine. That said however, I do have other reasons for using a
registry cleaner even on my own machines and have done so for years.
Most people, and you seem to have avoided the trap, seem to think that
registry cleaners have only one function: To clean out extraneous or
leftover entries. Case in point: I just re-installed MalwareBytes again
to see if it was any better than the previous version I tried; it seems
to be. But ... all of my previous settings from the last installation,
many months ago, "came to life" all of a sudden. I had killed the
folders on the disk, but never cleaned the registry of the leftovers and
now wished I had. I didn't WANT my history from the last install! So I
had to uninstall it and rather than fart around manually scrubbing it, a
registry cleaner made the job quick & easy. THEN I was able to
reinstall it, and test it properly against its prior results.
Unfortunately, it still finds a legitimate setup.exe in the ...\Windows\
directory to be a rogue installer; which it is not. IT's part of an
INNO install routine for a VB program I was testing out. I made the
file and t he INNO installed placed it there. But MalwareBytes insists
on giving it the name "Rogue: Installer". I have never had any other
program detect that as a problem except MalwareBytes. MalwareBytes is
declaring it a problem, I've figured out, due to its unusual location,
NOT from any analysis of the setup that MB looked at. So MB is
declaring things in unusual locations as rogue; it has done absolutely
nothing otherwise to decide whether it was or wasn't a rogue. I can put
that exact same file in another location, and MB will not report it as a
problem. So IMO it's using unreliable information.
OTOH, as long as you watch out for MB's little gotchas like that,
it's a reasonable malware detector but ... not one of my most prized
tools.
Woof! Sorry for the verbosity; that's usually a sign my pain meds
But for the average person who does not know *exactly* what they are
doing...running a registry cleaner could potentially create
problems...
We'll have to agree to disagree there, because a well written program
can make life a lot easier for the less than nearly expert level people.
I don't care if a person does or doesn't use such programs; but I do
care when they posit misinformation about them. Or msinformation about
anything else for that matter.
I'm not saying you are wrong, because running ANY program, or even
installing a program, can potentially create problems if it uses the
registry. I simply maintain that reputable, reliable registry cleaners
will not cause any more system problems than any other program used on
the PCs, including Microsoft's own applications. In fact, here on my
own machines, it has created 0 problems over the years, where Microsoft
over the same time span has created many, many issues one could consider
a "problem". Like the fix just prior to this week's onslaught: They
issued the emergency fix, and then a few hours later I received a fix to
fix I'd just allowed to install.
Regards,
Twayne`