Thanks I excluded the Comodo folder as you suggested. You think it’s necessary to do that with individual cfp and cmdagent exe’s too?
Are you running the “AVG Security Toolbar”? Since I posted on 12-26 that I turned off AVG Toolbar, I’ve had no more problems opening Comodo and no unreponsive Comodo program shutting off the computer.
How did you manage to add the folder to the exclusion list?
Open AVG, click Tools > Advanced Settings > Resident Shield > Excluded Items > Add Path, and find Comodo in the programs. See attached screenshot.
[attachment deleted by admin]
I’m not sure if it’s necessary to exclude cfp and cmdagent - I just did that to be safe. I guess I could try it without those two exclusions for a few days to see if the problems come back…
And also, no, I’m not running the AVG toolbar - I don’t even have it installed!
Thanks. Will see how I get on.
Sorry to report today after restarting the computer, I could not open the UI for Comodo, and after 3 reboots it is working, I can open Comodo.
In these cases where the UI won’t open, Comodo is not closing at shutdown either. Wait two minutes for it to time out and it will finally close and reboot. Back to the experimenting!
Dear Comodo engineers… Please fix the UI and not shutting down problem!
So I tried not having cfp.exe and cmdagent.exe in the exclusion list for AVG, and Comodo froze up once some time afterwards, and then went back to behaving well. (has been ever since)
It’s kind of strange, though; sometimes I double-click to open up the Comodo UI and it doesn’t open, and then I right-click the tray icon and the menu pops up, and I can open the UI from there. This only happened a few times, though.
I also forgot to mention that I have AVG’s Identity Protection disabled, but I doubt that has anything to do with Comodo not responding. After all, I though I had it disabled well before Comodo magically stopped not responding… (I don’t really remember)
Right now I’m testing it out with Identity Protection enabled…will see how it goes. (so far so good, but probably because it’s only been about 1/2 an hour since I re-enabled it)
Also, I wonder what process shuts down unresponsive programs during computer shutdown…if I could allow it to terminate Comodo, that might speed up shutdown because Comodo wouldn’t attempt to block that process from shutting it down (if that’s what it’s trying to do). (I’m assuming it’s not Task Manager because I already have that set to be able to terminate Comodo, and it’s not doing that very well during shutdown when the system trys to terminate Comodo.)
But so far I haven’t been able to figure out what shuts down unresponsive programs (or is Task Manager the only one that does that?)…
(still trying to deliberately get a program to freeze so I can shut it down (not using Task Manager) and see what it is that’s shutting it down)
Either way, though, there’s probably not going to be anything much we can do to solve this problem.
The BEST solution would just be for Comodo to fix this issue…eventually.
(Makes me wonder if the developers even know about this issue?)
I recall when I was using Comodo 3.x occasionally it would not close at shutdown, hang up the process for a couple of minutes. I went from 3 to 5 so don’t know what 4 might have done.
Did you by any chance makes changes to the programs that are allowed to terminate CIS executables. There is a list of 15 Windows executables that is allowed to do so.
But so far I haven't been able to figure out what shuts down unresponsive programs (or is Task Manager the only one that does that?)... (still trying to deliberately get a program to freeze so I can shut it down (not using Task Manager) and see what it is that's shutting it down)To make sure the devs see the problem it is best to file a bug report about it. Before filing it make sure you have the problem narrowed down the best of your abilities.Either way, though, there’s probably not going to be anything much we can do to solve this problem.
The BEST solution would just be for Comodo to fix this issue…eventually.
(Makes me wonder if the developers even know about this issue?)
15? In my list under both “Interprocess Memory Accesses” and “Processes’ Termination” I have only 13, and one of them is Task Manager which I added myself.
The 13 are:
Windows System Applications (System, %windir%\system32\svchost.exe, %windir%\system32\smss.exe, %windir%\system32\csrss.exe, %windir%\system32\winlogon.exe, %windir%\system32\spoolsv.exe, %windir%\system32\lsass.exe, %windir%\system32\wbem\WMIAdap.exe, %windir%\system32\wbem\WMIPrvSE.exe, C:\Program Files\COMODO\COMODO Internet Security\cavscan.exe)
C:\Program Files\COMODO\COMODO Internet Security*
%windir%\system32\msiexec.exe
And then Task Manager (C:\WINDOWS\system32\taskmgr.exe).
I didn’t change anything besides adding Task Manager.
So what three am I missing? (assuming Task Manager isn’t one of them)
These are the extra ones that I have in the Windows System Applications group in the exceptions of Process Termination:
%windir%system32\VSSVC.exe
%windir%system32\consent.exe
%windir%system32\Searchindexer
%windir%system32\SearchProtocolHost.exe
%windir%system32\dwm.exe
What Windows version are you on? I am on Win 7.
I am on Windows XP Home Edition (service pack 3).
None of those files exist on my system except for %windir%\system32\vssvc.exe.
A quick Google search says that it’s related to the Volume Shadow Copy service.
I don’t think this would ever need to terminate Comodo, would it?
VSCS is not the first thing that comes to mind when I think of possible Windows executable that could terminate CIS.
I was asking just to be sure you had not made custom changes with the exceptions of CIS termination.
It has been reported that installing AVG and CIS in order; the one after the other could be of help with this problem. Did you try that? The order has been reported in this topic I think.
I already had AVG 2011 installed before I installed CIS. Should I have temporarily disabled AVG before installing CIS?
(By the way, from reading the “Comodo Firewall running, but not opening?” thread, it appears that installing AVG and then disabling it and installing CIS didn’t fix the shutdown issue. So…)
Still it would be worth the try.
Hiya all,
Im on XP sp3 and i had all the issues raised in this thread, as part of testing i removed/uninstalled Comodo CIS and AVG 2011 and started with loading CIS and testing it for a few days, ALL the issues went away.
I THEN loaded AVG 2011 , i didnt get any conflicts and its all still working fine. It may be that loading CIS first could fix a lot of issues.
I hope this helps.
I saw that there was a Comodo update available a couple of days ago, and I eagerly downloaded it expecting my shut down issues to instantly disappear. But no, the problem is still there and now I get spammy pop-up adverts on my desktop. THANKS FOR THAT.
Still, not complaining, free product etc… :-\
The spammy pop up is actually the Comodo Message Center. That can be enabled under More → Preferences → General.
Hiya all,
Back again, i did the recent update of CIS too and now AVG wont run. It stopped loading at boot.
I eventually uninstalled AVG, downloaded the latest version and during installation it tells me there are conflicts with CIS and until its removed it wont load ???
Edit by EricJH: reverted all bold to normal case
Back again. I’ve been tolerating intermittent shutdown problems the last few weeks but the recent major AVG update has made it every time I use the PC. It also locks the dilogue boxes in SmithMicro Poser8, making it unusable. >:( I’ve downgraded to CIS V4 and currently debating on another Firewall or using MS Security Essentials AV. Anyone having probs with XP SP3/CIS/MS AV combination?