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...
Printable View
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...
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.Quote:
I do remember the installer asking me if I wanted to do a scan to make sure my PC was clean
During searching, I've noticed, that also CA Antivirus uses some cavscan.dll file.
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.
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.
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...
We may actually never know. You're very right in your next sentences.Quote:
Obviously something is going on but what, I don't know.
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.
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.
Now that is enough to make one scream. But I like the final, anyway I hope it is, fix.