Your sig states that your already using OA :
it’s working isnt it ??? Outpost firewall works good too
i dont know , im not a expert ;D
Hardov.
OA is ok. Up to now this behavior is affecting only Windows 7 64 bit using Windows firewall, Comodo FW, and now there is a new report that Private firewall is affected.
Online Armor is not affected as seen in https://forums.comodo.com/firewall-help-cis/comodo-firewall-and-avast-7-t82382.15.html Reply 28 / 47. I have Outpost in another pc and it’s not affected. Seems to be affecting x64 systems. I have Online Armor Premium ver5.5 with Avast IS Build 1426 on an Win7 x32 and it’s not affected. My other x32 with AvastFree and CIS ver5.9 seems to be functioning okay. I can block FF in CIS>Firewall rule while I have Avast WebShield enabled.
In my CIS FF is set as “web browser”(built-in rule in Comodo). The same rule I use for Google Chrome and IE/Opera. I tried to set it at “Blocked application” in Comodo and CIS blocks the connection and launching of the browser. On an x64 pc it ain’t like that.
are you guys setting any rules for the localhost communication. since it is actually the connection between the browser and Webshield that you want to control and it is between 127.0.0.1:xxxx and 127.0.0.1:12080, so really are your firewalls able to block the localhost traffic, or control it - are you sure you don’t have there some big rule allowing all trafic inside the computer (localhost only) etc.
Thanks for the reply.
1.This didn’t happen using Avast 6, it’s a specific ‘issue’ with Avast 7.
2. Some Applications specifically require access to loopback for internal communication, for example firefox.
3. Creating a specific rule to block all localhost communication, for IE, had no effect.
By the way, this ‘issue’ affects 32 bit and 64 bit Windows 7.
As I’ve said before - avast7 uses different driver API to do the redirection. It really depends on the firewall how they do treat that. Maybe before, with avast6 Comodo was not even aware of the fact, that the browser is not really connecting to the Internet (instead making only localhost connection to the scanning proxy) and hence it treated it with its outbound rules. Just guessing though.
Maybe a rule with “incoming connections to avastsvc.exe - ASK” will solve that.
I highly recommend that you use only avast or comodo firewall. In my opinion, avast is enough. You do not need to install any third-party firewall. Installing many firewall softwares does not insure that your computer is well-protected. In addition to that, there will occur conflicts between the sofwares which will slow your computer down or even cause the blue screen of death!
True, but we’re talking about avast! Free or Pro here. 
Second Asyn statement, and add that W 7 firewall is also affected so It is a must to have a working third party firewall with Avast! Free or Pro.
Hi All,
Please note that CIS was updated to version 5.10.228257.2253.
This issue with Avast and Comodo Firewall is still very much present.
Cool…i was waiting for an update coz i want 2 install the comodo firewall n use avast free alongside…so u mean that comodo have fixed the problem with avast and both r working fine???
No, Comodo has not fixed it yet. This issue is still happening with a few FW. If running Avast! 7 free under W 7 better get OA or Outpost.
Hi All,
Sorry edited my previous post as it made no sense.
I have no problem whatsoever. I installed Avast 7 first, then I rebooted and installed Comodo Firewall.
I read somewhere years ago that its better to install Avast first then only install Comodo Firewall.
But I am not sure.
I want to upgrade to Avast 7, but there’s no point if it’s going to mess up Comodo. I hope this problem gets sorted out soon.
Like to add latest version 5.10.228257.2253 blocks FF 11.0 if policy is set through Firewall>Network Security Policy. Change is made @ FF line from Web browser to Blocked Application and works as it should. FF is blocked. Changing setting back to Web Browser restores connectivity.
Bug in COMODO firewall does only seem to affect Win 7 systems from what I’ve seen here. What I’d like to find out why this is so, and why Win Firewall is also affected in Windows 7.
Bug does not seem to affect XP versions.
So in making this statement i would have to take it that Avast does not see this as a security issue?? When you consider all of the unsuspecting, don’t know otherwise Avast users around the world that are using Windows Firewall, Comodo Firewall and a couple of others mentioned such as Private Firewall
It means Firewalls should be able to block it, or malware also can bypass Firewalls. It is Firewalls’ fault (security hole).
Fixing avast to be blocked by Firewalls does not solve this problem. No one wants malware to bypass Firewalls using same technique.
I get what you are saying, so the reality is without beating around the bush Comodo and Windows Firewall aren’t up to scratch security wise and as i have read Online Armour is the one to have? Sorry i just need to hear the cold hard facts so i can make a sound decision without pussy footing around.