there is a new beta version ready - 22.3.6006 (build 22.3.7069).
What’s fixed
exception in one of our internal dll which should not have visible functional impact but generates dumps
Do not Distrub mode does not work for existing as well as new applications using full-screen mode
Known issues
some of the email attachments (PE files like exe or dll) are not scanned by Mail Shield (however you are still protected by File Shield when saving or opening those files)
Enjoy this beta!
We are looking forward to your feedback.
Also please be informed that we would appreciate if you would be so kind and try our Antivirus product based on so called “icarus” setup (installation and update engine) already used for other Avast products but now available also for AV. More information is here: https://forum.avast.com/index.php?topic=264883.0. Please note that in order to get it, you need to uninstall the current one (automatic migration is not supported at the moment).
I have reverted to and I remain blocked with program version 22.1.2504 (build 22.1.6921.715) since when I update to a newer version (22.2 and now 22.3) I cannot use the “SENSITIVE DATA SHIELD”. It’s red and there’s no way I can change it to green!!
I’ve been complaining since February but I get no reply.
It’s a shame!!
Alfred
Hi Asyn,
Could you please describe when does this issue occur?
When I installed the latest beta on W10x64, running the SmartScan and closing the UI, or even having it run from a custom scan, I always get a notification when it finishes
I got an email saying this is a reply to a topic I am watching - which it is not[ My problem is with the blocking of the "SENSITIVE DATA SHIELD (showing RED and IMPOSSIBLE TO CHANGE TO GREEN) with these new updates.
Is there any hope? For the moment, I’m happy with version 22.1.2504 and I have no intention of updating until this issue is solved
Alfred A Cauchi
When you have notifications turned on to be notified when there are replies to topics you’ve posted in, you’re going to get a notice anytime anyone posts in that topic.
It doesn’t necessarily mean there’s an answer to your particular concern or problem.
All is well for me except the problem that’s existed since at least 20.7 (maybe as early as 20.1!). Serial (COMx) port device enumeration at boot is broken in W7-64 if Avast is installed and not in passive mode (the only two conditions where all works). I originally reported this on ticket 11394513 back in 2020, but there’s never been any resolution. Fortunately my workaround is to schedule devcon.exe (from the driver SDK) to run after every boot. That re-scan also fixed a problem with a recently added USB mouse that was “dead”. Avast version 22.2 fixed the USB problem. None of this is a big deal for me as I have a workaround, but it would be nice to not have that kludge.