problem with MS updates

[jayt]

I have avast free v. 6.0.1289 on two computers. One is on Windows 7 and one is on WinXp Sp3.When MS sends out updates, the Windows 7 updates without any problem, but the Xp version pops up Avast on some updates and requests that it allow them. Sometimes it only requires clicking on Allow. Sometimes, it requires shutting down Avast before the update can continue. How can I fix this?

[Lisandro]

You don't need to shut down avast in any situation.
Set the avast autosandbox to ask (instead of automatic) and allow the Windows Updates to run.

[iyogisolutions1]

Hi jayt.

      Make sure that you never turn off avast! in your computer. Its not recommented. Because it will make your computer vulnerable.
.
     
      Have a wonderful day Good Karma!

[iroc9555]

Jayt.

Welcome to the club. It is a pain. Ever since installing Avast 6, I am also having those alerts by Behavioral shield. They are related to installment of .NETFramework updates and this past Tuesday I also got one alert by Outlook filter and one by Silverlight. There were about 40 alerts in total.

 

Since all are related to C:\WINDOWS\Installer\xxxxx.tmp, don´t know how would affect security if those file are given a wild card status in the Trusted Processes section of Behavior Shield as C:\Windows\Installer\*.tmp. I suppose that it would create a big hole in Avast since all Windows installer using a temp file would go thruogh undetected.

Anyway you could set in Behavior Shield > Expert Settings > Main Settings >  " Action to take " to ask and then every Microsoft update have to be there to allow the Alert. A pain I know.

Regards.

@ Tech

These are the same alerts we talked about a few months ago in the Spanish Forum. They are not generated by autosandbox but by Behavioural Shield.

[jayt]

Thanks iroc9555. You have it correct. It is an installer file that has to be given permission to run. And it is a pain. Guess we will have to grin and bear it -and click and click on the "allow"      

[Lisandro]

Or disable Behavior Shield only for a while, not all the avast shields.

[DBone]

Or set the Behavior Shield to Auto-Decide.

[Lisandro]

Or set the Behavior Shield to Auto-Decide.

And what if it blocks then?

[DBone]

Auto-Decide has yet to cause a single issue on any of the 7 family members' machines that I maintain, with all sorts of different OS's and architecture.

[Lisandro]

Auto-Decide has yet to cause a single issue on any of the 7 family members' machines that I maintain, with all sorts of different OS's and architecture.

Yeah. You're right. But, after all, avast could fault and block the Windows Updates.

[DBone]

I guess anything's possible, but Auto-Decide is the default setting and works great. People start tinkering with settings without fully understanding the ramifications of doing so, and they have "problems". 

[iroc9555]

@ DBone.

Well I suppose that if Avast Behavior Shield stop those .tmp files in ask mode, they will be stopped in autodecide too. Is it not the funtion of Behavior Shield to stop any file that do not have a range of criteria set for Avast ? The only differece between Autodecide and ask is that in ask mode the user decide while in autodecide Avast does, and if the file is outside that criteria the alert is popping out for the user to decide what to do, and I quote:

" ...The default action is "Auto-decide", which means avast! will decide whether or not it should be allowed based on a range of criteria,......If the action is changed to "Ask" you will see a message whenever such activity is detected and you will need to confirm whether or not it should be allowed. "

I believe those .tmp files during the installment of NET Framework are out side Avast criteria and that is why the alerts come out. Why this is happening in some systems and others are not ? well that is something that scape me.

Regards.

[DavidR]

I think auto decide would probably be well refined for windows update, but me I prefer to have it on Ask and yes windows updates can be somewhat noisy in the behavior shield set to Ask.

[DBone]

@ DBone.

Well I suppose that if Avast Behavior Shield stop those .tmp files in ask mode, they will be stopped in autodecide too. Is it not the funtion of Behavior Shield to stop any file that do not have a range of criteria set for Avast ? The only differece between Autodecide and ask is that in ask mode the user decide while in autodecide Avast does, and if the file is outside that criteria the alert is popping out for the user to decide what to do, and I quote:

" ...The default action is "Auto-decide", which means avast! will decide whether or not it should be allowed based on a range of criteria,......If the action is changed to "Ask" you will see a message whenever such activity is detected and you will need to confirm whether or not it should be allowed. "

I believe those .tmp files during the installment of NET Framework are out side Avast criteria and that is why the alerts come out. Why this is happening in some systems and others are not ? well that is something that scape me.

Regards.

Again, 7 different machines, ranging from XP x32, Vista x64 and W7 x64, all with avast! installed for over a couple of years, and I have never had one pop-up during a MS update. The people I maintain computers for are not a very computer savvy bunch, so any pop-up would almost be the end of the world. I have changed a few settings that I wanted, but I left the Behavior Shields @ Auto-Decide.

On my machine, (when I had the BS installed), I had it set to ask for a short period of time and I received notifications while updating Chrome, Flash and Windows Updates too. I quickly reset it to Auto-Decide and have long since uninstalled it.

[iroc9555]

@ DBone.

Will follow advice next Microsoft Tuesday. Will switch to AutoDecide for updates. Report later. Thank you.
Regards.