You got the engine there but you don't use it properly at all.
I mean it's really completelly useless, intrusive and far from what it suppose to do.
With just a small tweaking you could get very nice proactive protection but you simpy don't put any work into it :'(
I said this before and nothing was done, so i'll do it again in hope you'll realize this for version 4.8 or even before.
avast! should check what selected (or default ones) extensioned files DO, not what happens to THEM.
For example avast! now checks if lets say file SCR gets created, modified, deleted or renamed. But in fact it should check what SCR file does to the system. I mean it's not nearly common that SCR file creates other EXE files on hard disk.
Or VBS/BAT file deleting files located in system directory.
Or PIF files execution on Windiows XP/2000 systems. It's clearly a malware since no one uses this kind of stuff except for malware.
Now Behaviour Blocker warns you when SCR file is copied to HDD, but it should warn us not when SCR file is created on HDD but when SCR file tries to create new files on HDD. Screensavers don't do that...
You can maintain it with just few lines of rules on how behaviour blocker should act.
Back it up with nicer warning message (more like the ones used when virus is detected), exclusion system and updatability via VPS and you get an excellent stuff. Protection of critical registry entries could also be an option that i'd be glad to see.
You'll say that i'm nagging about this stuff just because i want to have heuristics/proactive protection but lets face it, engine is there, waiting to be twaked/improved but it hasn't moved anywhere since version 4.1 (don't know how it was before that). If done properly it could work nearly as good as Kaspersky's new Proactive Defense (which does pretty much the same thing).
But it's your choice...
