Avast 5 Web Shield and Mail Shield do not start

Hi,
I am running Windows XP Home with Avast 5 Free Edition and every time I start my computer, the web shield and mail shield do not start with the rest of the shields. The orange avast icon in the system tray has a yellow ! icon on it and when I open the interface, it tells me that I have to click the FIX NOW button to protect my system. Any ideas why those 2 services won’t start?? Incidentally, in the Microsoft Services Management Console, the Web Shield and the Mail Shield services are set to startup Manual, has that got anything to do with it?

Any replies would be appreciated!

You maybe want to try the latest build, as many problems were fixed with that pre-release.
Look/Download here: http://forum.avast.com/index.php?topic=58183.0
For a clean install, use this first: http://www.avast.com/uninstall-utility
asyn

I has this problem when my computer was infected by virus.

Try to clean PC with any tool and after reboot you might have a fully working avast.

[sorry my bad english]

If you think you could be infected, download and run Mbam.
http://www.malwarebytes.org/mbam.php
asyn

Nexus was trying to help. Not asking to help ;D

Mariner94 was asking if it has a connection “Microsoft Services Management Console, the Web Shield and the Mail Shield services are set to startup Manual”

“Avast Web Scanner” on my system (Win7 64-bit) is also set to Manual (in services.msc), if I try to change it, it gets denied. But I think it’s purposely set that way.

I didn’t install the Mail Shield, so I can’t help on that.

I know. :slight_smile: I posted a link to his advice…
asyn

Its a bug!!!

I tried my 3 Computer clients doing update today… After restarting 2 of my clients Load Avast Resident shields about 3minutes! Im sure its the Web Shield and Mail shield which was the OP asking here. 1client was doing fine.

Please fix Alwil Team.

To resolve just click repair and it will fix the issues.

Im using Avast Free 5.0.462 and Virus Update Version 100414-1.

Im sure again its the Virus update version 100414-1 causing this bug again.

I am having a similar problem. Avast has been working fine for a couple of months. Then, today, when the computer restarted after a power failure, Avast had difficulty starting. This had happened a couple of months ago, but recurred.

I am running Windows XP Home Edition, SP3.
Internet Explorer 6 (build 6.0.2900.5512.xpsp_sp3_gdr.100216-1514)
Avast 4.8 Home Edition Free (Build 4.8.1368)

Avast starts normally, except that Web Shield and Internet Mail Shield get stuck. Both display a message that they are waiting for a Subsystem to start. When I check my Task Manager, it shows 4 or 5 ashWeb.exe processes running, most of them going gangbusters. More interestingly, the process aawService.exe is obviously stuck, with Memory Usage over 100 MB and CPU usage raning from 10% to 98% at a time. During this time, the entire computer is so consumed with aawService.exe that it takes several minutes to open up Avast and terminate the two providers. It takes several minutes to open up any other program (such as Task Manager).

I installed the most recent update to Avast, but that did not resolve the problem. I do note that I currently have the same Virus update as the other user who has problems (100414-1).

I forced aawService.exe to end, but it started back up almost immediately. After a couple of reboots and a couple of times terminating and then trying to restart the two providers, I forced aawService.exe to end. This time it stayed inactive, and lo and behold the two providers began working again. Thus, it seems that the problem is not with the providers themselves, but with the “subsystem” represented by aawService.exe.

Could it be a sporadic incompatibility between Avast and IE6? I notice it is only the internet-capable “providers” that are having problems.

Any thoughts on how else to resolve this than spending an hour or more getting it to work?

Oh yeah, I should add that I am separately running the same version of Avast and its virus definition on my Windows Vista laptop, and have never had this type of problem occur.