AutoSandbox Test Tool

[rambo1940]

Thanks

[Asyn]

Thanks

You're welcome..!
Hope your problem can be solved asap.
asyn

[YoKenny]

I have two computers,
One with XP home 32 bit
The other Windows 7 Home Premium 32 bit
AutoSandbox does not work on either.
I have version 6.0.1091 on both

You can add both systems in your signature like I have.

The AutoSandbox Test Tool works just fine on both my systems.

[rambo1940]

I know it should work it just doesn't.
perhaps some informed person will tell me why not
I cannot, surely, be the only person who has this problem.
Regards.

[Asyn]

I know it should work it just doesn't.
perhaps some informed person will tell me why not
I cannot, surely, be the only person who has this problem.
Regards.

Even, if you should be the only person, it wouldn't help you much, would it..?
Hope you will receive some help/feedback soon.
Have a nice weekend,
asyn

[rambo1940]

Happy Easter and thanks

[Asyn]

Happy Easter and thanks

Happy Easter to you, too.
asyn

[Gopher John]

I ran the AutoSandbox Test Tool from a limited user account and allowed it to be sandboxed.  No text file was created nor was the indicated HKCU key added.  However, there was another registry entry created.  I ran RegEdit non-virtualized from a Command Prompt to search for autosandboxtest.  I am running Avast Free.

Code: [Select]

[HKEY_USERS\__aswSnx private storage\autosandboxme.e_{c7a72eef-6d06-11e0-aa17-0013200b7107}\Registry\USER\S-1-5-21-2232638717-1984840243-2864733914-1005\SofTWare\MicROSoft\WinDOws\CurRENTVERsion\Run]
"autosandboxtest"="If you can see this text even from a non-virtualized application then the application (avast! autosandboxme) wasn't sandboxed properly."

[Nesivos]

I regret that as far as i am concerned AutoSandbox does not work.
Not once has it run when i have installed a new program
when i run the test tool all i get is "Modify the system"
So much for a test tool.
I have posted this before but have not had any explanation.
I would very much like to know if it is working.

1.  Avast ASB will only ask if you run a "suspicious program".  So just because ASB doesn't come up when you have it set to the default "Ask" mode and you run an executable does not mean that it is not working

2. As far as the box around the message "Modify the system".  I suggest you go back and run the tool again.  This time look more closely.  If the box really not there, and it should be in "red" then maybe the issue is with how your computer displays certain images on the monitor.  

I would not suggest further testing of ASB by downloading and running a known suspicious or infected executable.

[Asyn]

1.  Avast ASB will only ask if you run a "suspicious program".  So just because ASB doesn't come up when you have it set to the default "Ask" mode and you run an executable does not mean that it is not working

He did use the testing tool.

[NON]

I ran the AutoSandbox Test Tool from a limited user account and allowed it to be sandboxed.  No text file was created nor was the indicated HKCU key added.  However, there was another registry entry created.  I ran RegEdit non-virtualized from a Command Prompt to search for autosandboxtest.  I am running Avast Free.

Code: [Select]

[HKEY_USERS\__aswSnx private storage\autosandboxme.e_{c7a72eef-6d06-11e0-aa17-0013200b7107}\Registry\USER\S-1-5-21-2232638717-1984840243-2864733914-1005\SofTWare\MicROSoft\WinDOws\CurRENTVERsion\Run]
"autosandboxtest"="If you can see this text even from a non-virtualized application then the application (avast! autosandboxme) wasn't sandboxed properly."

That is the "virtualized" registry entry (__aswSnx private storage), I also has this entry with admin account while test tool is running. Once test tool was closed the entry disappear.
Your entry does not disappear after closing all sandboxed application?

[Gopher John]

I ran the AutoSandbox Test Tool from a limited user account and allowed it to be sandboxed.  No text file was created nor was the indicated HKCU key added.  However, there was another registry entry created.  I ran RegEdit non-virtualized from a Command Prompt to search for autosandboxtest.  I am running Avast Free.

Code: [Select]

[HKEY_USERS\__aswSnx private storage\autosandboxme.e_{c7a72eef-6d06-11e0-aa17-0013200b7107}\Registry\USER\S-1-5-21-2232638717-1984840243-2864733914-1005\SofTWare\MicROSoft\WinDOws\CurRENTVERsion\Run]
"autosandboxtest"="If you can see this text even from a non-virtualized application then the application (avast! autosandboxme) wasn't sandboxed properly."

That is the "virtualized" registry entry (__aswSnx private storage), I also has this entry with admin account while test tool is running. Once test tool was closed the entry disappear.
Your entry does not disappear after closing all sandboxed application?

It persisted for several minutes at least.  I was able to find it although the AutoSandbox Test Tool was already closed.  Now, it is no longer there, >6 hours later.  It likely takes a few minutes to clean house.  Also, RegEdit likely was displaying it from the opened state, even though the cleanup had already occurred.  I exited RegEdit without saving, so that didn't alter anything.

I knew that __aswSnx had to do with Avast Sandbox.  The (avast! autosandboxme) wasn't sandboxed properly is what I am questioning.

[NON]

I knew that __aswSnx had to do with Avast Sandbox.  The (avast! autosandboxme) wasn't sandboxed properly is what I am questioning.

Registry accesses from sandboxed application are redirected into __aswSnx entry, as well as text file creation (redirected to "aswSnx private storage" directory).
So I think your sandbox is working properly.

[MayuraDeSilva]

Yep, its working out here... AutoSandboxing

[rambo1940]

Somebody surely must be able to answer my question
Devs?