Well, there's not much we can say about that...
Here's the avast program history page
http://www.avast.com/eng/av4_revision_history.htmlSee the line
- temporarily disabled the CHM unpacker (for security reasons) Seeing this line was enough for them to publish the above mentioned information (see the "Vulnerability reported by the vendor" note).
Anyway, the problem is there; it's in fact a Windows error - see
http://secunia.com/advisories/20061 . Since avast uses this library, it (probably) has this error as well (well, not the error, but the consequences). So we decided to disable the CHM unpacker until the problem is sorted out by Microsoft (or we find a way to avoid it - which is not too likely though).
Hmm, this is how easy it is to generate some bad press...
This sentence is completely unfair, and false:
"Betroffene Anwender sollten daher erwägen, bis zur sauberen Fehlerbeseitigung durch Alwil auf einen anderen Virenscanner umzusteigen."Cheers
Vlk
