Well, even a non-lopsided selection of user selections for what action to commit would help. For the same reason that you don't want to get annoyed by having to repeatedly allow a process to commit a suspect action (i.e., you get to whitelist the event so it is remembered and you aren't asked again about it), why wouldn't you want the same remembrance feature for an unwanted action that you always will deny? There's obviously a whitelist: Trusted Processes (although this is more about trusting the entire process' actions rather than a particular one). Yet just as obvious that's missing is the converse: a blacklist of Untrusted Processes.
I suspect why there is no blacklist is that a specific event that you want to disallow for a process doesn't mean you want to disallow all events for that process - and that means having to record the specific event for the specific process that you want to disallow. Avast doesn't seem to record to that level. Trusting a process means you trust everything it does, not just the event that caused the popup. Well, to be frank, just because I want to allow a process to commit one event for which Avast generated a popup doesn't really mean that I want to trust every event capable by that process. But, hey, at least I get a coarse granularity in regulating trusted processes. I get nothing for an unstrusted or unwanted event.
If I don't want a process to repeatedly restore its registry startup item everytime it is running or loaded, why would I want to see that same prompt EVERY time? I can allow and ignore repeat events in Avast but I cannot disallow and ignore repeat events.
Think about it. If you loved filet mignon but had to pick out sewing needles every time you wanted to eat it, how long before you gave up eating the filet mignon? I certainly wouldn't use a word processor where I had to hit the Insert key after every keystroke to get back into insert mode. Similarly, how often will you tolerate getting repeatedly nuisanced by Avast before making a correction (in this case, disabling the Behavior Shield or the portion of it that generates the repeated nuisance). Security products should be background processes and not something you waste your time time continaully reconfiguring. The more time you waste on a security product then the less time you have for actually using your computer. Avast isn't why I have a computer.
For now, I've disabled the "system" option in Behavior Shield because I'm fed up with the repeated prompts. Getting nuisanced to the point of disabling features in a product is why OnlineArmor, Comodo, and other security products provide white/blacklists of processes so users don't have to waste time with all those prompts on already known good/bad processes. I've had to disable Avast's script shield, too, (actually I did a reinstall with it excluded) since it never did get fixed to stop interferring with scripts internal to programs. It caused too much nuisance so it got turned off. That's what happens with a feature that doesn't work well - or works too well but without options to remember the prior choice by the user.
I have a DVD player that stupidly has its Power LED on when the unit is off and the LED is off when powered up. Well, obviously I know when the unit is powered up because I see video output so I don't need an LED to tell me the unit is powered up. When the unit is powered off, I don't need a reverse functioning LED that is on to tell me the unit is off. Solution is to put black tape over the LED. So I put black tape over the offending/incomplete Behavior Shield option (and, for now, will let WinPatrol alert me to [most of] the same changes - but the free version makes detections late and why I'll have to look for something realtime). To get rid of the nuisance, I disable an option under the Behavior Shield so, yes, I have that choice. That I made that choice exhibits that the option is missing something, namely the converse of remembering allowed repeated events so it remembers disallowed repeated events.
I don't remember in which version of Avast when the Behavior Shield first appeared. At that time, there were no user configurable options but this shield was very passive. Then options were added and this shield became more aggressive. Alas, with incomplete user selectable actions, it could become overly nuisancesome. So Avast may very well improve on the HIPS functionality of their Behavior Shield but obviously if they don't their customers/users want the enhancement. It's a pity they mix a help forum with a request forum since requests are not bug reports or asking for help but requests to improvement. I see lots of posts about deficiencies reported by users that would be appropriate in a Requests forum.
I reported a deficiency. Are you claiming that the deficiency doesn't exist? Yes, there's a workaround but that doesn't obviate the deficiency.