I do not want to downplay the irritation that folks feel when there is a false positive from any of the protection solutions they employ. Sometimes (I know it is only sometimes) those false positives turn out to be real detections.
You do have the choice to "continue" you also have the choice to add files you believe to be false positives to the "on access" exclusion list in the Standard Shield of avast while the problem is being resolved.
I know that there have been a number of "higher profile" false positives in avast recently and, having been affected by some of them too, I am aware of how it feels.
I am certain that the very professional team running avast are also keenly aware of this issue too.
This is one of those "damned if you do - damned if you do not" circumstances. In this forum you will find others complaining with equal vehemence that avast is not fast enough in adding detection for known viruses. So, the avast team's efforts to be more responsive and rapidly include detections made available to them produce the false positives we are seeing.
I sincerely hope that, on reflection of their quality control processes, the avast folks can find a balance that better satisfies the concerns of those irritated by false positive and those demanding faster responsiveness to threats.
When I reflect on the downside of false positives it is my hope that avast will err on the side of caution. Though I too get irritated and vent my frustration here when faced with false positives I try to remember how much I and those I support (do not) pay for this excellent product, for the outstanding interaction with the development team and the invaluable effort of others given freely in this forum.
All of us get to make the choices of which product we will go with. Can avast do better? I know they can but, more importantly, I believe they know they can ... and will. I will stick around to see them do so.