I look at real life experiences and not just tests which as far as I’m aware only test the on-demand scan. As a happy avast users for over two years, I have confidence in avast, however no single program is going to provide full protection, so the use of multi-level compatible security programs will beef up your overall protection.
If you haven’t already got this software (freeware), download, install, update and run it.
Well, let’s put it this way: the files were very questionable. They were not really malicious, but it was not clear whether they should be detected or not. Such files should not be in a cleanset for an official test.
I agree, and that again, causes me to wonder as to the expertise of the testers. It is a sad fact that bad news travels fast, and an erroneous report is sometimes remembered while the correct version either not noticed or forgotten.
It has happened a couple of times in the past, too.
Last time, it was Kasperky (if I remember correctly), about a year ago.
Once, it even happened to Avast (I think that was in 2001).
The problem is that the VB cleanset is not maintained too well - and sometimes, some questionable files slip in. This time, the files that avast was detecting were tools for adding the current user to the admin group, with the aid of a security hole in a Windows component. These were not false positives from avast - avast was detecting them intentionally (they were part of our database of samples). Strange that no other AV actually reported them as malicious…
Thanks for the additional information. Avast is too good an AV to suffer from such errors. However, I do not think a lot of folks are even aware of the test, and those of us who are can understand the problem, and that it is not an Avast shortcoming.