NOD32 high memory usage with COMODO updates? (not cmdagent)

I use ESET NOD32 Antivirus and COMODO Firewall.

Recently, every few days, there will be a moment in the day when suddenly my computer will start working hard. Things will freeze as it’s working, for about 5 - 10 minutes, and stay frozen through a silent lull of 5 - 10 minutes, followed by a few more minutes of working, then it’s done.

Afterwards, the VM size of ESET (ekrn.exe) will be around 350,000k (normally it’s 83,000k).

I’ve noticed the last couple of times that, after I’ve restarted my computer, COMODO will immediately update. Also, when the whole working/freezing thing finishes, COMODO will tell me it’s isolated steamerrorreporter.exe (if I had Steam open). Doesn’t matter if I’ve previously told it to not isolate it again, next time the above happens it’ll go the same way.

One theory would be that both NOD32 and COMODO are updating at the same time, causing a fuss, but I don’t see any option to decide when either looks for updates anyway.

Any theories?

P.S. It’s not the dastardly COMODO cmdagent problem.

What Comodo update are you referring to? Program update which is done by cfpupdat.exe or AV update which is handled by cmdagent.exe?

However you state you only use Comodo Firewall so that would mean it would be cfpupdat.exe. CIS waits with updating its av definitions a bit so it won’t update when windows and applications are starting during boot time.

It looks more like a possible compatibility issue between NOD and Comodo Firewall. Do you have D+ enabled?

Try this turn off eset self protection see if this lowers ekrn did for me. Then protect eset via cis forgot how to do this part as I no longer use eset.

Yes, both D+ and Firewall is on Safe Mode.

I’ll try that next time.

I temporarily disabled protection but that did not bring the memory down, if that’s what you meant (I’m guessing not), but then even if it did it still wouldn’t solve the problem. Are you saying you had this same problem?

I’m not using CIS, and have no desire to as long as the cmdagent problem exists. Considering it has been around for years, chances of me using it again are not high.