Avast asked for reboot after iAVS update

My father uses avast too and advised me that today after he updated his iAVS (not a program update) that avast asked for a reboot. I have never had this occur before and neither has he. What do you think happened?

My father reports that after doing the iAVS update and rebooting that Threatfire now reports that the avast email scanner is performing a potentially malicious action, just as I posted in this thread: http://forum.avast.com/index.php?topic=37456.0

The key is ‘potentially’ malicious action, it is I believe not very conversant with the use of localhost proxy use, where the Internet Mail provider intercepts emails so that can be scanned and then sends them on there way. This is neither malicious or suspicious but how the mail scanner works, Allow the activity and remember the answer.

In your other post there is a reply in reference to having possibly having increased the sensitivity of threatfire.

I knew it wasn’t really a malicious act on the part of Avast. I have allowed the process and told TF to remember the answer but I am still curious as to what changed to cause TF to suddenly start flagging the scanner as potentially malicious. It never did it before.

Also, does anyone have a guess as to the answer to the question from my original post? Why did Avast ask for a reboot after an iAVS update?

I have responded re TF in your ‘other’ topic.

The iAVS update shouldn’t ask for a reboot, but if you hadn’t rebooted after the program update then it would probably be that which is at issue.

Are you getting a request to reboot after each boot as this has happened on occasion and isn’t directly related to an iAVS update ?

My father has not updated his Avast program since I believe it was 4.8.1220 and he has rebooted many times since that update. He only updated iAVS and got the request to reboot. He has updated iAVS again since then and did not get a reboot request. (He was not getting a reboot request after each boot). I assume this was just some glitch when he updated the iAVS that one time?

Thanks for the help.

I would say it is a glitch that unless it occurs after an iAVS update on a regular basic it isn’t something to be overly concerned about.