Hey folks, whats Comodo got in it, that Avast (I’m using Home), doesnt like? Comodo Internet security isnt even installed on this (but I’ve got the latest install files). If I go to the Comodo folder, (and if Avast is running), Avast freezes the system for a few secs (it must be scanning this folder). Then I can click on whatever. Now, I’ve noticed that not only does Avast do this (freeze), it’ll will also crash explorer.exe (If I open the Comodo folder). It did this previously (with previous versions of Avast). BUT, its the 1st time, I’ve noticed / seen it crash explorer.exe (the shell). I’m usng XP Pro x64.
Avast doesnt crash when I open any other folder (there’s 63 folders (in the same folder the Comodo folder is in).
There are issues. I think consensus would be run comodo firewall as standalone with Avast.
From what I recall full CIS suite does not sit well with Avast and vice versa. If you go to general topics and search keyword ‘comodo’, there are a lot of entries. Likely someone from the forum will reply and the issues will be aired again to keep things up to date. I think also may have to configure in comodo frewall control set for comodo firewall to overrule one of avast’s responsibilities, but I’m not sure because I cannot find the relevant post. Likely someone will reply.
I dont use any comodo. But I can almost say for sure - rule out full CIS and Avast running error-free together on same computer.
Edit: Also - XP Pro x64.
Many security agencies have yet to accommodate wares to 64bit the way they have for 32bit.
My 64bit is gathering cobwebs in storage. I think time to set it up running again.
Like I said, its Comodo’s install file/s, Comodo ISN’T installed (So, I’m not running Comodo’s firewall, or AV). So, thats not the issue, just opening the comodo folder (that the install files are in), freezes the system and crashes the shell. (If Avast is running in the background).
What? Just having the install file in a folder? I dont think so. You dont have to do anything for it to crash. Just opening the folder (like I said), crashes explorer.exe. Like I said (for the 2nd time). I’m not even touching the install file / I’m not double clicking on it. So, I’m not installing it.
What if you disable avast! resident protection (or just the Standard Shield) beforehand? (and, e.g. try to display the properties of the mentioned executable)
Well its fine, if I kill Standard shield, since it disables Avast. What makes Comodo so special from any other file on the hdd? lol. There’s 20000+ files on the hdd, and the comodo folder is the only folder that makes the shell crash (If Avast is running).
So, Comodo is not installed, but you’re keep on mentioning “Comodo folder”. Do you mean folder where Comodo installer is located? Because if that’s the case, you have to thank Comodo team for creating the dumbest installer ever. Whole installer is packed with a runtime packer. If your system is low end one, i can assume the system will lockup or crash.
Thats right the folder. I wouldnt call this PC low end (XP Pro x64, 6 GB ram, 250 GB hdd, dual core 2.5). It DOESN’T crash the system (as in BSOD). It crashes the shell / explorer.exe. If I open the folder the Comodo installer is in (while Avast is running)
Is it a 64bit installer, or 32bit one?
Not that the 64bit one wasn’t rather ugly, but it’s not packed - at least when I checked last time (as there’s no 64bit PECompact at the moment, I assume)
I went to comodo website. They seem to have separated packages 64bit and 32bit, but too big to bother downloading to check. Is the version you have of comodo dated earlier?
I can give you a local connect if this really is important. As I say I am looking to set up my 64 xp pro again soon, so may provide some useful thoughts for me. you can email through Avast ‘My Messages’ on menu bar - search my user name and send your email address or some kind of connect in Auck.
Hmm well I dont really care what their SSL certs do. Or who uses what / when and how. Since I dont use it, and dont intend to use it. Thats not what the topic is about, or what I’m trying to find out. I’ll check out the comodo forum and either post the same ? Or see if someone has already posted a similar prob
Well its not the end of the world, if I cant fix it. Its just annoying that noone at Avast seems to know WHY it happens. I dont think anyone in Auckland will know WHY this happens either, or HOW to fix it. I’ll check out the comodo forum. As stated in my previous post. It also used to happen in 32 bit (but I didnt see it crash the shell), so its probably not a x64 problem.
What do you mean properties?? As I posted earlier, ones the 32 bit version, the other is the 64 bit version. Of the latest version of Comodo internet security. There’s only 2 files in the comodo folder obviously (x86 and x64)