system
13
Program version: 17.3.2291
Build: 17.3.3443.0
Virus definitions: 170425-2
Platform: Windows 10
(Values correct when email drafted today. Conceivably I was on slightly earlier versions when starting the problematic scan yesterday).
These problems are still unfixed. Surprising, as I read above that they were known problems at the beginning of the month.
I started a full scan yesterday. It stayed on 0% for several HOURS, so I left it running overnight (I have a lot of disks).
In the morning it had finished with a message saying that the scan had been cancelled at 98% complete.
Having said that, the results appeared to be complete.
These bugs aren’t just a minor irritation for experienced users. Try putting yourself in the shoes of an inexperienced user who is worried s/he has just been infected. S/he starts a scan and nothing happens (ie, progress stays at 0% for ages), so s/he worries that the infection is preventing the anti-virus software from running. Then s/he sees a message that the scan has been cancelled - s/he didn’t cancel it, so the infection must be to blame. And what do you do if an infection has bettered your anti-virus software? - you switch to another vendor’s product.
Avast developers… in my opinion leaving glaring bugs like this unfixed for weeks will cause you reputational damage, so I suggest you fix them pronto.