The bug, that prevents you from removing more than one item at a time from the Trusted Software Vendors list is still there.
At least it seems, that a modified list isn’t set back to the default list anymore.
My OS is WinXP, SP3, no other security software on a virtual machine (VirtualBox 2.2)
Steps to reproduce:
Remove two or more items from the Trusted Software Vendors list, click apply, reopen the window:
Not all previously removed items stay removed
If I have a file called ‘A.EXE’ in my exclusions and I manually replace it with a different executable renamed to 'A.EXE", will CIS detect the change and 1) report it, 2) remove ‘A.EXE’ from the exclusions or 3) continue to scan but not alert?
Judging by the information stored in the registry after an exclusion is made there is no way CIS can know whether it is the same file or not, therefore can only assume it would treat it as excluded. A better way would be to store hash information and compare that to the exclusion information and actual file on disk.
BSOD happened during My Computer scan.
I had a same problem with 4 previous non-beta versions.
Doesn’t happen always. Sometimes scanning goes without a problem.
Thanks dchernyakov, I know that, but I’m asking if CIS requires internet connection during its own installation to TC proper function. Does it need it?
I haven’t tried an installation without TC (then try to activate it), but I did notice during installation of CIS it connects to the server to register itself.
AVG detects a virus in the Comodo files while running a full system scan. It appears that the Comodo components are being detected as a threat.
Win32/PEPatch found at: C:/Program Files/COMODO/COMODO Internet Security/SCANNERS/heur.cav
Win32/PEPatch found at: C:/Program Files/COMODO/COMODO Internet Security/cmdagent.exe (1340)
I don’t mean ‘log in as Admin’ I mean exit (close) CIS (the GUI) from the Tray (right click on it).
then restart CIS as Admin.
Yes, I have done this and Export/Import (both) worked properly. Make sure you export the active configuration. When you load the file, it’ll ask to name the file. Use the default if you wish or give it another name. Allow it to overwrite the existing configuration if you use the same name as already exists
(e.g. Proactive configuration active, I named my export file ‘test2’ in my Documents folder. I imported this file and allowed it to use the same name ‘Proactive’ that already existed - I overwrote the existing one with the saved one. All settings remained and are correct.)