There does not appear to be any functional problem with Comodo that I have observed? The only message I recieve from the system tray is from Windows Security Center stating: “Actions Required”. But there isn’t anything that can be done? Clicking on Windows Security Center shows a red “x” on Firewall & network protection. Clicking “Open COMODO Firewall” does nothing. It doesn’t open COMODO or do anything… Shouldn’t it?
Screenshots attached. You can also see it was functioning correctly for about 5 - 10 minutes then Windows 10 states there is a problem with COMODO. And although it says “Turn On Now” … clicking this does nothing also.
thats it guys. im donne with windows 10. no more for me… back to win 7 as i should never leave… when the updates expire ill be back to linux for good…
running latest cis before this release on my win 7 pro x64 withuot any kind of problems… ill upgrade to this new edition as soon as it shows me to upgrade on cis interface dialogs.
The security center is nothing but a dashboard made for user convenience. It relies completely on what security programs tell about their state. It is also known to have problems with the communication with the security programs, hence why I asked to reset the security center first, making it not reliable.
Just open CIS using the shortcuts that are on the desktop, task bar or start menu. It should open normally. Then look at the main interface or look at the widget and see if it reports Secure. If CIS reports it is secure then it is running like it should.
Since the SC not always reliably reflects what security programs tell it it you should always default to what CIS reports about its state in the CIS interface.
That is a fair enough assessment on Security Center, but I have not experienced a situation like this with COMODO before. COMODO has tied in with it before with every version I have used in the past. Clearly there is an issue here that needs to be fixed on COMODO’s end as we would not be having this number of people posting issues with it. I even performed the reset as suggested but it does not work. Did you read the replies to your suggestion? It doesn’t work by default as those commands are denied. Additional steps are needed to be taken in order to properly reset it. Even then… it still did not work.
COMODO is reporting SECURE… but I would like this issue corrected so Windows isn’t telling me that there is a problem with COMODO. Every previous release has been fine with Security Center.
This one is for Comodo to figure out where things go awry between CIS and SC.
What I was trying to say in general is to always trust what CIS reports over what SC reports. It was meant to take away doubts people may have whether their system is secure or not. When CIS says its running secure your system is secure.
Oh I do believe that when COMODO says it’s secure it is indeed secure. And I apologise if I seem a little edgy… I’m just a tad annoyed that I can’t rectify this issue myself. I’m usually pretty good at figuring out how to fix software issues myself. But I do thank you for the assistance! I provided a mini dump file too so, hopefully it is of some use.
Np. Thank you for creating the minidump. That will help Comodo figure out what is going on. This issue may be beyound what end users can figure out by using common sense and experience of years.
Hi All,
We can’t really produce it, need further help, when you see snoozed status, please go to “Task Manager–>Details Tab” and select “cmdagent.exe” and right click on it and then select “Create dump file” and share dump with us.
Hi Umesh,
Could you please share more details about this.
As I know (please correct me if I’m wrong) this setting is responsible for:
(a) enabling additional HIPS techniques to “countermeasure extremely sophisticated malware that tries to bypass regular countermeasures”; CIS uses some tricks to improve the security for 64bit OS by circumventing the hooking restrictions caused by Kernel Patch Protection of 64bit OS;
(b) enabling use of Intel VT-x or AMD SVM Virtualization extensions (if available) for CIS to be able to operate as type-1 hypervisor; this (in theory at least) should improve both the security and performance of the sandbox.
In the past these were considered as valuable additions to security.
Does the announcement above mean that starting from now on both (a) and (b) technologies will not be available in CIS/CF?
By what kind of incompatibility issues it was reasoned? (My guess is some incompatibility with the upcoming windows release, because you decided to entirely remove the settings instead of making it opt-in)
And finally, how will it affect the security in comparison with installs where this setting were available and turned on?
By what kind of incompatibility issues it was reasoned? (My guess is some incompatibility with the upcoming windows release, because you decided to entirely remove the settings instead of making it opt-in)
And finally, how will it affect the security in comparison with installs where this setting were available and turned on?
In brief, with recent Microsoft Updates, in all relevant OS, Microsoft doesn't recommend certain hooks and even if you apply, they are void and won't work.
So there are OS limitations.
And I apologise if I seem a little edgy… I’m just a tad annoyed that I can’t rectify this issue myself. I’m usually pretty good at figuring out how to fix software issues myself. But I do thank you for the assistance!