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
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.
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