Avast! Refuses to stop sandboxing a .scr I downloaded, continuing to sandbox it and not allow it to play. It is in the exclusions, but continues to sandbox it for a few seconds every time it tries to play, rendering it useless.
How do I stop it?
Have you actually managed to get it downloaded and saved to your system ?
If so what have you entered as the exclusion, it requires the full path to the file and where exactly did you enter this exclusion ?
It’s downloaded, and it’s saved. It’s when I try and select/preview it in my screensaver settings that it will sandbox it. It also won’t play normally, because again, it sandboxes.
I attached an image of where the exclusion is. Everytime I click “continue execution”, it will add it again. But then re-sandbox it.
Clear all of your exclusions as it clearly isn’t working, why is the question if that is the actual location it is located.
Try setting the autosandbox to Ask not Auto, that gives you greater interactive control, once it intercepts this .scr file when you give it permission it should automatically add it to the exclusions. You can then check what the entry is that avast placed in the exclusions.
Did it say why it was being sandboxed ?
Most commonly this will be file prevalence/reputation is low.
I deleted all the exclusions, but it continued to sandbox it.
I then tried using ask, and told it to remember my choice to allow it, and it seems to have worked. It finally got the hint to stop sandboxing it.
And yes, that is the reason it was sandboxing it, the file prevalence/reputation was low.
My question is this, though: Why was avast ignoring its own exclusions?
I don’t know, that is why I suggested clearing them ‘and’ setting it to Ask (at the same time), that way you could at least check what entry the autosandbox placed in the exclusions either matched what you put in or was different.
What exclusions put in last time was: C:\Windows\Fluttershy_sound.scr
What it put in with ask was: C:\Windows\FLUTTE~1.SCR
Yes sometimes the old 8.3 file name format is required, but that normally depends on your system settings, which is a bit weird. I though it would have worked with either.