Guys… not sure if Avast! team is really looking into here or not, but letting you guys know…
You bunch are acting very irresponsibly. A critical issue MUST be resolved within 24 hours as promised, and should have atleast replied saying it has been accepted.
A critical issue has been logged, with multiple screenshots attached, and its been over 72 hours now with nothing as little as an acknowledgement.
Wake up folks… you surely are making customers unhappy spoiling your reputation!
Frankly in all fairness, given it is December 24th. Christmas eve/day and the Holidays with a weekend very near, I doubt very much there will be any response in the next several days.
What bug do you mean?
It could be that it is not a bug at all.
Besides, a bug is only critical if it is causing a severe security issue, not just because you say it it critical.
Ladies and gentlemen, let me clarify. I am a software engineer, enterprise architect to be exact. I know what a critical issue is and what a trivial one is. Anyways…
Issue 1: Trivial: Saying some shields are down, and not mentioning which are…
Issue 2: Critical: Clicking “resolve all” to turn all back on hanging avast many a times, needing restart of system.
Issue 3: Critical: Sometimes clicking “resolve all” internally freezes avast while pushing message to windows monitoring services that everything is alright, giving false impression of antivirus working, when it actually isn’t.
Anyways, all this, and more info, with screenshots, has been posted in the bug report.
@schmidthouse: Issue reported first on Dec 21, 3 days before holiday. @Eddie: Maybe not all, but atleast a few people know what is critical and what is not. So do not generalize. Please.
@all the good folks out there who feel people do now know what is critical and what is not:
This is the reply I got:
“We know about this issue. It will be solved in next program update in January 2015.
Than you for your cooperation.”
Ok, so you don’t know what critical is in this case.
If it was critical avast wouldn’t wait with a fix till the next release but had a fix supplied already.
A critical issue MUST be resolved within 24 hours as promised
Issue 2: Critical:
a. Clicking “resolve all” to turn all back on hanging avast many a times, needing restart of system.
b. Clicking Resolve All does not turn on all the shields 99.99999% of the time.
That’s the critical one, both part a and b.
But I am not part of Avast business development or tech support. So cannot force them into fixing it. If I was anyone on the decision making part of team, I would made this top priority.
And I do not know on what basis Avast pushed it out to next release. And if that was a generic reply sent to me, without even reading the details in the ticket. Reason being, they did not notice the ticket until I mentioned about it in this thread.
Before reporting anything did you try the obvious and run a repair of Avast? and if that failed to fix the problem then a clean install would be recommended as there maybe some corruption, if all that failed then reporting to the team is indeed necessary.
And this issue comes up only when I try the “resolve all” to turn on shields that are off. All shields come up after system restart.
And restarting system is costly for me since I tend to have significant number of applications and files open, and tend to hibernate-resume. Restarting my laptop is something I do less than once a month or two.
By the way, in a world where people use hibernate more than shut/start of laptops, and products being paid for, people expect them to work out of box, and be told to uninstall and install again. I do understand nothing is perfect, but things like this should’ve been QAed better.
And QA needs to be more rigorous for critical apps like anti virus, compared to software like word processors.
