comodo firewall

[frebo]

i have an update to my comodo firewall tonight

[stevejr]

Me too...took maybe 10 minutes or a little longer on broadband...not quite sure how long...seems to working just fine...no noticeable differences.

[frebo]

took 21 minutes for me on broadband

[HAN]

What version number does it show now? I update manually and AFAIK, the only way to manually update now is to use the Comodo Internet Security installer and decline the antivirus portion (I also decline the SafeSurf toolbar stuff.)

[frebo]

version 3.5.54375.427 it didnt download anything else that i could find what i did was check for updates in comodo and it downloaded it, on my other pc it alerted me that there was a update available, it didnt offer the antivirus or anything else, not that i would have

[Broni]

I update manually
I didn't receive any notification, but after seeing this thread, I opened Comodo, went Miscellaneous>Check for updates, and it updated.

[HAN]

version 3.5.54375.427
That's the latest!

I just have to update manually when I can get the file downloaded somewhere other than at home. At home, it would take forever to download a new version of CFP...

[fink]

Tried the (auto) update. Installed ok but slowed my computer down to a crawl (an opiated crawl at that). Programs would take minutes to open and the primary firewall process was stuck at nearly 100% CPU usage.

I rebooted a couple of times just to see if that made a difference.. it didn't so I'm back to version 3.0.x

[Broni]

fink
That's the very first, I ever heard.
Interesting.

[HAN]

Yeah, I haven't had any issues either. My Dell flies on CFP 3.5...

[Broni]

fink's computer is messed up...
fink's computer is messed up...
fink's computer is messed up...

....just kidding :D

[fink]

I had a look at the Comodo program folders and there were a number of exe's there that weren't before (and aren't now) with the 3.0 version.

By the names of them, at least one of them certainly looked like an a/v scanner. Maybe one of you can look in the Comodo firewall folder and see if there's one listed there as something like "cavscan.exe". I don't remember exactly what it was but I'm wondering if there was a scanner running in the background conflicting with NOD32.

I'll try the install again some time when I have more control over it and make sure it doesn't install part or all of the security suite.

[HAN]

Hmm... I'm running NOD32 ver 3 with CFP 3.5 and it's fine. One difference in my setup is that I didn't auto update. I uninstalled CFP 3.0, rebooted and then installed CIS 3.5 (and made sure the AV & Safe Surf were unchecked.) As I noted, the PC runs very well. Boots nearly as fast as it did out of the box with nothing on it...

[Broni]

cavscan.exe is present in my Comodo (firewall only) folder.

[Broni]

fink
I'd post in Comodo forum: https://forums.comodo.com/index.php
They're pretty quick in responding.
I also found some threads there concerning NOD32: https://forums.comodo.com/index.php?action=search2

[HAN]

cavscan is also in my version 3.5 folder too. I'm sure that the AV is not active but I do remember the installer asking me if I wanted to do a scan to make sure my PC was clean. So having the scanner on board does appear to be normal...

[Broni]

I do remember the installer asking me if I wanted to do a scan to make sure my PC was clean
Same here. I'm not 100% sure what is the purpose of it (making sure, that Comodo is installed in clean environment?), but I'm pretty sure, that scan comes up only once, during installation. Maybe cavscan.exe is needed for that scan.
During searching, I've noticed, that also CA Antivirus uses some cavscan.dll file.

[fink]

There are a number of questions regarding similar issues... mainly whether the a/v is included in the autoupdate and if it's installed along with the firewall and how to stop it from doing so.

Despite some input from the pros over there saying there should not be any problems and there should be an opt out switch on install for the a/v portion there's also some users who suggest that a clean install would be best.

I'll try that at some point when I have some time.

They also say that those cavscan files seem to be there for the initial scan on install even if you opt out of the a/v... that's still under some discussion though. There was also a folder of a/v dat files in the Comodo folders in my case so I think the a/v was at least partly active and creating a conflict with NOD32.

[fink]

So, I uninstalled ver 3.0, installed 3.5, deselected the a/v and refused the a/v scan, imported my original settings and the same thing happened.. a near complete freeze of my entire computer. I'm not going to waste any more time on this.

I'm happy with version 3.0 and I've got that one back up and running. Confirms what I've always thought.. just because something's newer it does'nt mean it's better.

[HAN]

Very odd! Considering I also run NOD32 and mine runs just peachy. Obviously something is going on but what, I don't know.

Reminds me of my NIS 2009 tests. One PC ran (and still runs) great on it and the other would hang at the opening desktop from boot. The PC that had the issue with NIS is the one that runs great on NOD32 and CFP 3.5...

[Broni]

Obviously something is going on but what, I don't know.
We may actually never know. You're very right in your next sentences.
Basically, there are not two identical machines, even, if they may look like having same settings, same programs, specs, etc.
There are so many variables, that it's almost like fingerprints from two different persons.

[fink]

I finally was able to update to the latest version of Comodo. I dropped NOD32 and installed Avast because NOD missed a drive-by install of a web based trojan. My subscription was nearly up anyway so I'm going back to Avast on my main PC for now.

In NOD's defence it was a slightly older version so I can't totally hold it responsible for missing the drive-by but I'm not inclined to pay for the latest one when I know that Avast will do just fine for free.

I have no idea why NOD wasn't working well with the latest Comodo upgrade though and that's another reason I was reluctant to continue using it but it did confirm my thoughts as to why Comodo wasn't getting along with my PC after the initial upgrade.

[Train]

Now that is enough to make one scream. But I like the final, anyway I hope it is, fix.