New beta version 22.6.6019

[petr.kolacek]

Hi everyone,

there is a new beta version ready - 22.6.6019 (build 22.6.7331).

For those of you who already updated to b7326 released yesterday with the issue (mentioned below) causing the main service to crash, please try to restart the service in the User Interface to be able to visit Settings and ask for program update or reinstall the application (do the repair installation, or uninstall and install it over again).
Thank you for your understanding and please accept our apologies for any inconvenience.

What was fixed

• clearing old log files → this should save some space on the disk
• crashing of the main service caused by imperfect detection of Hyper-V

Known issues

• site blocking page will not be displayed on MS Windows 10 and higher (site itself is blocked)
• blocking sites using h3 (quic) protocol leads to Avast main service crash

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

[NON]

Thanks for the new beta.

Successfully updated from b7326 to 7331, from internal updater.

[NON]

BTW, release date is wrong for months, is there any plans to fix?

[Asyn]

Thanks Petr, back on beta-channel.

[Asyn]

BTW, release date is wrong for months, is there any plans to fix?

Hi NON, that's a known issue (Icarus only) - I reported it many months ago, but no reaction (so far).

[goaion]

Since the update to version 22.6.6016, the Android emulators used cannot be used normally, and VT will be occupied. No matter which emulator is the same, can the function of virtual protection be removed?
I tried this 22.6.6019 version still can't solve my problem

[Dealx]

Since the update to version 22.6.6016, the Android emulators used cannot be used normally, and VT will be occupied. No matter which emulator is the same, can the function of virtual protection be removed?
I tried this 22.6.6019 version still can't solve my problem

This is not the first time Avast affects virtualization of VirtualBox related services (many emulators use those, like Nox, Memu etc.). Several years ago I remember the following workaround helped me until Avast finally fixed the problem: set Start=4 in HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\aswVmm and restart PC.

[Asyn]

Nice, I like the reworked design. Kudos to the UI team.

[petr.kolacek]

Since the update to version 22.6.6016, the Android emulators used cannot be used normally, and VT will be occupied. No matter which emulator is the same, can the function of virtual protection be removed?
I tried this 22.6.6019 version still can't solve my problem

Hello goaion, please accept our apologies for such issues caused. We are aware of the problem and our developers are working on a fix. What you can do now is to follow instruction from DealX (thank you for that ) as a workaround. Have a nice day! Petr

[goaion]

Since the update to version 22.6.6016, the Android emulators used cannot be used normally, and VT will be occupied. No matter which emulator is the same, can the function of virtual protection be removed?
I tried this 22.6.6019 version still can't solve my problem

This is not the first time Avast affects virtualization of VirtualBox related services (many emulators use those, like Nox, Memu etc.). Several years ago I remember the following workaround helped me until Avast finally fixed the problem: set Start=4 in HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\aswVmm and restart PC.

Thank you very much for providing the method, I will try it again

[goaion]

Since the update to version 22.6.6016, the Android emulators used cannot be used normally, and VT will be occupied. No matter which emulator is the same, can the function of virtual protection be removed?
I tried this 22.6.6019 version still can't solve my problem

Hello goaion, please accept our apologies for such issues caused. We are aware of the problem and our developers are working on a fix. What you can do now is to follow instruction from DealX (thank you for that ) as a workaround. Have a nice day! Petr

OK, thanks for your reply.