OK correction, it works on my system, but not on anything that is on my pc…so if I run autosandboxme.exe from a flash drive, I get the popup…(from what I can tell)
It looks like we’re getting closer to the official release.
The beta build has now been updated to version 6.0.1364.
This version should fix all the issues reported/discovered in build 1356 (with the exception of the mysterious 6008 event being written to the Windows Event Log during system shutdown).
Users of the previous beta can get this build by invoking the in-product update.
Thanks
Vlk
Thnx Ondrej 
Greetz, Red.
OK updated from 6.0.1356 and rebooted without issue, and everything appears to be working as it should (win XP Pro).
Still getting the mysterious 6008 event. 
On my W7 SP1 x64 update to .1364 worked fine.
On my W7 SP1 and W8-DP x64 dual-boot computer update to .1364 worked fine.
Another comment about the W7 and W8-DP dual boot set-up
When you are in W7, avast! will scan the W8-DP partition as well as the “FileHistory” folder created by the W8 backup.
6.0.1364 is working great! Keep up the great work. Can’t wait for 7.0
Downloaded setup_ais.exe of 6.0.1364 just now.
It does not detect my 6.0.1356 and does not have an upgrade (or update) option.
When I run it, it just acted as a brand new installation.
My system is Windows 7 Ultimate SP1 simple Chinese
I had to install this Beta version 6.0.1364 form scratch since I wanted to install it on the top of 6.0.1286 and it did not give me the Update Option and then it showed to install google chorme as if it was a version not installed in my PC, after that I said Next and it corrupted all files in version 6.0.1289, as I was not able to remove that version I had to go on safe mode and removed 6.0.1289 and install this one.
It seems working good here in my W/7 SP1 PC.
I will try it tomorrow in Windows XP SP3… rm
It did that to me as well and I had to re input my license file. But it does work well.
I just used the update function of v6.0.1356 to upgrade to v6.0.1364. The update went smoothly and after a reboot, everything appears to be working. My system is Windows 7 Ultimate (X86).
As i have never seen it work or know how to make it work other than run the test tool which said “modify the system”
I cannot answer your question.
Thank you for your interest
Updated from 6.0.1356 Free. So far no problems.
Hi all
Installed the new 6.0.1364 on top of 1289(the last stable version) and after the reboot the registration info dissaperead, now my antivirus says ”you have 30 days to register”.
Btw, the installation method was ”installing over the stable one”
Autosandbox is not working for RAM drive (worked as Removable media)…
Autosandbox works on normal HDDs.
Autosandbox is not working for me either. Tried running “autosandboxme.exe” and “OTL.exe” and neither one invokes the autosandbox feature of avast. Currently running 6.0.1364 free. Checked the settings and Autosandbox is enabled and set to “ask”.
Just installed the latest free antivirus 6.0.1364 beta over 6.0.1289 and it did not do it as an update but a fresh install, and i had to re-register it again !
This is on a windows 7 32bit netbook.
I’m slightly confused by your posts
So, which is it - the autosandbox popup doesn’t appear at all, or it does but (after selecting to sandbox the application) it doesn’t get sandboxed?
Just installed update to 6.0.1364 no problems at all (straight update and re-boot)
Windows XP Home SP3
Free Version On-line Update from 1356.
All OK inclusive Auto Sandbox (Red Border and no System modification)
My System: WIN 7 64 Bit
Nice Weekend
Christian