Behaviour Shield Confusion

[tandrew424]

Can anyone give me an accurate answer about this Behaviour Shield fiasco? Last thing I read was that it would be fixed when 17.7 was released. This turned out not to be the case (In my case anyway and it seems I'm not alone). I most definitely do not want to start altering anything, as historically it has always resulted in problems. Surely, it's an Avast glitch and the powers that be should correct it at source, rather than us meddling/re-installations etc. Anyone?

[bob3160]

Can anyone give me an accurate answer about this Behaviour Shield fiasco? Last thing I read was that it would be fixed when 17.7 was released. This turned out not to be the case (In my case anyway and it seems I'm not alone). I most definitely do not want to start altering anything, as historically it has always resulted in problems. Surely, it's an Avast glitch and the powers that be should correct it at source, rather than us meddling/re-installations etc. Anyone?

It is an Avast bug. I've been working with the developers for the past hr. and they are working on a fix.

[tandrew424]

Thank you Bob, it does seem to be turning into a marathon, for what you could consider a fairly minor problem. No big deal at all to press a button and reconnect, but that's not the issue really. A promise was made that it would be rectified in 17, in fact I think that you posted that statement, yet 'twas not to be and it could make people think that if Avast can't fix what appears a minor issue, what else lies beneath.....not really a confidence booster!

[bob3160]

Thank you Bob, it does seem to be turning into a marathon, for what you could consider a fairly minor problem. No big deal at all to press a button and reconnect, but that's not the issue really. A promise was made that it would be rectified in 17, in fact I think that you posted that statement, yet 'twas not to be and it could make people think that if Avast can't fix what appears a minor issue, what else lies beneath.....not really a confidence booster!

It was fixed as promised and now is broken again. That's why I'm again sending the scans Avast requested to try to fix it again.
Hope that this will be the last and final time.

[tandrew424]

I use the free version, however if I had paid for a program that is supposed to detect, clean and fix severe threats and the program itself had a bug then I'd be dismayed. However, if they fixed it and then it reappeared, my confidence in Avast protecting my machine would plummet. Thanks for staying on the case Bob.

[bob3160]

I use the free version, however if I had paid for a program that is supposed to detect, clean and fix severe threats and the program itself had a bug then I'd be dismayed. However, if they fixed it and then it reappeared, my confidence in Avast protecting my machine would plummet. Thanks for staying on the case Bob.

Your computer, your choice. I made mine and still like the way it keeps my systems secure.

[REDACTED]

Just upgraded to 17.8.2318 - Problem still exists.

[bob3160]

Just upgraded to 17.8.2318 - Problem still exists.

I haven't seen the problem since the update.
Want to solve yours, here's how:
https://support.avast.com/en-us/article/33/