I agree that “mistakes happen” , especially with this type of software.
However, Avast owes it to their users to explain why this happened, and what they are doing to prevent it in the future. This was not some minor problem… but was a very serious issue that had a large impact for many paying customers. If Avast expects us to STAY as their customers, they need to respond and help us understand what they are doing internally to prevent this from happening again.
Further, considering how obviously broken that definition update was, it is clear that Avast does not do any testing of their updates prior to pushing them to production release. That’s not great.