New Beta version 17.6.2307

DavidR · 2017-08-11T21:37:09.000Z

bob3160 post:30:

@ 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.

DavidR · 2017-08-11T23:04:45.000Z

Be Secure post:26:

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.

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

GopherJohn · 2017-08-12T00:54:32.000Z

@ 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.

Rednose · 2017-08-12T01:10:04.000Z

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

Greetz, Red.

BeSecure · 2017-08-12T01:16:21.000Z

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.

Rednose · 2017-08-12T02:12:25.000Z

DavidR post:28:

Rednose post:25:

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

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

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.

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.

Asyn · 2017-08-12T06:25:16.000Z

MartinZ post:22:

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?

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

DavidR · 2017-08-12T07:42:54.000Z

Asyn post:37:

MartinZ post:22:

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?

Hi Martin, please do so, at least we’d know what to expect… 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.

Asyn · 2017-08-12T08:13:00.000Z

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

bob3160 · 2017-08-12T13:06:19.000Z

Rednose post:34:

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

Greetz, Red.

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

DavidR · 2017-08-12T13:56:02.000Z

Asyn post:39:

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

The person responsible for the bug database, needs a big stick. There should be targets on said bugs and regular investigations on progress. Quality Control needs to get in on this as some of these bugs have been present for ages.

In the Military we used to have a saying, talk softly but carry a big stick!
Someone needs to take ‘active’ control over these bugs and wave the big stick.

Patrick2 · 2017-08-12T14:30:12.000Z

Avast has been my preferred AV product since 2006, Hits a Seven Big Drums for all the outstanding bugs to get resolved in stable and beta builds, maybe target a few bugs a month if they have so many it would take them a half a year to fix. Just be hopefully ready for Windows 10 Fall Creators update should be focus right now, then go back and tackle oldest outstanding bug and go from there in my opinion

I may put up with the new threat alerts, as one thing I don’t like Defender that much, scans so much slower, doesn’t offer same protection as Avast.

Anyhow will see how things go for rest of 2017, and 2018

MartinZ · 2017-08-14T07:31:09.000Z

DavidR post:32:

Be Secure post:26:

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.

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

Yes I know. it doesn’t make me feel satisfied.

Asyn · 2017-08-14T09:15:27.000Z

Asyn post:4:

karel.stavik post:1:

New SafeZone browser version

Are you sure…? I have the same version as before (3.55.2393.609).

OK, the new SZB version just arrived (4.58.2552.909).

bob3160 · 2017-08-14T12:10:44.000Z

Asyn post:44:

Asyn post:4:

karel.stavik post:1:

New SafeZone browser version

Are you sure…? I have the same version as before (3.55.2393.609).

OK, the new SZB version just arrived (4.58.2552.909).

So I pressed on the link to see what’s new and wound up on the forum with information on version
3.55.2393.607 ???

mchain · 2017-08-14T15:35:09.000Z

Yep, version SZB update confirmed. In fact, for me it came in yesterday on avast version 17.5.2303.

One of the reasons I don’t run a beta on my main machine is because of not fixing (minor) bugs in the last year or so. Why should I introduce new bugs when the old ones aren’t fixed? You’ve got betas running inside betas inside betas.

As an aside, AIS does have the ‘Sensitive Data Shield’ once again. It arrived today. Unlike the earlier iteration, it seems to be a bit buggy in that it took 40 minutes to complete and was stuck at 98% for 35 of those minutes. Almost stopped the scan several times.

I can understand programming changes made to consolidate programming forks so that all options are centered/originate on the main gui but some forks must be left alone. Toaster pop-ups are one such. And moving non-essential programs such as Data Shredder off the main gui is a step in the right direction.

Lord_Ami · 2017-08-18T10:26:46.000Z

Seems like new beta is out

Asyn · 2017-08-18T10:34:30.000Z

Lord_Ami post:47:

Seems like new beta is out

Thanks for the info. Just tried to update, no luck. Will try again in a few minutes.

Edit: Available now, back soon…

Asyn · 2017-08-18T11:16:17.000Z

Updated, all we need is a changelog now… ;D

bob3160 · 2017-08-18T11:38:15.000Z

Asyn post:49:

Updated, all we need is a changelog now… ;D

I was holding back to find out what was changed.
The change log should be available at the same time as the release notification.
It would be nice if they printed the changelog before the release so we know what to look for or avoid.

Announcements