Create Exception

[NVF]

Installed a Playstation 2 emulator called PCSX2 and Avast! sent 2 items to the chest, though they both seem to be the same. Both names are Uninst-pcsx2-r5875, locations C:\Program Files (x86)\PCSX2 1.2.1 and their descriptions are Win32:Dropper-gen [Drp]. This is a false positive apparently (and Virus Total found only one problem tinyurldotcom/nfax83a) and I want to know how to create an exception for it/them when I try to install again. Thanks.

[Asyn]

You can report a suspected FP here: https://www.avast.com/false-positive-file-form.php

[NVF]

Thanks.

So no one knows how to create an exception for this? Could I turn off my shields and install? And if that works wouldn't Avast see those/that item/s as a virus during a scan or if I tried to use it to uninstall the program? Thanks.

[Eddy]

https://www.avast.com/faq.php?article=AVKB168

[DavidR]

Probably because there is no file name given in your initial post - e.g. no file extension (.exe, etc.) - what appears to be given is a sub-folder Uninst-pcsx2-r5875.

If they are file names and have been sent to the virus chest, then they can be restored (and exclusion added) from the chest.

Right click the avast tray icon - select Virus Chest.
Right click on the file in the chest and select Restore and add to exclusions, etc.

You would have to be 100% certain that this is an FP not "This is a false positive apparently" as you would be putting your system at risk if it wasn't an FP.

Possibly FPs should also be reported to avast also from the chest Submit to virus lab...

EDIT: Image

[NVF]

Okay made a mistake. The name of the file/s has an .exe extension so it's Uninst-pcsx2-r5875.exe. If that changes anything let me know. Thanks for the replies. Appreciated.

If I create a global exclusion, what's the file path here? The folder the item is in I suspect? But will that prevent avast from stopping it during an install?

[Asyn]

Did you report it to the viruslab yet..!?

[NVF]

Yes, I reported it through the virus chest as DavidR suggested. When I scan the installation exe package Avast! finds nothing btw.

[DavidR]

Okay made a mistake. The name of the file/s has an .exe extension so it's Uninst-pcsx2-r5875.exe. If that changes anything let me know. Thanks for the replies. Appreciated.

If I create a global exclusion, what's the file path here? The folder the item is in I suspect? But will that prevent avast from stopping it during an install?

1. OK, I don't believe it would change anything, but that could depend on if it is being detected when extracted (into a temp location) from the installation file or directly into where the actual program is installed.

2. A copy of that file would remain in the chest (safety measure, so you have a copy), that files properties in the chest will tell you of the files location upon detection. That exclusion should then stop it being detected during the install process.  It is this location that would be added to the exceptions if you elected to Restore and add to the exclusions.

Hopefully that will allow for the program to be installed, if it does get pinged whilst using the program you can repeat the Restore and add to exclusions from the virus chest again. And also report it to the avast labs.

[Eddy]

I would wait till avast has looked at it and removed the false detection (which I believe it is).
If you set a exclusion and the file will get infected, this could mean that avast will not detect it.

[DavidR]

I would wait till avast has looked at it and removed the false detection (which I believe it is).
If you set a exclusion and the file will get infected, this could mean that avast will not detect it.

The OP has been warned of the risk of exclusion in Reply #4:

You would have to be 100% certain that this is an FP not "This is a false positive apparently" as you would be putting your system at risk if it wasn't an FP.

That is his decision, not ours.

[NVF]

Thanks. The reason why I believe the file is a FP is that the creators of the program say it is. Apparently only some anti-virus programs are detecting it as a problem. Thanks again. You guys are really helpful.

[DavidR]

You're welcome.

Though I don't know many developers who would say that their software is infected, mainly they are on a no win situation. I don't know if they consider digitally signing their files as that goes a long way to preventing detection if the signature is valid. Users can also see that the file is signed and is valid, any modification along the way would invalidate the digital signature.

Hopefully the avast labs can clear it when analysed. Periodically scan the file copy within the chest, when no longer detected is your indication that it has been cleared and you could remove the exclusion/s.

[NVF]

I trust the developers for several good reasons but I understand your caution. Thanks again for the help. It's really appreciated.

[DavidR]

No problem, glad I could help.