To some degree, I can understand that it detects the FRST64.exe file, because it’s new, but why does it detect Adwcleaner.exe from http://general-changelog-team.fr/en/downloads/view.download/2 now, even though the exactly same file didn’t trigger any false positive the past days?
To whoever is responsible for the signature updates: please do a better quality check.
You can upload files and report issues to avast here : http://www.avast.com/contact-form.php (select subject according to Your case)
You can use mail
send to virus@avast.com in a password protected zip file
mail subject: False Positive / undetected sample (select subject according to your case)
zip password: infected
or you can send files from avast chest
how to use the chest. http://www.avast.com/faq.php?article=AVKB21
Thanks for your posting, already did that, however the intention of this thread was to show that I’m tired of doing it and that Avast appears to look like a third-rated anti-virus program if this keeps going on.
Well…the only Thing we can do is report it to avast lab
then it is probably fixed in next stream Update…
Well, yes, I hope that’s the case like it’s been for the past occurrences, however I also hope that those incidents don’t repeat themselves that often.
I can confirm AdwCleaner false positive detection.
It is not fixed with 131203-0 VPS update.
I cannot wait anymore for Avast to fix this obvious false positive so I excluded AdwCleaner from File System Shield.
Glad to see it’s fixed now (at least for adwcleaner) and hopefully, it won’t happen that much again, that a legit file becomes suddenly detected after some update.
Yes,it is fixed through Streaming Updates.
Thanks.