CCleaner is finding things left by JV16 PT 2007!

thorz

I have always been very happy with the reg clean abilities showed by JV16 but after removing all Logitech software from my Quickcam and running the registry cleaner and program manager modules of PT 2007 I was very disappointed to find that:

- JV16 left lots of things without giving any info. Even running the regcleaner in aggressive mode didn't found the entries.

- There was even a "Logitech Video Enumerator" entry on Add/remove programs that Software manager was not detecting at all. It was detected and removed fine by CCleaner.

- Lots of Logitech missing shared DLLs, ActiveX/COM issues and Installer reference issues were detected (and veryfied by me after) by CCleaner were not detected by any of the PT 2007 modules. These files were deleted manually by me and CCleaner found the fail references instantly.

I cannot understand how a freeware tool like CCleaner can find so much valid data after a full scan and clean by JV16 PT 2007. There were dozens of entries.

I can only conclude that something is not ok with the PT 2007 scanners.

hanzie

Well ... guess what .. I use CCleaner, Regseeker and Easycleaner (all freeware) to get rid off the leftovers that PT 2007 does noet clean ;)

tommyone

I am disappointed that the PT 2007 registry cleaner is not cleaning as good as it used to in the good old days. I do not moan normally but when Ccleaner appears to make a better job then JV16....then it gives one a reason.

jrd1st

jv sould be aware of this fact as it's been reported several times. For instance here; http://www.macecraft.com/phpBB2/viewtopic.php?t=2034

So, I hope he's working on this as I've been looking at other RegCleaners to use so I don't need several to do the job of one, the way the old jv16 RegCleaner used to.

I understand the need to re-work the algorithm for the RegCleaner so it doesn't detect keys erroneously, especially in Vista. But it should still detect keys containing invalid files/paths, no matter what OS is used.

Hopefully the algorithm or whatever the problem is, will be fixed soon.

jv16

Thorz wrote

I cannot understand how a freeware tool like CCleaner can find so much valid data after a full scan and clean by JV16 PT 2007. There were dozens of entries.

Well, this could simple be because of PT registry cleaner's design goal: it's better to miss a hundred registry errors than one day to report a single valid item as an error. This policy is what makes the product safe to use.

But, there could be a bug that causes the program to miss some errors, I'll take a look.

hanzie

I do agree, however I think the goal of the developers of CCleaner, Regseeker and Easycleaner is the same: developing a safe product.

Besides that: I never had problems removing redundant/wrong registry entries with all the software mentioned.

Another point: the mentioned software has a backup utility too (in case ;)

Just try and compare the software ...

thorz

jv16 wrote
Thorz wrote

I cannot understand how a freeware tool like CCleaner can find so much valid data after a full scan and clean by JV16 PT 2007. There were dozens of entries.

Well, this could simple be because of PT registry cleaner's design goal: it's better to miss a hundred registry errors than one day to report a single valid item as an error. This policy is what makes the product safe to use.

But, there could be a bug that causes the program to miss some errors, I'll take a look.

Thanks. As I wrote above I have always recommended JV16 in the past due to the good work done by it cleaning the registry, but something is definitely going on with the scanner of the last version. It is just missing too many things that should be ok to remove. References to manually deleted DLLs should be spoted without any problems for removal.

squirekat

I have also noticed jv16 Power Tools 2007 seems to have a bug. I always run in Aggressive Mode. I also always run CCleaner first and then jv16 Power Tools 2007, as I did with 2006, however, with the 2006 version it would always find a minimum of 40-50 items (mostly MRU). Ever since I installed 2007 I get the same result each time... only 3 items. It never changes. I have taken to running jv16 Power Tools first and then CCleaner last to finish the cleanup because jv16 PT 2007 misses so much. There is definitely a bug (and a serious one) that needs to be addressed. At this point I consider jv16 PT 2007 to be basically useless. It's really a shame because the old version worked so well and I talked all my computer geek friends into buying it. Hopefully it will be fixed but I'm wondering why the problem persists after it has been reported for quite a while now. I'm a very faithful user and when I like a product I tend to stick with it through thick and thin, but my patience is really being tested here.

jv16

So far I have found one bug that caused the PowerTools to not to detect certain types of registry errors. This problem will be fixed in the next released version.

squirekat

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

jv16

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

squirekat

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

hanzie

Glad to read that there is progress :-) to make powertools the best of all.

(I am a loyal user too since years ..)

I am looking forward to the new release. However, when I notice that I still need the other freeware (in this way mru-blaster - ccleaner - regseeker - the-paid-for-powertools - easycleaner ;-) well what to do ...?

thorz

Thanks JV

squirekat

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.