New Beta version 18.6.2349

[petr.kolacek]

Hi everyone,

new beta version 18.6.2349 (build 18.6.3983) is released.

This is the Release Candidate for PUBLIC channel with final "tunning" changes ;-)

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

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

AVAST Team.

[Vitdom]

After running a Smart Scan, the Avast main UI disappeared and this window popped-up. There was no internet outage. "Reloading" solved it.

[schmidthouse]

Auto update fine.
No issue here with GUI disappearing after Smart Scan. All working fine here. 

[REDACTED]

ENG: Hello. In World of Tanks, when the power maximazition is turned on, the screen turns black and the game crashes.

CZ:Dobrý den.Ve hře World of Tanks při zapnuté maximalizaci výkonu dochází k zčernání obrazovky a k pádům hry.

[FranceBB1]

Auto-updated, it works, but just like 18.6.2347 (build 18.6.3973) and 18.6.2348 (build 18.6.3977) TLS1.3 in Mozilla Firefox 52.9 ESR doesn't work when HTTPS Scan is enabled.
Does Avast rely on windows crypto.dll to scan the cryptography used?
I'm thinking about crypt32.dll, 'cause, for instance, Windows XP is not actually able to load TLS1.3 using crypto.dll, so all the browsers who rely on the default Windows engine can't load them (Internet Explorer, Google Chrome, Chromium ecc).
Anyway, Microsoft will also release an update to support TLS1.3 later on the next year for companies who have the paid Extended Support and for Windows Embedded POSReady 2009 users.
Firefox, however, has its own cryptography manager and handles TLS1.3 just fine under XP already, but as long as Avast is not able to scan it and blocks its traffic, it's pretty much useless.
I know that TLS1.3 is still yet to be deployed for many sites, but since version 18 is gonna be the latest version of Avast supported on XP, it would be nice to have TLS1.3 supported before the end of support.

Thank you in advance,
Frank.

OS: Windows XP Professional Service Pack 3 x86 - Microsoft Extended Support.

[Asyn]

Thanks Petr, testing...

[Asyn]

I don't have DND installed but it shows up in the GUI (loading endlessly).

[NON]

Thanks for the new beta

[schmidthouse]

I don't have DND installed but it shows up in the GUI (loading endlessly).

+1
Also here in AIS

[DavidR]

I don't have DND installed but it shows up in the GUI (loading endlessly).

+1
Also here in AIS

Is is also like that in the New 18.6.2349 (just released) version, not the beta and not the RC version but the NEW Version with the same bloody version number.

I really do hate this practice of keeping the same version number when going from beta or RC version to regular program update release.

[alanb]

I really do hate this practice of keeping the same version number when going from beta or RC version to regular program update release.

+1

[schmidthouse]

I don't have DND installed but it shows up in the GUI (loading endlessly).

+1
Also here in AIS

Is is also like that in the New 18.6.2349 (just released) version, not the beta and not the RC version but the NEW Version with the same bloody version number.

I really do hate this practice of keeping the same version number when going from beta or RC version to regular program update release.

Agreed David
It's not logical and is confusing.

[SpeedyPC]

Is it also like that in the New 18.6.2349 (just released) version, not the beta and not the RC version but the NEW Version with the same bloody version number.

I really do hate this practice of keeping the same version number when going from beta or RC version to regular program update release.

I strongly agree with David on this very important issue before releasing the final version.

[Filip Braun]

Auto-updated, it works, but just like 18.6.2347 (build 18.6.3973) and 18.6.2348 (build 18.6.3977) TLS1.3 in Mozilla Firefox 52.9 ESR doesn't work when HTTPS Scan is enabled.
Does Avast rely on windows crypto.dll to scan the cryptography used?
I'm thinking about crypto.dll, 'cause, for instance, Windows XP is not actually able to load TLS1.3 using crypto.dll, so all the browsers who rely on the default Windows engine can't load them (Internet Explorer, Google Chrome, Chromium ecc).
Anyway, Microsoft will also release an update to support TLS1.3 later on the next year for companies who have the paid Extended Support and for Windows Embedded POSReady 2009 users.
Firefox, however, has its own cryptography manager and handles TLS1.3 just fine under XP already, but as long as Avast is not able to scan it and blocks its traffic, it's pretty much useless.
I know that TLS1.3 is still yet to be deployed for many sites, but since version 18 is gonna be the latest version of Avast supported on XP, it would be nice to have TLS1.3 supported before the end of support.

Thank you in advance,
Frank.

OS: Windows XP Professional Service Pack 3 x86 - Microsoft Extended Support.

Thank you, we'll check out what's going on.

[FranceBB1]

By the way, I made a typo. I obviously meant crypt32.dll.