Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Vlk on May 06, 2011, 06:31:32 PM
-
The update has now been officially released as version 6.0.1125.
See http://forum.avast.com/index.php?topic=77801.0 for details.
Thanks to everyone who helped testing the pre-release builds.
Hi,
we will soon be releasing another service release of avast Free/Pro/IS. Before we make it official, we're making it available here on the forum for anyone to test.
How to get it
links removed
How to install it
Just run the setup executable (links above). You can either install it from scratch, or on top of an existing avast installation (installing over both 5.0.xxx or 4.8.yyy should be fine). A reboot will be required to complete the installation.
What's new
Most notable improvements include:
- solved a problem in aswSP.sys that could lead to a system crash
- improved tolerance for corrupted installations
- when updating from a previous version of avast Pro/IS, SafeZone is now automatically added
- fixes in Chrome WebRep plugin
- Behavior Shield: improved compatibility with other applications
- improvements in the CommunityIQ submission system
Thanks much
Vlk
-
has avast ever considered adding an option into the avast settings to "update to beta/RC versions"? these pre-release versions come out and i think it would be convenient to have an option in the settings for users that like to test pre-release versions to be auto updated like regular program updates. some other AV's have this option like Emsisoft, ESET and such.
-
Updated from 1091 with the downloaded AIS. Looks good so far, even with my "AIS/FW not installed, OA instead" configuration. :)
-
Installed from scratch. I had not selected to install P2P shield, but it was installed - I remember reporting this once, in one of the previous betas. Everything else is fine.
-
Just updated over the top of 6.0.1091 and appears to be fine.
Seems there has been some compression to the setup_av_free.exe at 54.2MB much smaller than the 6.0.1091 installation file.
-
Quite a surprise.
Thanks
-
Auto SandBox still does not work
When i run the test tool all i get is "Modify System"
Windows 7 home Prem 32 bit
Firefox 401
-
Surprise!
- improved tolerance for corrupted installations
What does it mean?
- when updating from a previous version of avast Pro/IS, SafeZone is now automatically added
Thanks.
- Behavior Shield: improved compatibility with other applications
Such which? I mean, is it the compatibility with other behavior scanners (Threatfire, for instance)?
- improvements in the CommunityIQ submission system
Can you elaborate?
-
The update went fine for me, but webrep still seems to be inactive (chrome):-\.
Thanks nonetheless :)
-
Auto SandBox still does not work
When i run the test tool all i get is "Modify System"
Windows 7 home Prem 32 bit
Firefox 401
Sandbox ist set to "Ask"...?
-
Will this release fix the problems with the following:
Characters overlaid in Google My Account when using Firefox 3.6.x or Google Chrome Browsers (only started after installing Avast Pro).
After going into SafeZone, it dims the monitor, but when you exit, it remains dimmed and you must restart the computer for it to go back to the normal monitor settings.
Please let me know.
Ingrid
-
Auto SandBox still does not work
When i run the test tool all i get is "Modify System"
Can you post the contents of the file C:\ProgramData\AVAST Software\Avast\Log\AutoSandbox.log?
Will this release fix the problems with the following:
Characters overlaid in Google My Account when using Firefox 3.6.x or Google Chrome Browsers (only started after installing Avast Pro).
After going into SafeZone, it dims the monitor, but when you exit, it remains dimmed and you must restart the computer for it to go back to the normal monitor settings.
Yes it should fix this problem.
-
Thnx, I will install it later tonight :)
Greetz, Red.
-
Updated over .1019 without any problem.
On the first glance system works flawlessly as advertised.
Either there are no problems or I don't see them!
Sorry, do not discuss my last statement ;D :-X :-X
-
Everything smooth - except, as expected, this WebRep thingie.
Still the voting window remains open for at least 10 sec before closing itself after clicking on "vote"... with 10 sec being the lower end of the range. Average about 12 to 15 sec. :(
-
And what about the language-depending GUI bug in Vista (http://forum.avast.com/index.php?topic=75220.0)?
-
Just updated over the top of 6.0.1091 and appears to be fine.
Seems there has been some compression to the setup_av_free.exe at 54.2MB much smaller than the 6.0.1091 installation file.
See http://forum.avast.com/index.php?topic=76488.msg634347#msg634347 (http://forum.avast.com/index.php?topic=76488.msg634347#msg634347).
There's not much difference between 6.0.1091 and 6.0.1119 Free installers if you downloaded after April 18th. Around 700KB.
File: D:\Downloads\John\setup_av_free.exe
Size: 56816368 bytes
File Version: 6.0.1119.0
Modified: Friday, May 06, 2011, 2:49:37 PM
MD5: 0AD991930AAFA761CFEC6B55B101FC54
SHA1: B6E8BE189223E4D46FCDD2A01CD6E93F2DCAD7C7
CRC32: 1F8518BD
File: D:\Downloads\John\Security CD\AntiVirus\setup_av_free601091.exe
Size: 56189640 bytes
File Version: 6.0.1091.0
Modified: Wednesday, April 20, 2011, 9:18:54 AM
MD5: B355C07A9EF81C73B75A537B20301888
SHA1: 8E6BE284623496109B3E2ABFDD10280069252E3C
CRC32: 868714FB
I added the 601091 to the filename when I saved it, before.
-
Well my copy of 6.0.1091 was 63MB, I don't keep historic copies and was downloaded when it first became available.
-
Well my copy of 6.0.1091 was 63MB, I don't keep historic copies and was downloaded when it first became available.
Yes, as noted in the post I referenced. :)
-
well considering that my current AIS setup runs flawlessly, I may wait for the official release this time.
-
going to wait here too for the official since none of those improvements really affect my computer.
-
Hi,
Installed avast! Internet Security 6.0.1119 from scratch and notified improvement of my boot time. Make sense of resource usage too. This time avast! shows more stability and improvements over previous 6.x versions.
Love avast! :-*
Cheers...
-
I installed this new version on the top of the official one and seems to be working fine in my XP Home Edtion SP3 PC.
rm
-
I installed this new version on the top of the official one and seems to be working fine in my XP Home Edtion SP3 PC.
rm
Same here. It retained all settings. Did a Quick Scan and all is well.
-
Any new word on fixing the uTorrent AIS firewall system slowdown? It's been since February when any official mention
of progress was made in the forums. Otherwise keep pushing these updates out to stay on top of the game. :)
Cheers
-
Just updated over the top of 6.0.1091 and appears to be fine.
Seems there has been some compression to the setup_av_free.exe at 54.2MB much smaller than the 6.0.1091 installation file.
No, it's actually about 1MB larger. Re-download the 1091 installer and you'll see.
-
The update went fine Free AVAST 6.0.1119 the language french (XP Professional sp3 - IBM THINKCENTRE 8189)
thank you
-
..update on top of the last beta.... everything fine as supposed to :)
Greets
S@uDepp
-
Hi!
The latest compilation works for me without a glitch (Win 7 x64)! And indeed, the boot performance seems to be slightly better as well.
I don't know, if it's the place for a suggestion (I'm sorry in advance if it's not): could you put the "potentially dangerous programs" detection option to be activated in all (or some) shields as soon as during installation? Like in ESET products (I hope mentioning ESET doesn't mean death penalty ^_^)?
-
No problems here so I'm waiting for the release too. I don't expect it to be very long of a wait. ;D
-
Just updated over the top of 6.0.1091 and appears to be fine.
Seems there has been some compression to the setup_av_free.exe at 54.2MB much smaller than the 6.0.1091 installation file.
No, it's actually about 1MB larger. Re-download the 1091 installer and you'll see.
No need it was explained that the compression package wasn't applied to the download that I got.
-
Updated over existing AIS 6.0.1091 and so far no problems.
DJBone
-
Just upgraded from 6.0.1091 to 6.0.1119 on my Windows 7 (X86) system. So far no problems.
-
Downloaded and Installed and thank you
-
Installed over 6.0.1091 and it's working very smooth so far. :)
-
Installed over last stable build..and everything working fine
but why is -when updating from a previous version of avast Pro/IS, SafeZone is now automatically added this option added...i dont want safezone so it should not be automatically installed
and there can be more options added in custom installation
-
Hi Vlk,
I just installed avast on top of previous version, and from the performance and speed is quite good enough.
But i found that on WebRep function which's previously if we search link from google in example, avast WebRep will displayed in detailed beside each's link.
But on this new version, i don't see avast WebRep graphic (please see attached file)
-
Oh my goodness... What the hell is AVAST doing? Permanent Beta isn't a good strategy.
After expericing BSOD when updating to 6.0.1901 (FIRST occured in a RC version just before 6.0.1901, the build number of which I can't remember), I've switched to F-secure...
Please DO solve all bugs before releasing an OFFICIAL STABLE VERSION, Not forever fixing, please.
-
Oh my goodness... What the hell is AVAST doing? Permanent Beta isn't a good strategy.
After expericing BSOD when updating to 6.0.1901 (FIRST occured in a RC version just before 6.0.1901, the build number of which I can't remember), I've switched to F-secure...
Please DO solve all bugs before releasing an OFFICIAL STABLE VERSION, Not forever fixing, please.
Ziucqea this is not a final release of Avast, release candidate mean beta testing for another words Avast get many users to help test the beta software to report back for bug problem. When all the problem get solved Avast will release as a final version, so try not to get worried because I'm very glad to see more and more users helping Avast for testing the release.
-
Oh my goodness... What the hell is AVAST doing? Permanent Beta isn't a good strategy.
After expericing BSOD when updating to 6.0.1901 (FIRST occured in a RC version just before 6.0.1901, the build number of which I can't remember), I've switched to F-secure...
Please DO solve all bugs before releasing an OFFICIAL STABLE VERSION, Not forever fixing, please.
I wouldn't describe the situation as a permanent beta. 6.0.1119 is a Release Candidate, not a release, but I do think that 6.0.1091 should have been an RC rather than an official release.
Ah, the wonder of hindsight. ::)
That said, I do have AIS 6.0.1091 running sweetly on all but one of my PCs. However I'm sticking with 5.1.889 on my "Xtreme BSOD" machine until I'm well and truly convinced that the issue/conflict is fixed.
-
Oh my goodness... What the hell is AVAST doing? Permanent Beta isn't a good strategy.
After expericing BSOD when updating to 6.0.1901 (FIRST occured in a RC version just before 6.0.1901, the build number of which I can't remember), I've switched to F-secure...
Please DO solve all bugs before releasing an OFFICIAL STABLE VERSION, Not forever fixing, please.
Ziucqea this is not a final release of Avast, release candidate mean beta testing for another words Avast get many users to help test the beta software to report back for bug problem. When all the problem get solved Avast will release as a final version, so try not to get worried because I'm very glad to see more and more users helping Avast for testing the release.
You msiunderstood me, I'm talking about 6.0.1091, the latest official released stable version.The BSOD first occured at the RC version just before it.
Btw, do you know what is meant by 'Permanent Beta'?
-
Oh my goodness... What the hell is AVAST doing? Permanent Beta isn't a good strategy.
After expericing BSOD when updating to 6.0.1901 (FIRST occured in a RC version just before 6.0.1901, the build number of which I can't remember), I've switched to F-secure...
Please DO solve all bugs before releasing an OFFICIAL STABLE VERSION, Not forever fixing, please.
I wouldn't describe the situation as a permanent beta. 6.0.1119 is a Release Candidate, not a release, but I do think that 6.0.1091 should have been an RC rather than an official release.
Ah, the wonder of hindsight. ::)
That said, I do have AIS 6.0.1091 running sweetly on all but one of my PCs. However I'm sticking with 5.1.889 on my "Xtreme BSOD" machine until I'm well and truly convinced that the issue/conflict is fixed.
No No No, 6.0.1091 IS an official stable version.
-
6.0.1091 IS an official stable version.
Yes it is. The thread you are now posting in is for issues pertaining to version 6.0.1119, so if you installed this version, continue to post in this thread. Otherwise, please open up a new thread. Thank you.
-
has avast ever considered adding an option into the avast settings to "update to beta/RC versions"? these pre-release versions come out and i think it would be convenient to have an option in the settings for users that like to test pre-release versions to be auto updated like regular program updates. some other AV's have this option like Emsisoft, ESET and such.
I would like that too, because my ISP charges me Rs.750 or approx $17 for 2GB data. So it will be very beneficial..
Helpful for those who always want avast in its latest form like me whether beta or RC or pre-release...
We will be thankful...
Thanks
Ash
-
Surprise!
- improved tolerance for corrupted installations
What does it mean?
- when updating from a previous version of avast Pro/IS, SafeZone is now automatically added
Thanks.
- Behavior Shield: improved compatibility with other applications
Such which? I mean, is it the compatibility with other behavior scanners (Threatfire, for instance)?
- improvements in the CommunityIQ submission system
Can you elaborate?
I thought somebody will explain this...
Well Waiting...
Thanks
-
Can you post the contents of the file C:\ProgramData\AVAST Software\Avast\Log\AutoSandbox.log?
If you tell me how to i would be most grateful
-
Just open the file, it opens in notepad, and then you can copy the contents.
I would guess that any relevant info would be near the bottom, so take a look through to save you pasting loads of it. ;)
ProgramData is hidden, so you will have to unhide it. (or just open notepad, and post that path into it)
-
:44 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
30/04/2011 11:18:44 Autosandbox candidate: C:\Program Files\Common Files\Logishrd\eReg\SetPoint\eReg.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
01/05/2011 06:46:53 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
01/05/2011 06:46:54 Autosandbox candidate: C:\Program Files\Common Files\Logishrd\eReg\SetPoint\eReg.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
02/05/2011 07:35:45 Autosandbox candidate: C:\Program Files\Common Files\Logishrd\eReg\SetPoint\eReg.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
02/05/2011 16:48:21 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
02/05/2011 16:48:23 Autosandbox candidate: C:\Program Files\Common Files\Logishrd\eReg\SetPoint\eReg.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
03/05/2011 06:40:24 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
03/05/2011 06:40:38 Autosandbox candidate: C:\Program Files\Common Files\Logishrd\eReg\SetPoint\eReg.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is tru
Is this OK?
-
03/05/2011 06:40:24 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
03/05/2011 06:40:38 Autosandbox candidate: C:\Program Files\Common Files\Logishrd\eReg\SetPoint\eReg.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
03/05/2011 08:47:42 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
03/05/2011 08:47:45 Autosandbox candidate: C:\Program Files\Common Files\Logishrd\eReg\SetPoint\eReg.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
03/05/2011 09:14:57 Autosandbox candidate: C:\Users\MyName\Documents\New Issues\autosandboxme.exe
[Source: http://public.avast.com/dev/autosandboxme.exe]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (based on user's decision).
03/05/2011 12:03:03 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
03/05/2011 12:03:10 Autosandbox candidate: C:\Program Files\Common Files\Logishrd\eReg\SetPoint\eReg.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
03/05/2011 16:27:53 Autosandbox candidate: C:\Users\MyName\Documents\New Issues\autosandboxme.exe
[Source: http://public.avast.com/dev/autosandboxme.exe]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (based on user's decision).
03/05/2011 18:02:43 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
03/05/2011 18:02:47 Autosandbox candidate: C:\Program Files\Common Files\Logishrd\eReg\SetPoint\eReg.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
04/05/2011 07:21:59 Autosandbox candidate: C:\Program Files\Common Files\Logishrd\eReg\SetPoint\eReg.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
04/05/2011 13:43:25 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
04/05/2011 13:43:28 Autosandbox candidate: C:\Program Files\Common Files\Logishrd\eReg\SetPoint\eReg.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
04/05/2011 15:44:12 Autosandbox candidate: C:\Users\MyName\AppData\Local\Temp\nstE42F.tmp\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Users\MyName\Documents\New Issues\SetupAnyDVD6800.exe]
--> Result: Not sandboxing (because the file is trusted).
04/05/2011 15:44:13 Autosandbox candidate: C:\Users\MyName\AppData\Local\Temp\nstE42F.tmp\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Users\MyName\Documents\New Issues\SetupAnyDVD6800.exe]
--> Result: Not sandboxing (because the file is trusted).
04/05/2011 15:44:22 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Program Files\SlySoft\AnyDVD\AnyDVD.exe]
--> Result: Not sandboxing (because the file is trusted).
04/05/2011 15:44:24 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Program Files\SlySoft\AnyDVD\ExecuteWithUAC.exe]
--> Result: Not sandboxing (because the file is trusted).
04/05/2011 15:45:07 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Program Files\Elaborate Bytes\CloneDVD2\ExecuteWithUAC.exe]
--> Result: Not sandboxing (because the file is trusted).
04/05/2011 17:57:06 Autosandbox candidate: C:\Users\MyName\AppData\Local\Temp\DC3Dx86.exe
[Source: ]
[Opened by: C:\Windows\system32\rundll32.exe]
--> Result: Not sandboxing (because the file is trusted).
04/05/2011 18:00:40 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
04/05/2011 18:00:42 Autosandbox candidate: C:\Program Files\Common Files\Logishrd\eReg\SetPoint\eReg.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
04/05/2011 18:08:35 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
04/05/2011 18:08:37 Autosandbox candidate: C:\Program Files\Common Files\Logishrd\eReg\SetPoint\eReg.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
05/05/2011 06:59:22 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
05/05/2011 06:59:25 Autosandbox candidate: C:\Program Files\Common Files\Logishrd\eReg\SetPoint\eReg.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
05/05/2011 16:07:59 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
05/05/2011 16:08:03 Autosandbox candidate: C:\Program Files\Common Files\Logishrd\eReg\SetPoint\eReg.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
05/05/2011 17:38:22 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
06/05/2011 10:20:47 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
06/05/2011 13:10:54 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
06/05/2011 18:27:47 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
06/05/2011 18:29:06 Autosandbox candidate: C:\Users\MyName\Documents\New Issues\autosandboxme.exe
[Source: http://public.avast.com/dev/autosandboxme.exe]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (based on user's decision).
06/05/2011 18:38:24 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
06/05/2011 20:27:11 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
07/05/2011 07:47:18 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
07/05/2011 09:30:50 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
07/05/2011 10:08:46 Autosandbox candidate: C:\Program Files\SlySoft\AnyDVD\AnyDVDtray.exe
[Source: ]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (because the file is trusted).
-
after i update to the new version i have a problem when i start ultra defrag 5
can not query bootexecute value!
process canceld and handle invalid
-
rambo1940,
Seems from what I can see that it is working. I also see that you have it on ask.
Auto SandBox still does not work
When i run the test tool all i get is "Modify System"
06/05/2011 18:29:06 Autosandbox candidate: C:\Users\username\Documents\New Issues\autosandboxme.exe
[Source: http://public.avast.com/dev/autosandboxme.exe]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (based on user's decision).
So you didn't elect to run the file in the sand box. Hence the modify system thing came up without the red border. If you choose to run it in the sandbox, then it will be in a red border and modifications will be kept in the sandbox, and deleted when the app is closed.
-
same problem as with 1091 build,
my script shield shows zero behaviour on IE9 (both 32bit and 64bit)
this includes pages opened locally (from HDD) and from web
OS: Windows 7 SP1 x64
-
rambo1940,
Seems from what I can see that it is working. I also see that you have it on ask.
Auto SandBox still does not work
When i run the test tool all i get is "Modify System"
06/05/2011 18:29:06 Autosandbox candidate: C:\Users\username\Documents\New Issues\autosandboxme.exe
[Source: http://public.avast.com/dev/autosandboxme.exe]
[Opened by: C:\Windows\Explorer.EXE]
--> Result: Not sandboxing (based on user's decision).
So you didn't elect to run the file in the sand box. Hence the modify system thing came up without the red border. If you choose to run it in the sandbox, then it will be in a red border and modifications will be kept in the sandbox, and deleted when the app is closed.
Thanks
I am just beginning to understand at long last
Regards
-
Thanks. Updated over 6.0.1091 Free and no problem so far. 8)
-
Did a thorough uninstall of AIS and reinstalled Pro. Was able to verify in the OA case at least that AIS without firewall with OA loads programs significantly more slowly than Pro with OA, even programs that are excluded from OA. So the OS understands they are both there and is doing something differently even with the uninstalled firewall. Avast! action is to provide a way for users with AIS licenses to downgrade to Pro if they want to use a different firewall-reports here say that for standard AIS licenses that is not possible because of the installer recognizing the license class-see http://forum.avast.com/index.php?topic=77198.msg639986#msg639986 .
Another problem with both installations was that I was unable to bring up the Safe Zone Browser until I reset the Safe Zone, and that bringing it up takes 2 clicks in spite of my selecting single click for launching programs. That fixes the problem, apparently permanently, but is a workaround not everyone will find easily.
Otherwise all still working well. ;D And faster.
-
sded I don't know what you did but simply disabling the firewall in AIS doesn't have the same effect as actually uninstalling it. As long as the FW driver is loaded the module will keep monitoring connections, even if no rules are applied anymore on Avast side. As to the slow down, I've experienced this by just disabling AIS fw and running Comodo fw several months ago. Only way out is to uninstall the component, but there's a drawback, like if you change your mind it's rather hard to re-install AIS fw, it just fails most of the time (module not running/service not present) and requires a new install from scratch.
edit: reading your post again I see you uninstalled the FW from AIS so okay I don't know, I never observed any slow down in these conditions (ie running another firewall)
-
logos, the slowdown is apparent and repeatable for certain applications (Power Desk for example in my case, others in the referenced thread in the OA Forum). I first tried excluding slow programs from OA also, but that didn't fix the problem. I think being able to downgrade AIS licenses to Pro would be a satisfactory solution for most users (unless they desperately need the anti-spam add on). I actually did a custom installation of AIS with the firewall unchecked for the latest builds, BTW, although I have uninstalled it before with similar results.
-
has avast ever considered adding an option into the avast settings to "update to beta/RC versions"? these pre-release versions come out and i think it would be convenient to have an option in the settings for users that like to test pre-release versions to be auto updated like regular program updates. some other AV's have this option like Emsisoft, ESET and such.
Now that is a very good suggestion imho. Might worth considering there.
-
Now that is a very good suggestion imho. Might worth considering there.
Well, you can always come to the forum to get the latest beta/pre release... ;)
Else, just wait for the final version.
-
logos, the slowdown is apparent and repeatable for certain applications (Power Desk for example in my case, others in the referenced thread in the OA Forum). I first tried excluding slow programs from OA also, but that didn't fix the problem. I think being able to downgrade AIS licenses to Pro would be a satisfactory solution for most users (unless they desperately need the anti-spam add on). I actually did a custom installation of AIS with the firewall unchecked for the latest builds, BTW, although I have uninstalled it before with similar results.
Ed, this is good news. I do use PowerDesk and it seems to take forever to load. Just disabled Firewall for 10 minutes and up popped PowerDesk very quickly. Never suspected AIS.
Appreciate the tip. Now to check the other computers.
-
has avast ever considered adding an option into the avast settings to "update to beta/RC versions"? these pre-release versions come out and i think it would be convenient to have an option in the settings for users that like to test pre-release versions to be auto updated like regular program updates. some other AV's have this option like Emsisoft, ESET and such.
Now that is a very good suggestion imho. Might worth considering there.
To be honest making it too easy for people to use beta or pre-release builds is a bad idea. Even with beta or pre-release versions being notified in the forums there are still people that shouldn't be running beta builds of security software on their systems.
For many they don't understand the potential for problems and that it could have serious repercussions that they simply aren't experienced for. Unless you are using a test-bed system or have a robust backup and recovery strategy (disk imaging software, etc.), then you really shouldn't be running beta builds of security software and that includes avast.
But this is rather off-topic for this topic.
-
I think making easy the beta update is a good thing. It could be a setting with a further warning.
By the way, working normally in my system. Another very stable beta version.
-
The update on my Windows 7 x64 went fine. No problems here.
-
Hi
Auto sandbox is not working.Using test tool a notification appears "modify system'. Can it be fixed?
Thanks
Relu
-
Hi
Auto sandbox is not working.Using test tool a notification appears "modify system'. Can it be fixed?
Thanks
Relu
That notification is supposed to appear but if you choose to run the file in the sandbox, no changes will be made. If you choose to run it normally (outside the sandbox) the changes are made to the registry and the root of the hard drive. That is the test, to look in those areas and see if the changes occur while the file is sandboxed.
-
I was thinking if Avast could add automatic computer shut down option after a full scan into the latest version when some virus are moved into chest, and later on or the next day or two when you turn the computer on an automatic pop-up box saying a number of virus have been found and moved to chest etc etc.
What do you think about this option ??? sound like a good idea or not ??? ???
-
I was thinking if Avast could add automatic computer shut down option after a full scan into the latest version when some virus are moved into chest, and later on or the next day or two when you turn the computer on an automatic pop-up box saying a number of virus have been found and moved to chest etc etc.
What do you think about this option ??? sound like a good idea or not ??? ???
Its already there..
-
Ur handwriting very bad ashish :P
-
One Problem area was covered by .1119 which I never thought it was an avast! associated thing:
In version .1019 when you closed the Firefox window and immediately reopened it I allways got a warning that the process is still running. So I had to wait after closing for about 5 seconds to be able to reopen Firefox again.
With version .1119 this behavior does not exist anymore. I can reopen Firefox now immediately after closing without any Problems and/or warnings.
Good move!
-
Ur handwriting very bad ashish :P
Sorry off topic...Ya but only in paint..or say computer not in real..I am a winner of Handwriting competition at regional level both in Hindi and English..
Thanks I just wanted the user to understand avast and was not showing my handwriting
See better version here
Ash
-
Hello,
just a short feedback regarding the aswSP.sys BSOD condition. To of our users testing the new pre-release in this regard already reported that the situation got better due to the installation of the pre-release. Of course we are awaiting more feedback from them, because the BSOD condition only appeared intermittently.
-
If Avast really wants to get serious about limiting the usage of its Beta releases, which by the way I agree with @DavidR on this one they need to tighten up access to the Beta installer links.
This is what I would suggest. :)
1. Avast needs to start identifying the installer file as a Beta in the file name
2. Avast needs to start identifying the release as Beta in the GUI.
3. The forum needs to set up a Beta thread that users have to opt into in their profile in order to get to the Beta release download links. People who want to download the Beta should be required to opt into the Beta thread for each new Beta release.
4. Eliminate GUI updates for Betas.
5. Put up a big disclaimer and warning right above the installer links, not a one sentence comment about the release being a Beta release.
-
4. Eliminate GUI updates for Betas.
And how do you want to test the update process? The way it was handled in v4 was the best, there was a few kB update that just patched the server list and the update was done through the builtin updater.
-
I took place in the last RC test, but the current version is running so well on my machines, that I will wait for an official version this time around. :P
-
And how do you want to test the update process? The way it was handled in v4 was the best, there was a few kB update that just patched the server list and the update was done through the builtin updater.
+1
Why are you that afraid about betas? Do you really think people that come here in forum does not read the original post with beta links? C'mon... We have a lot of people here, advanced users, that do not (or can't) test the beta...
-
1. Avast needs to start identifying the installer file as a Beta in the file name
yes, because too many people don't read or understand Vlk's posts... although it's crystal clear ::)
2. Avast needs to start identifying the release as Beta in the GUI.
yes, same reason as above.
3. The forum needs to set up a Beta thread that users have to opt into in their profile in order to get to the Beta release download links.
there's already a beta thread. We're now talking about pre-release versions of Avast, not betas really.
4. Eliminate GUI updates for Betas.
why ??? as said that's needed to test updating abilities of the build, and once you're on the beta channel, you expect beta updates, nothing wrong about that. >>> people who are not on the beta channel, ie people who didn't download and install the first beta manually and purposely have nothing to gear from beta updates: as they won't happen. Having to state something so obvious for the nth time is sort of... okay ::)
5. Put up a big disclaimer and warning right above the installer links, not a one sentence comment about the release being a Beta release.
yes okay, although Vlk again makes it clear that the build is a pre-release.
-
By the way, I agree with you and Logos on 1 and 2.
-
Why should Avast! be interested in limiting usage of an open beta or RC or prerelease? The idea is to get it out to as diverse a group of testers as possible before it is released in order to try to cut down the problems of the wider audience of 150M or so people. And if a few people get it unintentionally and have problems that go into the fixit pile, so many problems less to deal with downstream. ;D
-
Clean install of this build in Windows 7 x64, all run well but Mozilla Firefox 6.0a1 x64 (Nightly build) no more start (error everytime). Mozilla Firefox 5.0b x86 running well, no errors, but the web app of Avast is incompatible.
:-\
-
Well, seeing the thread having gone completely off topic, i.e. rendering the beta kinda pointless... maybe we should forget about betas altogether?
-
Nice, I just changed my connection and because AIS was unable to detect the new network (bug 1) I just manually deleted all network profiles, stopped the firewall, restarted it and this time it detected the new network just fine, but immediately froze. Looking in Process Explorer, I now have two afwServ.exe processes, one at 100% CPU (bug 2).
-
Well, seeing the thread having gone completely off topic, i.e. rendering the beta kinda pointless... maybe we should forget about betas altogether?
No Igor... just the thread is bloatware by its nature... Maybe you have to open the beta forum each time and each user open a thread for his/her problem.
-
i have determined that avast is blocking something on my internet connection because every once and awhile i get no internet connection. i know this has to do with avast because when i have avast on i receive this problem and when i turn avast off it goes away :-\
-
nice beta test copy no issue other than google chrome web rep :P
-
Just downloaded 6.0.1119 So far, everythings fine. But in the past Avast 6.0 versions, I would get a BSOD after one week. Will keep testing.
-
has avast ever considered adding an option into the avast settings to "update to beta/RC versions"? these pre-release versions come out and i think it would be convenient to have an option in the settings for users that like to test pre-release versions to be auto updated like regular program updates. some other AV's have this option like Emsisoft, ESET and such.
Now that is a very good suggestion imho. Might worth considering there.
To be honest making it too easy for people to use beta or pre-release builds is a bad idea. Even with beta or pre-release versions being notified in the forums there are still people that shouldn't be running beta builds of security software on their systems.
For many they don't understand the potential for problems and that it could have serious repercussions that they simply aren't experienced for. Unless you are using a test-bed system or have a robust backup and recovery strategy (disk imaging software, etc.), then you really shouldn't be running beta builds of security software and that includes avast.
But this is rather off-topic for this topic.
At least many ESET users run pre-release updates without any ill effect, including myself.
They are thoroughly tested before they are release for public consumption.(Off topic) :-[
-
I am a little confused,
There is a Beta forum that says, "Discussion About The New Beta" for it's subtopic, so why not put all Beta and Release Candidate Releases in that forum? Or would not enough people go to the Beta forum, so we should keep the Beta and RC releases in the General Forum like they are now?
Jack
-
I am a little confused,
There is a Beta forum that says, "Discussion About The New Beta" for it's subtopic, so why not put all Beta and Release Candidate Releases in that forum? Or would not enough people go to the Beta forum, so we should keep the Beta and RC releases in the General Forum like they are now?
Jack
+1
-
I am a little confused,
There is a Beta forum that says, "Discussion About The New Beta" for it's subtopic, so why not put all Beta and Release Candidate Releases in that forum? Or would not enough people go to the Beta forum, so we should keep the Beta and RC releases in the General Forum like they are now?
Jack
+1
+2 ;)
-
may be try to correct this before releasing the next build:
http://forum.avast.com/index.php?topic=77717.0
(tested with current stable)
-
I have to repeat my question. What about the language-depending GUI bug in Vista (http://forum.avast.com/index.php?topic=75220.0)?
-
10 minutes before while i m browsing a pop up window appeared showing "avast network shield blocked a threat"(using 6.0.1091 updated from 1027).But the network shield log shows connections blocked 0, why? Sorry if this question irrelevant to this topic, I m here for the first time. :o
-
Hey VLK,
There is a longer thread going about this, but if it helps.
I am experiencing a conflict with the core part of AVAST (not a shield) that renders Auto CAD LT 2002 unusable.
For V6.0.0 I could disable the shields and use AVAST. For this beta release, and the full release before it, something changed and disable all shields no longer solves the problem. I'm hoping this is something that can be corrected.
Thanx
Hawker
Last post of the old thread below...
I spent some time this morning trying to work this out with little luck.
Here is where I am at. All these are "free" versions.
Avast 6.0.0. ACAD LT crashes with GEDIT 3 errors. If I disable all shields AVAST ACAD runs fine.
Avast 6.0.1091 same as above but disable all shields does not allow ACAD LT to run.
Avast 6.0.1119 same as .1091.
I tried uninstalling the behavior shield and nmb suggested with no effect. I then uninstalled every shield one at a time to see which one caused the problem. With all shields uninstalled ACAD still crashed fairly fast. To check myself I then completely uninstalled AVAST and ACAD ran fine again.
What I can conclude from this is the problem is not in a particular shield but in some common core part of AVAST that runs outside the shields themselves.
Any idea what to do next other than use a different AV program?
-
I am a little confused,
There is a Beta forum that says, "Discussion About The New Beta" for it's subtopic, so why not put all Beta and Release Candidate Releases in that forum? Or would not enough people go to the Beta forum, so we should keep the Beta and RC releases in the General Forum like they are now?
Jack
+1
+2 ;)
+3! LOL!
Seriously Avast,
You guys have a Beta forum for the community, so it would help if all Beta releases and questions went in there. This forum, Avast Free/Pro/Suite, should be about the current releases to the general public. This is because IMO, there are too many people who don't understand that Beta/RC candidates mean "Not Done Yet. May be buggy!"
However, at the same time, the Beta forum would provide ample testing for experienced users, who understand about Beta's. The Beta forum should provide the opportunity to test, without current full release threads getting in the way. This would simplify things for everyone.
Jack
-
yeah I guess they should use something similar (screen shot) ... that's what they say on the Opera blog when they release a new beta ;D
-
A bug in 6.0.1119?
1. avast didn't detect the ZIPPED Eicar even when I check 7zip archive, RAR archive and ZIP archive in File System Shield Packers settings. I have set File System Shield to test whole file. The rest of the settings are in default.
-
I am getting an error message any advice please.
-
It wouldn't hurt if you tell us what was the error...