Regarding the loss of configuration, I’ll give you an example :
A customer uses software that originates from a country in conflict.
The software is very good.
However, the customer doesn’t want to take any risks.
HIPS and firewall rules are applied so that the software can only do what it is supposed to do.
The publisher is taken off the trusted list and manually set to “unknown”.
The customer validates the procedure and feels at ease with it.
Visit a week later:
The config has disappeared, along with all the settings and parameters.
The customer doesn’t know if he’s been exposed: Total loss of confidence!
Impossible to recommend this product (CIS) or brand (Comodo)!
I’m losing face!
Try, for example, setting an editor to “Unknown” and then saving the config.
Some time later, go back and check = it’s set to “Approved” again…
The installer itself is 32-bit, but it installs 64-bit CIS Premium.
Also, devs, can I make a few requests?
When CIS is under password protection and when the password prompt pops up, can you make the text input field grab focus? It’s just a minor annoyance that I always have to put my cursor in the text field before typing the password.
Or is it for security reasons designed like that?
Also, I would like to have an additional option for on-screen alert timeout: “Indefinitely”. As stuff happens when I’m away and setting the timeout to 999 seconds is silly and insufficient.
Number 8 bug is true there is no green border when running a sandboxed app which launches CMD or powershell,but on Xcitium AEP it does sandbox cmd,powershell etc
I actually have the same problem as you, it’s the same BUG.
As my CIS is password protected, when I go to use it and enter the password it doesn’t stay focused, every time I have to click to be able to enter the password, as shown in the image below.
It appears here for me, but when I restart it doesn’t appear, then from time to time it appears again, so I have to restart the computer.
I find this very strange.
Oh, is that actually fixed in the latest version? I remember in old version when timeout value was not set then CIS used some default value, a couple minutes perhaps?
So in this new version the alert actually stays until interacted with?