Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Beta - Avast => Topic started by: petr.kolacek on June 23, 2022, 12:54:14 PM
-
Hi everyone,
there is a new beta version ready - 22.6.6020 (build 22.6.7343).
What was fixed
- blocking sites using h3 (quic) protocol leads to Avast main service crash
- shorter period in abanonded DNS resolvers (Real Site component)
- removing of all Avast system certificates after uninstallation
Known issues
- site blocking page will not be displayed on MS Windows 10 and higher (site itself is blocked)
Download links
Avast Free: https://bits.avcdn.net/productfamily_ANTIVIRUS/insttype_FREE/platform_WIN/installertype_ONLINE/build_BETA
Avast Premium: https://bits.avcdn.net/productfamily_ANTIVIRUS/insttype_APR/platform_WIN/installertype_ONLINE/build_BETA
Avast Clear: https://s-beta9x.avcdn.net/beta9x/avastclear.exe
Enjoy this beta!
We are looking forward to your feedback.
AVAST Team
-
Thanks Petr, already up and running.
-
Thanks for the new beta :)
-
Hello everybody, please let me inform you about a small update being released now (b7351). There is fixed way of using settings by one of the internal modules.
Have a nice weekend! Petr
-
Hello everybody, please let me inform you about a small update being released now (b7351). There is fixed way of using settings by one of the internal modules.
Have a nice weekend! Petr
Thanks Petr, updated. Have a nice weekend as well. :)
-
Hi, found some missing translations (German) - interestingly everything was correctly translated in the last beta.
-
Hello, Petr. I made initial contact on the version 6017. I don't know if you continue to follow the older threads. I've uploaded the file you requested. I still had the issue with 6019, but it *appears* to have been fixed with this 2020 release. I'll report on this thread if this problem recurs.
Thanks.
-
Hi, in case you need a workaround see: https://forum.avast.com/index.php?topic=319959.msg1689307#msg1689307
-
Hi, in case you need a workaround see: https://forum.avast.com/index.php?topic=319959.msg1689307#msg1689307
Thanks, Asyn. I apparently got confused with the versions. After I posted that last message, I checked again, and I was only running 6019. So I updated to 6020 and re-enabled all the shields, and my system is working again. So, apparently Avast addressed the problem I was having in 6020. For those that are encountering VirtualBox VMs crashes recently, try upgrading to this 6020 release. If that doesn't help, then please see my workaround in the 6017 thread here (disable the Anti-Exploit Shield.)
Thanks for your help.
-
You're welcome and thanks for the feedback.
-
Hi, in case you need a workaround see: https://forum.avast.com/index.php?topic=319959.msg1689307#msg1689307
Thanks, Asyn. I apparently got confused with the versions. After I posted that last message, I checked again, and I was only running 6019. So I updated to 6020 and re-enabled all the shields, and my system is working again. So, apparently Avast addressed the problem I was having in 6020. For those that are encountering VirtualBox VMs crashes recently, try upgrading to this 6020 release. If that doesn't help, then please see my workaround in the 6017 thread here (disable the Anti-Exploit Shield.)
Thanks for your help.
Hello guy.rouillier, please accept my apologies for not getting back to you. The situation is as follows. We disabled part responsible for making the trouble with virtualbox (and similar products based on this) and working on "proper" fix that would take more time and testing. So basically, the problem should be fixed on any of the Avast client version as the disabling is done via virus definitions update (not via program update). Thank you and have a nice day! ;)
-
Hello everybody, there is one more small update to be performed today (b7355) where is fixed possible problem with updating user interface. ETA: ~1hr.
Have a nice day, Petr
-
Thanks Petr, testing it asap...
-
Got it, thanks :)
-
Hi, found some missing translations (German) - interestingly everything was correctly translated in the last beta.
FYI, the latest beta update initially fixed the issue (UI 713), but after a reboot the UI reverted to 712.
-
Hi, found some missing translations (German) - interestingly everything was correctly translated in the last beta.
FYI, the latest beta update initially fixed the issue (UI 713), but after a reboot the UI reverted to 712.
I can confirm that.
(https://i.imgur.com/Gtk8HmFm.jpg) (https://i.imgur.com/Gtk8HmF.png)
-
Hi, found some missing translations (German) - interestingly everything was correctly translated in the last beta.
FYI, the latest beta update initially fixed the issue (UI 713), but after a reboot the UI reverted to 712.
I can confirm that.
Thanks Bob. :) It was some kind of test from UI-team (see Slack), UI 713 is back now.
-
So basically, the problem should be fixed on any of the Avast client version as the disabling is done via virus definitions update (not via program update). Thank you and have a nice day! ;)
Thanks to the whole Avast team for finding a solution.