the biggest group of reports is from W7 users and you are W10 user. I may be wrong of course.
We appreciate your help and sharing the system logs. Your system logs were checked by couple of ppl and the root cause was not found in them. The problem in your case is not related to the Behavioral Shield. It suffers only because of someone else and the system didn’t even let it to start.
To my request: even if we found the possible issue in your logs. Others may suffer the same symptoms but the root cause may be different and we’d like to compare the logs from more than one user.
there may be small differences in the content for the offers as the beta is using different servers than release build but there isn’t change in the code between the beta and release builds.
To Bob2160: the problem in your case is the slow start-up of the whole system (it starts in a matter of minutes for both beta and release) and the behavioral shield startup problem is just a consequence of it (the system doesn’t give a chance to run the service in release) and to be honest I’m surprised that the shield is running on the beta build. We don’t have any proof to say it’s because of the Avast AV or it’s because other software.
All I can add is that since being back on the beta I’ve never had the Behavior Shield not start at boot time.
While on the regular build, I always needed to turn the Behavior Shield on manually.
Hi,
Does the agent must access the server before being enabled by system?
is there a faster access to the beta servers at system startup which could explain the system gives a chance to run the service in beta but doesn’t in release ?
no, it doesn’t. The comment was to answer general comments about the code difference between beta and release builds with the same build number made by Bob and David. It wasn’t related the problem with the shield start at all.
After followng the link I suppose there is no fix in sight in the near or far future. So I might as well get used to turn it on myself. I´m a little confused that they (avast team) can´t recreate the problem. But i´m not an technician so what do I know. As I recall the problem started after an update of the avast version. I do not longer recall if it was when the bahavior sheild was introduced or if it was at a later time.
does all of you have Comodo also running on your Windwos 7 machines? I was not having this issue since yesterday when I updated my Comodo Firewall version and from that moment the behavior shield is turned off after Windows reboot. Just an idea…
Nothing else was changes in the near time…pervious change was the install of the MS security patch because of the Meltdown. But you guys have the issue mothnes ago, so…
Moved to this product about a month ago and have been reasonably happy with it but over the last few days I have also been getting " Behaviour Shield not turned on" warning message. O/s is Windows 7 Professional Service Pack 1. Avast is Avast Free Program version 18.2.2328 (build 18.2.3827.307)
