Sorry, am I reading correctly?
The file was NOT sandboxed and your computer get infected and it’s a sandbox bypass?
Probably I’m reading something wrong ;D
So weird, I didn’t change anything, I went to have lunch and now I have tried again now the file is being sandboxed, even if I open it again I can read in the log that the file was sandboxed every single time.
Before I didnt have anything in the log, everything was active, the file was not in trusted files…
So the bypass of the sandbox seems to be a false alarm
I think you see the popup only the first time you run the file. After that, it’s automatically sandboxed without popup (you can see it if you open CIS from the systray).
Version 4 had the nasty habit to alert it sandboxed a file rather late. May be that is what’s going on here. The way to find out would be to check the D+ logs and see if it got sandboxed the first time or not.