41

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

42

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…

43

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

44

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…

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 ?

46

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

47

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

48

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.

49

It is.

50

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.

51

See the difference under W7.
BTW: If you start a scan, all avast features are working, but ‘UI’ twice!
:wink:
=Snake=

52

When will be this version released as final? It is known? Thanks

53

Description says “Behavior Shield”, but the file naming scheme itself is still totally out of place…

54

Actually it is not out of place. aswbIDSAgent - Avast Software behavior intrusion detection system agent. The description should be enough for the users though.

55

Opposed to simply calling it “AvastBehaviorShield.exe” ? :-\

56

I find that the full scan has unfortunately too little details (what grade scan avast or if he finds anything that you don’t look which file is made and always have to wait until the full scan to the end is.) And it takes forever just to the scan starts I hope that will change.
Yesterday it took 40 minutes to avast did the scan at 1%.
In the scan history is unfortunately also not what were scanned is.

Sorry if my English is not the best.

57

Seems like new beta (17.2.2288) is released.

Avast… (checkboxes were unchecked by me!)
Beta testers are doing you a favor. If possible, please stop pushing this nonsense to BETA users.
Kinda takes away the will to beta test… really.

58

Well beta testers have to test ‘everything’ even this onerous push for Chrome.

EDIT: Typo

59

Yes, sure. But I’ve been reporting this “irritation” for quite some time. They told it’s not gonna happen with each update. So far - it has been (between betas).
It’s just that BETA users should be free of such things. I specifically used “if possible” because most likely these things are hard-programmed and can not be removed for BETA only (or not that easily).

60

We have been shouting about this (pre-checked option) for some considerable time, as they say there are none so deaf as those that won’t listen.

It is still there and I can’t see that changing any-time soon, it still attracts derision from those who don’t see it (or don’t take time to read before clicking) and end up with chrome.