New Beta version 17.6.2307

Regarding the not fixed bugs:
we are not happy about them and we are fixing the most important ones. For you it might be viewed as major issue but we know from data how many users is affected.

So e.g. not smooth animation of systray icon. Yes it looks as stupid bug, but we know that 98% has the animation turned off, plus the animation doesn’t affect your protection status. So we rather work on better anti-phishing protection and other new features that will affect 100% users once released and increase their protection status.

And of course as we are adding new features, we are also producing new bugs. Just fixing all the bugs we know about would take us approx half a year, without introducing any new feature, improvement etc… And honestly we can’t afford this.

I hope you at least like the fact that we are removing the non-AV components from AV, this month we will start with Cleanup and next month the browser, they both will be working as standalone applications.

That doesn’t mean that you should stop reporting us bugs, it’s very valuable for us to know about them, but maybe we should better communicate back to you if we plan to fix them or not and why. What do you think?

Not included, you have to upgrade to Premier ( see attached screenshot ).

Greetz, Red.

@MartinZ

And the Threat Alert Popups in Middle of the screen? whats the reason for that? so annoying and aggravating to have it popup when doing something in normal use of the machine, i’m thinking as of real world use for non technical folks as well as Technical folks. Those steal focus right now, which is problem in itself. What was wrong with the old from the taskbar alerts for a threat detected?

With a 3rd reboot since the update, Sensitive Data Shield is suddely available.
But what does " QUET NGAY " mean :stuck_out_tongue: ( see attached screenshot ).

EDIT : I think it is Klingon for " Run Scan " ;D

EDIT 2 : I got a private message from MartinZ :

it might be delayed as we started the distribution of this component yesterday it can be delivered independetly on the program update

Greetz, Red.

we are not happy about them and we are fixing the most important ones. For you it might be viewed as major issue but we know from data how many users is affected.

So e.g. not smooth animation of systray icon. Yes it looks as stupid bug, but we know that 98% has the animation turned off


Hi MartinZ, It is not about number game.If 2% users are affected by any of the bugs it is Avast duty to solve the issue(small or big).Thanks for the info.

The bugs should be eliminated first, before adding new features. Adding new features without fixing long existing bugs indicates that marketing directs the evolution of Avast over the customer’s usability and satisfaction.

Language appears to be Vietnamese, but Google translation isn’t great either “QUET NOW” which may be QUIET NOW, if that makes any sense in context of the Button.

@Be Secure
@Gopher John

I think you did not read Martin’s post entirely. As he stated, fixing all known bugs would take them half a year. Of course they are aware of much more smaller bugs that we haven’t reported (be it missing icon or broken text). But the main focus should always be protection rather than UI (which is most of the time invisible). They got the statistics and I’m pretty sure main UI is not used daily or weekly by “average Joe”.

You got to look at the bigger picture sometimes :slight_smile: I’m more than sure that with merging AVG and Avast, they can bring features (including those invisible - backend/cloud/processing of samples etc) and fix old stuff better than even before. That’s why we have these betas - known bugs are not going to be on final release. So we have plenty of time to test and report our findings.

my 2 cents.

@ Lord_Ami,
There are lot’s of Known Bugs in the current final release.
That’s one of the complaints. Bring out new features that in some instances aren’t complete when introduced
which only adds more to the problem pot. Usually when something new screws up something old, we wind up losing the old feature.

+1

I have said it, others have said it, Avast needs a period of consolidation and fix the outstanding bugs and known issues before introducing any others.

Of course the purchase of AVG has thrown a spanner in the works, with the incorporation of components from both Avast and AVG into two new programs doesn’t help. The next spanner in the works is some time off when presumably the two programs will become one.

All of that is no excuse for known issues not being higher up the priority list.

Well 2% of hundreds of millions are a lot of people, working only on 200 million users (avast states more than that), that would make it 4 million unhappy users :wink:

@ Lord_Ami,
Addind new features to a program that has known problems(not just the UI) is like adding fresh vegetables to a compost pile. Trying to sort out whether a bug was created by the new feature or was an existing bug adds to the backlog of problems to solve. The compost pile keeps getting larger.

As for the bugs, we should make more noise on Avast Slack.
It is as simple as that.

Greetz, Red.

I think you did not read Martin's post entirely. As he stated, fixing all known bugs would take them half a year. Of course they are aware of much more smaller bugs that we haven't reported (be it missing icon or broken text).
Then what is the meaning of beta tests and reported bugs for the years? There are lot's of Known Bugs in the current final release.Avast is King of Bugs.

The funny thing is, it shows the right translation in the Dutch UI : " Nu scannen " = " Scan now " ( see attached screenshot ).
So I still think in the English UI it is Klingon ;D

Greetz, Red.

Hi Martin, please do so, at least we’d know what to expect… :wink: Cheers.

I don’t know if there is a database with known bugs, when reported, their progress, etc. than can be referenced. That way we can tell if a bug has already been reported, on what Avast version what OS and crucially what progress.

Whilst there is most certainly said bug database, it isn’t available, so there is no confidence whether it is being fixed or not.

Yep, in fact there is such a bug-db, but it’s for internal use only.

I can’t make the noise any louder. :slight_smile: Bang Bang Bang.