Behavior Shield Not Starting On Windows 10

Since the update to Avast Free 19.4.2374 on Windows Home 64 the Behavior Shield
does not automatically start & has to be manually started … When will they get this fixed ? ?

Same behavior on Windows Pro 64.

same with me always have to switch it on manually and i tried a repair and it never worked :frowning:

How did you upgrade your version?

I my self used ui to update

Sometimes the better option is to do a clean install, especially when version numbers move from say, version 18 to 19. You can always back up your settings before you do so. But if you’ve got a scheduled scan and you don’t want to keep that a clean install will allow you to start fresh. For that, I suggest using the offiine installer as the online installer can cause issues. A clean install can fix nagging issues carried over from a previous version.

ok il try again though i once tried the clean install and the issue persisted …maybe offline installer would work

Clean Install of Avast:
https://goo.gl/4Ptzkf

To answer Bob’s question: It was an update from within the Avast UI from 19.4.2369 o 19.4.2374
I do not recall if the issue was there before it went to 19.4.2374 … But I did do a complete uninstall,
reboot and clean install from the off line installer … So far it is ok … Will see how it is come next
cold boot

It was an issue a version back for me but not now on either Win 10 64 Bit OS’s

Just did the cold boot on the windows 10 laptop and Avast came up fine with the behavior shield enabled.
So I guess the full uninstall, reboot, reinstall with the full off line installer did the trick. Avast coders should
fix the way it does program upgrades from within the GUI … If it will cause issues, then they should not do
it that way.

I have the same problem. The clean install help to resolve the issue?

It did for me, would probably work for you as well. Just be sure to backup any exclusions or special settings first
so you can restore them later on.

Follow these instructions:
Clean Install of Avast: https://goo.gl/4Ptzkf

Today after a windows update the problem reappear :cry: