If cmdagent.exe doesn’t have internet access, when opening (especially) an unsigned executable, cmdagent.exe tries to send about 6 requests to an external IP, with a delay between them of about 2 seconds. As a result, the opening of the app is delayed for about 12-15 seconds. This is very annoying. File Rating is turned off.
Consecutive openings of the app happens instantaneous; but after a couple of days, maybe a few restarts, the delay happens again.
Windows 10 x64
How you tried to resolve the problem - File Rating is turned off, but to no avail.
Hello velurrel, cmdagent.exe stands for COMODO Internet Security Agent, it a service from Comodo internet security and from my knowledge it monitors applications and checks them in CIS data base, i will forward this post so CIS moderators can help you further. This a Comodo Ice Dragon Topic (our browser).
All of the bugs I mentioned were encountered on a clean Windows, fresh-installed.
Including these 2, I tested separately, on a clean Windows virtual machine:
Version 10.0.2.6420 is working normally.
Oldest version to reproduce the issue - 10.1.0.6474. All version after it are affected.
It is not a bug when you block CIS process from functioning properly, and the apps you listed are in fact digitally signed with a digital signature, which means CIS was attempting to check the validity of the digital signature. If the application is not signed then this check does not happen, and this check is independent of file lookup so disabling file lookup will have no affect with certificate revocation checking.
You can’t it is hard-coded into CIS, you can try disabling Rate applications according to their vendor rating in file rating settings. Btw, this isn’t something special that only applies to CIS, Windows also does certificate revocation checks of signed applications when they are executed.
“you can try disabling Rate applications according to their vendor rating” - it was already disabled.
“Windows also does certificate revocation checks of signed applications when they are executed” - If you mean Windows Defender - maybe, It’s disabled on my machines.
Otherwise, Windows executables are also blocked by Comodo\Firewall, and no issues experienced.
I think Comodo should be flexible enough to allow to disable certificate revocation checking.
I’d like to add my experiences, too. I updated 5 computers for my family from CIS 10.0.1.6420 to the latest CIS 188.8.131.5236.
Every computer shows the identic symptoms. Starting any app takes now 3 or more seconds now. Starting Firefox, Chrome or WinRAR takes even longer. For example, right-click on a RAR archive and selecting “extract here” takes over 10 seconds till WinRAR starts extracting.
Also tested on fresh installed Win10 1909 x64 and Win10 2004 x64. No other apps installed. Tried to start the following portable apps: Firefox, Chrome, Media Player Classic, Media Player Black Edition, VLC Media Player, WinRAR, 7-Zip, Aida64, Teamviewer, NirLauncher. It took moren than 3 seconds or longer until any of those apps started. With CIS 10.0.1.6420 this behaviour never happened. Apps started right away.
Please fix this or give us at least the option to deactivate the Comodo check running in the background.
Is there any security reason to keep on using CIS 10.0.1.6420 for my family? We only use the Firewall and HIPS.
Maybe stop blocking network access for cmdagent and you wouldn’t have such issues. There is no reason to block OSCP revocation checking, even Windows performs this check when launching digitally signed applications.
“Maybe stop blocking network access for cmdagent and you wouldn’t have such issues” - I tested with a slow network. It also introduces some significant delay (because cmdagent waits for a response). Which makes this bug more serious than I thought.
“even Windows performs this check” - Windows (svchost, explorer.exe, etc.) is also blocked, with comodo firewall. Such delays don’t occur.
This bug is more bad than initially thought - if the apps are opened from start menu, the whole taskbar, start menu are blocked/frozen (Windows 10 1903). Windows 10 1909 restarts the taskbar. (I’m not sure if 1909 has taskbar hosted in a separate process, or it kills and starts explorer.exe, which is worse).