[tr][td]C:\Users\Scott\autosandboxme.exe[/td][td] No AutoSandbox prompt, it just runs[/td][/tr]
[tr][td]C:\Users\Scott\Desktop\autosandboxme.exe[/td][td] No AutoSandbox prompt, it just runs[/td][/tr]
[tr][td]F:\autosandboxme.exe[/td][td] I get an autosandbox prompt (F:\ is a flash drive)[/td][/tr]
I did have an issue with Fences but this is different (I think). Even running from explorer the file does not get any sandbox alert.
After reading the above post I tried something similar. . . .
C:\Users\Bob\Downloads\autosandboxme.exe → program just runs, i.e. no Autosandbox prompt nor red outline
C:\autosandboxme.exe → program just runs, same as above
F:\autosandboxme.exe → prompt from Autosandbox appears, and program has red outline when run as it should
Hopefully this helps identify where the problem might be . . . .
EDIT: same thing happens when using OTL.exe as the test file
As you are from Germany you may want to go to PROFILE then Modify Profile then Forum Profile Information then select your country in Please select your country: then update your Signature: with information like my signature as this helps the helpers offer pertinent advice.
In Account Related Settings select Hide email address from public? to prevent scammers and spammers harvesting your web.de email address.
See my post #342. The F:\ drive that successfully ran the avast! Autosandbox on my system is not a removable drive. It is a second SATA drive that is installed in my system.
I also took the liberty of trying the same “experiment” on my D:\ partition (which is on the same physical drive as my C:\ partition). Autosandbox worked as it is supposed to. Looks like something is messing with the Autosandbox feature when run on files that are on my C:\ partition . . . .
And yesterday in the Russian sub-forum we got complaints (it’s the first in the list) about the bug. I advised to drag down a bit the bottom border of the main Avast window: if you drag enough to make the scroll bar disappear, the bug disappears too. But my advice only made the man angry: he insists that it is a bug to be solved by the developers, not by users. And I’d like to ask the developers if this bug will be solved.
Don’t know. I can tell you that the Autosandbox feature was working fine up until I installed the beta. As far as I know, nothing else has changed on my system.
I have sent some additional information to the avast! team (requested by them) about this so hopefully they will be able to figure it out. It might, however, be fairly elusive since it appears that only some people are having the problem. We’ll see . . . .
You have got to be joking, beta trials aren’t without fault (because it will be deployed across a myriad of different systems), that is the nature of beta testing. Though I have had zero issues with this build and the last, I did have with the first release because of the installation package problem of it rolling back to the regular build (I didn’t have an issue with the beta itself).
But that is neither here nor there, a beta is a beta is a beta, so asking if there are any problems before you are going to install it is crazy (your system configuration is likely to differ). You either accept the fact that beta builds may have issues and get on with it or you simply wait until the regular release if you can’t accept that.
Same here, autosandbox works on D drive but not on C drive. Both are on same disk.
Drive C → No autosandbox prompt, no sandboxing
Drive D → Autosandbox working normally
RAM drive (R:) → Autosandbox prompt appears, no sandboxing
USB thumb drive (F:) → Autosandbox working normally
Edit:
Huh, I found something strange…
2011/11/27 1:20:35 Autosandbox candidate: C:\autosandboxme.exe
[Source: local://*C:\windows\explorer.exe ]
[Opened by: C:\windows\explorer.exe]
--> Result: Not sandboxing (because the file is trusted).