** INTRODUCING: BETA VERSION OF AVAST 5.1 [NOW 5.1.807] **

[Hermite15]

okay all works fine now, concerning the wrong program update prompt, doesn't happen anymore after installing the new package. But I got another problem, all shields are off after each reboot. They get re-activated in a click but still, there's a problem. Also, I'm getting the message again that my AIS license has expired, and that's probably causing the shields de-activation...lol, re-activating the shields reactivate my licence too. Okay no big deal.

 That said I just gave a shot to my first boot scan on W7/64 and it worked fine. For obvious reasons it cannot scan EFS files but that doesn't matter, I'm glad to have the boot scan again, last time was with 4.8 on Vista32.

edit: Hi Red

[zfactor]

i installed my lic and i still have the buy now green box at the top but it shows my normal subscription anyone else see this?

[disPlay]

Downloaded and Installed it. Everything is running smoothly here

[DavidR]

OK I have seen my first Behaviour Shield event blocked, this belongs to Outpost Firewall Pro "ACS stands for Agnitum Client Security Service, part of Outpost Firewall Pro" which is required.

This is strange since Vlk said it was in Passive mode (so why would it record a blocking action ?):

*The Behavior Shield functionality is still incomplete in this build. And even in the final v5.1, it will work only in "passive mode", which means that the new sensors will be active but won't be stopping the attacks, just reporting them to our backend infrastructure (unless you have opted out from the avast! community membership). This is to allow us to collect enough data before enabling the real thing in Q1 2011.

Does this mean that although the Behaviour Shield says it has blocked this, that it actually hasn't (see image as it is running) ?

Edit: There is still no data relating to detections being entered into the BehaviourShield.txt file. This was something we were screaming in 5.0.677, but nothing seems to have been done about this as there were 12 & 9 so called infected items, image 3

[Hermite15]

nice option, the timing of Avast popups is now tweakable ...also,I'm noticing that the quickscan (so a pre-set scan) sensitivity and packers settings are not grayed out anymore. IIRC this was already doable through Avast.ini but I preferred to leave it to default, well it's supposed to be a pre-set scan, but okay, may be that's just for the beta phase.

 Oh yes, no change at all with the firewall... I was expecting at least the ability to abort connections, may be in 6.0...

[zfactor]

okay hmmm. if i do a fresh install and DELETE the 2 leftover folders from the uninstaller it works fine with no buy now green box???

[Coolmario88]

I hope i don't cause problem to anybody for asking but. Does the Interface of Avast 5.1 look different?

[zfactor]

no it really does not

[jadinolf]

Many thanks Vlk

[GloobyGoob]

• The Antispam will not scan emails unless: "avast! 5" in Exchange Client Extentions is unchecked, with avast! Antispam checked in DCOM Add-ins. (This is in Outlook 2007)
• The Firewall Packet Rules GUI bug is fixed, however, new rules that are added cannot be saved.
• I'm also experiencing the problem with some of the shields turned off at startup. (Mail + Web)

So far that's what I've found.. from a clean install (from scratch). Will continue to test.

[Hermite15]

hmm guys... I'm getting again and again the issue with all shields deactivated and a license expired message after each reboot, always fixed manually as I described above but it happens again.
 I installed from scratch, so an upgrade problem can't be the issue.

edit: the behavior shield doesn't seem to do more than it use to (on W7/64), not that it's just passive as Vlk described, but it still doesn't scan anything, probably still no rule sets like before.

[NON]

Installed and rebooted over 5.0.677 Free. Seems working properly.

OK I have seen my first Behaviour Shield event blocked, this belongs to Outpost Firewall Pro "ACS stands for Agnitum Client Security Service, part of Outpost Firewall Pro" which is required.

This is strange since Vlk said it was in Passive mode (so why would it record a blocking action ?):

*The Behavior Shield functionality is still incomplete in this build. And even in the final v5.1, it will work only in "passive mode", which means that the new sensors will be active but won't be stopping the attacks, just reporting them to our backend infrastructure (unless you have opted out from the avast! community membership). This is to allow us to collect enough data before enabling the real thing in Q1 2011.

Does this mean that although the Behaviour Shield says it has blocked this, that it actually hasn't (see image as it is running) ?

Edit: There is still no data relating to detections being entered into the BehaviourShield.txt file. This was something we were screaming in 5.0.677, but nothing seems to have been done about this as there were 12 & 9 so called infected items, image 3

Same here, but we can see some kind of details if you set BS options to "Ask".
I already see 5 "Asking" dialogs, 3 are about Mozy, 1 is services.exe and 1 is CIS.

Anyway, is it strange that there is too many (75) "blocked" actions, though "Analyzed" events are only 16... still increasing...

[Lisandro]

1. The firewall popup is not dismissing in some cases. Need to be closed/killed. It's frozen.
2. I didn't install a custumized sound package. There is only the possibility of exclusion
3. The Behav blocked Mozy :'(

[Hermite15]

nice on demand scan popup

[Charyb-0]

After three attempts to install finally got it. I guess I didn't get the correct install package the first two times. First time it reverted back to .677 after restart. Second time file shield and network shield did not work. Third time is a charm. I noticed that when you right click the avast ball that the menu disappears as it should now.