@david 12, @Ed Blackshaw
Most of my "constituents" are using 2002 or later, most of them using 2005. So I have not had the opportunity to cross this particular issue. Even so, when AVG removes an offending binary it is placed in the Virus Vault, which can be restored and set to ignore in the event of false positives. FAQ 1203 tells you how to deal with false positives, including submitting them to AVG.
AVG Free tends to be a little more "in your face" than the full editions. Anything free has a trade-off. I am running Internet Security on my production laptop and I never see it.
But that is not to say that I do not have some objections to the AVG system. In particular, as IT I frequently advocate against the use of browser tool bars as multiple tool bars can conflict with each other, and older or poorly coded ones can simply stop the browser from working (*ahem* Lexmark.) So AVG introduces the AVG Toolbar. Not exactly a happiness for me, and I certainly expressed that to them.
As for any other problems I have with AVG, I submit my concerns and they are quickly answered. I often field feedback from my, and from other, users and get them up to AVG which, again, deals with them in a timely manner. I even go so far as to send ElReg articles up through my support channels, though I believe some folks in the chain are regulars here already.
Believe me, AVG listens to you. I think it is one of the few software vendors which still does. Even the LinkScanner debacle (on which you can find my opinion in other Reg articles) was dealt with based upon user and non-user feedback.
And I fall back upon my previous statement that no AV vendor is perfect, and doubly so for software vendors as a whole. But that does not excuse them from completely disabling a system. And given that, I believe that AVG has never rendered a system non-bootable by its own actions.
In any case, my intention is not to hijack this article to push AVG, but rather to answer to what I can.
Paris, a little more in-your-face as well.