Avast and Comodo conflict

[drummerman]

It was mentioned to me over at the Comodo forum that a v6.0 will resolve the issue. Public beta should be released end of August/early September.

Until then apparently v5.8 gets around the problem but I haven't yet looked into it.

Hope this helps.

regards

[bob3160]

Helps who

[drummerman]

Helps who

Anyone who uses/used Comodo, likes the FW and may want to return using it or is hoping for a fix to the problem.

[MrMaxaMan]

Yes hopefully they will correct this problem with the next update. I've been waiting long enough.

[DavidR]

Yes hopefully they will correct this problem with the next update. I've been waiting long enough.

Who will correct what, as this isn't an avast issue but a comodo one ?

[drummerman]

I probably should have made it clearer, it is a Comodo update that will tackle this. Clearly not an Avast issue, as you kindly explained to me in another thread.

regards

[gdiloren]

Just went back to Avast from a year. I was finally able to get rid of other AV leftovers in my Registry so now it works EXCELLENT or seem to. Only problem is I won in a giveaway OnlineArmor Premium licence for 1 year but uninstalled it (too complicated and unworkable for me/ First who PM me will have the licence emailed) to go back to Comodo FW which is at top of Matousec ranking (Ok, they pay for that, anyway...!). Except we have this: http://forums.comodo.com/firewall-help-cis/comodo-firewall-and-avast-7-t82382.0.html and they say there is a conflict between Avast 7 WebShield module and CFW. Except if I stop all traffic on CFW I can't browse, so it works,  so I guess I don't see the problem! I was using Private Firewall previously and no problem at all with Avast but would have a chance to try CFW for it's given 100% efficiency by Matousec with D+ and Sandbox implemented
PROBLEM SOLVED: see http://forum.avast.com/index.php?topic=93953.105     

[MrMaxaMan]

Yes hopefully they will correct this problem with the next update. I've been waiting long enough.

Who will correct what, as this isn't an avast issue but a comodo one ?

I meant the next Comodo update.