Oppps I broken it again. Thanks Avast this makes at least the 3rd time.

[cry4dawn]

The title says it all.

Lets look at the original forum posts where this has been talked about for the last few years:

https://forum.avast.com/index.php?topic=210755.0    (Nov 2017 and finally fixed like 6 months later)

https://forum.avast.com/index.php?topic=228721.msg1516598#msg1516598   (Aug 2019 and took months to fix it AGAIN)

Guys what can I say.. This marks the 4th time you have broken the same problem again and again with the latest engine change.

You can clearly read the previous topics of the same problem that is broken today. We just got this issue fixed a few months ago and NOW with the new update it is broken again.

AVAST do you have a Q.A. Department and do they do regression testing? If they do, can you please contact your Q.A. Manager and make sure this is a REGRESSION TEST so this stops happening year after year.

So once again when the user has Silent Mode on, if you do a manual scan on a file you should get a result. No problems found or IT HAS A VIRUS. I dont want to debate the actions of what it should or should not do, but bottom line if I ask the software to scan a file when silent mode is on, it should return a result.

WELL TODAY once again it does not after the most recent update.

Can You PLEASE make a critical fix and fix this problem NOW. Not in another 6 months like all previous fixes normally take. You know what the problem is, please resolve the issue. This makes your company look bad considering your job is to protect people from a virus. If you keep breaking the same thing over and over, what makes your customers think we have any faith that this product will help me stop a virus or even catch it? Free or not, fix your problems and start making this a regression test case.

Can we PLEASE get an estimate on when this issue will be fixed?

[bob3160]

It wasn't broken back then and still isn't now.
Turn of silent mode and it works as it should.
Turn on silent mode and it works as it should. It's silent.

[cry4dawn]

Really? Have you tested that?

Please stop spitting our false information.

1. Why would I turn off Silent Mode. Silent mode is designed to suppress the garbage that Avast spits out 20000000 times a day.
2. Really so Silent Mode and a manual file works on avast? Funny how the last 2 years people in my posts have said the same thing that IT DOES NOT!
3. Its been working since the last major update and now all of a SUDDEN the new major update comes out and it STOPS WORKING!

The only way to make a manual scan work is to turn off slient mode and then run a manual scan. Are you kidding me? So let me understand your ignorance. If I am on silent mode, and I tell your program to scan a file, it should do NOTHING? Why allow for a manual scan if it wont give you feedback. You can't be that stupid and think what you are saying makes any sense. You should seriously run for Congress with that logic.

Stop trolling people

[bob3160]

Really? Have you tested that? If silent mode is turn on it does not work with a manual scan. It was working for a few months with the latest updated. Now with the new update it is broken now.

Stop trolling

Just because you don't like the answer, doesn't mean I'm trolling.
To address your other concern, I don't work for Avast. I'm not staff.
I'm an Avast user same as you.

[cry4dawn]

Then stop trolling dude.. No one cares about your comment then. You clearly have no clue what you are talking about. You Trolled in the previous posts and you are doing it again. I am not here to argue with you nor do I care about your opinion which is wrong.

[bob3160]

Then stop trolling dude.. No one cares about your comment then. You clearly have no clue what you are talking about. You Trolled in the previous posts and you are doing it again. I am not here to argue with you nor do I care about your opinion which is wrong.

Your conception of trolling is way off base.
If you don't like my answer, simply ignore it. You obviously already do.

[Asyn]

Guys what can I say.. This marks the 4th time you have broken the same problem again and again with the latest engine change.
You can clearly read the previous topics of the same problem that is broken today. We just got this issue fixed a few months ago and NOW with the new update it is broken again.

You can submit a bug report in "About Avast". (Add the link to this thread)

[MartinZ]

I apologize it's embarrassing. Reported as a bug and we will fix it in next version. Thank you for reporting.

[cry4dawn]

Martin,

Thank you for the reply. Can you please let Q.A. Know to add this test to regression testing for each release? This is missed every single time. If Q.A. is not testing for this issue everytime, It will happen again and again.

[cry4dawn]

Fixed again in the June 3, 2020 update.

Thank you, and I hope this is now added to Q.A. regression testing so this does not happen again in the future :O