Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: allskin on September 22, 2008, 11:42:48 AM

Title: Making file a "exception"
Post by: allskin on September 22, 2008, 11:42:48 AM
Hello,

First of all, sorry my english.

I have a file that i know that is not a virus but Avast detects as.

So, i want to add this file as a exception in "on-access protection".

How can i do it?

Thanks in advance
Title: Re: Making file a "exception"
Post by: Bluesman on September 22, 2008, 12:07:08 PM
Hello,

First of all, sorry my english.

I have a file that i know that is not a virus but Avast detects as.

So, i want to add this file as a exception in "on-access protection".

How can i do it?

Thanks in advance

Welcome to the forum! :)

What file is it?

You need to use the Exclusion lists:

Standard Shield provider (on-access scanning):
Left-click on the avast-ball in the tray area, click on the provider icon at left and then click on "Customize".
Then go to the "Advanced" tab and click on the "Add" button...

For the other providers (on-demand scanning (such as the screensaver) or the Simple user interface):
Right-click on the the avast-ball, then click on "Program Settings"
Go then to the "Exclusions" tab and click on the "Add" button...

If you want it, you can use wildcards like ? and *
Title: Re: Making file a "exception"
Post by: allskin on September 22, 2008, 12:17:23 PM
Hello,

So, if the file is "madplay.exe", i can add only "madplay.exe" in the exclusion list?

I'v done this:

(http://www.hdd.pt//images/1335206480.png)

But when i try to use the file, the virus message appears.

Thanks

Title: Re: Making file a "exception"
Post by: Bluesman on September 22, 2008, 12:29:09 PM
But when i try to use the file, the virus message appears

I have never used the exclusion lists, so I just guessing, maybe you need to add the full path to the file and not just the file name, like this:

c:\program files\madplay.exe

And also restart the computer, so you reset the memory (if the file is loaded in the memory)

If you know that the file is a false positive ( try it with VirusTotal . http://www.virustotal.com ), zip it and set an password on the archive, and send the file to virus@avast.com (and remember to write the password in the mail)
Title: Re: Making file a "exception"
Post by: allskin on September 22, 2008, 12:39:37 PM
Hello,

Yes, i'v tryed the full path but don't work and the file is not loaded in ram.

VirusTotal Report: http://www.virustotal.com/analisis/77d1f43d2f6a99e30db0900fea4cb094

I'll try to send a e-mail for virus@avast.com.

Thanks a lot.

Regards
Title: Re: Making file a "exception"
Post by: allskin on September 22, 2008, 02:28:40 PM
Ok, e-mail sended to virus@avast.com

I'll wait for the answer.

Thanks
Title: Re: Making file a "exception"
Post by: DavidR on September 22, 2008, 03:47:36 PM
Since most of the detection in VT are either generic (-gen) or heuristic (suspicious) it is highly likely this is an FP.

What exactly did you enter in the exclusion for the path ?

Try this in your exclusions, c:\*\madplay.exe if it is on the c drive, the use of the * wild card means you don't have to put in the full path.
You have to exercise care when using wild cards so as not to leave holes in your security, but like this it should be OK>
Title: Re: Making file a "exception"
Post by: allskin on September 22, 2008, 06:36:33 PM
Hello,

i'v entered: C:\PROGRAM FILES\(Folder Name)\(Program Folder)\madplay.exe

EDIT: Used c:\*\madplay.exe and it works!

Thanks a lot one more time DavidR and Bluesman ;)

Regards
Title: Re: Making file a "exception"
Post by: DavidR on September 22, 2008, 08:03:57 PM
No problem, glad I could help.

Welcome to the forums.
Title: Re: Making file a "exception"
Post by: Lisandro on September 23, 2008, 12:00:32 AM
allskin, add the file to Chest (right clicking the Chest and choosing add) and scan it. Check back if after you update your avast installation the file is still being detected as infected.
If it's clean, you can remove the exception ;)
Title: Re: Making file a "exception"
Post by: rogman49 on September 23, 2008, 04:22:25 PM
All,

I was having a similar problem as Allskin. I use a free software program to open / close dvd drives. Using it for years. After yesterday's virus update Avast started flagging it as a virus. I tried to add full path to exception list to no avail. I then used the C:\*\XXXXXXX.EXE and it worked fine. Wonder why full path name does not work? ???
Title: Re: Making file a "exception"
Post by: Lisandro on September 23, 2008, 04:44:27 PM
I then used the C:\*\XXXXXXX.EXE and it worked fine.
Is it an example or the file is called XXXXXXX.EXE really?

Wonder why full path name does not work? ???
Sometimes it's invoked (run) by the short path (something like C:\Program~1\Files~1\name.exe).
Title: Re: Making file a "exception"
Post by: rogman49 on September 23, 2008, 05:11:41 PM
Hi Tech,

The XXXXXXXX is an example. It is a simple program from RJL Software.  ;D
Title: Re: Making file a "exception"
Post by: Lisandro on September 23, 2008, 05:30:31 PM
Hi Tech,

The XXXXXXXX is an example. It is a simple program from RJL Software.  ;D
So, you the real path should work if you write it down correctly.
The short (8.3) also can be necessary sometimes.
Sometimes, you need to boot to activate the exceptions.
Title: Re: Making file a "exception"
Post by: DavidR on September 23, 2008, 05:49:48 PM
I was having a similar problem as Allskin. I use a free software program to open / close dvd drives. Using it for years. After yesterday's virus update Avast started flagging it as a virus. I tried to add full path to exception list to no avail. I then used the C:\*\XXXXXXX.EXE and it worked fine. Wonder why full path name does not work? ???

Since you don't give us the full path that you entered we can't possibly comment.

When avast detects it, you can actually copy and paste the full path from the alert window.

However exclusion is only masking a symptom and not treating the problem, you need to use virustotal to confirm it is a false positive and send a sample to avast rather than just exclude.
Title: Re: Making file a "exception"
Post by: rogman49 on September 23, 2008, 05:56:44 PM
Guys,

We are not communicating very well.  ::). I have been using this program for a thousand years. It is not a virus. If I copy the full path to the exception list, it does not work. Same as Allskin. I had to use the C:\*\XXXXXXXX. X's are an example.
Title: Re: Making file a "exception"
Post by: DavidR on September 23, 2008, 06:10:58 PM
It is all right saying you copy the full path but by displaying what you type it might just show why it isn't working.

I know one thing by not displaying it we will never know so are wasting our time, I hope I have communicated that well enough for you.
Title: Re: Making file a "exception"
Post by: rogman49 on September 23, 2008, 06:37:53 PM
All,

Does anybody know why Allskin was not successfull when adding full path name to the exception list?
Title: Re: Making file a "exception"
Post by: Lisandro on September 23, 2008, 10:58:16 PM
All,

Does anybody know why Allskin was not successfull when adding full path name to the exception list?
Please, post here the real full path name...
Title: Re: Making file a "exception"
Post by: rogman49 on September 24, 2008, 03:45:46 PM
All,

Full path name does not work. Tried all types of combinations. It seems to ignore it. I did some experimenting and found out that C:\XXXXXXXX\* does work. X's contain folder name. This has been posted before on the forum. Full path name does not work.  ???
Title: Re: Making file a "exception"
Post by: DavidR on September 24, 2008, 03:55:14 PM
As has our request for the full text that you entered, we simply can't begin to say why something didn't work when we can't see what it is exactly that you entered, it is that simple. Even then we might not see why, but we would at least have a shot than dancing around in the dark wasting time.

In the time you have been avoiding the question we may have been able to make a suggestion as to why it didn't work and move on but this is like pulling teeth, I don't understand your reluctance to post what you entered. 

So for me I'm done being a dentist.
Title: Re: Making file a "exception"
Post by: rogman49 on September 24, 2008, 05:56:59 PM
No, the right syntax would be
C:\MyPix\*
It excludes all files in C:\MyPix, including all subfolders.
It is not possible to exclude only the files in C:\MyPix and not the files in its subfolders.

If you use C:\MyPix* - it will work too, but it will also exclude files like C:\MyPixListing.txt, also files in C:\MyPix2 or C:\MyPixAnything folders, etc.
*******
*******
The answer above was given on 06/18 by Igor. As I stated full path name will not work. The lowest level you can go down to is folder name.
Title: Re: Making file a "exception"
Post by: Lisandro on September 25, 2008, 03:29:05 PM
It is not possible to exclude only the files in C:\MyPix and not the files in its subfolders.
Yes, you can write down C:\MyPix\*.*