The avast version introduced a self-defence module and that has provided good protection against many viruses that go after the AV and firewall applications. However there is a new variant of beagle that can disable avast.
Not the actual version of avast wont make the slightest difference to detections as that the the province of the virus signatures and that is constantly being improved and for that they require samples of the virus file.
Now, from all your protestations (a more than slight over exaggeration of 1 million FPs) and information re detections avast has been getting on top of the majority of this problem, but hasn’t found what is launching the rootkits found on the anti-rootkit scan. However there hasn’t been a single shred of information of the file name and locations, etc. and that helps us to help you.
Check the avast! Log Viewer (right click the avast ‘a’ icon), Warning section, this contains information on all avast detections.
Also for the rootkit scan log, see C:\Program Files\Alwil Software\Avast4\DATA\log\aswAr.log
I appreciate your are angry, but don’t lets lose sight of the fact we are trying to help (and who clicked the .exe file).
Also see, anti-rootkit, detection, removal & protection http://www.antirootkit.com/software/index.htm. Try these as they are some of the more efficient and user friendly anti-rootkit tools.
Don’t forget if something is found, before deleting it try to capture a sample into the avast chest.
Send the sample to virus@avast.com zipped and password protected with the password in email body, a link to this topic might help and undetected malware in the subject.
Or you can also add the file to the User Files (File, Add) section of the avast chest (if it isn’t already there) where it can do no harm and send it from there (select the file, right click, email to Alwil Software). No need to zip and PW protect when the sample is sent from chest. A copy of the file/s will remain in the original location, so any further action you take can remove that.