** NEW AVAST PROGRAM UPDATE RELEASE CANDIDATE 6.0.1119 **

[DavidR]

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.

[Lisandro]

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.

[BrollyLSSJ]

The update on my Windows 7 x64 went fine. No problems here.

[Relu]

Hi
Auto sandbox is not working.Using test tool a notification appears "modify system'. Can it be fixed?
Thanks
Relu

[Dch48]

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.

[SpeedyPC]

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

 

[Ashish Singh]

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..

[The_ChamP]

Ur handwriting very bad ashish

[jrace]

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!

[Ashish Singh]

Ur handwriting very bad ashish

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

[avadas.de]

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.

[Nesivos]

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.

[warlock]

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.

[DBone]

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.

[Lisandro]

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...