i found that avast has detected (cmdagent.exe)the process of comodo firewall as virus(win32:fakevimes-b[trj]) for a few months?what’s wroung with avast?why this false positive still hasn’t been fixed?anybody has a reply for that?
Because avast! is detecting uncrypted virus signatures in Comodo’s memory. So it’s not really a false positive, but more a conflict of two antiviruses.
but how should we solve this problem???
I’d say either ignore the results from the mentioned process, or don’t use the memory scan… that’s about it, I’m afraid.
Hi,
I use avast free in conjunction with Comodo firewall (without Antivirus)and it picks up cmdagent.exe
Why would it install signatures if they will never be updated because the corresponding component is not installed?
Just I thought (sorry for busting in the conversation)
I too have been baffled by this for quite some time.
Regards,
Hellion
You will have to ask comodo that question, as igor said you can untick the scan memory box from your custom scans or simply use the default full and quick scans.
Hi CraigB,
I have opened a thread in “Bug reports” over at Comodo,
Here is the link:
https://forums.comodo.com/bug-reports-cis/avast-comodo-and-cmdagentexe-t75271.0.html
Thanks for the help,
Hellion
Your welcome, i didnt say anything different really from what igor said just in different words 
Well, I have to admit that I didn’t check the particular signature or process (not having Comodo installed), so I’m not 100% sure about it - but I find it quite likely; if the memory scan detects something in another AV’s memory, it’s usually the case.
Hi Igor,
I understand.
I will wait and see Comodo’s response
Regards,
Hellion
Btw, I don’t think the memory scan is very useful; the existing signatures are mostly aimed at files, not memory - so I believe you won’t really lose anything by replacing the memory scan by something else (such as auto-start programs).
Hi Igor,
I have 4 Terra-bytes of data so doing a full scan takes about a day for me so what I do is I create a custom scan with Memory + Auto Start + Rootkit (full) and let that run on a schedule.
It doesn’t really bother me that bad, but I know it shouldn’t be happening.
Regards,
Hellion
I’m not saying you should make a full scan - just that for a quick scan, Auto-Start should be quite enough.
The memory scan, even if the necessary signatures were in the virus database, is unreliable by default - virus signatures may be found in memory of a browser if it downloaded some, possibly even blocked, malware in the past, file managers may have some signatures in their memory if you moved some strange files in the past, etc.
I’ve had them installed, but did not detect virus in Comodo …
Have you made sure to exclude Comodo in Avast in both the program Settings and in the File System Shield settings?
Hi Corsair,
It’s not really a problem as this is only an issue encountered with memory scans and even after detection there is nothing you can do. (there is no option of deleting/Quarantining the detection)
I did try your suggestion now, I added the exclusions for both manual/auto scans and File system Shield, But this had no effect.
Regards,
Hellion
Just a query:
Do your avast! settings and file system shield exclusions look like the attachments below?
Hi Corsair,
Yes, they look EXACTLY like that.
It’s very hard to screw something like that up
Regards,
Hellion
Excluding comodo in avast won’t make a difference in this case as:
a) this isn’t an alert on any comodo file
b) is in memory, not a file or comodo location
c) whilst you can exclude a file from being scanned, you can’t exclude its actions, e.g. in this case the insertion of unencrypted signatures into memory.
Well, I believe you probably could exclude the memory detection, but you’d need an advanced magic for that 
Let me know what exactly the detection says in the first column, I’ll try to make the exclusion mask.