Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: jerry23 on September 17, 2011, 06:05:13 PM
-
Hello!Auto-sandbox in new version 6.0.1289 is missing auto-sandbox tab. Sandbox in Windows XP 64 bit does not work.Checked with with sandbox tester-tries to modify the system.Support is helpless,so far the best solution is version 6.0.1203.Any input is greatly appreciated.
-
I don't think the AutoSandbox ever worked on WinXP x64 - only the GUI items have been shown by mistake.
-
I don't think you know the product: Currently running Windows XP 64 bit SP2 with Avast 6.0.1203 Sandbox works just fine:File system shield Expert Settings Auto sandbox is here works just great. tested it with down loadable sandbox tester stopped dead on the tracks. version 6.01289 no sandbox. Any previous versions sandbox is there and operational! Any reasonable suggestions are greatly appreciated.
-
I don't think the AutoSandbox ever worked on WinXP x64 - only the GUI items have been shown by mistake.
I don't think you know the product
;D Igor, you don't know the product...
-
igor is.......... right ;D
autosandbox/sandbox/safezone components are not working on WinXP 64-bit, because this OS is "old" and it doesn't contain registry filtering engine which is used in these components (and hooking is blocked by PatchGuard). Version 1203 shows the autosandbox popup from file-system shield (functionally it's separated from autosandboxed code), but if you choose to virtualize the app, it won't work, because autosandbox component isn't loaded in this OS. This was a GUI bug and it was fixed in 1289 build, please see system requirements for virtualization:
OS supported:
Windows XP SP2+ 32-bit
Windows Server 2003, Vista, 7 (32-bit and 64-bit) only RTM versions are supported (Windows 7 SP1 is currently also supported)
OS not supported:
Windows 2000
Windows XP 64-bit (with any SP installed)
Windows Server 2003 64-bit
-
PK
igor is.......... right
autosandbox/sandbox/safezone components are not working on WinXP 64-bit, because this OS is "old" and it doesn't contain registry filtering engine which is used in these components (and hooking is blocked by PatchGuard). Version 1203 shows the autosandbox popup from file-system shield (functionally it's separated from autosandboxed code), but if you choose to virtualize the app, it won't work, because autosandbox component isn't loaded in this OS. This was a GUI bug and it was fixed in 1289 build, please see system requirements for virtualization:
OS supported:
Windows XP SP2+ 32-bit
Windows Server 2003, Vista, 7 (32-bit and 64-bit) only RTM versions are supported (Windows 7 SP1 is currently also supported)
OS not supported:
Windows 2000
Windows XP 64-bit (with any SP installed)
Windows Server 2003 64-bit
PK !This is OS requirements of avast site:http://www.avast.com/en-us/free-antivirus-download#tab2 (http://www.avast.com/en-us/free-antivirus-download#tab2) where it clearly states that Windows XP 64 bit is fully supported. Windows XP 64 came in two(2)flavors. Windows 5.2(Build 3790.srv03_sp2_gdr.101019-0340:Service Pack2)has Full Support of AMD Virtualization !!!. the following link:http://forum.avast.com/index.php?topic=76650.0 (http://forum.avast.com/index.php?topic=76650.0) Avast 6.0.1203 triggers the autosandbox feature on this file. That's why I can state that Autosanbox does work.Version 6.0.1289 needs just couple of lines of C++ code.Hopefully it will be supported again in upcoming version.
-
PK is saying that the popup will indeed be triggered, as it's a different part of the code - but if you choose that the application should be run inside of the sandbox, it won't work. The program will still be able to modify the registry of your computer, i.e. it won't really be sandboxed.
-
PK is saying that the popup will indeed be triggered, as it's a different part of the code - but if you choose that the application should be run inside of the sandbox, it won't work. The program will still be able to modify the registry of your computer, i.e. it won't really be sandboxed
Igor it does not let the application to run at all if I choose do not run option http://imageshack.us/photo/my-images/827/snap3ch.png/ (http://imageshack.us/photo/my-images/827/snap3ch.png/).Run in the sandbox DOES NOT LET it to modify the registry which is easy to check by going to HKCU\software\Microsoft\windows\current version\run\ there is NO entry run autosanboxme/exe.
Anyway We are still talking about version 6.0.1203:
THE PROBLEM IS WITH AVAST VERSION 6.0.1289-WHERE AUTOSANBOX DOES NOT EXIST AT ALL AND THE AUTOSANBOXME PROGRAM TEST RUNS AT WILL, the only thing that stops it is my registry guard not the Avast.
Changing from old reliable XP 64 which is supported till 2014 to Windows 7 just to get autosanbox feature to show up does not make any sense at all since Windows 8 is coming out soon.
Hopefully auotosanbox will be back at the scene for Windows XP in upcoming version of Avast.
-
Astounding.
There are two developers of the Avast software who explain, that a certain feature does not work on XP 64 bit, they even explain in detail why that is so - and nevertheless the TO clings to his (wrong) statements and opinions...
I'ld rather believe those who made that thing instead of someone merely using it. ;)
-
Dear Steven Gail!
1)Avast developer stated autosanbox does not exist in Windows XP 64 bit.
2) When I proved it them that it does, they admited it and stated that it works partially according to them.
3) All that in Avast version 6.0.1203
4) The post subject was avast 6.0.1289 where autosanbox is missing completely.
5) Next time read the whole topic before you put your foot in your mouth.
6) Have a good day!
-
jerry23,
1. autosandbox/sandbox/safezone components have NEVER worked in WinXP 64-bit (virtualization driver isn't loaded on this OS, because WinXP 64-bit is old system and it doesn't contain several internal libraries which are required by our sandbox)
2. prior to build 1203, all avast versions contained a bug in UI where you saw autosandbox options even for WinXP 64-bit OS -- please note, UI is separated from avast components (UI just sends commands to the components to do a work - it's only a thin communication layer; for example, when UI in 1203 sent autosandbox's commands to this component, they were never completed, because this component was missing on this OS)
3. so, if you got an autosandboxed popup in UI, it actually never worked, because the main autosandbox component was missing and not working on this OS
-
PK ! I read your last reply. I have a question for you or two.
1) Puran defrag does not work till it is added to exclusions of autosandbox which according to you is a bug?
2)AMD processor driver, Outpost Firewall, JV16 and other programs are in the same situation.
3) Bug or not it works.
4) If your company dropped the support to a "bug" feature starting from version 6.0.1289 you could state that.
5) Food for thought: Why is the Corporate World is still using Windows XP(the one you called OLD OS)? May be you rushed to drop the " bug" feature called autosanbox for Windows XP?
-
5) Food for thought: Why is the Corporate World is still using Windows XP(the one you called OLD OS)? May be you rushed to drop the " bug" feature called autosanbox for Windows XP?
The ASB works on 32-bit XP systems.
-
Jerry23
One thing is triggering AutoSandbox popup, another is actually sandboxing the assigned application. What Igor and pk are saying is that avast! will still show the AutoSandbox popup, but it won't actually sandbox the app it was triggered for due to GUI glitch.
The AutoSandbox tester has dual functionality and you have to check both. First one is triggering the AutoSandbox dialog and second one is checking if the data has been actually modified on the system. In your case, i can safely say your registry key or file on the disk has been created, meaning it's not working at all on WinXP 64bit.
-
I think most readers of this topic should get the difference by now, having so many posts explaining the difference between the real function / feature and what the User Interface is / was showing.
For anyone still not understanding all the lingo, it's like an illusion. Avast was "showing" you something (by means of its User Interface), hence the user sees on the computer screen all these things happening.
But, as said, illusion. The actual function, the real thing, the "objects" (folders / files / registry keys) that were supposed to be protected against permanent changes (that's the real goal of this function / feature) are not really protected.
It *seems* like they were. They were not :( .
With the latest program update to version 6.0.1289, the illusion is gone. Now the real thing and what the User Interface shows, are the same.
-
Guys I am well aware of the difference!
I work for large corporation that expressed the desire to purchase the product asking me to check tech support for it,monitoring the replies on the RAS connection. The following is I what I was allowed to leave as my statement.
1)The average consumer has to go pass the series of put downs and insults prior to getting the straight answer.
2)This young company has a lot to learn about ethics.( No wonder it's corporate sales are very low).I was dropping hints left and right.
3)Take an educated guess what the Corporation decided to do.
-
Sorry, but you don't want to hear the answers... which I gave you in the first post. Therefore, you shouldn't be surprised by what you get, especially on a public forum where most answers come from avast! users.
I installed version 1203 on WinXP x64 - and no, the sandbox doesn't work.
Yes, I get the AutoSandbox popup - but after choosing "Open in sandbox", the test application runs normally - the registry key, and also the file in the root of the C: drive, is created.
As for 32bit XP, there's no need to remove any functionality from there, because it does work, via hooking. However, hooking is not possible on XP x64 because of PatchGuard, and XP x64 doesn't have the necessary (additional) API to use instead of hooking, because it wasn't added before Vista.
Edit: as for the "young" company... really not sure how you came to that conclusion.