I just noticed that the excluding AvastSvc.exe from the “Detect shellcode injections” did not provide a solution and the problem is still there! 
:-[ :-\ 
I think you should reinstall CIS by first downloading CIS 5.3 32bit/64bit and CIS clean up tool. Now you uninstall the cis that you use and use CIS clean up tool in safe mode as admin. After that you install CIS (what components you install is up to you) as admin and add AvastSvc.exe in Detect shellcode injections.
I think this will stop the high cpu usage… at least I hope
Regards,
Valentin N
Thnx for the reply Valentin, but I already have tried that specific solution as you mentioned in the past (when the problem first appeared. So I don’t think that it will give a solution. Ofcourse I am gonna try it, but I sincerely have my doubts. 
Don’t loose hope. After you have tired tell me if that helps.
May I ask what you had before (that would be before CIS and Avast)?
Regards,
Valentin N
I been using Comodo for a loooooong time. Before that I had Outpost Firewall Pro and Kaspersky AV. But both became to bloated and usually that means the quality diminishes (like Comodo now? 
Thank God you can still choose firewall only ;))
I just dl-ed the lastest version of the Firewall only application. Let’s see if it’ll work 
CIS 5 is good and configurable. I have also tried the combo that you know have problem with but I have never got any problem. Have you cleaned the rest from Outpost’s firewall and Kaspersky’s AV?
Regards,
Valentin N
avast is also giving high CPU usage in some scenarios.
Maybe it is the culprit and not Comodo Firewall…
For instance: High CPU usage for AvastSvc.exe
Well Tech, whenever I see the spike, it is cfp.exe that is at 50 % CPU and not Avast. I deïnstalled Comodo and with only Avast running I have no CPU spikes, so it’s safe to say that it’s not Avast in this case.
However, I installed the latest version (clean install) and at first I still had the CPU spikes. But then I removed the earlier setting of excluding AvastSvc.exe from the “Detect shellcode injections” becuz I noticed if I used the Fiorewall configuration I had no spikes. When I used my (exported) pro-active defense config, they were back, untill I removed the exclusion from the “Detect shellcode injections”.
For now, it seems to be back to okay. I’ll monitor it for a few days and let you know later on if the problem is really gone.
Those have never been installed on my current OS (I am using Win7 now for almost a year now, before that I used XP). Like I said I been using Comodo and Avast (and Avira AV before that) for a loooong time. So there are no remnants of Kaspersky, Avira or Outpost present in this current OS.
I am running out of ideas. Give my suggestion a try and see if it helps
Take care
Regards,
Valentin N
;D :azn:
it could be related to the Avast behavior shield not playing nice with Comodo.
Maybe. try to disable it or uninstall it. I don’t know how Behavior blockers works but if they are similare to HIPS then it’s good if it’s disabled.
Regards,
Valentin N
HIPS is not Behavior Shield.
Behavior Shields analyses the actions of the programs/files based on rules, activities, signatures. Right now avast BeS is on “passive” mode (allow all). It will be active on version 6 or before. Then it will warn (block) the infected actions.
HIPS monitors all actions, clean or not, and depending on the settings level, warn all of them.
thanks for the explanation Tech :-TU.
Regards,
Valentin N
Well, it seems the problem still persists, although on a lower scale. It’s not spiking constantly, but every now and then it still does. So I decided to turn of Defense+ altogether as someone suggested in this thread before, and lo and behold, the problem is gone. Now, I myself do not really need the Defense+ feature as I got my PC pretty well secured in various ways, but it’s not really a solution to turn it off I would imagine. Hopefully in the near future this can be sorted out and solved. As for now, I’ll just have to do without Defense+ I guess.
I do think it’s a problem that really resides within Comodo and not so much Avast, as I have read similar problems from other users who use totally different AV software (I’ve seen someone mention Kaspersky and NOD32 for example).
Hopefully the Comodo devs will investigate and try to resolve it.
I am truly sorry that my suggestion hasn’t helped you I don’t know if I have given you this tip but look if windows defender is on. if it is turn it off.
Regards,
Valentin N
I have Windows Defender, but it’s not really in an active state. For instance, real time protection is shut off, so it only does manual scans. I don’t think Defender is the culprit. Funny thing is, if I disable Defense+ there’s no problem, if I enable it I get spikes every now and then on cfp.exe. I seriously think this should be looked into on the side of Comodo itself. With all the info that already has been given and no other software going haywire except Comodo I think the devs should start to look into the fact that this indeed is a problem of Comodo itself, although they might find it hard to admit cuz no one who works for Comodo is going against it’s own software.
Also take the fact into consideration that this problem has started to emerge as of version 5. With version 4 everything was okay and this particular problem did not exist. Add to that there are users also experiencing this problem who run other AV software then Avast, and taken into account that everything that’s possible to exclude certain factors on both Comodo and Avast to solve the problem (which in some cases worked for a few users and in other cases did not)… well add that all up and you will come to a certain conclusion as where the problem really might reside.
Don’t get me wrong, I don’t want to hammer down the Comodo software as I think it’s the best firewall out there, hence I still use it, but I just tell it like I see it. If I am wrong, then I am wrong, but it’s at least something to take into consideration as the problems still occurs for quite a lotta people as of the start of the implementation of v5 of Comodo.
I don’t know if it has been mentioned yet. At the risk of repeating it. Look under View Defense Events and see if Avast is continuously trying to access cmdagent.exe in memory; then the self protect of CIS will start eating cpu like crazy.
When that is the case add the CIS installation folder to the Avast Exclusions.
Well I’m getting high cpu spikes with this again, despite having previously “solved” the issue and my patience has finally ran out with Comodo 5. Anyone know where I can download version 4 from please?