10

I did both, first chose no action because I wanted the file to remain on the c:\ drive to run a second test to choose delete.

It is entirely possible to download a file that isn’t on the VPS (undetected), which in the future is added to the VPS, then if executed it should be detected then you choose an action.

It would be a slightly false test to choose no action to simulate an unknown virus. avast has already detected the eicar string in the file when it was executed and then comes the choose an action, you can choose no action before running the eicar.com file.

Even when you choose no action upon detection avast should stop the execution of an infected file, the no action relates to leave the file there, don’t delete it, move to chest, etc. Why do you thing we need to add FPs to the exclusions in order to be able to run an .exe file detected as infected, even if you choose no action the file won’t run.

I don’t know if this differs with com files, but the use of the eicar.com cause its own problems (the eicar string doesn’t represent a valid command) in that it isn’t a valid com file, e.g. it doesn’t have any actions that we can test, even if that were a print to screen command.

So I don’t see an easy to test this for certain with eicar.com.