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.
I’m not having much luck with this version. I’ve tried both x86 and x64 on bare metal and VMware and in all cases it’s reporting “The network firewall is not functioning properly - Run Diagnostics” It also kills the network connection. If I deselect the firewall driver on the NIC, the connection is re-established. Diagnostics suggests all is well
Edit: The above was on Windows 7. However, unless I misunderstand, that was fruitless exercise, as these versions are Windows 8 only?
Thanks for the Win 8 version. Will install it on my Win 8 CP. Good to have CIS on it as well.
Out of sheer curiosity. Could you elaborate a bit on the three mentioned layers and where Win 7 and Win 8 differ with regard to the fliltering? Do you have some type of schematic diagram to make it visual for us non techies?
I managed to get it working under Windows 8 CP, although had initial comparability issues. CIS installed ok, and the initial launch was fine but after a reboot it wouldn’t run. changed the comparability and on the second install it seemed to work. With regard to the question at hand, it now blocks Avast correctly. :-TU
The question then, is this ‘fix’ only going to be available under Windows 8 or are the problems with the driver I reported a couple of posts up, just a bug under Windows 7?
I encountered the same problem as Radaghast in Win8 CP. Windows asked to solve the problem and when I checked the option that the software was working fine in win7, Windows could solve the compatibility issue.
I tried the Program Compatibility Troubleshooter. I ran the installer and again it blue screened.
After boot up the Program Compatibility Troubleshooter did not start again. Which was a disappointment as it seemed nothing was registered, I ran it again, installed CIS and it worked. Yaaayyyyy… 8) ;D
Seems I misunderstood the original post, I thought these new versions were backward compatible with Windows 7, but that doesn’t seem to be the case?
That aside, the ‘Compatibility’ issue with Windows 8 CP seems a bit hit and miss. On x86 CP, I had the problems outlined in my earlier post. on x64 it went straight through without any problems. Either way, it’s certainly not a deal breaker and once working, seems quite stable. It’s interesting to see how CP is changing the rule requirements for system services.