Posted 10 May 2014 - 03:36 PM
I actually just uninstalled COMODO INTERNET SECURITY (CIS), earlier today. I've been using CIS since 2009 or 2010. On 2014_04_09, I had placed the CIS current version on my computer and since then had it running in the training mode. The training mode is suppose to learn what I do, and add appropriate rules for me.
Well, I went from training mode to safe mode earlier today, CIS was suppose to know what my habits were. So I started up one of the programs that I used countless times in the past month, CIS kept asking permission to let the program execute. I checked the programs in the area where the programs were listed, and the program was there, with permission to run, CIS kept asking permission to allow it to run.
If you you look at the "ALLOWED APPLICATION" category, you'll see that the run as EXE parameter doesn't have an allow option, only ASK. To override this, then you have to drill down, and one at a time, add an exception, which is ridiculous. Once you say the program is OK, you shouldn't have to do this.
Then, at times when I reboot my computer, I'd have to reboot it 4-5 times, because CIS is causing things not to display or run on bootup. I have to start the task manager, and attempt to terminate CIS, before something would show up. I uninstalled CIS and the boot process went just fine. I installed an INTERIM FIREWALL (at least that's the plan) I'm using, and I had no problems. This INTERIM FIREWALL (NO THIS ISN'T THE NAME OF IT) had been running on my testbed, desktop computer for a month.
The INTERIM FIREWALL detects when a program is running, and asks permission to let it run. I tell it AOK, and it remembers it. Only on occasion will the INTERIM FIREWALL ask again. But that would be like the program trying to access the INTERNET, when previously it was say trying to do something in say C:\\WINDOWS, for example.
But the INTERIM FIREWALL will allow you to highlight a program in the list (or multiple programs on the list), and with just a couple of mouse clicks allows all actions on the list, deny all actions on the list, or selectively choose certain actions. All tests I performed blocks incoming access, unless specifically allowed.
CIS didn't think things out. When there's a "ALLOWED APPLICATION" category, the run as EXE should have a "ALLOW" option, it's only common sense, not an "ASK" option!