Behaviour Shield

[tandrew424]

My Behaviour Shield is still turning itself off from time to time, lots of promises about repair but they've all come to nothing. Anyone know why it's happening?

[RejZoR]

Interesting, I never got this. I wonder what's triggering this for some (you guys) but not for others (me). Are you using any other 3rd party security tools like HIPS or firewall?

[Pako7]

when did it really start?

[tandrew424]

Began about the time they switched to the new version of Avast Free and I'm not using anything that I didn't use before when it didn't happen. Lots of others affected and lots of promises from the company that the bug would be fixed..."It will be fixed in the next update", but it never was. No big deal really, it's only a click to restore, but I'd prefer it if it didn't happen.

[bob3160]

I can confirm this happening on occasion since updating to this latest version.

[Rundvleeskroket]

With a large enough userbase a small percentage is still many systems. These two claims are not mutually exclusive

By the way; 'a small percentage' is speculation without knowing how many people are able to find their way here to complain. Maybe the vast majority is silently waiting for a fix or is trying to troubleshoot the problem on their own.

[rocksteady]

I can confirm this happening on occasion since updating to this latest version.

My experience also after 17.9 update. On startup blue dot on Avast icon in sys tray which tells me Behaviour Shield is off. Not always the case just seems random.
Ed

[Asyn]

-> https://forum.avast.com/index.php?topic=201143.msg1431155#msg1431155

[tandrew424]

C'mon bob 3160, you and I had a couple of conversations about this, long before the latest update....remember? You told me that it would be addressed and fixed a couple of updates ago and obviously it hasn't been. You were very helpful, but got it very wrong. With regard to a "small percentage" of millions........that is most definitely rather a lot of users.

[bob3160]

C'mon bob 3160, you and I had a couple of conversations about this, long before the latest update....remember? You told me that it would be addressed and fixed a couple of updates ago and obviously it hasn't been. You were very helpful, but got it very wrong. With regard to a "small percentage" of millions........that is most definitely rather a lot of users.

And like you, on occasion, I also still need to manually start that component.
Yesterday, I started it manually. Today, no problems That makes it hard to track.

[DavidR]

C'mon bob 3160, you and I had a couple of conversations about this, long before the latest update....remember? You told me that it would be addressed and fixed a couple of updates ago and obviously it hasn't been. You were very helpful, but got it very wrong. With regard to a "small percentage" of millions........that is most definitely rather a lot of users.

Bob is no different to you, he too is an avast user, whilst Avast has supposedly issued fixes (plus workarounds) during beta and program updates, however it hasn't worked for everyone (him included). 

I on the other hand have never experienced this on my XP, win7 or win10 systems.

So my take on this is, because of this inconsistency it is hard to pin down the cause and why Avast team members on the forums suggested running the support package to try and get more detailed information from the logs.

[bob3160]

I had no problem while using the beta.
I did a clean install of the full (regular) version and again, on occasion, have the problem.

[tandrew424]

Thanks anyway Bob, you're very helpful and patient.

[bob3160]

Thanks anyway Bob, you're very helpful and patient.

Now if that would only cure these ills.