I have big problem and cant not find out what exactly and why it occures.
Here the details.
I have brand new Laptop Toshiba, Windows 7 (64bit) installed.
With this laptop I was not online and didnt install anything else besides AVAST Antivirus and Comodo Firewall.
Ok, at first I installed Avast Pro 4.8, rebooted, everything OK. next step to install firewall. so I installed Comodo Firewall (actuall version 3.13.xxx from December), reboot … and noticed that the WebShield of Avast is not active. Of course de- and reinstall I tryed too but no success. Repair also. When I first deinstall Comodo and reboot, the Avast Webshield get active again.
Then I thought maybe it is because of Avast version. At this moment Avast 5 came out so I deciced to try this. So I deinstall old Avast 4.8 and Comodo and installed first Avast 5 Pro - after reboot the WebShield was running, every Avast component was running. Then I installed Comodo Firewall - after reboot the WebShield of Avast was disabled again
I tryed the same with Avast 5 Free but the result is the same.
I tryed also the reverse order - at first installing Comodo Firewall and then Avast, but the result is the same too
As I said deinstalling Comodo activates the Avast Webshield again.
So after all thi I thing the issue occures because of Comodo. The problem should be in Comodo. I looked in the Comodo settings but I didnt find anything. All settings were at default, both Firewall and D+. I set Firewall and D+ to training mode but the WebShield doesnt get active
I dont know what else I can do .
PS: I disabled in msconfig the whole Toshiba stuff starting on Windows Startup - without success.
Can comeone test it on his system - -Windows7 (64bit), Comdo Firewall and Avast 5 Free.
I havent been online yet. As I wrote I wanted to set Av and firewall first.
Without Comodo Avast Webshield works prperly.
Comodo is detecting avastSvc.exe as trust
Delete the entry, as I said this should force it to either ask permission or re-evaluate it. There are times when even though allowed the firewall still seems to block, deleting the entry seems to resolve this inconsistency.
I’ve always heard on several tech forums you should always install your firewall first, then your antivirus software, and finally your antispyware. I have always installed my Comodo FW first, Avast next and have never had any problems doing it in that order. You might try it that way. Maybe third time’s a charm? I too just installed Avast5 (in Safe Mode) this week (with CIS already installed) on a brand new Win7 Home Premium 64 bit HP desktop. Went smoothly as it always does.
ok, I will try.
Without WebShield is bad, isnt it?
well I already tried this without success.
But as you have Win7 64bit too and you dont have this issue… hm, then I dont know :-
With version of Comodo do you have?
I have latest Comodo 3.13.126709.581 (Gee their version numbers are ridiculously long, aren’t they?)
Maybe your downloaded copy of the Avast5 installer (or Comodo Installer) got corrupted “en route” and a fresh download copy of both is worth a try. I know it happens and did happen to me one time with an Avast D/L.
EDIT: Forgot to mention it’s the Avast5 Free Home Edition I installed. You’re working with the Pro version, aren’t you? Oh, no…now I see you ARE using the free version. Hmmmm.
Well, I’ve exhausted my thoughts on this. I’ll have to let the experts here try to get back with you on this. I just thought the “order” in which you were doing things might be a factor.
One other thought…you have got a FW rule in Network Security Policy that grants ashWebSv.exe both inbound and outbound access? That would be necessary.
I also have a Network Security Policy that makes AvastSvc.exe a “Trusted Application” (allows inbound/outbound access). You might set up this rule and see if that makes any difference.
Not entirely correct, cska133 has version 5.0.377 installed and as such ashWebSv.exe doesn’t exist (did in 4.8). Si it doesn’t need permission as the controlling process is AvastSvc.exe, which needs permission (which cska133 had done, Reply #2 of this topic).
oh I can not believe it, it was the ***** McFee Angry It was already installed on the laptop, but I though it was not active, because I already disabled it in Services and Msconfig.
So now I deinstalled McFee compleately and it looks like Comodo and Avast 5 were working well … so far.
Thanks for the feedbacl and glad that you now have it resolved.
That is the problem with resident antivirus applications, as they load low level drivers to hook files for scanning even if the main element is disabled and these can still conflict.
I too just installed Avast5 (in Safe Mode) this week (with CIS already installed) on a brand new Win7 Home Premium 64 bit HP desktop. Went smoothly as it always does.