New Beta version 18.6.2348

[petr.kolacek]

Hi everyone,

new beta version 18.6.2348 (build 18.6.3977) is released.

Fixed

• Reporting Antivirus and Firewall state to the Windows Security Center after performed upgrade or downgrade

Known issues

• Crash related to TLS 1.3 support under specific circumstances
• Two detection dialogs displayed for phishing detection
• No detection dialog displayed for Webshield or Fileshield detections under specific circumstances (malware is blocked and moved to quarantine, but dialog not shown)
• Problems with signing to Avast account via Facebook
• Do not Disturb mode - not working correctly in Edge browser

Download links:
https://forum.avast.com/index.php?topic=179943.0

Enjoy this beta!
We are looking forward to your feedback.

AVAST Team.

[NON]

Thanks for the new beta, fast beta refresh

[Alikhan]

Are these BETA thoroughly being tested by QA before being released?

We would rather have BETAs which include more fixes and take more time rather than quick new BETA versions.

[Asyn]

Thanks Petr, testing it asap…

[petr.kolacek]

@Alikhan post:3

Are these BETA thoroughly being tested by QA before being released?

We would rather have BETAs which include more fixes and take more time rather than quick new BETA versions.

Hi Alikhan, we are close to the 18.6 public release and therefore you can see shorter time between the updates as well as less changes in it. Generally, we aim to release a new beta once per week to keep some rythm and amount of changes.

[Asyn]

Detection sound is back, thanks Martin. Else, nothing to report so far.

[schmidthouse]

auto update. Up and running
Thx Petr

[DavidR]

@petr.kolacek post:5

@Alikhan post:3

Are these BETA thoroughly being tested by QA before being released?

We would rather have BETAs which include more fixes and take more time rather than quick new BETA versions.

Hi Alikhan, we are close to the 18.6 public release and therefore you can see shorter time between the updates as well as less changes in it. Generally, we aim to release a new beta once per week to keep some rythm and amount of changes.

If we are so close to the public release, why are there are there so many Known Issues ?

When known issues are carried forward they just don’t seem to get resolved there are some problems that have been carried forward for many program updates. Asyn has a topic on one of these that has survived several program updates.

I would agree with Alikhan as to why some of these things aren’t picked up in Q&A and Alpha testing (I have mentioned this in the past). I think this constant monthly program update leaves us in a permanent Beta state.

[Alikhan]

@DavidR post:8

If we are so close to the public release, why are there are there so many Known Issues ?

This is why I raised the question. There are many known issues there and probably more must be more known internally.

@DavidR post:8

I would agree with Alikhan as to why some of these things aren’t picked up in Q&A and Alpha testing (I have mentioned this in the past). I think this constant monthly program update leaves us in a permanent Beta state.

I also think this monthly program update is causing problems. Far too many BETA versions are coming out (not necessarily close to public release) which have many known issues.

In the past, there used to be Release Candidate (RC) before the final stable version was released and would last a few days for final checks. Currently, the process seems rushed.

[Patrick2]

Perhaps slow down of the beta releases, fix the outstanding bugs in current and previous versions might be a better idea, don’t know why the need to rush releases for, i know your probably trying to stick to a Windows 10 monthly release schedule, but is that really the best idea in terms of product stability, folks recommending Avast Free/and Paid versions to friends and Family

I’ve been using Avast Free since 2006 after major issues I had with WIndows Live One Care, sure getting my machine infected then probably was my own fault, but nowadays I keep all programs up to date, and Avast Free.

[alanb]

I think this constant monthly program update leaves us in a permanent Beta state.

Well, nearly, but I totally agree with your sentiment, @DavidR.

Standards like ITIL and SOX require thorough and well-defined staging.

[schmidthouse]

I personally am fine with it.
When they come, they come and they come on auto update.

[Pako7]

it would be better if you fixed some of the known issues before you could release the final stable version…i don`t mind your constant Beta updates …but i mind them when they come with nothing being fixed …and having more and more issues arising…

[DavidR]

@schmidthouse post:12

I personally am fine with it.
When they come, they come and they come on auto update.

I no longer allow Program Auto Update, pretty much the same as other programs on my system I decide when they should update.

Originally Avast only had the virus definitions on Auto Update and the program update was on Ask. I do prefer that old option, but now I have gone a step further and set program updates to Manual.

What bothers me is happening currently, there are Known Issues listed in the topic for the last beta, https://forum.avast.com/index.php?topic=220998.0. These known issues aren’t reported in this beta version information at the top of the topic. The problem is they don’t appear in the Fixed list for this beta, nor do they appear in the Known Issues list, they have just disappeared into the ether.

[schmidthouse]

@DavidR post:14

@schmidthouse post:12

I personally am fine with it.
When they come, they come and they come on auto update.

I no longer allow Program Auto Update, pretty much the same as other programs on my system I decide when they should update.

Originally Avast only had the virus definitions on Auto Update and the program update was on Ask. I do prefer that old option, but now I have gone a step further and set program updates to Manual.

What bothers me is happening currently, there are Known Issues listed in the topic for the last beta, https://forum.avast.com/index.php?topic=220998.0. These known issues aren’t reported in this beta version information at the top of the topic. The problem is they don’t appear in the Fixed list for this beta, nor do they appear in the Known Issues list, they have just disappeared into the ether.

The betas have been quite passive/refined lately as there hasn’t been a beta released that has messed things up on my OS for a long time so I set to auto update.
So far it’s been OK.
I agree there should be closer accounting/documenting of fixed and new issues.

[Asyn]

Let’s put it this way, if you can’t stand the heat, get out of the kitchen.

[DavidR]

@Asyn post:16

Let’s put it this way, if you can’t stand the heat, get out of the kitchen.

Not the heat but the hassle and time. I’m more than capable of looking after myself, but looking at some of the topics in the forums, with bug that remain in place for some considerable time.

[Asyn]

@DavidR post:17

Not the heat but the hassle and time.

Too bad, as there are only very few beta testers for XP.

[schmidthouse]

@Asyn post:18

@DavidR post:17

Not the heat but the hassle and time.

Too bad, as there are only very few beta testers for XP.

I suspect there will be/is a point where (unless a specific version is kept) Avast software will cease to function on XP
There are already issues on some XP systems that weren’t existent in the recent past.
However my XP OS runs still OK with latest version of Avast Free. The GUI is too high of Resources

[Asyn]

@schmidthouse post:19

I suspect there will be/is a point where (unless a specific version is kept) Avast software will cease to function on XP

Yep, please see: https://forum.avast.com/index.php?topic=220639.0