Avast and Win32 Trojan/Worm warnings real?

Avast Free Antivirus / Premium Security
1

Hi, I have recently started using avast as my antivirus as AVG has managed to make a very bad follow up version of their virus scanner.

I like what i see with avast so far, except for one thing.
When I start to install a program I often get a Win32 Trojan/Worm warning.
In most cases I can hardly believe this is the case, as I install it from a retail CD/DVD version of the program.
If it would have been an illegally obtained version I would be able to believe this, but that is not the case here.

My girlfriend has the same problem, as she tried to install the software that came with her new MP3-Player.
Is their a way to make a file be ignored, even in future events when you install it? I believe their are a lot of programs that somehow use this Win32 and don’t mean any harm, can this be true?

I can’t believe that every single warning I got from avast about this Win32, that it really is a virus.
When can I assume it is real and when can I safely continue the installation?
Is there a way for me to make avast a little less strict about some files or even ignore a specific file.
I ask this as it give a lot of trouble with installing program’s as it also blocks it, even when you say ‘no action’.
Then I have to go and pause the provider and after install resume it again.

Can anyone shed some light on this for me?
I would like to continue to use this application, but this one thing might force me to abandon it.

Grtz,
MyDomain

2

hi MyDomain,

You should find the information your need here:

http://forum.avast.com/index.php?topic=7779.0

Send the file/s to avast! if posible so the FP can be corrected and other users spared the same inconvenience.

3

Welcome to avast forums.
To know if a file is a false positive, please submit it to VirusTotal and let us know the result. If it is indeed a false positive, send it in a password protected zip to virus@avast.com
Please, mention in the body of the message why you think it is a false positive and the password used. Thanks.

As a workaround, you can add these files to the Standard Shield provider (on-access scanning) exclusion list.
Left click the ‘a’ blue icon, click on the provider icon at left and then Customize. Go to Advanced tab and click on Add button…
You can use wildcards like * and ?. But be careful, you should ‘exclude’ that many files that let your system in danger.

4

Thanks for the really, really, fast reply.

The tutorial will help me indeed, i’ll see if these buggers are really false positives and mail them in case they are.

I thought the exclusion list would only apply if i ran a system scan, but they also work on live scan?

Thanks!

5

There are two Exclusion lists:

For the Standard Shield provider (on-access scanning):
Left click the ‘a’ blue icon, click on the provider icon at left and then Customize.
Go to Advanced tab and click on Add button…

For the other providers (on-demand scanning such as the screen-saver or the Simple User Interface):
Right click the ‘a’ blue icon, click Program Settings.
Go to Exclusions tab and click on Add button…

6

Oke thanks, gues problem is solved then… thanks for the help!
This one can be closed…