exclude from resident protection revisited

Yes, I know, there have been many posts dealing with the problem of excluding certain applications from resident protection.

However, I have followed all of the suggestions and I am still unable to run an application which Avast says is infected. I want to run it in spite of Avast’s opinion. Please do not ask me why I would want to do that. I am fully aware of the dangers. :slight_smile:

I have put the file into the Chest. I have put it into a C:\Suspect folder. I have added it to all exclusion lists. I still can’t run it without first disabling Avast. Surely there must be a feature somewhere in the program which allows a particular “infected” application to run.

You need to use 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…

You can use wildcards like * and ?.
But be careful, you should ‘exclude’ that many files that let your system in danger.

What exactly did you enter in the exclusion lists ?
e.g. the full path and file name or something else.

What is the infected file name, where was it found e.g. (C:\windows\system32\infected-file-name.xxx) ?
Check the avast! Log Viewer (right click the avast ‘a’ icon), Warning section, this contains information on all avast detections. C:\Program Files\Alwil Software\Avast4\ashLogV.exe - Or check the source file using notepad C:\Program Files\Alwil Software\Avast4\DATA\log\Warning.log

I am an advanced user. This is the standard answer that is always given to this question. I have entered the full path to the file in question in both exclusion areas and it is still not excluded.

In any event, I have found a different app to replace the one in question so the issue is resolved for me. However, I think it remains a problem with Avast which will not allow “infected” apps to run even if the user chooses to do so.

Please, answer this David’s question.

Then as an advanced user you would appreciate that answering questions helps us to help you. Without information we are working in the dark.

I asked both questions, standard or otherwise to compare what you had actually entered in the exclusions against what was actually detected. Only if we know what you entered could we possibly have any idea if it was correct.

We can only find out if the problem is with avast if we have the information to make that determination and if so to try and resolve it.

I found the problem - and I must admit it was not an Avast issue. My bad. :slight_smile:

The “infected” file was not the correct version of the application and therefore did not correspond to the file that was being excluded.

Thanks for the input.

You’re welcome.

Don’t worry. Welcome to avast forums.