Been getting quite a few of these recently, behaviour shield turns itself off. Turns on manually OK, but for that I have to notice it is off. version is 18.6.2349 build 18.6.3983.371 Win 7 SP1 fully patched.
Any ideas anyone? Bugette? (that’s the conclusion I come to from previous instances of this that folk have mentioned)
I have found this to occur when I try to open a program too early after the desktop appears and it also depends on how many startup items you have. Try waiting a few minutes after the desktop appears before taking any action and see if this helps.
Just FYI - Same problem here, intermittently on my Win 7 Pro 64-bit machine. My Avast Free is version 18.6.2349 (build 18.6.3983.371).
Yes, I have quite a few programs turning on when I reboot my Win 7 Pro 64-boot machine (with 16 GB RAM), such as TeamViewer Free resident, SpiderOak, PCloud, OneDrive, iReboot, Start Menu X, MalwareBytes. Shouldn’t Avvast play nice anyway and not occasionally give me a warning that somehow the behavior shield is off?
Not sure if this is the right forum topic, but all of a sudden my web shield has turned off and I cannot get it to turn back on. I am on Avast Premier (could not find the version number), Lenovo Win 10 OS, 64 bit, not sure of the version number but have had the laptop for approximately a year. I have had the shields get turned off before but never a problem turning them back on. A reboot was done with the same results, could not turn that shield back on. I have used Avast for many years with very few problems which were usually minor.
Please try the following: 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
couple minutes after booting … avast notified me the “behavior-shield” was disabled. quickly checked avast-forum … realized i had acted a bit hasty, initiating a certain program on my computer … decided to take your advice. rather than engaging b-shield manually … i simply rebooted … this time, giving adequate time for avast to engage itself … only then, did i initiate the program in question. voilà … avast started with b-shield fully intact.