Sorry, but you obviously don't get the concept.
Suppose for a while that the autosandbox wasn't there at all - so you'd be saying "running an executable is a security risk, because we don't know (in advance) whether the file system shield will detect it" (and you might be right, but that doesn't really help).
With autosandbox, it's the same - you don't know whether the executable you are running will actually be autosandboxed, it might be started normally.
And when it actually is autosandboxed, it doesn't mean that it's bad in any way. When the autosandbox scan finds the file clean, then it offers the possibility to run the file normally - that's the logical conclusion. The initial decision (whether to autosandbox the file or not) is just a coarse pre-filter for the autosandbox scan - it will, and should, place also clean files there.
So I repeat what I've said previously - autosandbox has been turned into a scanning method (quite different from the other methods avast! uses) for executable files. Perhaps we should have renamed it, because "autosandbox" might be a bit confusing now. Something along the lines of "dynamic scan" would describe the feature better.
If you want every file you start to be run in a sandbox, then I suggest to get yourself a full/manual sandbox - avast's or other, doesn't matter. But that isn't an option for ordinary users, sandboxing every possible file isn't acceptable - you lose your work (that you might have done inside the sandboxed application), installers get broken, complex things simply don't work, etc.
