New beta version 19.5.2378

Consumer Products Public Beta Avast Antivirus Beta
1

Hi everyone,

new beta version 19.5.2378 (build 19.5.4444) is released.

What was fixed

  • Final fixes before release to public

Download links:
http://public.avast.com/mkt/betaav/avast_free_antivirus_setup_online.exe
http://public.avast.com/mkt/betaav/avast_internet_security_setup_online.exe
http://public.avast.com/mkt/betaav/avast_premier_setup_online.exe
http://public.avast.com/mkt/betaav/avast_pro_antivirus_setup_online.exe

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

AVAST Team.

2

Thanks Karel, testing it asap…

Edit: The beta is running smooth here, no noticeable issues (so far).

3

Thanks for the new beta :slight_smile:

6?

4

Editing mistake

5
[b]What was fixed - Final fixes before release to public[/b]
What was the Final fixes?
6

System startup Normal or still slow in this beta?@Asyn

7

Nope, back to normal.

8

updating via in program update.
Thanks.

Edit:
Slight glitch after first Reboot. (See Screenshots)
2nd reboot cleared it up and running fine.

9

Same behavior from 19.4.2373

This is my system now

19.5.2378
W10 x64 17763.503
FF67

Still broken the scanning of HTTPS pages.

https://i.imgur.com/K0n8JNv.png

10

It is working fine in stable avast v.19.4.2374 (build 19.4.4318.491)
FF67.0 (64-bit)
But the site got 1 critical issue+7 warnings
https://rescan.pro/result.php?81608bfdd293ddc0c799f2cd0e7d7ef6
Sucuri give Site is Outdated notice.
https://sitecheck.sucuri.net/results/https/horoscoponegro.com

11

I confirm stable 19.4 updated to 19.5

Update: Ran a smart scan, prior to 19.5, it should used to say there was sensitive information and I used to skip it to finish scan. In 19.5, it completes saying no sensitive data found. Not sure if this is good or bad. I mean, earlier if there was sensitive information and if I hadn’t deleted, where did it go? Or free version stops detecting? This morning it is working as expected, dont know if second reboot was required but all good now. :slight_smile:

12

Interestingly, my Stable installation v.19.4.2378 showed version out of date and updated to 19.5.2378, the same version as the beta

13

Yep, it’s the latest stable version now. Still waiting for an official changelog…

14

Hello everyone!

We have prepared and new detection into the packet layer of WebShield for the recent vulnerability via Remote Desktop (RDP) protocol (CVE-2019-0708 ). To test this, you need to restart the PC so that the new components are loaded. Those of you, who use Remote Desktop, please do and report any issues (false positives) when connecting to your machines via Remote Desktop!

Thanks!
HK

15

Luckily Mozilla apparently was aware of this issue and fixed it in the last version of Firefox (68)

“When an HTTPS error caused by antivirus software is detected, Firefox will attempt to automatically fix it”

https://www.mozilla.org/en-US/firefox/68.0beta/releasenotes/

No more SSL/TLS issues with Avast! :smiley:

16

Hi HK, does this detection work on server side or client side? (i.e. Avast needs to be installed on Remote Desktop Host machine or client machine?)
Does this work with non-default port number (other than 3389)?

17

Hi NON,

sorry for late reply. Avast blocks both In and Out directions and it checks default port (3389) only.

HK

18

Thanks HK, I’ll try and see :slight_smile:

19

Trying RDP. Mainly on client use (Client machine has Avast Beta installed, server machine doesn’t), no problems so far. :slight_smile: