« Reply #46 on: January 03, 2019, 11:26:14 AM »
The issue of Behaviour Shield being an uncertain starter has existed as long as has Behaviour Shield. Since Avast know what shields are required by the user to run and what shields are actually running, why is there no mechanism to check on this and to automatically restart or start any shields which should be running but are detected not to be?
I guess that this must only require a fairly trivial bit of programming compared with the really awesome stuff inside Avast. It would better ensure protection if it could be ensured that shields are actually running. One shield not running is one shield providing less protection and Behaviour Shield does protect against zero-day hazards. Behaviour Shield must have been a reason (among others) why Avast acquired AVG.
The yellow alert flag (with an exclamation mark?) on the Avast icon in the system tray is not the most conspicuous thing on the screen so it is easily missed and all the while Behaviour Shield is not protecting.
« Last Edit: January 03, 2019, 06:00:44 PM by loungehake »
Logged
Windows XP SP3, Avast Free 10.4.2233, Agnitum Outpost Firewall Pro 9.3, Malwarebytes Anti-Exploit, Comodo Memory Firewall, OSArmor
Windows 7 Ultimate x64, Avast Free 20.10.2442, Malwarebytes Anti-Exploit, Malwarebytes Anti-Ransomware, OSArmor
Windows 8.1 Pro x64, Avast Free 20.10.2442, Malwarebytes Anti-Exploit, Malwarebytes Anti-Ransomware
Windows 10 Pro x64, Avast Free 20.10.2442, Malwarebytes Anti-Exploit, Malwarebytes Anti-Ransomware
