jv16 PowerTools 2010 and CCleaner

charlesn56

I have been using PT and CCleaner both for some time. With the current version of PT 2.0.0.967. I can find 143 ActiveX and Class Issues in CCleaner that do not show up in PT. This is the only 2.0 version of PT I have tried with CCleaner. and noticed any leftover issues. Any ideas?

redseujac

What options/settings do you use in jv16 PowerTools 2010 Registry Cleaner?

charlesn56

redseujac wrote
What options/settings do you use in jv16 PowerTools 2010 Registry Cleaner?

I am running XP SP3 and the current version of CCleaner 2.34.1200.

I clean with the following settings of PT. Engine setting set to: Normal registry cleaning policy.

I test with the following settings of PT. Engine setting set to: More and Most aggressive. Advanced engine settings:

Enabled all custom scans.

Still can not find the ActiveX errors that CCleaner can.

abide.in.the.vine

Hi,

I use CCleaner as well and have had the same thing happen. I have a good sized list of several obsolete registry entries in CCleaner which I have been unable to pick up with JV16 Power Tools 2009 or 2010. Now, overall, I have found far more entries with JV16 Power Tools to clean out than with CCleaner, and it also emphasizes safety. So I think JV16 Power Tools is certainly better. I do know that several of these entries (if not all of them) can be safely deleted (on my system anyways). For example, I had the trial version of ZoneAlarm installed about a year ago but decided to use Norton Internet Security instead. After uninstalling ZoneAlarm, JV16 Power Tools was able to find and delete several entries left behind with both the Registry Cleaner and the Software Uninstaller. But there has been a single entry that CCleaner is able to pick up that JV16 Power Tools has not been able to. I have not deleted these with CCleaner yet because I was trying to use JV16 Power Tools almost exclusively, but have yet to get JV16 Power Tools to find these entries.

*EDIT* - I have attached pictures of CCleaner to see the entire list of registry entries it finds which JV16 Power Tools has not been able to find.

CCleaner - Registry List (1).png

CCleaner - Registry List (2).png

CCleaner - Registry List (3).png

CCleaner - Registry List (4).png

redseujac

The policy of jv16 PowerTools since a long time is always: safety first (header on page 6 of the Handbook 2010) :

And under "Design goals" (page 5 of that Handbook) you read the following:

We take safety very seriously. There can be no point in optimizing or cleaning your


computer if that action creates problems. Since the inception of RegCleaner, first developed in
the late 1990's, we have had the policy of operating on the side of caution: missing some

potential registry errors to prevent incorrectly deleting one valid registry entry.

Maybe that's the reason why CCleaner finds more...

aagaard

redseujac wrote

Maybe that's the reason why CCleaner finds more...

I have tried a lot of registry cleaners over the years, including CCleaner. I have had some very bad experiences with other cleaners including CCleaner.

The reason always was that these cleaners 'cleaned up' some rather important things (that is things that should not be cleaned)!

Now I only trust jv16 Powertools and never have had bad experiences with this tool - no forced restores and that's the way I like it..

jv16

charlesn56 wrote
I have been using PT and CCleaner both for some time. With the current version of PT 2.0.0.967. I can find 143 ActiveX and Class Issues in CCleaner that do not show up in PT. This is the only 2.0 version of PT I have tried with CCleaner. and noticed any leftover issues. Any ideas?

If you can send me a list of these items I could take a look.

But generally speaking ActiveX related registry errors are really tricky to pick safely. That's why the entire ActiveX scan is not even run by default, it's only run in Aggressive Mode.

charlesn56

jv16 wrote
charlesn56 wroteI have been using PT and CCleaner both for some time. With the current version of PT 2.0.0.967. I can find 143 ActiveX and Class Issues in CCleaner that do not show up in PT. This is the only 2.0 version of PT I have tried with CCleaner. and noticed any leftover issues. Any ideas?

If you can send me a list of these items I could take a look.

But generally speaking ActiveX related registry errors are really tricky to pick safely. That's why the entire ActiveX scan is not even run by default, it's only run in Aggressive Mode.

Here is the file containing the list I removed with CCleaner. I could not even get PT to show these items in any mode even Aggressive Mode.

Thanks for you help.

doogie

jv16 wrote
charlesn56 wroteI have been using PT and CCleaner both for some time. With the current version of PT 2.0.0.967. I can find 143 ActiveX and Class Issues in CCleaner that do not show up in PT. This is the only 2.0 version of PT I have tried with CCleaner. and noticed any leftover issues. Any ideas?

If you can send me a list of these items I could take a look.

But generally speaking ActiveX related registry errors are really tricky to pick safely. That's why the entire ActiveX scan is not even run by default, it's only run in Aggressive Mode.

I agree with you there Jouni, especially after participating in the beta testing of PT 2010, a lot of false positives were shown in the ActiveX entries.

However I also have to agree with charlesn56 comments regarding these entries. From the last couple of beta builds up to the current release I haven't seen any ActiveX entries at all showing up after running Registry Cleaner in the most aggressive mode.It's almost like that part of PT has been dumbed down excessively.

dayhu

This appears to be the same issue with pt 2010 vs pt2009 With a scan using pt2009 I get over 500 active x items identified. With 2010 none -- both in aggressive mode How important is it in any case is it to clean these entries

doogie

dayhu wrote
This appears to be the same issue with pt 2010 vs pt2009 With a scan using pt2009 I get over 500 active x items identified. With 2010 none -- both in aggressive mode How important is it in any case is it to clean these entries

What OS are you using dayhu, and also is it x64?

dayhu

Windows 7 32 bit

I have also posted some info on this forum with subject rt 2010 vs 2009

redseujac

dayhu wrote
Windows 7 32 bit

I have also posted some info on this forum with subject rt 2010 vs 2009

Look in this thread.

And notice the warning by our developer not to use the (most) aggressive mode of the Registry Cleaner because it's dangerous.