 Avast Beta 17.2.2287

system · 2017-02-18T12:43:50.000Z

disable behavior shield , avast status monitor still have warning alert

system · 2017-02-18T14:29:13.000Z

unable delete instantly a sample that blocked by behavior shield

system · 2017-02-18T14:54:16.000Z

ymchen post:32:

unable delete instantly a sample that blocked by behavior shield

I can confirm that

Everything is blocked by the behavior shield cannot be delete from the virus Chest

system · 2017-02-18T15:22:11.000Z

system is dreadfully slow after this update. can barely browse the net going to reinstall and see if that helps.

edit: all seems fine after a clean install. something during the update must have caused an issue.

Para-Noid · 2017-02-18T19:21:01.000Z

I’m with the others. The GUI opens painfully slow. First I get an “over-sized” white box, then after a few seconds the GUI finally opens up.

system · 2017-02-19T06:07:12.000Z

restore setting config doesnt work

download latest configuration (thanks rejzor)
https://rejzor.wordpress.com/avast-protection-tweaks/

RejZoR · 2017-02-19T06:11:08.000Z

It fixed itself somehow only on one of my PC’s. On two of them it’s still broken. I don’t get it. And majority of people also can’t import it because the dialog is just empty. Why isn’t this getting fixed properly so people can finally import my config file?

system · 2017-02-19T10:36:55.000Z

only behavior shield not exclude . this option should excluded all shield scanning .

RejZoR · 2017-02-19T13:02:15.000Z

No, Behavior Shield should always have exclusions separate.

Lord_Ami · 2017-02-19T13:36:18.000Z

This just happened in VMware virtual machine I’m using. Any logs I should send?

Avast icon - About opens just fine.

system · 2017-02-19T14:30:43.000Z

RejZoR post:39:

No, Behavior Shield should always have exclusions separate.

disable all shield , behavior shield truely disable , that means behavior protection is a part of shield. i dont understand why need exclude scanning separate .

RejZoR · 2017-02-19T15:23:20.000Z

Because behavior and file scanning are VERY different methods of protection. Just because you want to exclude something from signatures, you don’t necessarily want to exclude it from behavior protection as well. Signatures are far more prone to false positives than behavior analysis…

Shaun985 · 2017-02-19T19:41:38.000Z

Maybe include an option on the global exclusions page to apply exclusions to Behavior Shield.

Eddy · 2017-02-19T21:11:03.000Z

And still no answer from avast about the 30+ fixes >:(

How are we supposed to test/check things if we don’t know what changes (amongst the other things) that we should test/check…

system · 2017-02-20T11:32:45.000Z

hi friends i have installed on system 17.1.2286 now i isntalled this 17.2.2287 when this 17.2 will be final
not beta it go automatilly show me final ? or i must manually install final 17.2 when will be online ?

Asyn · 2017-02-20T11:34:58.000Z

tubabuyukustun post:45:

hi friends i have installed on system 17.1.2286 now i isntalled this 17.2.2287 when this 17.2 will be final
not beta it go automatilly show me final ? or i must manually install final 17.2 when will be online ?

Both will work. If you don’t want to stay on the beta channel, you need to reinstall the final version.

Alikhan · 2017-02-20T12:51:09.000Z

It’s nice to see the process name of the behaviour shield changed to “Avast Behaviour Shield”.

DavidR · 2017-02-20T13:38:07.000Z

Alikhan post:47:

It’s nice to see the process name of the behaviour shield changed to “Avast Behaviour Shield”.

Not seeing any change here still shown as aswidsagent.exe in XP task manager 17.2.2287 (build 17.2.3409.0) a manual program check indicates I’m up to date.check.

Don’t know if this might be an XP thing, but avast indicates the behaviour shield is running.

Asyn · 2017-02-20T13:47:50.000Z

DavidR post:48:

Don’t know if this might be an XP thing…

It is.

Alikhan · 2017-02-20T14:01:13.000Z

DavidR post:48:

Alikhan post:47:

It’s nice to see the process name of the behaviour shield changed to “Avast Behaviour Shield”.

Not seeing any change here still shown as aswidsagent.exe in XP task manager 17.2.2287 (build 17.2.3409.0) a manual program check indicates I’m up to date.check.

Don’t know if this might be an XP thing, but avast indicates the behaviour shield is running.

Maybe it is XP related but they should be able to rename aswidsagent.exe in my opinion.

I’ve attached a screenshot of how it looks on Windows 10.

Announcements