I am comodo user since v2. When I upgraded to v3, I found that Defense+ is a really nice feature. (M)
All seem good, however when I try to build a dot net application, I noticed that the compilation was takes too long. (around 3-5 minutes while on normal it only takes less than 30 seconds). I did several test, when I instruct my Visual Studio to build my project, I noticed in the task manager that cmdagent.exe consume 30-70% CPU resources and in the “proactive defense” the number of files waiting for my review was growing from 0 to 9000++.
Yes of course, when doing compiling, many files were created or modified (especially library *.dll).
As far as I know, the only solution is to SHUT DOWN Defense+ permanently (require restart). But losing this feature on my PC is just…too much.
Are there any ways to tell defense+ not to monitor or logging any files which were created or modified in “C:\Windows\Microsoft.Net” ?
I have try to put everything under dot net framework as trusted group, but this doesn’t work. Still the firewall logged all created/changed files leading to high resources usage and slowing down compilation process.
Looks like the only solution is to shut down Defence+ permanently…
Have you try disabling defense+ before compiling your program? You know, turn off the alarm, do thing, turn alarm back on. When there are times that I need D+ out of the way, I just right click the tray icon → D+ —> Disable then when I am done, I’d turn to back to the mode I set earlier (usually clean PC)
Try putting Defense+ in training mode when you are compiling. This is also the gaming mode and should not give you any popups. (at least not many). Let us know if this helps
I don’t think he ( ecadre ) is talking about pop-ups… i seem to have a similar problem but in my case its with file shredding… defense+ registers every over-write as a pending file and with so many new files being created so quickly the software (comodo firewall ) cannot handle it and cmdagent rises to over 50% usage and the whole computer slows down and freezes at times… :THNK
BTW … in my case, Disabling defense+ does not help since the files still register as Pending… like ecadre said the only solution for me is permanently deactivating defense+ and restarting without it which is kind of sad (:SAD)
I just installed Comodo to try it out in place of ZoneAlarm and I’ve noticed the same thing. For the most part, Comodo doesn’t seem that much slower but using Visual Studio to develop web apps, it’s a killer. I’m developing a webapp using VS 2008 hosted via IIS (not the standalone server). VS will build the app quickly and get to the ‘succeeded’ msg. But then when I want to launch and debug the application, most times, there’s just the most absurdly long delay before the browser comes up. I can get up and go get a drink sometimes.
I exited comodo, problem didn’t go away. I noticed that cmdagent was still in my task list. So I finally got the task off and comodo removed from startup and VS is super fast again at starting my debug sessions. So it’s off for now while I research other options.
Actually I just registered to this forum to find out and post questions about Comodo Firewall issue with Visual Studio 2008 installation. But I think this thread is close enough so I decided to post here.
Seems like no solution yet to problems posted in this thread?
I was trying to install Microsoft VS 2008 days ago and it took forever before eventually failed to installed. Commenced the installation at 4PM and it still hasn’t finish next day in the morning, that was overnight. The task manager shows cmdagent consumes avg 50% CPU and my notebook became sluggish and not responsive. The installation mode didn’t help. I’ve tried various mode of D+: Clean PC, Training, Disabled, they didn’t help either. Even closing the CF didn’t cure the problem, the background service still running. I suspects this due to D+ logging every new files being copied and files modified by VS installer, and there were thousands of file, so no wonder.
Then I decided to uninstall CF, restart the machine, and then the VS 2008 installation took only about 30 minutes!
I also remember installing VS 2005 SP1 which took almost 1 hour. It was success though.
However I plan to reinstall CF again because aside of this logging/pending files issue, the features are great, but before that I just want to find solution of this particular issue. I wish there is an option to disable the monitoring of files during installation providing the user knows for sure that the software being installed is 100% safe and can be trusted.
Anyone know the best solution for this case, or will the next version of CF address this issue?
Well, I did… as I already mentioned in my previous post. And it didn’t help. I don’t think this mode suppress the pending files logging. Moreover the installation mode keeps asking to restore the previous mode every 5 minutes which is annoying because the slow installation requires overnight (and ended up failed)!
I agree most of typical software installations work fine or the performance is acceptable. But this VS 2008 installation with tremendous number of files being copied is a killer.
Perhaps I didn’t configure it right or overlooked something? And BTW I’m on laptop with WinXP Pro SP3/NTFS/1.5GB RAM/AMD Turion X2 TL56 FWIW.
What you can do is to set it to Installation Mode, start the VS2008 install and just leave it.
When the reminder appears, if you take no action, it assumes you want it left in installation mode and goes away for another 5 minutes. It will continue doing this for as long as you need.
Pending files is easily fixable by not using “clean pc mode”. I use safe mode for both the firewall and D+. I agree that the alert box popping up every 5 min or so is annoying but then again I have never installed anything that takes longer then 10 minutes. Even my games. Never had to install anything over night. How big is the file? You can always disable D+ then do your install then re enable it when you are done.
Thanks Ewen. Although the popup reminder is not the primary concern, it’s relieving to know that
That overnight installation is the due to the problem. Normal installation (I mean without CF installed) only needs approximately 30 minutes. Also I already did the Clean PC mode, Learning mode, and even Disable D+. I did all those and yet cmdagent still consumed +/- 50% CPU no matter what. Perhaps thats because I changed the settings in the middle of installation process, so it didn’t take affect immediately? Should I abort the installation on every D+ configuration changes and restart the installation again?
I don’t remember the disk space required by this installation but I think the individual file size is pretty small, the number of files is big nonetheless.
I’d like to take another chance and experimenting with various D+ settings. But right now I’m exhausted ;D
