Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Vlk on April 20, 2011, 11:51:11 AM

Title: AutoSandbox Test Tool
Post by: Vlk on April 20, 2011, 11:51:11 AM
Hi guys,

In case anyone is interested, here's a test tool that you can be used to test the avast! autosandbox feature.

http://public.avast.com/dev/autosandboxme.exe


It's a tiny program that creates a file in the root of disk C:\ and in the registry Run key.
Avast should trigger the autosandbox feature on this file, so you can test whether the feature is working as expected (in the latest version 6.0.1091, it should work on all supported OSes). If the file is not autosandboxed, there may be some problem.

Thanks
Vlk
Title: Re: AutoSandbox Test Tool
Post by: Zyndstoff (aka Steven Gail) on April 20, 2011, 11:52:56 AM
Vlk, I love you!

Thx.
Title: Re: AutoSandbox Test Tool
Post by: Yanto.Chiang on April 20, 2011, 11:56:29 AM
Hi Ondrej,

Great and nice tool, have tested and running well.

Title: Re: AutoSandbox Test Tool
Post by: logos on April 20, 2011, 12:01:25 PM
okay... will give it a shot...
Title: Re: AutoSandbox Test Tool
Post by: jrace on April 20, 2011, 12:04:37 PM


Perfect - works as advertised  :D!

Title: Re: AutoSandbox Test Tool
Post by: logos on April 20, 2011, 12:06:00 PM
seems to work fine here...
Title: Re: AutoSandbox Test Tool
Post by: Vlk on April 20, 2011, 12:18:05 PM
Vlk, I love you!

Thx.

Uh oh, I hope my wife's not watching... ;)
Title: Re: AutoSandbox Test Tool
Post by: Zyndstoff (aka Steven Gail) on April 20, 2011, 12:20:42 PM
Vlk, I love you!

Thx.

Uh oh, I hope my wife's not watching... ;)

She would understand me for sure. She loves you too.  ;D
Title: Re: AutoSandbox Test Tool
Post by: Silk0 on April 20, 2011, 12:51:09 PM
avast! AutoSandbox appeared up and I've selected to Cancel the opening of the app.

Result: Sucess!

Great job.  ;)
Title: Re: AutoSandbox Test Tool
Post by: spg SCOTT on April 20, 2011, 12:59:32 PM
I tried this out on another computer, and was wondering why it didn't bring an alert...took me a while to work out avast wasn't on it ;D

Works on an avast machine though :P
Title: Re: AutoSandbox Test Tool
Post by: Dwarden on April 20, 2011, 02:03:02 PM
yep seems work fine and as intended
Title: Re: AutoSandbox Test Tool
Post by: Ashish Singh on April 20, 2011, 02:07:12 PM
Working here.....Changes are made without sandbox but no change when sandboxed  ;D
Title: Re: AutoSandbox Test Tool
Post by: SpeedyPC on April 20, 2011, 02:55:22 PM
Vlk, I love you!

Thx.

Me too I wanna give him a big  :-*
Title: Re: AutoSandbox Test Tool
Post by: NON on April 20, 2011, 03:02:59 PM
Thanks for the tool! It's working great 8)
Title: Re: AutoSandbox Test Tool
Post by: sded on April 20, 2011, 03:34:31 PM
Does not work for me.
COCKPIT ERROR:  I see that with the Opera dialog I was just downloading it, not executing, so when I selected the right answer it worked.  But when I selected "don't execute", I got a BSOD as a bonus.  Will send the minidump to you.
sded_ASBtest.dmp
Title: Re: AutoSandbox Test Tool
Post by: YoKenny on April 20, 2011, 03:42:55 PM
It works well on both of my systems.  8)
Title: Re: AutoSandbox Test Tool
Post by: happy avast user on April 20, 2011, 04:03:20 PM
Hi Vlk,

Auto sandbox working fine fine for me did test and Auto Sandbox popped up and asked me and gave the recommendation.

Thank you. 
Title: Re: AutoSandbox Test Tool
Post by: pk on April 20, 2011, 04:07:22 PM
sded_ASBtest.dmp

thanks, fixed (as a workaround you can turn sandbox logging off: sandbox / expert settings / report file)
Title: Re: AutoSandbox Test Tool
Post by: Qwertz321 on April 20, 2011, 05:05:10 PM
works great! thank you very much to share the internal tool!!!
Title: Re: AutoSandbox Test Tool
Post by: Llanziel on April 20, 2011, 05:14:19 PM
Ummm! avast! put this text log in LocalDisk, what exactly is this? It failed?

edit: WinXP SP3
Title: Re: AutoSandbox Test Tool
Post by: pk on April 20, 2011, 05:17:19 PM
@Llanziel: what's your avast version (build number)? thanks
Title: Re: AutoSandbox Test Tool
Post by: hayc59 on April 20, 2011, 05:25:41 PM
vlk, this does not work for the free version correct?
thank you  8)
Title: Re: AutoSandbox Test Tool
Post by: davexnet on April 20, 2011, 05:33:57 PM
I haven't tested this program yet, but I got a sandbox alert when I tried to uninstall
my PC TV tuner card from add/remove programs.  I assume it's a false positive?

What criteria does Avast use to sandbox a program?  I later ran a scan on the uninstall folder and it
didn't detect anything.
Title: Re: AutoSandbox Test Tool
Post by: DavidR on April 20, 2011, 05:38:32 PM
vlk, this does not work for the free version correct?
thank you  8)

Since the auto-sandbox in the free and paid versions are the same it works in all versions.

Edit: See images from my running it on avast! 6.0.1091 free.

Note: my firewall also chimed in between images 1 & 3 on permissions for autosandboxme.exe.
Title: Re: AutoSandbox Test Tool
Post by: Llanziel on April 20, 2011, 05:40:23 PM
@Llanziel: what's your avast version (build number)? thanks

6.0.1091 (installed from scratch yesterday) autosandbox is in auto mode
Title: Re: AutoSandbox Test Tool
Post by: Asyn on April 20, 2011, 05:45:58 PM
Thanks for this testing tool...!! :)
Works as expected.
asyn

PS: Also D+ did catch it. ;)
Title: Re: AutoSandbox Test Tool
Post by: hayc59 on April 20, 2011, 05:56:16 PM
@DavidR...thank you  ;D
your a daisy!!
Title: Re: AutoSandbox Test Tool
Post by: DavidR on April 20, 2011, 06:00:33 PM
You're welcome.
Title: Re: AutoSandbox Test Tool
Post by: hayc59 on April 20, 2011, 06:13:15 PM
Ok tht was cool!!
using free you dont get the sndbox feature that often ;)

First Pop-Up...OA---Hit Allowed
(http://i.imgur.com/FMCC1.jpg)
Second Pop
(http://i.imgur.com/CtcLp.jpg)
Third Pop
(http://i.imgur.com/ciu1x.jpg)
Title: Re: AutoSandbox Test Tool
Post by: Dieselman on April 20, 2011, 06:16:12 PM
Gotta love OA's gigantic yet annoying and informative pop ups.
Title: Re: AutoSandbox Test Tool
Post by: hayc59 on April 20, 2011, 06:17:54 PM
Gotta love OA's gigantic yet annoying and informative pop ups.
I dont get them very often but
if its early in the morning
it will scare the shit outta of U...hehehe
Title: Re: AutoSandbox Test Tool
Post by: danny96 on April 20, 2011, 06:21:01 PM
Are the registry keys also gone when program opened in sandbox?
Title: Re: AutoSandbox Test Tool
Post by: Dieselman on April 20, 2011, 06:21:39 PM
Just too much for me. Like Comodo. This test is also good for anyone running Sandboxie or BufferZone.
Title: Re: AutoSandbox Test Tool
Post by: Dieselman on April 20, 2011, 06:22:41 PM
Are the registry keys also gone when program opened in sandbox?

Look for yourself. If it was opened up and run inside then sandbox it will actually not be there when you close it out.
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 20, 2011, 06:24:07 PM
All i get is a notice which says "modify the system"
Please can i have some guidance
thank you
Title: Re: AutoSandbox Test Tool
Post by: Dieselman on April 20, 2011, 06:26:30 PM
Your suppose to click it..................Download the program. Run it. Open it inside Avast's sandbox. Now you will see a red box around "modify". Now click modify. Here let me click my Staples Easy Button.
Title: Re: AutoSandbox Test Tool
Post by: igor on April 20, 2011, 06:31:29 PM
Well, the main purpose of this tool (internally) wasn't really to test the sandbox functionality - but rather the autosandbox part, i.e. that avast! offers you to sandbox it on execution. The rest is... kind of a side effect (i.e. please don't consider it a comprehensive sandbox testing tool :)).
Title: Re: AutoSandbox Test Tool
Post by: Dieselman on April 20, 2011, 06:33:32 PM
Well, the main purpose of this tool (internally) wasn't really to test the sandbox functionality - but rather the autosandbox part, i.e. that avast! offers you to sandbox it on execution. The rest is... kind of a side effect (i.e. please don't consider it a comprehensive sandbox testing tool :)).

Exactly. Its more like a drop my rights then a full fledged virtualzation program.
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 20, 2011, 06:37:53 PM
All i get is a notice which says "modify the system"
Please can i have some guidance
thank you

Can you please expand.
I have downloaded the tool and tried to run it.
That's when i get the "modify" notice
Title: Re: AutoSandbox Test Tool
Post by: RejZoR on April 20, 2011, 07:00:19 PM
Vlk, i'm writing a tutorial on how to use this tool for our distributor, but i'd prefer if there is any way to make it a two steep test where test tool itself checks the presence of these hardcoded values. Would that be possible?
So that program checks if the values were in fact written to a physical HDD. If yes, show warning that AutoSandbox is not working properly and if it doesn't find them, show a green checkmark that everything seems to be in order.
Just a thought. It's still a very useful tool for diagnostics.
Title: Re: AutoSandbox Test Tool
Post by: Vlk on April 20, 2011, 07:12:54 PM
Well, the main purpose of this tool (internally) wasn't really to test the sandbox functionality - but rather the autosandbox part, i.e. that avast! offers you to sandbox it on execution. The rest is... kind of a side effect (i.e. please don't consider it a comprehensive sandbox testing tool :)).

Exactly. Its more like a drop my rights then a full fledged virtualzation program.

Can you please explain what you mean? Avast sandbox is definitely not a drop my rights -like thing.
Title: Re: AutoSandbox Test Tool
Post by: Vlk on April 20, 2011, 07:13:51 PM
Vlk, i'm writing a tutorial on how to use this tool for our distributor, but i'd prefer if there is any way to make it a two steep test where test tool itself checks the presence of these hardcoded values. Would that be possible?
So that program checks if the values were in fact written to a physical HDD. If yes, show warning that AutoSandbox is not working properly and if it doesn't find them, show a green checkmark that everything seems to be in order.
Just a thought. It's still a very useful tool for diagnostics.

Not quite possible from inside autosandboxme.ext as the program sees the changes there. You'd need to have a second process (not sandboxed) that would check if the changes were made to the real system.
Title: Re: AutoSandbox Test Tool
Post by: RejZoR on April 20, 2011, 07:20:53 PM
I was thinking of something like this. You have a test tool that then spawns another EXE which actually triggers AutoSandbox. As far as i understand the sandbox anbd its chain of sandboxing, in this case the main tool would not be sandboxed but the newly spawned EXE would be. Then the main test tool would check for the presence of that file and registry value. If found, Sandbox is not working. If not found, sandbox is working fine.
It's just that you'd have to figure out how to make timings and stuff like that to properly connect spawning and checking part so they would be properly correct and not try to check before it would actually spawn the new file/reg value. In theory you should only check the physical locations and if test data is not found there, it's fine.
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 20, 2011, 07:21:53 PM
All i get is a notice which says "modify the system"
Please can i have some guidance
thank you

Can you please expand.
I have downloaded the tool and tried to run it.
That's when i get the "modify" notice

Can somebody please tell me how you open the file in autosandbox.
Thank you
Title: Re: AutoSandbox Test Tool
Post by: Dieselman on April 20, 2011, 07:44:46 PM
Already gave you instructions. When you see "modify" just click it. It's that easy.


Vlk ......I said like a drop my rights. Full virtualzation cannot be obtained in a 64 but OS unless you can by pass patch guard.
Title: Re: AutoSandbox Test Tool
Post by: igor on April 20, 2011, 07:46:40 PM
I was thinking of something like this. You have a test tool that then spawns another EXE which actually triggers AutoSandbox. As far as i understand the sandbox and its chain of sandboxing, in this case the main tool would not be sandboxed but the newly spawned EXE would be. Then the main test tool would check for the presence of that file and registry value. If found, Sandbox is not working. If not found, sandbox is working fine.
It's just that you'd have to figure out how to make timings and stuff like that to properly connect spawning and checking part so they would be properly correct and not try to check before it would actually spawn the new file/reg value. In theory you should only check the physical locations and if test data is not found there, it's fine.

Well yes, that would be possible (as for the timings, it would be best simply to wait for the spawned process to terminate.
However, keep in mind that it's more a test of the sandbox than autosandbox - in real life, you don't have control of whether you get the autosandbox offer for the particular file or not.
(Basides, I'm kinda scared when I read about "writing tutorials about using this tool"... it's just an artificial example that triggers the autosandboxing heuristics, no big deal - while it seems to be handled like some complex pen-testing tool ;))

Can somebody please tell me how you open the file in autosandbox.
Thank you

There is no "how" - you just execute it.
Title: Re: AutoSandbox Test Tool
Post by: Nesivos on April 20, 2011, 07:55:27 PM
Downloaded and ran the tool on all three of my computers.

On two of them a got message "Modify the System" which had the sandbox lines around them.

On the third computer I got the following message.

Quote
Congratulations Loyal Avast Customer.

You have won an all-paid two weeks vacation in beautiful Prague, Czech Republic.

Please contact us with the Loyalty code number that is on your screen and your Avast customer number to receive your all expenses paid travel packet.

Offer good through 31, December 2011

Thanks again for being a loyal Avast customer.
[/i]
Title: Re: AutoSandbox Test Tool
Post by: gautam7 on April 20, 2011, 08:01:06 PM
well when i clicked modify it went all black with a red border. Does this suppose to happen when a real danger run inside a sandbox. I am asking because untill now whenever i run some suspicious program inside the sandbox nothing seemed to happen.
Title: Re: AutoSandbox Test Tool
Post by: Desirae Spencer on April 20, 2011, 08:03:01 PM
Doesn't Avast! auto-sandbox support Chinese path? It's failed. :o
Title: Re: AutoSandbox Test Tool
Post by: Asyn on April 20, 2011, 08:04:36 PM
On the third computer I got the following message.

Congrats. :)
Title: Re: AutoSandbox Test Tool
Post by: igor on April 20, 2011, 08:09:34 PM
Doesn't Avast! auto-sandbox support Chinese path? It's failed. :o

Can you be more specific, please?
What exactly was the path you started it from? What operating system?
Title: Re: AutoSandbox Test Tool
Post by: Desirae Spencer on April 20, 2011, 08:40:04 PM
Can you be more specific, please?
What exactly was the path you started it from? What operating system?

Auto-sandbox doesn't trigger when I run the "AutoSandbox Test Tool" on my Desktop. (桌面; desktop in Chinese)
C:\Documents and Settings\Administrator\桌面\autosandboxme.exe

But it works fine at C:\autosandboxme.exe

Windows XP SP3
Title: Re: AutoSandbox Test Tool
Post by: jrace on April 20, 2011, 08:41:16 PM
Could anybody tell me what actually the trigger is for the Auto-Sandbox because when I try to execute "EasyBCD 2.0.2.exe" (installation file of program "easyBCD") the Auto-Sandbox is triggered  ??? ??? ??? ?

Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 20, 2011, 08:49:45 PM
I was thinking of something like this. You have a test tool that then spawns another EXE which actually triggers AutoSandbox. As far as i understand the sandbox and its chain of sandboxing, in this case the main tool would not be sandboxed but the newly spawned EXE would be. Then the main test tool would check for the presence of that file and registry value. If found, Sandbox is not working. If not found, sandbox is working fine.
It's just that you'd have to figure out how to make timings and stuff like that to properly connect spawning and checking part so they would be properly correct and not try to check before it would actually spawn the new file/reg value. In theory you should only check the physical locations and if test data is not found there, it's fine.

Well yes, that would be possible (as for the timings, it would be best simply to wait for the spawned process to terminate.
However, keep in mind that it's more a test of the sandbox than autosandbox - in real life, you don't have control of whether you get the autosandbox offer for the particular file or not.
(Basides, I'm kinda scared when I read about "writing tutorials about using this tool"... it's just an artificial example that triggers the autosandboxing heuristics, no big deal - while it seems to be handled like some complex pen-testing tool ;))

Can somebody please tell me how you open the file in autosandbox.
Thank you

There is no "how" - you just execute it.

Thanks
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 20, 2011, 08:57:08 PM
When i try to run the tool.
I get "Modify the System"
If i click on that.i get
If i click on OK nothing happens
Please may i have some advice please
Title: Re: AutoSandbox Test Tool
Post by: Asyn on April 20, 2011, 08:58:20 PM
When i try to run the tool.
I get "Modify the System"
If i click on that.i get

Good, that's how it should work. ;)
Wait, do you mean the Autosandbox didn't jump in..??
Title: Re: AutoSandbox Test Tool
Post by: bogdan_77 on April 20, 2011, 08:59:50 PM
Hi, I`m new on this forum and first of all I want to thank Avast for the great program. The test tool works fine ( after I let it through Comodo Defense+ and Zemana  ;D). Once again, thank you Avast and keep up the good work.
Title: Re: AutoSandbox Test Tool
Post by: Zyndstoff (aka Steven Gail) on April 20, 2011, 09:01:23 PM
Yep...

Run sandoxed: no modifications made.
Run without sandbox: you will find those modifications.

But yes, it would have been nice if a little explanation was found in that pop-up so a new user would know what the right / wrong outcome should be.
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 20, 2011, 09:10:07 PM
It would appear as if AutoSandbox just does not work
Title: Re: AutoSandbox Test Tool
Post by: Zyndstoff (aka Steven Gail) on April 20, 2011, 09:30:02 PM
Now I am confused.

I run the Autosandboxme.exe
Autosandbox kicks in, I select "open normally".
The next window with the modify-button shows "Autosandbox" in it's title...? I selected "open normally", why Sandbox?
I click the button and the window "Check for..." appears.
I click ok and check for changes: none.

Shouldn't the cahanges appear when selecting "open normally"?

 ??? ??? ??? ???
Title: Re: AutoSandbox Test Tool
Post by: Zyndstoff (aka Steven Gail) on April 20, 2011, 09:31:34 PM
2
Title: Re: AutoSandbox Test Tool
Post by: Zyndstoff (aka Steven Gail) on April 20, 2011, 09:32:12 PM
3
Title: Re: AutoSandbox Test Tool
Post by: Zyndstoff (aka Steven Gail) on April 20, 2011, 09:35:07 PM
The registry key however is created...
Title: Re: AutoSandbox Test Tool
Post by: Excess on April 20, 2011, 09:36:05 PM
Not working...
Avast! doesn't ask me to load the program in the autosandbox, I checked my options 3 times, everything is OK.
Title: Re: AutoSandbox Test Tool
Post by: igor on April 20, 2011, 09:36:38 PM
Zyndstoff: If you've got any kind of UAC enabled, it probably won't work (or rather, the file operation might get virtualized by UAC).
The registry operation, going into HKCU, will succeed.
Title: Re: AutoSandbox Test Tool
Post by: Dieselman on April 20, 2011, 09:37:04 PM
The registry key however is created...

Do you have a screen shot of the key string created?
Title: Re: AutoSandbox Test Tool
Post by: Zyndstoff (aka Steven Gail) on April 20, 2011, 09:39:56 PM
The registry key however is created...

Do you have a screen shot of the key string created?

I already deleted it. Why?
Title: Re: AutoSandbox Test Tool
Post by: Zyndstoff (aka Steven Gail) on April 20, 2011, 09:42:04 PM
Zyndstoff: If you've got any kind of UAC enabled, it probably won't work (or rather, the file operation might get virtualized by UAC).
The registry operation, going into HKCU, will succeed.

Igor,

is this unique to this testprog?
Or will this happen everytime I select a program to run normally when AutoSB kicks in? That would be a bug...

Yes, I have Win 7 UAC active.
Title: Re: AutoSandbox Test Tool
Post by: igor on April 20, 2011, 09:47:25 PM
is this unique to this testprog?
Or will this happen everytime I select a program to run normally when AutoSB kicks in? That would be a bug...

Yes, I have Win 7 UAC active.

It's got nothing to do with the testprog, nor with autosandbox, nor with avast! - it's just UAC. If a program (possibly only when running under admin, I'm not sure - but not elevated) tries to create files in folders normally inaccessible (e.g. C:\), or registry keys (HKLM\*) - the request somehow succeeds (from the program's point of view) - but the operation is virtualized, just like if it were running in a sandbox. So the file/registry key won't actually appear.
Title: Re: AutoSandbox Test Tool
Post by: Zyndstoff (aka Steven Gail) on April 20, 2011, 09:50:17 PM
The key does appear, the file doesn't...?
Strange - I never heard of this UAC behavior before.

So if I disable AutoSB and try the prog again - there will be no file in C:\ bevause of UAC?
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 20, 2011, 09:50:38 PM
When i try to run the tool.
I get "Modify the System"
If i click on that.i get

Good, that's how it should work. ;)
Wait, do you mean the Autosandbox didn't jump in..??


It did not
Title: Re: AutoSandbox Test Tool
Post by: igor on April 20, 2011, 09:54:03 PM
Actually, I may be wrong - I'm not sure when the operations get virtualized by UAC, and when they are simply blocked.
Possibly the creation of the file in the root of the C: drive is just blocked (and the tool, being really just a simply internal util, doesn't report any errors about that ;)). In any case, yes, it's UAC, and yes, it shouldn't appear even without autosandbox - unless you run the executable elevated.

The key is in HKCU, so UAC doesn't have any problems with that. If it went into HKLM instead, it should behave the same (as the file) I think.
Title: Re: AutoSandbox Test Tool
Post by: Zyndstoff (aka Steven Gail) on April 20, 2011, 10:00:58 PM
Actually, I may be wrong - I'm not sure when the operations get virtualized by UAC, and when they are simply blocked.
Possibly the creation of the file in the root of the C: drive is just blocked (and the tool, being really just a simply internal util, doesn't report any errors about that ;)). In any case, yes, it's UAC, and yes, it shouldn't appear even without autosandbox - unless you run the executable elevated.

The key is in HKCU, so UAC doesn't have any problems with that. If it went into HKLM instead, it should behave the same (as the file) I think.

Okay, the file is not created even without AutoSB.

Everything works as it should.

But: why didn't you choose a folder that would show the file created when "open normally" is selected. It's hard for a user to understand if the apparently anticipated outcome is not visible...

I'm an experienced user - but even I was astonished...
Title: Re: AutoSandbox Test Tool
Post by: igor on April 20, 2011, 10:34:38 PM
OK, I'll repeat it once again ;)
This is an internal tool that wasn't really meant for public (which doesn't mean it's any secret, just that it was build rather quickly, without any attempts to make it bulletproof or user friendly). You asked for it, so you got it... but there wasn't any additional time spent on that.

Its main purpose was to trigger the autosandbox pop-up, that's all - nobody actually used to it verify sandbox functionality (OK, maybe once, but that's really all). Red-framed window --> OK, no red frame --> something's wrong.

And even though I didn't write it myself, I certainly wouldn't notice the problem with C: drive - as disabling UAC is the first thing I do on my computers, I really can't live with that.
Title: Re: AutoSandbox Test Tool
Post by: Vlk on April 20, 2011, 10:36:56 PM
The one and only purpose of the tool was to trigger the AutoSandbox prompt.
Title: Re: AutoSandbox Test Tool
Post by: RejZoR on April 20, 2011, 11:01:00 PM
And to also verify if sandbox is in fact sandboxing :P It'll do the job as i've written a guide in our language on how to read and use this tool. It would be nice though if avast! had some sort of automated self-diagnostics that would be triggered in certain intervals to make sure that everything is really working as it should.
Title: Re: AutoSandbox Test Tool
Post by: jadinolf on April 20, 2011, 11:01:46 PM
Before this thread was begun, I copied the program PureRa onto a flash drive. I double clicked it and up came AutoSandbox.

Love it!
Title: Re: AutoSandbox Test Tool
Post by: DavidR on April 20, 2011, 11:31:01 PM
The one and only purpose of the tool was to trigger the AutoSandbox prompt.

Yes, a little bit like an eicar test file for the auto-sandbox ;D
Title: Re: AutoSandbox Test Tool
Post by: Dieselman on April 20, 2011, 11:34:53 PM
The one and only purpose of the tool was to trigger the AutoSandbox prompt.

But if the sandbox is working the registry string should not be there when we click modify.
Title: Re: AutoSandbox Test Tool
Post by: logos on April 20, 2011, 11:39:44 PM
The one and only purpose of the tool was to trigger the AutoSandbox prompt.

But if the sandbox is working the registry string should not be there when we click modify.

and guess what it's not, at least on my system...
Title: Re: AutoSandbox Test Tool
Post by: Dieselman on April 20, 2011, 11:47:54 PM
There were others that claimed it did. I will run the tool tonight.
Title: Re: AutoSandbox Test Tool
Post by: DavidR on April 21, 2011, 12:24:07 AM
The one and only purpose of the tool was to trigger the AutoSandbox prompt.

But if the sandbox is working the registry string should not be there when we click modify.

and guess what it's not, at least on my system...

It wasn't created on my system either.
Title: Re: AutoSandbox Test Tool
Post by: NON on April 21, 2011, 01:19:44 AM
The one and only purpose of the tool was to trigger the AutoSandbox prompt.

But if the sandbox is working the registry string should not be there when we click modify.

and guess what it's not, at least on my system...

It wasn't created on my system either.
+1

With UAC disabled, C:\autosandboxtest.txt is also created when I choose "Open normally".
Title: Re: AutoSandbox Test Tool
Post by: igor on April 21, 2011, 01:20:55 AM
Can you be more specific, please?
What exactly was the path you started it from? What operating system?

Auto-sandbox doesn't trigger when I run the "AutoSandbox Test Tool" on my Desktop. (桌面; desktop in Chinese)
C:\Documents and Settings\Administrator\桌面\autosandboxme.exe

But it works fine at C:\autosandboxme.exe

Windows XP SP3

What if you create the folder C:\桌面 (or something similar) and try to start it from there?
I mean, is it really because of the special characters, or is it rather the desktop itself, its name being actually unrelated?
Thanks.
Title: Re: AutoSandbox Test Tool
Post by: GrandPrixGXP on April 21, 2011, 02:11:51 AM
Works for me. A very good testing tool to prove that the sandbox does not allow a system change. I looked in C:............nothing. I looked in the registry nothing. All this after clicking modify. So proof that it work. Nice job Avast team.
Title: Re: AutoSandbox Test Tool
Post by: shek on April 21, 2011, 03:14:57 AM
Can you be more specific, please?
What exactly was the path you started it from? What operating system?

Auto-sandbox doesn't trigger when I run the "AutoSandbox Test Tool" on my Desktop. (桌面; desktop in Chinese)
C:\Documents and Settings\Administrator\桌面\autosandboxme.exe

But it works fine at C:\autosandboxme.exe

Windows XP SP3

What if you create the folder C:\桌面 (or something similar) and try to start it from there?
I mean, is it really because of the special characters, or is it rather the desktop itself, its name being actually unrelated?
Thanks.

The autosandbox works fine in my computer, win7HP 64 bit sp1, no matter the path containing Chinese characters or not. I even changed the test file name to Chinese, auto sandbox window still pops up.
Title: Re: AutoSandbox Test Tool
Post by: Zyndstoff (aka Steven Gail) on April 21, 2011, 07:12:33 AM
There were others that claimed it did. I will run the tool tonight.

You refer to my post?

I did not claim that: I wrote the file was not created, the Reg key was when run normally was chosen.
Title: Re: AutoSandbox Test Tool
Post by: Zyndstoff (aka Steven Gail) on April 21, 2011, 07:17:46 AM
OK, I'll repeat it once again ;)
This is an internal tool that wasn't really meant for public (which doesn't mean it's any secret, just that it was build rather quickly, without any attempts to make it bulletproof or user friendly). You asked for it, so you got it... but there wasn't any additional time spent on that.

Its main purpose was to trigger the autosandbox pop-up, that's all - nobody actually used to it verify sandbox functionality (OK, maybe once, but that's really all). Red-framed window --> OK, no red frame --> something's wrong.

And even though I didn't write it myself, I certainly wouldn't notice the problem with C: drive - as disabling UAC is the first thing I do on my computers, I really can't live with that.

Igor,
don't get angry at me.  ;D

This little tool is handy just to quick-test the AutoSB. I did not know the fact that UAC prevents the writing of the file, that's what confused me.

As to the disabling of UAC - isn't that something that increases your security? I'm using Win 7, and it is set to low (or whatever the setting is called...) and I don't find it too disturbing.
Title: Re: AutoSandbox Test Tool
Post by: Desirae Spencer on April 21, 2011, 08:00:24 AM
Can you be more specific, please?
What exactly was the path you started it from? What operating system?

Auto-sandbox doesn't trigger when I run the "AutoSandbox Test Tool" on my Desktop. (桌面; desktop in Chinese)
C:\Documents and Settings\Administrator\桌面\autosandboxme.exe

But it works fine at C:\autosandboxme.exe

Windows XP SP3

What if you create the folder C:\桌面 (or something similar) and try to start it from there?
I mean, is it really because of the special characters, or is it rather the desktop itself, its name being actually unrelated?
Thanks.

shek,
Oops! My mistake, you are right. Thanks. It's no matter the path containing Chinese characters or not.

igor,
The issue that avast! Auto-sandbox doesn't trigger on my Desktop  is caused by the software "Fences".
Thank you for your help.
Title: Re: AutoSandbox Test Tool
Post by: WSA on April 21, 2011, 08:50:02 AM
Great tools
it work.
if we run it in AutoSB no change will happen.
runnig in normally mode then Behavior shield alert about registry change and stop him but file in C:\ will copy.
Title: Re: AutoSandbox Test Tool
Post by: igor on April 21, 2011, 10:12:56 AM
As to the disabling of UAC - isn't that something that increases your security? I'm using Win 7, and it is set to low (or whatever the setting is called...) and I don't find it too disturbing.

Yes, and I didn't mean it as a suggestion ;)
It's just that my way of using the computer is probably slightly different from most people (copying files to system folder to check some avast! behavior, running special logging versions which create their log in C:\ for easier access, attaching a debugger to running processes... too much troubles with UAC :)).


igor,
The issue that avast! Auto-sandbox doesn't trigger on my Desktop  is caused by the software "Fences".
Thank you for your help.

Can you tell me something more about this software? What does it do, can it be downloaded somewhere?
Title: Re: AutoSandbox Test Tool
Post by: Zyndstoff (aka Steven Gail) on April 21, 2011, 10:14:23 AM
As to the disabling of UAC - isn't that something that increases your security? I'm using Win 7, and it is set to low (or whatever the setting is called...) and I don't find it too disturbing.

Yes, and I didn't mean it as a suggestion ;)
It's just that my way of using the computer is probably slightly different from most people (copying files to system folder to check some avast! behavior, running special logging versions which create their log in C:\ for easier access, attaching a debugger to running processes... too much troubles with UAC :)).


That's how I understood it.  ;D
Thx
Title: Re: AutoSandbox Test Tool
Post by: Zyndstoff (aka Steven Gail) on April 21, 2011, 10:15:47 AM
FENCES (http://www.stardock.com/products/fences/)

It's nice looking... maybe I'll try that...
Title: Re: AutoSandbox Test Tool
Post by: Desirae Spencer on April 21, 2011, 10:43:38 AM
igor,
The issue that avast! Auto-sandbox doesn't trigger on my Desktop  is caused by the software "Fences".
Thank you for your help.

Can you tell me something more about this software? What does it do, can it be downloaded somewhere?

Thank you, Zyndstoff. That is the software I use.

igor,
Fences (http://www.stardock.com/products/fences/index.asp) is a free desktop customization software and you can download it from their official website.
Title: Re: AutoSandbox Test Tool
Post by: GaAs on April 21, 2011, 01:41:54 PM
Hi All.
AutoSanbox test: ok here. :)
Title: Re: AutoSandbox Test Tool
Post by: Lisandro on April 21, 2011, 02:06:17 PM
The issue that avast! Auto-sandbox doesn't trigger on my Desktop  is caused by the software "Fences".
Thank you for your help.
Very strange... What does Fences have anything to do with autosandboxing not being triggered?
I use Fences and it never (it can't) block autosandoxing...
Title: Re: AutoSandbox Test Tool
Post by: GrandPrixGXP on April 21, 2011, 03:33:00 PM
Why uses Fences with Windows 7? Just pin everything to the superbar.
Title: Re: AutoSandbox Test Tool
Post by: Lisandro on April 21, 2011, 03:38:13 PM
Why uses Fences with Windows 7? Just pin everything to the superbar.
To hide icons on desktop? To group them?
Title: Re: AutoSandbox Test Tool
Post by: Flash999 on April 21, 2011, 03:42:17 PM
Great tool. Work perfect. AutoSandbox working.
Title: Re: AutoSandbox Test Tool
Post by: GrandPrixGXP on April 21, 2011, 03:48:08 PM
Everything I use daily is pinned. No desktop icons at all including the recycle bin. Just my wallpaper and forecast gadget.
Title: Re: AutoSandbox Test Tool
Post by: JuninhoSlo on April 21, 2011, 04:38:48 PM
Thank you for AutoSandobx Test my autosandobx works without any problems  :P
Title: Re: AutoSandbox Test Tool
Post by: Desirae Spencer on April 21, 2011, 05:11:50 PM
The issue that avast! Auto-sandbox doesn't trigger on my Desktop  is caused by the software "Fences".
Thank you for your help.
Very strange... What does Fences have anything to do with autosandboxing not being triggered?
I use Fences and it never (it can't) block autosandoxing...

Tech,

I've got no idea. :'(
1. The same file ( AutoSandbox Test Tool ) on Desktop but just in different way to appear. http://k.min.us/imXf60.png (http://k.min.us/imXf60.png)
2. Run the left one → AutoSandbox can't be triggered. http://k.min.us/inb4sW.png (http://k.min.us/inb4sW.png)
3. Run the right one → trigger the AutoSandbox pop-up and get message with red frame. http://k.min.us/inb61e.png (http://k.min.us/inb61e.png); http://k.min.us/inbvM0.png (http://k.min.us/inbvM0.png)
Title: Re: AutoSandbox Test Tool
Post by: spg SCOTT on April 21, 2011, 05:46:16 PM
kyokodash2, I can confirm the behaivior...with a similar fence setup and the tool inside or outside a fence autosandbox does not take any action - no red border.

Run from explorer, it generates an alert.

This is not limited to just the tool, but other things that generate alerts, like OTS. Behavior is the same with fences.

EDIT: Also...not just AutoSandbox tool :P (Doesn't happen every time though?)
Title: Re: AutoSandbox Test Tool
Post by: Lisandro on April 22, 2011, 01:13:26 AM
Thanks for this testing tool...!! :)
Works as expected.
PS: Also D+ did catch it. ;)
I didn't know you use D+ ::)
Title: Re: AutoSandbox Test Tool
Post by: Excess on April 22, 2011, 09:55:52 AM
Hello,

Same problem here, I use Fences, and when I run it directly from my fences desktop, Avast! doesn't ask me to run the test tool in the AutoSandbox, but when I go to the desktop by windows explorer and I run the test tool, everything is working well.
Title: Re: AutoSandbox Test Tool
Post by: Asyn on April 22, 2011, 10:24:24 AM
I didn't know you use D+ ::)

No..?
It's in my sig.
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 22, 2011, 10:46:51 AM
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.
Title: Re: AutoSandbox Test Tool
Post by: Asyn on April 22, 2011, 10:51:31 AM
I would very much like to know if it is working.

Have you set ASB to ask..?
Is there a red border around "Modify the system"..?
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 22, 2011, 10:56:07 AM
Thanks for your interest.
By default it is set to "Ask"
There is no border around "Modify the system"
Regards
Title: Re: AutoSandbox Test Tool
Post by: Asyn on April 22, 2011, 11:04:08 AM
Thanks for your interest.
By default it is set to "Ask"
There is no border around "Modify the system"
Regards

Well, it seems the ASB doesn't work on your system.
Which OS do you have, which avast..? (Would be good to add a sig.)

Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 22, 2011, 11:08:52 AM
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
Title: Re: AutoSandbox Test Tool
Post by: Asyn on April 22, 2011, 11:11:10 AM
And you tested it with version 6.0.1091..?
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 22, 2011, 11:14:20 AM
Sorry i forgot to mention which version.I have now modified my post
I have 6.0.1091 on both computers
Title: Re: AutoSandbox Test Tool
Post by: Asyn on April 22, 2011, 11:17:07 AM
Ok, have you other security related software on your machines..?
Interesting, that it doesn't work on both.
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 22, 2011, 11:24:24 AM
On XP i only have The Windows Firewall and on W7 the windows Firewall and Windows Defender but the real time is not active
I have AdMuncher on both.
Title: Re: AutoSandbox Test Tool
Post by: Asyn on April 22, 2011, 11:33:08 AM
On XP i only have The Windows Firewall and on W7 the windows Firewall and Windows Defender but the real time is not active
I have AdMuncher on both.

The Fws shouldn't be a problem.
Don't know if AdMuncher could block the ASB somehow..!??
The devs have to answer this.
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 22, 2011, 01:10:20 PM
I have tried disabling Admuncher it makes no difference
Where do we go from here.?
I really would like to get it sorted out
Regards
Title: Re: AutoSandbox Test Tool
Post by: Asyn on April 22, 2011, 01:18:10 PM
I have tried disabling Admuncher it makes no difference
Where do we go from here.?
I really would like to get it sorted out
Regards

As said, wait for a dev to answer.
Sorry, I can't help you here.
asyn
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 22, 2011, 01:25:07 PM
Will it get picked up on the Forum by a Dev or should i contact the Company for advice
Thanks
Title: Re: AutoSandbox Test Tool
Post by: Asyn on April 22, 2011, 01:28:33 PM
Will it get picked up on the Forum by a Dev or should i contact the Company for advice
Thanks

As this thread got started by Vlk and also other devs did already answer here, they'll see it. ;)
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 22, 2011, 01:31:02 PM
Thanks
Title: Re: AutoSandbox Test Tool
Post by: Asyn on April 22, 2011, 01:33:04 PM
Thanks

You're welcome..!
Hope your problem can be solved asap.
asyn
Title: Re: AutoSandbox Test Tool
Post by: YoKenny on April 22, 2011, 03:57:16 PM
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.
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 22, 2011, 07:17:17 PM
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.
Title: Re: AutoSandbox Test Tool
Post by: Asyn on April 22, 2011, 07:52:16 PM
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
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 22, 2011, 07:56:27 PM
Happy Easter and thanks
Title: Re: AutoSandbox Test Tool
Post by: Asyn on April 22, 2011, 07:58:53 PM
Happy Easter and thanks

Happy Easter to you, too. :)
asyn
Title: Re: AutoSandbox Test Tool
Post by: Gopher John on April 22, 2011, 08:21:55 PM
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."
Title: Re: AutoSandbox Test Tool
Post by: Nesivos on April 22, 2011, 08:41:27 PM
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. :)
Title: Re: AutoSandbox Test Tool
Post by: Asyn on April 22, 2011, 08:49:05 PM
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. ;)
Title: Re: AutoSandbox Test Tool
Post by: NON on April 23, 2011, 01:41:30 AM
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?
Title: Re: AutoSandbox Test Tool
Post by: Gopher John on April 23, 2011, 02:49:38 AM
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.
Title: Re: AutoSandbox Test Tool
Post by: NON on April 23, 2011, 04:34:19 AM
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.
Title: Re: AutoSandbox Test Tool
Post by: MayuraDeSilva on April 23, 2011, 08:40:17 AM
Yep, its working out here... AutoSandboxing :)
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 28, 2011, 01:29:32 PM
Somebody surely must be able to answer my question
Devs??????????
Title: Re: AutoSandbox Test Tool
Post by: Forest62 on April 29, 2011, 11:10:45 AM
Yep, this works great! Thanks, Vlk and AVAST team! I think this is a great addition to the program.
Title: Re: AutoSandbox Test Tool
Post by: EmoHobo on April 29, 2011, 02:08:14 PM
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.
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on April 29, 2011, 02:45:20 PM
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.
Title: Re: AutoSandbox Test Tool
Post by: logos on April 29, 2011, 03:04:23 PM
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.
Title: Re: AutoSandbox Test Tool
Post by: rambo1940 on May 03, 2011, 02:56:45 PM
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
Title: Re: AutoSandbox Test Tool
Post by: jafTwo on May 03, 2011, 11:51:11 PM
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.
Title: Re: AutoSandbox Test Tool
Post by: DavidR on May 04, 2011, 12:18:07 AM
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.
Title: Re: AutoSandbox Test Tool
Post by: Rednose on May 04, 2011, 02:10:48 AM
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.
Title: Re: AutoSandbox Test Tool
Post by: Rednose on May 05, 2011, 12:52:17 AM
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.
Title: Re: AutoSandbox Test Tool
Post by: mag on May 05, 2011, 08:10:50 PM
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.
Title: Re: AutoSandbox Test Tool
Post by: happy avast user on May 06, 2011, 11:00:14 AM
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. :)
Title: Re: AutoSandbox Test Tool
Post by: Zyndstoff (aka Steven Gail) on May 06, 2011, 11:03:44 AM
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..?
Title: Re: AutoSandbox Test Tool
Post by: happy avast user on May 06, 2011, 11:08:54 AM
Ok Thank you very much for your reply to my question, I really appreciate it :)
Title: Re: AutoSandbox Test Tool
Post by: mag on May 06, 2011, 01:45:48 PM
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.
Title: Re: AutoSandbox Test Tool
Post by: mag on May 06, 2011, 03:24:40 PM
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)
Title: Re: AutoSandbox Test Tool
Post by: Libra on May 07, 2011, 09:05:00 PM
I used the AutoSandbox Test Tool on my Vista sp2 computer.  It worked as it should.  I had to first click on the file to run it and then got a prompt from the computer asking if I wanted to run it (saying something couldn't be verified) and then Avast popped up recommending I run it in the sandbox, which I did.

I was thinking of trying to install a coupon printer .exe which I DO NOT want on my computer, but I'm reluctant since I don't know if Avast will pop up or not to run it in the sandbox.  Is there any way to be sure of this?

I am running the free Avast and the setting has the sandbox enabled and it is set to ask (I noticed that I had set it to auto, but it changed back to ask - I'm assuming maybe that is for the pro version?)

Any thoughts on this?

Thank you.

Sincerely, Libra
Title: Re: AutoSandbox Test Tool
Post by: igor on May 08, 2011, 12:42:57 AM
No, sorry, there is no way.
The full manual sandbox functionality is only in the Professional and IS version of avast!.
Title: Re: AutoSandbox Test Tool
Post by: Libra on May 08, 2011, 04:00:04 AM
Thank you igor for your reply.

Sincerely, Libra
Title: Re: AutoSandbox Test Tool
Post by: sooners2win on May 12, 2011, 07:05:28 AM
Comodo got it, I have autosandbox turned off....I may turn off on comodo and
try the avast sandbox though
Title: Re: AutoSandbox Test Tool
Post by: Libra on May 15, 2011, 09:39:40 PM
Thank you.  Unfortunately I won't go near Comodo.  They purchased BoClean and proceeded to treat it's developer very shabbily instead of doing what they agreed to. 

Sincerely, Libra
Title: Re: AutoSandbox Test Tool
Post by: rysiu on June 01, 2011, 04:01:37 PM
Is it possible to implement sandboxie feature to context menu? Like you click right mouse button on file and there you can use option "open with sandbox"
Title: Re: AutoSandbox Test Tool
Post by: igor on June 01, 2011, 04:02:56 PM
That's already implemented, of course - but you need avast! Pro or IS.
Title: Re: AutoSandbox Test Tool
Post by: pcclean3453 on June 03, 2011, 02:42:40 PM
I got a question about the test tool. Do you have to delete it from the registry immediately or can it stay there?

             Regards,
                    Pcclean3453
Title: Re: AutoSandbox Test Tool
Post by: kariuro on June 07, 2011, 09:09:47 AM
seems to work fine here.  :)
Title: Re: AutoSandbox Test Tool
Post by: Rednose on June 07, 2011, 10:58:25 PM
I have to say that the Test Tool is very handy for explaining users the AutoSandbox. Although I noticed that for some users the AutoSandbox can be complicated.

Greetz, Red.
Title: Re: AutoSandbox Test Tool
Post by: LexCi on June 19, 2011, 08:08:19 PM
For whatever it may be worth, "For the BEST protection with all of their SandBox and other settings this Avast! 6.0.1125 is the very BEST, IMHO."

Vlk,

Just ran your little test program and Avast! 6 did what it was designed for, except should not the box that shows "Avast auosandbox" say "Attempted Modification of the System" instead of "Modify the system!" when nothing has really taken place?  Plus the keeping those two windows open and on top so you may follow to the locations to verify they are not modified is also good.
Title: Re: AutoSandbox Test Tool
Post by: emel on July 01, 2011, 11:09:07 AM
i have downloaded the tool into my PC. so after running the exe file, what indicates avast is  working properly when this sandbox test tool is used?
i am  blind and using XP with jaws10,  which is 2 versions older than what the sandbox is built for.
Title: Re: AutoSandbox Test Tool
Post by: emel on July 02, 2011, 10:52:48 AM
just to clarify my previous query:
if i run the test tool and sandbox is triggered, then find my screen reader cannot read anything [silent in the sandbox environment] how do i terminate the test? is there any button outside the sandbox that i can use to terminate the test? [a STOP BUTTON outside the sandbox i presume can be read and used by my screen reader?]
thanks
emel
Title: Re: AutoSandbox Test Tool
Post by: Ashish Singh on July 03, 2011, 08:03:44 AM
Click ok after clicking Modify my System and the process gets terminated itself
Title: Re: AutoSandbox Test Tool
Post by: emel on July 04, 2011, 03:33:29 AM
thank you  :) so the OK button can terminate the test?
Title: Re: AutoSandbox Test Tool
Post by: ericz on July 05, 2011, 06:21:52 PM
Win XP, SP3, did the download. Not using Avast to monitor realtime web traffic. Monitoring software that checks downloaded files for malware, MS Sec. Essentials, did not flag the download as a questionable file. Presumably Avast does not either or others would have noted that.

With the other modules activated except for realtime web traffic monitoring, the sandbox popped.

On scrolling options, run in Sandbox worked fine. On cancel the install, got a Win XP OS error popup message, "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item." 

I have administrator privilege. Did the error message mean the Auto Sandbox, on the "kill it" selection, did not fully kill it?

If so, that might be a serious bug. Run in Sandbox, okay; but choose to kill, and it tries an install anyway? Have any other users, on other systems tried that option?
Title: Re: AutoSandbox Test Tool
Post by: DavidR on July 05, 2011, 06:37:34 PM
Well if you are using MSE and avast on your system, you are likely to experience conflict and that can present itself on many ways. One can block the other so it would be hard to say that avast missed something if there is no way to even know if it was scanned.

There is absolutely no way I would disable the avast web shield in favour of MSE, it is a far greater tool and one of the highest risks on the internet are hacked sites and the web shield is hot on these hacked sites and various exploits. This could well block the download of a file that many not even be on the avast signatures.
Title: Re: AutoSandbox Test Tool
Post by: bob3160 on July 06, 2011, 01:10:51 AM
Since 85% of all infections come directly from the Web,
cruising the web without the protection of the webshield
is asking for a system meltdown.
Not a very smart thing to do.  :'(
Title: Re: AutoSandbox Test Tool
Post by: Lisandro on July 06, 2011, 03:53:42 AM
Fully agree with Bob :)
Title: Re: AutoSandbox Test Tool
Post by: Ashwyn on July 06, 2011, 03:06:15 PM
nice one..good goin
Title: Re: AutoSandbox Test Tool
Post by: harryjamesuk on July 06, 2011, 09:26:56 PM
Worked For Me! Never Knew What The Sandbox Was Like When It Spotted Something Until Now :D
Title: Re: AutoSandbox Test Tool
Post by: TheCakeIsaLie on July 15, 2011, 01:50:57 AM
I will try after getting my Left 4 Dead 2 issue resolved
Title: Re: AutoSandbox Test Tool
Post by: yarin on August 16, 2011, 04:12:53 AM
thanks~~~
Title: Re: AutoSandbox Test Tool
Post by: JuninhoSlo on October 03, 2011, 10:28:10 PM
Hi ;)

When you run/open AutoSandbox Test Tool Avast gives you the opportunity to run this test in sandbox mode but can you tell me why program CCleaner creates new startup entry:

Da   HKCU:Run   autosandboxtest   If you can see this text even from a non-virtualized application then the application (avast! autosandboxme) wasn't sandboxed properly.

Can I simply remove this entry from CCleaner?  Avast sandbox mode works well on my PC. ;)

Thank you
Title: Re: AutoSandbox Test Tool
Post by: leona65 on November 02, 2011, 10:23:04 PM
Just ran the tool, it worked fine.
I was a little confused at first becuase when I first ran it without using the sandbox - I could find the registry entry but not the file.  Finally realized I needed to run as administrator - I have windows 7 and it was not letting me write to  C:\   without it.
Once I thought of that - it worked as expceted both ways.

Thanks,
Fay
Title: Re: AutoSandbox Test Tool
Post by: Bartmole on January 08, 2012, 08:18:02 PM
No sign of autosandbox with the tool or since upgrading to Avast Pro though Avast Free did show it. Windows 7 Ultimate 32 bit, UAC disabled, only security programs ever installed are Spywarewareblaster, Malwarebytes, Superantispyware (both on demand) with Windows firewall. And, autosandbox is enabled, tried tool numerous times as Administrator and in IE as well as Opera.
Title: Re: AutoSandbox Test Tool
Post by: Bartmole on February 09, 2012, 05:34:02 AM
Working fine with public beta 7.
Title: Re: AutoSandbox Test Tool
Post by: Dch48 on February 24, 2012, 07:23:34 AM
Not working right with the release version of Avast 7. At least not in my opinion. Actually it's the new sandbox that's not working right.
Title: Re: AutoSandbox Test Tool
Post by: DavidR on February 24, 2012, 01:45:17 PM
Not working right with the release version of Avast 7. At least not in my opinion. Actually it's the new sandbox that's not working right.

Care to expand on what isn't working right ?
Title: Re: AutoSandbox Test Tool
Post by: Dch48 on February 24, 2012, 06:52:33 PM
Yes, I don't think it should automatically terminate the program that you have chosen to run in the sandbox. It does it so fast I never even get a chance to click the test button. Once you've chosen to run something sandboxed, it should run until you close it yourself. I have the autosandbox set to ask.
Title: Re: AutoSandbox Test Tool
Post by: lil marlau on February 24, 2012, 10:23:01 PM
I don't have the autosandbox tool installed yet. I tried to install it and got an "malicious warning" from Avast and it closed. I guess it's just a bug with the new version. I will try again in a couple of days.
Title: Re: AutoSandbox Test Tool
Post by: bob3160 on February 25, 2012, 12:25:15 AM
I don't have the autosandbox tool installed yet. I tried to install it and got an "malicious warning" from Avast and it closed. I guess it's just a bug with the new version. I will try again in a couple of days.
It's a part of avast! not a separate program ???
Title: Re: AutoSandbox Test Tool
Post by: lil marlau on February 25, 2012, 01:09:35 AM
That's what I'm saying. A bug. Doesn't recognize itself.
Title: Re: AutoSandbox Test Tool
Post by: decroft on February 27, 2012, 11:26:01 PM
Don't need to test it, sandbox sucks.  On  auto it doesn't trust  Word, Access, Excel, and runs them in  the sandbox.  I'm surpirsed it lets the operating system run.   What a joke, idea is good, but implementation is poor. 
Title: Re: AutoSandbox Test Tool
Post by: Dch48 on February 27, 2012, 11:30:43 PM
A word of advice. If you use the avast! gadget, turn it off now. It causes glitches in the auto sandbox. In particular it prevents things from being excluded properly When you tell avast to run the program normally the next time it's supposed to add that program to the sandbox exclusions but if the gadget is running, it doesn't work. It puts a meaningless entry in the exclusions list instead of the actual file. With the gadget turned off,  the exclusion is added  and works properly.
Title: Re: AutoSandbox Test Tool
Post by: aklaren on March 06, 2012, 11:59:48 AM
I like the sanbox feature, but don't quite understand why the sandbox is terminated after the analysis determines that there is NOT enough evidence to mark the file as malware. I would expect it to continue running unless there is ENOUGH evidence to mark it as malware. This means that legitimate processes are terminated when Avast! is unsure.

Also, does Avast! considder all programs that are run directly from the Internet as suspicous or does it look at certain suspicious instructions? I have built a program that a.o. READS the system registry and optionally WRITES the data to a file, but would like it to pass/skip the Avast! analysis (the program is digitally signed with a COMODO code signing certicate). Is there any documentation on this? Thanks.
Title: Re: AutoSandbox Test Tool
Post by: DavidR on March 06, 2012, 02:38:50 PM
There is no point in it continuing to run as it is in a virtual environment, when the sandbox closes all within it would be lost depending on what that application in the sandbox does.
Title: Re: AutoSandbox Test Tool
Post by: aklaren on March 06, 2012, 03:23:50 PM
Thanx for the quick reply. In our case, and I think in many other cases, it does make sense to continue. Why don't you leave it up to the user to decide to continue or stop? Now the application is terminated and the non-technical user will not know what to do and because of the strong warning given, he/she will think our application is malware. BTW: selecting "sandbox" will terminate the application each time (we use the online MS ClickOnce mechanism in IE). 
Title: Re: AutoSandbox Test Tool
Post by: Dch48 on March 06, 2012, 06:46:35 PM
In the latest R2 build the ask option of the auto sandbox has been reverted to it's original behavior.  If you set the sandbox to ask, it will then give you a window with the option to run the app either sandboxed or normally. If you tell it to run normally and check off to remember the answer, it will never be sandboxed again.  I'm sure this will be the behavior in the final release of v7 R2. You don't even see the analysis windows and the app does not terminate even if run in the sandbox.
Title: Re: AutoSandbox Test Tool
Post by: aklaren on March 07, 2012, 10:06:58 AM
I updated from 7.0.1407 to the R2 beta 7.0.1414 to try it out, but it looks like the default sandbox option is "auto". That would mean that by default, our application is sandboxed and terminated after 10-15 secs, leaving the user the option to open it next time either in the sandbox (recommended) or normally. The average and the cautious user will use the default, but then each time the analysis is done and the application is terminated. Why?

If I change the autosandbox option to "ask" and tell it to run in the sandbox all works fine. So to use our application (and other similar apps), every Avast! user must either allow it to run normally next time and start our application again or a) first find the autosandbox configuration setting b) change it to "ask", c) run the application and d) confirm that they want to run it in the sandbox. This is quite cumbersome and virtually impossible to explain to beginners (large part of our users).

I would like to suggest that the sandbox is ONLY terminated if the analysis finds ENOUGH evidence that the application is malware. Otherwise, explain to the user that the application is being run in a sandbox and changes are not saved and ask if they want to continue. So e.g. change the OK button to a Yes/No/RunNormally button (with the default to Yes) and change the combobox to a checkbox to remember this choice. This makes much more sense.

In the R2 beta it now shows that the reason for the sandbox is that "The file prevalence/reputation is low". Since our application is initially local and updated frequently, this will usually be the case. But it is signed with a trusted COMODO code signing certificate. Again, is there any further documentation on this?
Title: Re: AutoSandbox Test Tool
Post by: aklaren on March 24, 2012, 02:27:38 PM
In the absence of any further replies :(, I have done some more testing on v7.0.1426 and it looks like the sandbox is NOT activated in our production environment (anymore?), but only in development and test environments (which are in a subdirectory of the main URL). All environments use the exact same source code (incl a code signing signature), the only difference being the version number: 1.5.0.0 for production vs 1.5.0.1 and 1.5.0.2 for the dev/test environment (as ClickOnce applications in different environments cannot share the exact same version).

I am not sure if the sandbox WAS activated previously in the production environment or only in the dev/test ones. Or could it be that the prevalence/reputation of the 1.5.0.0 version is now "acceptable"? But that would mean that a next version will have the same problem again. ???

I understand and I "second" the sandbox mechanism, only I do not fully understand why and how it sees some applications as potentially risky and what we can do about it. And as I said earlier, I don't agree to the sandbox being terminated if not enough evidence is found to mark the file as malware.

Can anybody shine some light on this for me please?
Title: Re: AutoSandbox Test Tool
Post by: Akash1 on April 17, 2012, 08:04:06 AM
Great tool. Only avast was able to react to it. None of the other auto sandboxing soft or other antivirus. Eg:- Norton , Comodo auto sandbox
Title: Re: AutoSandbox Test Tool
Post by: draz on June 02, 2012, 11:05:47 AM
I do not speak English
hola soy draz y ya que vi esta tool me dio animo para investigar sobre el Sandbox y pues esto pude lograr
miren ustedes mi video en youtube http://www.youtube.com/watch?v=BM0X1MGUZkc&feature=youtu.be espero bueno comentario y si pueden en ESPAÑOL MEJOR saludos !!!
Title: Re: AutoSandbox Test Tool
Post by: Salabim on June 17, 2012, 05:48:30 AM
EDIT: This post should be in the regular forum since it is related to the auto-sandbox-on-suspicious feature of the regular Avast 7 program.

running PS3 Media Server ( http://www.ps3mediaserver.org/ ) gives me a "suspicious" popup, and no matter if i choose "run sandboxed" or "run normal" the program is started in a buggy environment, the loaded module javaw.exe even gives me a BSOD afterwards.

Please fix your sandboxing issues, or don't try to incorporate one at all.

I had to uninstall Avast and go back to good old Panda Cloud AV for it to work normally.
Title: Re: AutoSandbox Test Tool
Post by: True Indian on June 27, 2012, 02:13:00 PM
EDIT 2: had to turn off comodo D+ and sandbox...to trigger avast sandbox. ;D

figured out...my COMODO was on blocked..moved to restricted...kept everything on and now CIS and avast both jump on the file correctly :)
Title: Re: AutoSandbox Test Tool
Post by: RejZoR on June 30, 2012, 01:31:29 PM
It would be nice if you could trigger Low reputation event with it as well because a different popup warning appears before the Auto Sandbox. I'd also like Auto Sandbox Test tool to trigger positive identification by the analysis engine. This way we can test it properly during beta stages, otherwise it's a real pain to test with live malware that is still not covered by signatures...
Title: Re: AutoSandbox Test Tool
Post by: Lisandro on June 30, 2012, 01:49:04 PM
This AutoSandbox Test Tool is not working for me at all... I mean, no popup... Oh, of course, my AutoSandbox is set to Ask if it makes any difference.
Title: Re: AutoSandbox Test Tool
Post by: DBenjamin85 on August 07, 2012, 08:27:15 PM
I noticed this (only later did I notice it was originally posted in 2011) but the tool does not seem to be working for me at all.  Is this tool compatible with the current version of avast IS? 

I'm running the 7.0.1456 version of Internet Security with current definitions and the program simply runs, asks to modify and then tells me where the text file is.  The text file then tells me it was not sandboxed properly.

I've noticed people posting about issues with the Auto-Sandbox feature and was just wondering if this program should not be working?
Title: Re: AutoSandbox Test Tool
Post by: Dch48 on August 08, 2012, 01:00:20 AM
In the latest beta, the tool does not trigger the autosandbox but when you try to "modify the system" you get an alert from the Behavior Shield instead.
Title: Re: AutoSandbox Test Tool
Post by: True Indian on August 09, 2012, 01:52:45 PM
doesnt sandbox it here even on 1456 running win 7 system now  :o
Title: Re: AutoSandbox Test Tool
Post by: Charyb on August 09, 2012, 02:04:46 PM
Vlk answered this.

http://forum.avast.com/index.php?topic=102811.msg823604#msg823604
This is as expected. Sorry for that. We will shortly post a new version of autosandboxme.exe.

Thanks.


http://forum.avast.com/index.php?topic=102811.msg823686#msg823686
It's all in the VPS.
Title: Re: AutoSandbox Test Tool
Post by: True Indian on August 09, 2012, 02:15:21 PM
thankyou! for bringing it to my notice charyb  ;D
Title: Re: AutoSandbox Test Tool
Post by: kotoroshinoto on August 09, 2012, 09:10:04 PM
I'm trying to develop a small program using C++ for my own use (and possible free distribution once it works), the problem is, EVERY TIME I execute the program, the autosandbox thing captures it. I know it isn't a virus, cuz I WROTE IT.

How do I stop this annoying behavior?
Title: Re: AutoSandbox Test Tool
Post by: bob3160 on August 09, 2012, 10:03:04 PM
See if this helps:


(http://my.jetscreenshot.com/2701/m_20120809-yibs-101kb.jpg) (http://my.jetscreenshot.com/2701/20120809-yibs-101kb)


When you're asked, select Run Regular and then select Remember My Answer.
You'll not be asked again but you'r bypassing a part of your protection. (Your computer. :) )

Title: Re: AutoSandbox Test Tool
Post by: igor on August 12, 2012, 09:54:19 PM
Here is an updated version of the autosandbox test tool
http://public.avast.com/dev/autosandboxme2.exe
Right now, the "File prevalence/reputation is low" reason must be enabled in autosandbox configuration (for the file to get autosandboxed).

Note that the tool is meant to test:
1. the fact that the file gets autosandboxed
2. the fact that the file is properly sandboxed, i.e. the changes performed when it's running do not reach the real operating system
It is not meant to test the detections; the file will be reported as clean.
Title: Re: AutoSandbox Test Tool
Post by: DavidR on August 12, 2012, 10:29:59 PM
Presumably the AutoSandbox Info PDF will be updated in due course http://public.avast.com/mkt/20110124_Avast_Autosandbox.pdf (http://public.avast.com/mkt/20110124_Avast_Autosandbox.pdf).
Title: Re: AutoSandbox Test Tool
Post by: Dch48 on August 12, 2012, 11:54:35 PM
The new test tool works like a charm.
Title: Re: AutoSandbox Test Tool
Post by: True Indian on August 13, 2012, 10:48:40 AM
Works on my win7 running 1456 too.. ;D
Title: Re: AutoSandbox Test Tool
Post by: philip brampton on August 13, 2012, 02:09:45 PM
When i try to run the AutoSandbox tool i get this message.
Please may i have some advice
Thank you

Windows XP SP3
Avast Beta 1464
Title: Re: AutoSandbox Test Tool
Post by: Vladimyr on August 13, 2012, 02:27:37 PM
When i try to run the AutoSandbox tool i get this message.
Please may i have some advice
Thank you

Me too!
Windows XP SP3
AIS 7.0.1426 & avast! Free 7.0.1456

Title: Re: AutoSandbox Test Tool
Post by: DavidR on August 13, 2012, 03:03:36 PM
Snap, XP Pro SP3, avast 7.0.1464 beta.
Title: Re: AutoSandbox Test Tool
Post by: philip brampton on August 13, 2012, 03:13:24 PM
You usually have a sensible opinion.
Surely you are not lost for words this time.
Philip
Title: Re: AutoSandbox Test Tool
Post by: igor on August 13, 2012, 03:18:21 PM
Hmm, seems it's not compatible with XP. :(
Will be checked.
Title: Re: AutoSandbox Test Tool
Post by: philip brampton on August 13, 2012, 03:23:24 PM
looks like it.
Works perfectly with Windows 7.
Back to the drawing board
Title: Re: AutoSandbox Test Tool
Post by: ivory888 on August 30, 2012, 02:05:19 PM
I downloaded autosandbox.me, clicked on it, on which the following window appeared:

"Modify the system."

Title: Re: AutoSandbox Test Tool
Post by: DBenjamin85 on October 13, 2012, 12:23:24 PM
I figured it would be best to post in this topic and not start a brand new thread to clutter the forum up to get a question answered. 

I noticed that since using an older version of the autosandbox tool (and it not working, due to compatibility issues which have been stated), it basically succeeded in making changes.  In my items that start up from boot up there appears to be something related to the autosandboxtest tool which I'm not sure how to get rid of (or anything from that boot list for that matter).

Is there a way to get rid of autosandboxtest off my computer entirely?  It seems to be lingering.
Title: Re: AutoSandbox Test Tool
Post by: Para-Noid on October 14, 2012, 01:53:40 AM
I noticed that since using an older version of the autosandbox tool.
Is there a way to get rid of autosandboxtest off my computer entirely? 

Did you use the original autosandboxme or the new one http://forum.avast.com/index.php?topic=76650.msg825680#msg825680 ?  :)

If all else fails uninstall using safe mode.  :)
Title: Re: AutoSandbox Test Tool
Post by: DBenjamin85 on October 14, 2012, 02:17:40 AM
I noticed that since using an older version of the autosandbox tool.
Is there a way to get rid of autosandboxtest off my computer entirely? 

Did you use the original autosandboxme or the new one http://forum.avast.com/index.php?topic=76650.msg825680#msg825680 ?  :)

If all else fails uninstall using safe mode.  :)

I use the original tool and then realized there was an updated version, the old version didn't work on win7 so it basically told me it had made a change to my registry and left that little text thing near the documents folder saying it hadn't worked. 

I don't understand what you meant by uninstall in safe mode if you mean AIS I've actually reinstalled it since using the autosandbox test tool, the fact is there is still a boot program (currently unticked to boot on startup) which says it's the autosandbox tool.  Or did you mean uninstall the autosandbox tool?
Title: Re: AutoSandbox Test Tool
Post by: Para-Noid on October 14, 2012, 02:18:56 AM
The autosandbox tool.  :)
Title: Re: AutoSandbox Test Tool
Post by: DBenjamin85 on October 14, 2012, 02:26:46 AM
The autosandbox tool.  :)

I'm not really following how this would fix the issue of what the autosandbox test tool has done to my registry, there is from what I know nothing wrong with the autosandbox itself.  I was noting the fact that in my boot up programs along with things like my OS, Messenger etc there is an autosandboxtest that I can't seem to get rid of.  I was showing a tech my boot list when we noticed it, I assumed that the autosandboxtest was completely safe... yet it seems to be left on my boot program list in msconfig lol.
Title: Re: AutoSandbox Test Tool
Post by: Para-Noid on October 14, 2012, 10:02:21 PM
How did the tool get into your "boot list"? I keep the autosandboxme2 tool in my downloads. All I do is Control Panel>Downloads>double click the tool. It never leaves my downloads folder. It should not affect the registry in
a negative way. Have you used CCleaner to clean/fix your registry? http://filehippo.com/download_ccleaner/
CCleaner is completely safe to use.

I just can't understand how it got to your "boot list".  ???
Title: Re: AutoSandbox Test Tool
Post by: NON on October 15, 2012, 01:21:53 AM
I just can't understand how it got to your "boot list".  ???
Maybe he wants to state about "start-up" list in msconfig. First autosandbox.exe adds an entry into it.

@ DBenjamin85
The entry added by autosandbox.exe is completely inert, it has no bad effect even if it remains.
You have to use some 3rd-party tools like CCleaner to delete it though.
Title: Re: AutoSandbox Test Tool
Post by: DBenjamin85 on October 15, 2012, 01:01:16 PM
I just can't understand how it got to your "boot list".  ???
Maybe he wants to state about "start-up" list in msconfig. First autosandbox.exe adds an entry into it.

@ DBenjamin85
The entry added by autosandbox.exe is completely inert, it has no bad effect even if it remains.
You have to use some 3rd-party tools like CCleaner to delete it though.

Sorry that was what I meant, thank you NON, I meant the start-up list and am glad that is what that is.  I'll do a clean a bit later, that or I'll go ahead with a format anyway which I was going to do already.