My latest experience with the currently latest avast home, that scan exclusion for single file, or path is only effective, when scan is started from the user interface, but the setting doesn’t affect standard on-access scan.
Problem originates with latest update, producing false alarm for factory-made exe identifiying as Trojan. Workaround was decided to suspend/contiue standard shield while specific application is in use.
Any ideas?
Did you also add it to the exclution list here?
Left click the"a" icon , click stanard shield, customise button, advanced tab.
hth
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…
You can use wildcards like * and ?.
But be careful, you should ‘exclude’ that many files that let your system in danger.
What is the suspect file name, where was it found e.g. (C:\windows\system32\suspect-file-name.xxx) ?
You could also check the offending/suspect file at: VirusTotal - Multi engine on-line virus scanner Or Jotti - Multi engine on-line virus scanner if any other scanners here detect them it is less likely to be a false positive. You can’t do this with the file in the chest, you will need to move it out.
Send the sample to virus@avast.com zipped and password protected with password in email body and false positive in the subject.