Behaviour Shield problem with Avast Free 17.0.2286

loungehake · 2017-02-09T15:38:03.000Z

I am using Spybot - Search and Destroy v2.3 on Windows 7 Ulimate (64bit). Avast Behaviour Shield prevents me form closing Spybot’s child windows, the system freezing when that is attempted. Disabling Behaviour Shield removes the problem.

Another Windows 7 Ulimate (64bit) system also has Spybot and Avast Free 17.1.2286 with Behaviour Shield enabled and the problem described above does no occur. The two systems use different system boards.

DavidR · 2017-02-09T15:59:43.000Z

Whilst this is strange to have a different reaction on two systems with the same OS.
Do you have the same security applications installed on both systems ?

Personally I think Spybot - Search and Destroy is a somewhat dated program - it is absolutely years since I gave up on it for the likes of MBAM (MalwareBytes AntiMalware), but it should work consistently across systems. Do you have Spybot’s - Tea Timer functions enabled as that has in the past effected avast.

I just wonder if this programs actions monitoring startup entries could be considered suspect. That said if you have the same settings for spybot on both systems, the result should be the same.

Asyn · 2017-02-09T16:19:10.000Z

I strongly advice to get rid of Spybot…!!

loungehake · 2017-02-09T19:49:41.000Z

The reason that I posted this is to draw attention of the developers to a possible flaw in the Behaviour Shield. I am not bothered that it is Spybot that triggered the issue but am concerned that the problem might also cause difficulties with other applications.

DavidR · 2017-02-09T20:29:21.000Z

I’m not entirely sure how this might draw attention/help the developers to pin this down when you have two systems (presumably with the same software, settings, OS, etc. and one works fine but the other not.

It might help if you Generate a support package https://www.avast.com/en-gb/faq.php?article=AVKB33#artTitle on the system with the issue when it occurs.

loungehake · 2017-02-10T09:38:41.000Z

Thanks David. I am am following your suggestion.

DavidR · 2017-02-10T10:15:04.000Z

You’re welcome, hopefully it will give them some useful information.

loungehake · 2017-02-10T12:37:43.000Z

Report submitted. I belatedly realised that an exclusion would be helpful and so it has proved. I also excluded Agnitum Outpost while was at it.

DavidR · 2017-02-10T13:21:04.000Z

I have no exclusions for the Behaviour Shield as yet, I want to see if there is any interaction.

I have some in the avastUI > General > Exclusions for acs,exe and op_mon.exe for outpost firewall pro. But they are explicit for those files not for the whold folder.

Announcements