@
iroc9555,

and you sat there saying Allow, Allow, Allow, ... right?
Thanks, I saw it once, ages ago, so it won't hit me again. I usually set avast into its default auto decide mode before allowing win update to run. If I forget it, oh, well, it's my problem.
And it won't be on patch tuesday, 'cause I usually delay for a little bit.
@
davidR,
I actually do know where the log is, that's how I was able to do post#1. As to your other comments, they're valuable to me. I'm taking time studying and thinking a bit, since I really want to learn to use avast the best way I can.
Re your reponse 1 and 2: The only way I can learn what a particular shield does is to look at what it does. So your suggestion to know what it does before
playing with the Ask setting worries me at this point, and is one of the reasons I ask on this forum.
Re 3: yup, that
winsock2 is weird, still hasn't happened again, go figure. Visual studio might make sense.
Re
"Monitor the system for unauthorised modifications" - hmm. When I used Outpost, I did the same, but Outpost doesn't like my laptop waking up from sleep in their every other version, so can't use it even though I have a lifetime license.
I've disabled, on purpose, all behavior blocking and HIPS in my firewall, so Avast system watch is essential for me. Also, I think, as I watch things, Avast might be watching more than my firewall did. So I need to get all that figured out.
If I'm back with more questions, plese don't be surprised, thank you.