Twice since I updated the Avast Free engine yesterday, I have received a 
message that Avast needs to reboot.
I have been using Avast Free for several yrs (no, I don't let it load 
Chrome) and haven't seen this before.
I updated the engine yesterday and let it restart and do its thing and 
(after refusing Chrome, etc) it finished up. Many hours later it asked for 
another reboot. WTF?
Then today, it asked for another one.
When I did the engine update yesterday, it found and stopped an MBAM file , 
forgot the name but it was in System32/Drivers, and then I had to let it put 
it in the exclude part to keep MBAM Pro functioning.
Just wondering why Avast would ask for a reboot when no further engine 
updates were voluntarily  installed.
Thanks,
Buffalo


--- NewsGate v1.0 gamma 2