THANK you

...
This is actually the most valuable post i've seen on RegCure. When i wrote here to the Paretologic rep. i stated that i would comment no further on her "explanations". Still true and i would have left the forum on it's own, since i found that i made my point of view - AND warnings.
I checked up on the link in your post, so see if i could get a date on the post in Pandaweb.
WOW, the date was as late as: Detection updated on: June 28, 2007
The content, the description, the date and the consequences tells it all doesn't it ... PARETOLOGIC.
The most scaring thing is ... that i was actually NOT the least surprised when i read the post, but instead it confirmed MANY suspicions.
***
My own suspicion was awaken the first time i let regcure run on its own after doing the proper settings in my firewall concerning auto updates:
I have the policy NOT to let any new and therefore not a thoroughly tested program do an autoconnecting to the net, aside from first time update. After that i have a feeling of how a program behaves with net connections:
1. The first time i clicked RegCures auto update, my firewall asked me how i wanted the settings for two entries to behave. I clicked full access.
Now RegCure was registered in my firewall where i could afterwards get in control of how i would let it access the net. Standard settings and no problem there.
2. I then in an INSTANT cut all net connection, so nothing serious would happen ... IF ... in case !
3. I then entered the options in RegCure. Setting all to null (meaning NO autoupdate, NO scan, NO nothing ... actually in fact i deactivated RegCure through its own means as much as possible).
4. I then entered the two entries in my firewall, set the access for Regcure to NULL, meaning i in every way blocked for all attempts for regcure to get on the net - it simply could NOT get an available port to create transmissions.
5. I then rebooted my machine with cablemodem running, so when window was fully running with all applications loaded, i would see how Regcure behaved netwise.
6. THEN my suspicion was awake and my awareness was on the highest alert.
7. Regcure did a persistent request to connect to the net. THAT is completely opposite to how a decent program should behave. I.e. i am running two scanners: ComputerAssociates (Firewall is effecient, but scanners (as the american term) s-u-x. Will let it run the subscribed period of time then change to Bullguard). And SuperAntiSpyware.
To compare: They do NOT try to go on the net autoupdate disabled. They wait patiently until i by myself find it about time to update.
8. AND interesting: WHY do Regcure HAVE to go on the net, when i in every way have told it "wait until I find it necessary to let you update" ???
EVERY other program i have that can be updated (well except for Windows Media Player *LOL*), do NOT persist a connection, but is dormant until i decide to update.
As in the movie "Contact" - the endcomment in the film is: "That IS interesting" !!! Isn't it !!!
Good work ...
Highball
Ps. Still ... i CAN recommend CCleaner, since it doesn't demand any amount in order to work (i HAVE though paid them a fee - they deserve it).
For me it is safe to use - i stopped a couple of years ago to make a safe backup of registry before it cleaned. I have discovered NO harm on my machine.
It doesn't do THAT much of a job - but to let it do most of the job, it is Xcellent. Afterwards i have very little work on the registry.
Try it. No problems if you before cleanup make a copy of registry. If you read the entries in its list you can clearly recognize the entries as invalid ... in the sense: Safe to clean.
PPs ... Regcure has a thread on it's own ... That
IS interesting ... isn't it !!!!!