Updating delay

I have read that when you first turn your computer on is when your most open to virus’s and malware.
I use eset on another computer and when I turn it on as it boots it’s automacticly updating the anti-virus,
is there a way to set Comodo up to do this ?

CIS updates 2 or 3 minutes after Windows reaches the desktop. At what point does Eset start updating?

If Eset is updating as your computer is starting up, it is slowing down your startup.

But no, as long as protection is loaded at the kernel level, your system isn’t really at any greater risk than any other time.

And surely Eset can’t get its updated definitions in place before windows loads. :wink:

Comodo should have the way user change update secheduler. Such as when computer idle or by time.
However I never feel Comodo update makes my computer and internet connection slower. :slight_smile:

Yes, it could definitely use a bit more flexibility when it comes to updating.

I never did until I upgraded to 3.12. Now I get massive disk I/O bogs that make my system unusable for 5 or so minutes. And my machine is fairly powerful.

ESET NOD32 delayed Windows Start-up so badly only 2 or 3 of my icons appeared in the notification tray.

I always got the clock, but volume control and battery charge and safely remove took it in turns.

There was no problem with a USB powered Thomson ST330 modem that had to get a fresh dynamic IP address upon start-up - there was no Internet and no downloads / updates until after Windows had settled and put the icons in the tray.

The problem came with an upgrade to a mains powered Always-On Router that allowed ESET to update instantly.

The problem was MOSTLY resolved by cancelling the ESET GUI start-up and instead launching my own start-up script which delayed the GUI until the tray was updated.
Delaying the GUI delayed when it did the update - but the ESET kernel was still protecting me with yesterday’s signatures, and I was only vulnerable to last-night’s “day zero” exploits for 15 seconds.

The last bit of the problem was resolved by similarly delaying the Comodo GUI - I found that even with cfp.exe not running the Comodo Kernel still obeyed the rules and blocked what was not allowed.

I have now replaced ESET NOD32 and Comodo 3.5 with the full Comodo CIS 3.12,
and my tray still gets all the icons.

It is possible I no longer need to delay the cfp.exe start-up, BUT

  1. I do not have time to investigate;
  2. It probably takes about 20% of the CPU initially and I am happy with 80% of the CPU for my own use,
    I would be less happy with 100% of the CPU if the initial update added to an existing Windows start-up of 95% and delayed my launching of Firefox by a further 20 seconds.


Since XP SP2, if I recall things correctly, firewalls get started very early in the boot process to better protect the computer

Remember that CIS uses the Default Deny principle, the buffer overflow protection and that the firewall starts early in the boot process. So if there is something new it should be blocked by the default deny or the BO protection.

To be absolutely sure set CIS to “Block all unknown requests if the application is cllosed” (Defense + → Advanced → Defense + settings).

Thanks for the advice. Now implemented