I am using the latest version of CIS (FW + D+) and Avast 7.
In the FW rules, how should I define Avast? Should I set Avast to “Trusted Application – allow all outgoing and incoming requests”, or should I only set it to “allow all outgoing requests”? Every time after rebooting my pc, I get an alert from CIS asking if I allow Avastsetup.exe to connect to the internet.
Also keep in mind that Avast 7 has Streaming Update feature, so I am not sure if it requires incoming traffic.
I have strictly followed this instruction. However, after a system reboot, the first two files just disappear from the list (the icons change to a Windows folder icon, and the application paths are empty), and the FW asks me again if I allow avast.setup to connect to the Net.
Your experience is caused by using the purge function of comodo lists. Somehow one process of avast is not “permanent” (avast.setup), so if you would let comodo clean the rules list from non existing entries, this one avast will be among them.
Only the avastUI has a symbol. The other two have the placeholder icon.
Same goes for purge of the defense+ list. But if you use safe mode of defense+, avast will get the defense+ list entry automatically again.
I dont know what you mean with, the path is empty.
Block rules should be on top of allow rules in the list.
Actually, there’s something not quite right here! I didn’t realise, at first, that you could still connect, even though fx was blocked. So, having now played with things, bearing in mind that problem, it does seem like Avast is making a hole in the firewall with it’s web shield. as soon as that’s disabled, things work as they should. Curious!
I’m not really sure who’s problem this is, although I suspect it’s Avast, as the firewall works correctly when Avast is not installed, or when the web shield disabled. It’s certainly worring and perhaps a good reason not to use the web shield, or even Avast 7, until this is resolved.
I dont use the web shield. Is there a security decrease with comodo and avast without web shield?
If not, thats the workaround.
I wondered about some comments from others who said, there wouldnt be a problem with the new avast web shield, while others can reproduce it.
The thematic is spread around some topics meanwhile. I would suggest a merging too.
Basically, a lot of users could be facing this problem, without knowing about it!
This is definitely an Avast problem. If you use the Windows 7 firewall and set the policy to disallow outbound connections without an explicit rule, launching a browser and trying to connect to any web site fails. As soon as one adds avastsvc.exe to the policy and allows it to make outbound connections, any browser will connect, even without a rule.
I don’t personally use any Real-time antivirus products, but if I did, Avast 7 would not be on the list, at least until this is resolved. I’d rather have a good firewall anyday.