Processor usage

My standalone Comodo Firewall is consuming 25% of the CPU power when computer is in wait mode (75%).
Something must be wrong here.

Something is wrong indeed. Can you show a screenshot of the D+ logs?

Do you have other security programs installed? Which ones run on demand and which ones run in the background?

Please make sure that there are no left overs of previously uninstalled security programs around. Not all uninstallers do a proper job. Left over applications, drivers or services can cause all sort of “interesting effects”.

Try using removal tools for those programs to remove them. Here is a list of removal tools for common av programs: ESET Knowledgebase .

I don’t have D+ in this standalone Firewall.
I had the Firewall installed, then I Internet Security above it, but I only choose the anti-virus install. Then I removed the Internet Security.
To be sure I removed the Firewall too, checked all traces where gone in the register and AppData folder.

I have Avast as anti-virus, disabled the background scans, but Comodo Firewall still consumed 25% CPU. I have no other background processes. Oh wait now the consumtion is about zero, maybe it needed a minute or two after the Avast background termination, I’m not sure further testing needs to be done.

I also have OpenDNS, DNScrypt, as a secure DNS, it runs as a standalone program and permissions are granted in the Firewall to go through.

Further testing Avast scans are on now, and Comodo is still down to about zero CPU power, and 25 Mb memory consumtion, but not so sure, it needs some time to adapt. When it’s comsuming 25% the memory consumtion is 65 Mb. But 25 Mb still seems high, as I have seen it comsuming 2-3 Mb when working as best.

Avast background on = high consumtion CPU for Comodo it seems after further testing.

Edit by Dennis2: I removed the spam like notification that your image was uploaded to a well known image sharing site

It might be a background process one of these that is causing this.

How can I configure Avast and Comodo, keep the best scans for each application. Having some background on in Avast and other in Comodo, although I still don’t understand because this is just a Firewall, could it be some settings in Monitoring Settings, like the Interprocess Memory Access… and all the other that don’t work well with Avast.

Do I understand the above correctly that, after several configurations, you did a clean install of Comodo Firewall only?

Avast is known to try to access CIS/CFP in memory intensively and that this hammering triggers the self protection which in turn uses a lot CPU cycles.

Add the Comodo installation folder to the exceptions of Avast and see if that does the trick.

I removed everything about Comodo and installed the Firewall only again.
The exception in Avast doesn’t seem to work.

Is there any exclusions I can do in Comodo regarding Avast?

I understand the changes to be made should take place in Comodo under Defense+ for Avast to get to the bottom with this, I will update what changes I did regarding Avast in there.

I am not an Avast user but have the following bookmarked that may be of help. Notice that they are for a previous version of Avast:;msg386783#msg386783

This is what I did, everything was ticked as ask, when I ticked the permissive, Comodo runs just fine, it also worked with the reject boxes. I haven’t read what they actually do. How do you recommend I give Avast the permission, I mean what should be under reject/permissive or what is recommended to use, permissive/reject: