CCleaner shows two avast!

Ok I know I should be hit on the head for this for not asking it earlier but Im seeing two avast! antivirus 6, and 8 under utilities in the applications menu of cleaner from the program CCleaner(free version). Not sure how I have two, Same thing with macromedia 10 and 11 (not sure how this got in). I probably just answer why my avast is having problem sense both could be conflict with each other when I hit quick scan, Still not sure how it showing up sense one should over right the other.

Don’t worry about CCleaner showing two version of Avast and Macromedia. Probably it’s a bug in CCleaner. Your Avast is working fine.

It’s a CCleaner fault and one that needs to be fixed as it’s been there since version 8 of Avast was released.

Just now I made a new account at CCleaner Forum. I will report this issue at their forum. Hope it get fixed asap.

Good job :slight_smile:

Thanks mate :slight_smile:

Why is this an issue?

It might well be that more recent AVAST versions still contain left overs or uses active elements from v.6 and CCleaner is correctly listing it in things to check whether to clean even if there is nothing to remove.

In its Tools > Programs list CCleaner shows, as it should, just the current installed AVAST version.

It would be interesting to know if this non-problem occurs after a proper full AVAST uninstall/reinstall.

Has anyone tried that?

yes. also reinstalled ccleaner, same result. no issues, just unchecked both.

skinnypops

I believe it is simply an issue where in that the avast location doesn’t change and ccleaner simply can’t tell what avast version you have after avast 8.

In the same way avast 6, 7 & 8 having once detected avast 6, 7 & 8 it just doesn’t clear the old entries (in ccleaner applications list) when the latest version is detected.

I haven’t a clue exactly what ccleaner is looking for to identify what avast version you are using, but clearly it isn’t getting it right. As it hasn’t got an entry for avast 9 or avast 10.

I have done a number of clean installs of avast and it hasn’t made a blind bit of difference in ccleaner, it can’t really identify what version of avast is installed, NOW.

I wouldn’t let ccleaner touch any avast version check boxes that it may have.

I have been in the CCleaner Forum and one of the members there said this

"If ccleaner add another detection which is [Avast! Antivirus 10] that use the same HKLM+HKCU\Software\Avast Software\Avast, you will get 3 entry in CCleaner

DON’T DELETE THE REGISTRY
it’s not your fault, it is a detection bug in CCleaner
to be on the safe side, disable the entry until it is being fix.

the dev do read thread but rarely comment
i hope a mod can come here and report this to the dev".

I guess we have to wait for a fix until a mod sees my post and reports it to a dev. That I think it’s going to take a while or longer!!!

N.B.: Current detection by CCleaner is avast 6 and 8. When he mentioned the third detection by CCleaner if it detects it avast 10 (2015).

You will notice from my attached there are already 3 versions listed 6, 7 & 8 - but no mention of avast 9 or avast 10.

So the ccleaner avast detection is weak at best and very poor at worst in detecting what version of avast you have and worse still not removing old ccleaner entries for avast version that are no longer installed. Not to mention this has been this way for some considerable time.

If they can’t determine that then they have to look at something else to get the exact avast version that is installed.

Oh that’s so strange DavidR. I too have Avast 2015, but CCleaner is detecting only two version of Avast. Versions 6 and 8. DavidR do you mind if I download your attachment and post as part of my post at CCleaner forum?

Help yourself - it will show that the detection is poor and it hasn’t detected avast 9 or 10. But more so why are the redundant avast versions still on the Applications list.

You can see from my signature I’m using avast free - if that is what you are asking.

Posted it. Don’t know why this bug hasn’t been reported in the past. Looks like I will have to do that #takeonefortheteam :slight_smile: