Despite numerous pledges that the Shield would stop appearing on startup as “turned off”, the latest upgrade still hasn’t fixed the problem. I repeat my opinion from an earlier post…if they can’t fix a simple glitch like that, what other problems are inherent?
Follow instructions: https://support.avast.com/article/33/
This glitch affects the minority of users and not all the causes are the same. There’s many different hardware/software combinations that can cause this.
You can submit the support file and then let us know the File ID here so we can get it escalated to the devs.
You haven’t mentioned your operating system or other security software either…
Grrr.
Just had my first instance of unexpected turning off of Behaviour Shield after following a Win10 restart.
Blue dot appeared in avast system tray icon and this status screen.
Ed
screenshot failed to attach to my last message
correction. yes it did.
Install the latest version:
https://forum.avast.com/index.php?topic=212045.0
Bob,
Yes. That is what is annoying me. Never seen that problem myself before I updated yesterday to 17.9.2322.
Ed
Strange since that was a constant bug for some time but fixed in the last version.
I haven’t seen it since the update. Only suggestions I can offer are as follows: Repair Avast:
Control Panel> Program and Features (Add/remove program)>Select Avast> Select Repair. Reboot when completed
https://www.avast.com/faq.php?article=AVKB204
If Repair doesn’t fix the problem, try the following:
Clean Install of Avast:
https://goo.gl/4Ptzkf
If you need additional help with the Clean Install, watch this:
https://youtu.be/p-h3myRD51A
Interesting though, I never had this problem on 3 different systems. I wonder what’s in common with people who do experience this problem…
Also now seen exactly same problem on my WinXP SP3 machine.
New 17.9.2322 avast add-on also screws Outlook 2010 on that machine and had to be disabled. This problem has been posted separately.
Ed
Same, I’ve never had this problem too.
Pleased to report behaviour shield started ok when booted this morning. Both Win10 and WinXPSP3 machines. The problem occurred yesterday on second restart after update via GUI. Same on both machines. Maybe things are now sorted now after a couple more boots have been performed.
Only problem now with this update is Avast Add-On having to be disabled on Outlook 2010 to get that running under WinXPSP3.
Don’t know if that is part of the wider Avast v Outlook problem I have seen reported elsewhere on the forum.
Ed