And “the Exclusion is still there on the list, but it is ignored, and not run.” means that the file is detected when you run it? What is the detection name?
I’m asking because I wanted to try to reproduce the behavior, but the content you posted is not detected.
. . . And “the Exclusion is still there on the list, but it is ignored, and not run.” means that the file is detected when you run it?
No, it is not detected, either - meaning that it does not put it in the Virus Chest. Quite simply, it just doesn’t do anything with it. It ignores it, and remains in the Exclusions list.
. . . What is the detection name?
n/a, it is not detected, but I’m talking about my “Startup.bat” file.
. . . asking because I wanted to try to reproduce the behavior, but the content you posted is not detected.
After I post this, I’ll remove my “Startup.bat” from the Exclusions list, that path, and do a Restart to verify that Avast puts it in the Virus Chest. I bet it will. I will then Restore it, and put the path back.
I re-tried putting then file name “Startup.bat” in the Exclusions path, and it works as expected - there was no double-opening of programs - so something got fixed! Here’s the path:
1.) When you delete the “whole Startup folder” Exclusion vs. “Startup.bat,” you will see that this causes the computer to choke a lot harder - the computer is not easily recoverable vs. recoverable.
2.) When you delete the “Startup.bat” Exclusion, it puts it in the Virus Chest as virus “IDP.Generic,” with no notice - it would be nice if it said something.
3.) When you have the “whole Startup folder” as an Exclusion (and not specifying “Startup.bat”), the programs in “Startup.bat” are not ignored, but taking an extra 3 minutes to load. Why?