Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Comodo
Drawbacks of Comodo Cruelsister Config
Message
<blockquote data-quote="AtlBo" data-source="post: 832072" data-attributes="member: 32547"><p>It's understandable for sure. I just spent the better part of a day today trying to determine what was wrong with CF. It suddenly would not enforce rules for a .bat on the desktop. I tried everything, removing every trace of the file from Comodo settings, moving the file, making another by a different name and still the .bat would run with HIPs on in safe mode and auto-contain on too. Nothing. So, I finally gave up and tried ZoneAlarm for about an hour, until I saw it isn't for me. It's much better than a year or two ago, however, that is for sure (no comparison almost). Then I uninstalled ZoneAlarm and finally reinstalled Comodo. I reimported the same settings I saved before uninstalling, and now it's working perfectly.</p><p></p><p>Comodo have got to get the run time reliability of the FW to a respectable level. There have to be warnings in the program when something is not functioning as it should. Look at Avast. If something isn't working, Avast will say so in the system tray and or with an alert. Seriously, if the program is just going to be off while it sits there using the processor, should it be there?</p><p></p><p>Maybe conflicts with Kaspersky are the problem here, I don't know. For now, I will go as long as Comodo is functioning and just run a test every once in awhile to see if it is. In the mean time I will be counting on KSC and NVT OSArmor too, so I am not too worried...</p></blockquote><p></p>
[QUOTE="AtlBo, post: 832072, member: 32547"] It's understandable for sure. I just spent the better part of a day today trying to determine what was wrong with CF. It suddenly would not enforce rules for a .bat on the desktop. I tried everything, removing every trace of the file from Comodo settings, moving the file, making another by a different name and still the .bat would run with HIPs on in safe mode and auto-contain on too. Nothing. So, I finally gave up and tried ZoneAlarm for about an hour, until I saw it isn't for me. It's much better than a year or two ago, however, that is for sure (no comparison almost). Then I uninstalled ZoneAlarm and finally reinstalled Comodo. I reimported the same settings I saved before uninstalling, and now it's working perfectly. Comodo have got to get the run time reliability of the FW to a respectable level. There have to be warnings in the program when something is not functioning as it should. Look at Avast. If something isn't working, Avast will say so in the system tray and or with an alert. Seriously, if the program is just going to be off while it sits there using the processor, should it be there? Maybe conflicts with Kaspersky are the problem here, I don't know. For now, I will go as long as Comodo is functioning and just run a test every once in awhile to see if it is. In the mean time I will be counting on KSC and NVT OSArmor too, so I am not too worried... [/QUOTE]
Insert quotes…
Verification
Post reply
Top