New Beta version 18.6.2346

Consumer Products Public Beta Avast Antivirus Beta
1

Hi everyone,

new beta version 18.6.2346 (build 18.6.3956) is released.

New Features

  • Migration of Secureline VPN addon to stand-alone SecureLine VPN app

    • VPN addon is not offered during clean AV install anymore
    • If user has VPN addon licensed, then it’s automatically switched to standalone VPN, otherwise the addon is uninstalled. The user can install easily standalone VPN anytime later from AV user interface

  • DND mode - Basic setting available in Components

  • TLS 1.3 scanning support in Web Shield

    • Full support in Firefox
    • Chrome only with Draft 28
    • Internet Explorer, Edge do not support TLS 1.3

What was fixed

  • Fixed occasional DNS resolve time-outs
  • Fixed issues with loading of sites using EV certificate
  • DND mode - “new app added” toaster does not appear in some cases

Known issues

  • DND mode - maximize performance option is enabled after DND mode disabled in single app
  • DND mode - not working correctly in Edge browser
  • DND mode - 3rd party app notification could not be blocked at very first attempt

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

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

AVAST Team.

2

Thanks Karel, testing it asap…

3

Great, the bug from 2345 is fixed now, good job.
Else, the new beta is running smooth here, so far.

4

Thanks for the new beta. I got an “Avast is not running” error window before reboot, but I don’t know it was beta related. I’ll post when I found something.

5

Downloaded avast_free_antivirus_setup_offline.exe, disconnected from the network and installed, the license is invalid, and network activation is required.

6

Thanks
Auto update installed.
All running nicely :slight_smile:

7

What about TLS 1.3 scanning in Opera?

8

Is the “stable” version approaching?

9

What this means?

10

I can confirm the DNS issues are fixed in this Beta. It does not occur anymore.

11

Opera does not yet support TLS 1.3 by default.
However Opera is very similar to Chrome in this regard so once enabled, scanning of TLS 1.3 in Opera should work.

12

When TLS 1.3 is being designed, each iteration is called a “Draft”. As the design process nears the end the changes between each draft are smaller.
This means that it makes sense to only support the later drafts and then the final version.

Avast now supports TLS 1.3 Draft 26, 27 and 28 and will support the future and final version of TLS 1.3

Chrome uses Draft 23 by default right now. However you can enable usage of Draft 28 manually in Chrome settings.

13

Thanks :slight_smile:

14

Thanks for answer. But majority users not change this setting in Chrome and that means they will not be protected.
And because Chrome is most used browser this should be problem.

15

Bug report, please see: https://forum.avast.com/index.php?topic=221024.0

16

Hi all
My ignorance is showing here, how do you change it as I went into settings in Chrome and couldn’t see how to change it. :-[

Thanks for any assistance

17

This is more of a slower adoption on Chrome’s side. But Chrome will switch to Draft 28 by default soon.

18

Strange problem, it failed to license. The error message said “sorry, something went wrong.” Back on the regular non-beta channel in the meantime.

19

It seems applying update from previous beta will result failing AvastSvc until reboot is performed. It is similar to previous beta issue (VPN related).

20

Small thing… since updating to the .2346 with the new VPN, I get the continuous reminder in Premier that there are privacy issues and can be fixed buying the subscription to VPN (even when the VPN is active with a valid license). ::slight_smile: