Here we are happy to announce that Comodo Cleaning Essentials V10.0 new version is now released !
It has been a long time since CCE product has not been released with significant new features .From now on we will keep improving Comodo Cleanning Essentials with constant updates according to your feedbacks and comments.
Please keep providing your feedbacks for us to serve you the best!
Note: Users with previous versions installed will receive an update with this release.
Thank you very much to you all in advance and we will keep improving.
Hi L.A.R. Grizzly,
We have investigated. Seems you have CIS v7.x installed.
When CIS is installed, KillSwitch makes uses of CIS services to scan a file. CIS v7 is not compatible with latest KillSwitch and therefore it exit.
With next CIS release, KillSwitch version that comes with it will be updated so you can use that and in future CCE releases, we will capture this scenario where KillSwitch may end up running with very old CIS version and behaves accordingly.
Command line parameter to randomize CCE window names
I've suggested this for quite a long time. It's a good addition. How about other window info? For example, Class and Visible/Hidden Text?
Here’s visible text:
Here’s hidden text:
Start a scan to unearth and remove viruses, rootkits, hidden files and malicious registry keys hidden deep within your system.
Loading engine and collecting system information ...
Please wait while the virus database is being updated.
This might take a few minutes...
Updating virus signature database...
Keep virus signature database up to date so that COMODO Cleaning Essentials can detect and remove the latest viruses and rootkits.
Not to mention, command-line sniffing protection → actually, I am not sure why users would need to pass command-line arguments. It would be better to use random values by default. :-La
Thanks for reply. Glad you are considering it & wouldn’t expect less. I rarely used it with real scenarios (and I usually make “undocumented tests” based on my ideas-- too many to list). I did make a suggestion based on such experience : Add boot-time scan to CCE [M1138].
Keep up the good work (as always).
PS: I’m a bit confused if your post was directed at me personally. Made my ego boost a bit. (just kidding)
When you have a malware that controls system at boot level and even if you scan at load time, you don’t know if your module is hooked itself.
As both malware and your scanner could be at same Kernel level.
The best route in such scenarios is to use some rescue disk like tool and boot from that and then scan PC, everything else is half cooked measures.