Newly Updated Chart of Registry Cleaner Reviews!

[Marianne]

Both you and Marianne just proved what I said. Orphaned entries are NOT
ignored. Are orphaned run key entries ignored? Almost all the posts in
here about error messages on startup are caused by orphaned run keys
entries. How is newbie going to know what or where a run key is?. It has
been mentioned several times that MS includes a registry cleaner in it's
OneCare yet none of you "registry is snake oil" guru's ever answer why
that is. If MS thinks it is necessary then it is necessary and they did
not have Win98 in mind when they created OneCare..

That one is easy to answer. One Care was an attempt to get in on the
multi-billion dollar AV market. Instead of starting this AV venture from
scratch Microsoft purchased an already existing AV software company (Giant).
Giant had a registry cleaner and One Care just kept it as a marketing
gimmick, they didn't create or develop a cleaner just for One Care. We all
know that One Care was (is) a complete flop! The product was consistently
rated as one of the poorest AV product out there and it never generated the
revenue stream that Microsoft had envisioned, to wit Microsoft has decided
to discontinue it, no registry cleaner could save it.

You are ignorant of the process which owns and calls the registry run keys,
a hint for you: it isn't the applications referred in the keys. You are
grasping at straws, using a registry cleaner to clean out the run keys is
nonsense, it's akin to using a bazooka to kill a fly, the potential for
collateral damage is much greater than the problem being addressed!
Instead of telling users that cleaning the run keys is a good reason to use
a cleaner why don't you instruct users to use the built-in MSConfig utility
to remove these obsolete entries? Because you don't know any better, that
is why. Using the MSConfig utility is simpler and much safer than using
registry cleaners but you keep on insisting that those who know the least
use the most dangerous methods to remove these entries.

Why don't you tell the readers what happens when your cleaners remove
"orphans" from the Winlogon key? Why don't you tell them what happens when
registry cleaners "think" that the Userinit value is "orphaned"? Using a
registry cleaner to cleanup a virus or malware problem is sheer stupidity,
something that only the most ignorant would ever recommend. You
conveniently forget to mention the problems caused by these cleaners, posts
with tales of woes and problems caused by registry cleaners do show up in
these groups but when they show up you and your ilks in the "registry
cleaners are great" stable just put on your blinders and trot right by the
hapless folks who desperately need help after heeding your advice to use
these cleaners.

M

 

[Marianne]

Anything that is the registry run keys is in msconfig. Your own words:
"Almost all the posts in here about error messages on startup are caused by
orphaned run keys entries." These banal errors on startup saying that a
certain file is missing are all from entries in the run keys and *all* of
these run key entries are in msconfig. Your ignorance shows that you don't
know the difference between the run keys and startup locations. There is no
need for registry cleaners to cleanup these run key entries and only idiots
would use cleaners to cleanup malware.

Re: The userinit value. There usually aren't any problems with the malware
affected value until registry cleaners come by and improperly remove the
value, then the computer doesn't start and the user can't properly edit the
key. This is well known and many users have posted of this problem with
cleaners improperly removing the value, yet as usual you conveniently forget
to mention this because you're in denial and you would go to any length to
defend these cleaners, that includes recommending them to novice users who
can't properly interpret the actions taken by these dangerous tools.
Experienced people who are competent and who understand Windows don't
recomend registry cleaners, none of the MVPs recomend them, only phony MVPs
and ignorant trolls advocate the use of these dangerous tools.

M

 

[Marianne]

What the Fck does your userinit tool, a tool that like all your other tools
you stole from others, have to do with this discussion about registry
cleaners? Did you fall off a cliff again and hit your head and forget what
the discussion is about? We have seen *many* posts in these groups from
people who could not boot their computers after cleaners did a hatchet job
on their userinit value! If these users had properly manually edited the
value they would not have been left with non booting computers! Only idiots
and trolls like you and Twayne keep on ignoring the fact that registry
cleaners can and *do* at times cause problems. Even in the camp of the
posters who think that the tools have limited uses there are few who would
ever recommend these tools to novice users. You're in denial and you simply
cannot accept facts so you will just go on forever with your ill advice.

M

 

[Marianne]

WTF does any of that have to do with registry cleaners? Are you stoned or
are you just plain fscking stupid by nature? STFU, will you, nobody cares
about your stupid stolen tools, the discussion was about registry cleaners.
Is your tool a registry cleaner? If your tool doesn't touch the registry
then what does it have to do with cleaners that do? Get a fscking life or
drop dead you troll!

M

 

[Twayne]

....
We have seen *many* posts

in these groups from people who could not boot their computers after
cleaners did a hatchet job on their userinit value! ...

I challenge you to find 5 (five) such posts from "these groups" and give
their locations.

I haven't yet seen you post anything legitimate; maybe this is your
chance!

Twayne

 

[Mike Hall - MVP]

...
We have seen *many* posts

I challenge you to find 5 (five) such posts from "these groups" and give
their locations.

I haven't yet seen you post anything legitimate; maybe this is your
chance!

Twayne

You might want to take up your own challenge..

 

[Twayne]

You might want to take up your own challenge..

Did. Can't find them. So passed it on...

 

[Anteaus]

Ok, gentleman and lady, let's do this the honourable way, not like some
uncouth ruffians...

You will, on my mark, both walk twenty paces to your respective SSME, turn,
and activate the startup sequencer. Let's have a clean incineration with no
unscheduled shutdowns.

:-D)

 

[A-TechnicalUser]

I know those who love to make spam accusations and who literally hate
Registry Cleaners so much that they closed mindedly and constantly
attempt to force their misguided opinions and misinformation onto the
public will come crawling out of the woodwork over this, but I think
this group could use this post anyway.
I'm not spamming because I have NO investment of any kind in any of
the upcoming links and references; they are simply that which the web
was/is intended for: The dispersal of information.

Although I didn't bother to read them, I did notice the latest cacophony
over Registry Cleaners by the typical group of misinformationists and
ignorant sock-puppets that usually accrue when someone disagrees with
any of them that Registry Cleaners do and will continue to, have a valid
place in most anyone's toolbox of troubleshooting utilities. I'm fairly
sure they'll repeat their silliness here. Oh, and I even came across a
white-paper dated in 2006 I hadn't seen before, but I'm not going to
expose it until one of the narcissistic egos here presents some valid
information for their own claims that there does not exist a Registry
Cleaner that is any good, that won't damage a system, and that will
eventually make the system unbootable, separate from the causes of ANY
program that could cause that to happen.

So whether you're just curious or are looking for a decent Registry
Cleaner, here's a list of reviews of them from several different places.
There are a lot more but I hoped I would find just one site that made a
full comparison of all of them in one place. Not finding that, I
settled for the following:

Ever wonder how Registry Cleaners compare?
Ever wonder if opinions on their outputs are similar from place to place
where different opinions appear?

http://registryrepaircompare.com/
RegCure was #1

Registry Cleaner Reviews:
http://www.registrycleanersreviewed.com/
RegCure made #1

Registry Cleaner Geeks
http://www.registrycleanergeeks.com/
RegCure came out #1

5 Registry Cleaner Reviews: Which Is The Best?
http://www.registrycleaner-reviews.org/
RegCure was on top

Advanced Registry Cleaner
http://registry-repair-software-review.toptenreviews.com/advanced-registry-cleaner-review.html
Not all that great. Techie. Limited Features.

Registry Cleaner Reviews
http://www.registrycleanerreviews4u.com/compare_chart.html
RegistryEasy won, but ... they also sell that one<g>.

Registry Cleaners Reviewed
http://www.registrycleanerreview.us/
and RegCure won yet again.

A discussion on cleaners (toward the bottom of the page)
http://www.informationweek.com/news/windows/showArticle.jhtml?articleID=171203805

The "best" Registry Cleaner?
http://forums.cnet.com/5208-6138_102-0.html?threadID=116309
Discussion

A pretty bad Registry Cleaner: Complete Registry Cleaner 1.0
http://www.pcmag.com/article2/0,2817,1585462,00.asp


RegCure seems to be doing pretty good even with their last little
glitch. What I'd really like to see is a comparison of the freebie
Registry Cleaners versus the pay-fors; maybe next time.

If you don't think a Registry Cleaner is worth using, that's fine and
your perogative. But forcing, intimidating and shoving others to share
your misguided opinions is just plain wrong.

Twayne`
--

--
Regards,

Wrong does not cease to be wrong
because the loud ones scream it consistently. -Me

 

[A-TechnicalUser]

I hope no one objects if an actual "new user" weighs in. "Twayne," even I
can see that the domain names in your lengthy list of links, are for
commercial sites and not those of objective evaluators of registry cleaner
software. In fact, they may well have all been created by the same
person/entity, who merely changes the domain name slightly from time to time,
ala spammers. One possible exception is the link to PCMag, but I looked at
that article and saw it was from 2004 and did not consider/test any of the
products that I have read about before turning to Microsoft for advice.
(e.g., CCleaner)

Although I am not sure who decides who is a "MVP" in Microsoft discussion
boards, I am more inclined to listen to those people than to someone who,
like you, has a blank profile and no accountability for what happens to those
who take his advice.

And, in case anyone actually employed by Microsoft is listening, I am very
disappointed that Microsoft offers no information on the subject of registry
cleaning, and instead leaves users to sift through all the BS on these boards.

Twayne, don't bother flaming me, as I will not be back here.

 

[bangloreagent1]

I know those who love to make spam accusations and who literally hate
Registry Cleaners so much that they closed mindedly and constantly
attempt to force their misguided opinions and misinformation onto the
public will come crawling out of the woodwork over this, but I think
this group could use this post anyway.
I'm not spamming because I have NO investment of any kind in any of
the upcoming links and references; they are simply that which the web
was/is intended for: The dispersal of information.

Although I didn't bother to read them, I did notice the latest
cacophony
over Registry Cleaners by the typical group of misinformationists and
ignorant sock-puppets that usually accrue when someone disagrees with
any of them that Registry Cleaners do and will continue to, have a
valid
place in most anyone's toolbox of troubleshooting utilities. I'm fairly

sure they'll repeat their silliness here. Oh, and I even came across a

white-paper dated in 2006 I hadn't seen before, but I'm not going to
expose it until one of the narcissistic egos here presents some valid
information for their own claims that there does not exist a Registry
Cleaner that is any good, that won't damage a system, and that will
eventually make the system unbootable, separate from the causes of ANY

program that could cause that to happen.
--------------------------------------------------