PrivateFirewall, Outpost Firewall and Online Armor all work fine with avast, iv been testing all of them this week 
Itsâ also just the outbound protection of the windows firewall that causes some problems but in itâs default state it works fine.
Thank you both, sorry for being a blunt. I just got to my wits end dredging through threads not only here and running multiple scenarios myself to try and sort it that it got to a stage i just needed some straight answers.
My apologies and thank you both
Youâre welcome.
Craig, of these 3 third party firewalls, which is likely to be the quietest after the initial learning period? As per my signature, you can see that Iâm using Sygate and itâs catching changes to Firefox, etc. after they are updated and asking. However, itâs been EOL for some time now.
Even though i have a Pro license for Outpost which the latest version 7.5.2 i think is there best version yet for compatibility and system lightness but i think i still prefer Privatefirewall more. I only recieved a couple of popups which were for my mobile broadband and Total Media Theater in that whole week of testing and the lightness on the system was excellent, it feels lighter than the windows firewall.
Theres a very informative pdf file on there website that is well worth downloading and reading, good to keep for future refrence
Thanks, Craig. I have Private Firewall install and the pdf downloaded. Iâll read thru the pdf, and likely change over to it sometime this next week.
No worries, enjoy
Just to update you PrivateFirewall doesnât stealth my ports properly with mobile broadband but does work fine with routered connections, Outpost is superior concerning mobile broadband.
I also having the problem, avast webshield with comdo firewall. Is there is any fix available other than disabling the webshield in avast
+1 I strongly agree with craigb as I have mobile broadband too using Outpost Pro, craigb did you get yourself a lifetime license when you got your Outpost Pro FW
Sure did, bought two of them for $30 each if i remember correctly
Here is a reply from the comodo developers about the situation
Hello Guys,The issue is avast intercepts WEB connections at the driver level and redirects connections to its own local proxy.
Because CIS operates at NDIS layer i.e. the lowest layer of the protection, it sees the actual connection i.e. avast proxy. Normally CIS should have blocked the loppback area connection to the proxy however because of the limitations in Windows 7, it fails.
CIS uses TDI, WFP and NDIS to provide its firewall functionality. WFP maybe enough ti implement an average firewall but it is not enough for a firewall like CFW so that it could not be used alone wihtout the support of the other 2 technologies. Windows 8 allowed us to use WFP more than previous windows editions and it should not be a problem with the next CIS editions which support Windows 8.
Hello Guys,The issue is avast intercepts WEB connections at the driver level and redirects connections to its own local proxy.
Because CIS operates at NDIS layer i.e. the lowest layer of the protection, it sees the actual connection i.e. avast proxy. Normally CIS should have blocked the loppback area connection to the proxy however because of the limitations in Windows 7, it fails.
CIS uses TDI, WFP and NDIS to provide its firewall functionality. WFP maybe enough ti implement an average firewall but it is not enough for a firewall like CFW so that it could not be used alone wihtout the support of the other 2 technologies. Windows 8 allowed us to use WFP more than previous windows editions and it should not be a problem with the next CIS editions which support Windows 8.
Thatâs nice, but how about fixing CIS so it will work with windows 7?
Hello all!
I can confirm this, I made a lot of tests: this is an exclusive Avast bug. The same behaviour written in first post it happens with:
Avast 6 OR Avast 7,
Comodo OR Privatefirewall,
Win 7 OR Vista,
in any combination.
So, this is not a matter of Comodo or Privatefirewall, Seven or Vista problem. The sole common factor in all combinations is Avast, 6 OR 7. When Avast is disabled and the common factor gone, all the setups are working well.
And a little offtopic: beggining with the first release of Avast v.7 and its database (available for v.6, too), many well known apps, like FotoSketcher, UltraISO, WinTools.net and Cool Edit (yeah, I now, itâs old) are detected by sandbox as possible dangers.
I think this version of Avast was made in a big hurry and without the old respect for this brand, sorry.
Tnank you for your attention!
So itâs an âexclusive Avast bugâ that only occurs in combination with other products. :o
(My brain hurts!)
Privatefirewall works fine with avast, i spent a week recently testing that firewall and no problems at all except for detection of mobile broadband networks.
You need to add exclusions between avast and privatefirewall for them to function correctly, outpost and online armor firewalls also function without problems so i believe the problem lieâs with comodo but im not willing to test that one
Well for me the First post in this shows an inadequacy in the firewall if it canât determine the process using the localhost proxy.
I did a simple test, blocked the network connection for firefox.exe in my Firewall Outpost Firewall Pro (image1) and then tried to read unread posts (image2) and no content. So it wasnât able to tunnel through the avastSvc.exe proxy undetected.
Yes, THIS specific bug, in this thread, is exclusevly related to Avast. The combinations only, and only them, with a single constant, reveal the âownerâ of the bug. Youâll not be able to know there is a bug in a soft if this is only on your cd or dvd. There, in dvd case, all softs are perfect. Your brain hurts because you have it AND you feel it. And yet, only the brain hurts, exclusivelyâŚ
It hurts, ah?
Thank you, Iâll try, perhaps. But too many headaches 
for an AV. Maybe itâs time to change. Or go back to the 4.8. :-\ Thank you again.
Hi All,
@Sceleron.
No need to go to 4.8. Version 6 works just fine.
Also, this issue is caused by avast, but should be fixed by Comodo.
Itâs shocking that a proxy service is able to bypass their Firewall⌠What a disgrace.
Whatâs even worse is that this bug has been live for so long and they have done Nothing!.
I got/get what youâre saying. All I meant was that the problem canât simultaneously be âexclusiveâ and occur âin any combinationâ.
'Exclusive" means, (a) on itâs own, (b) not with or apart from anything else.
Ergo, âexclusiveâ use of AIS 7.0.1426 causes me no problems on My Windows 7 machines.
As well I donât think itâs best described as a âbugâ in avast!
If any antivirus using MS approved methods and APIs can bypass the outbound monitoring of a firewall (Microsoftâs or Comodoâs), I tend to think that fixing it should be a priority for the vendor of the functionally-compromised component.