Avast has acknowledged their scanner as error for creating this issue and are correcting it.
Avast changing the design of their software does not eliminate the basic problem. It will only mean that the problem won’t be seen when running Avast. Correction: only means that Avast won’t proxy confuse Comodo Firewall. Some other program still could. I for one would like to see that hole closed.
This is from egemen the head developer:
There Mr. Tas tells us why this is happening: 1) The user installed a program that redirects to a local proxy in a particular fashion, and 2) Some rules Comodo Firewall wants to apply don’t work because of some aspects of Windows 7. I’m asking about #2. Sometimes a developer can work around OS limitations by modifying their own software, and they do. Sometimes a developer can’t work around OS limitations, or they simply decide not to. Sometimes a developer puts off trying to answer that question while they are trying to push something else out. I’m just asking for an update; trying to get a sense of where things stand and are headed. Is Mr. Tas around?
Note also the Avast issue affected MS firewall also. Are you going to demand from MS they repair their firewall to prevent this from happening again?
If not, this issue is done and closed as of now!
This issue has been beat to death.
Just be content knowing CIS 6 will protect you.
Thread locked.