AutoSandbox Test Tool

[Forest61]

Yep, this works great! Thanks, Vlk and AVAST team! I think this is a great addition to the program.

[EmoHobo]

I downloaded this, ran it in sanbox, checked the C: location found nothing, however in my registry I found an entry saying if I see this the sandbox failed.

Does that mean I did something wrong?  I haven't changed any settings for the autosandbox and I enabled it.

[rambo1940]

Isn't it amazing.
Whenever you need a serious question answered you can't see a dev for miles.
And also you can't even an answer for the ticket you have written to the support dept.
No matter what you think of Zone Alarm and Comodo at least they replied to your questions.
I take a very dim view of the service from Avast.

[Hermite15]

Isn't it amazing.
Whenever you need a serious question answered you can't see a dev for miles.
And also you can't even an answer for the ticket you have written to the support dept
They will take you money but the backup is dreadful.
No matter what you think of Zone Alarm and Comodo at least they replied to your questions.
I take a very dim view of the service from Avast.

I wouldn't use that tone about the Avast team but I got to admit that there's actually almost no Avast presence on the forums when there's no beta testing.

[rambo1940]

I did get a reply from the Support Dept
It said make sure Auto Sandbox is enabled which it is by default.
lets see if anybody comes up with an answer which works.
To my mind Auto Sandbox and WebRep are just not working
Regards

[jafTwo]

This is kind of conflicting information.  The first post in this thread mentions it should work on all operating systems, but I was told to disable autosandbox if I'm running winXP x64.

[DavidR]

Well that was because that generally it does work on all supported OSes, like it works with win7 64bit. But for some unforeseen reason it doesn't appear to work with XP Pro 64bit, now I don't know the reason for this. But I have a suspicion as the XP Pro 64bit version is based on the windows 2003 server version and I think that it is this being based on a server OS version where the problem may be.

Not to mention that the user base of XP Pro 64bit must be very small, so it may not have been found during alpha, beta and pre-release versions of avast6 with the autosandbox feature. So it appears that it is only since the introduction of this test file which has brought this to light.

[Rednose]

That the Avast! Sandbox, and so also the AutoSandbox, is not compatible with Win XP 64 ( neither is Sandboxie ) is not unforseen, but has to do with the architecture of Win XP 64. Petr Kurtin ( Avast! Sandbox Developer ) once explained it to me, and I beleve he did also here on the forum, but I can't dig it up right now

Greetz, Red.

[Rednose]

Yes, I found the email from Petr in which he told me that the sandbox (= autosandbox, sandbox, safezone) isn’t supported on WinXP 64-bit. But I can't find the technical explanation he gave me and/or on the forum, and that really irritates me

Greetz, Red.

[MAG]

Tried it on my w7 64 bit system, and it worked fine.

Interestingly (though perhaps not to many in this forum) avast autosandbox got in before D+.

D+ didn't kick-in until the attempt to modify the registry.

[happy avast user]

Hi all,

Please could anyone let me know how I could check and see if AutoSandbox test tool is running in my Registry thank you in advance.

happy avast user.

[Zyndstoff (aka Steven Gail)]

You can not see if the test-tool is running in your registry, because the test-tool does not register.

The tool only runs if you start it - and then you know that it is running.

I do not get the deeper meaning of your question maybe..?

[happy avast user]

Ok Thank you very much for your reply to my question, I really appreciate it

[MAG]

Tried it on my w7 64 bit system, and it worked fine.

Interestingly (though perhaps not to many in this forum) avast autosandbox got in before D+.

D+ didn't kick-in until the attempt to modify the registry (when I clicked the Modify System button in the red border box).

OK, so now I ran the test on my xp machine.

The autosandbox kicked in as expected, the box with Modify System came up in a red border when I accepted the Recommendation.

This time though, when I clicked Modify System, D+ didn't kick in to warn of an attempt to modify registry.

I am a bit confused (not uncommon) by the difference betweeen the W7 and xp system responses, but I wonder if the autosandbox on my W7 64bit machine is a bit leaky, whereas on xp it is watertight?

(otherwise why should D+ see an attempt to modify registry by a program that is running in a sandbox?)

Any thoughts?

Edit:
I set D+ to allow, and no system change was actually made (no text file added to C and no registry entry).

So, whilst I am still not quite sure what was going on with D+, the autosandbox seems to work fine!

Further Edit:
Looking a bit more closely I see that D+ was actually alerting on the attempt to modify the sandbox registry entry aswSnx privatestorage, not the entry that the tool asked us to check.

[MAG]

Hi all,

Please could anyone let me know how I could check and see if AutoSandbox test tool is running in my Registry thank you in advance.

happy avast user.

Did you want to look at the registry to see if it has been modified?

If so (being very careful not to modify anything) you could open regedit and look under HK current user to the entry  advised by the tool (I've just shut it down, but I think it was software\microsoft\windows\currentversion\run)