I have been using Sunbelt’s Vipre Antivirus and have been extremely happy with it. A couple of weeks ago I installed CIS ( firewall only with Defense +). Ever since then Vipre is unable to finish a scan. Previously a quick scan took 5 minutes and a deep scan 80 minutes. A quick scan will run for hours now and still never finish. After corresponding with Vipre’s support people they suggested uninstalling Defense +. After doing that all scans will finish in the proper time.
Sunbelt says they are aware of a conflict with Comodo but have been unable to get any assistance from Comodo’s developers as of yet.
I am posting this in hopes of bringing it to someones’ attention who is able to do something about it. I really want to be able to use Defence + on my computer.
Hello, Is there anything in the defensE+ events?
Comodo → Defense+ → Events
Well there is nothing now because I had to reinstall the Firewall without Defense +. I couldn’t tell you if there was before. Sorry.
Any idea if this is being looked at?
Have you tried to add Defense+ policy to treat Sunbelt’s AV executables as Safe?
Have you also tried just to set Defense+ to disabled mode before scanning(and did it help)?
Yes, I tried both of those and found no improvement.
Hi,
Pls try running the Vipre scan after exiting CIS from system tray.
Regards,
Vicky.
I tried that with the same results.
Here is what I posted on the Vipre support site:
I have been using Vipre for about a month and was very happy with it. I recently upgraded my Comodo firewall to Comodo Internet Security. Now I can’t get Vipre to complete a scan. A quick scan that took 5 minutes will run for hours and never get past 60%. I have added Vipre to Comodos safe file list, I have disabled Comodos defence +(hips), even exited the firewall with the same results. I saw on another thread here that I should disable rootkit scanning to improve performance, but the quick scan never got past 8%. Any ideas what I should try next?
And a couple replies:
It sounds like this is a problem caused by running VIPRE alongside Comodo. We are working on this problem but have gotten no response from COMODO.
There is a known conflict between VIPRE and Comodo. I believe people have been able to get them working together correctly by not installing the anti-spyware part of Comodo.
Hi again
I’ve reproduced the issue. Actually Vipre hangs on trying to scan cfp.exe in memory. The problem could be resolved with adding cfp.exe to exclusion list but unfortunately Vipre scans the file anyway.
The only workaround I’ve found is to exit cfp.exe while scanning with Vipre. Or using some other anti-virus
As CIS works well with VIPRE, I assume that it’s VIPRE problem with scanning protected files in memory. Anyway it would be easier for VIPRE developers to debug their scanner and see what happens during scanning CFP.exe.
Thanks for your efforts, I will forward this on to Vipre.
Same problem with VIPRE and Comodo Firewall where VIPRE freezes upon scan. Still no solution even after unhooking PC from internet and totally disabling the Comodo Firewall and Defense+ before running scan. [I did not install the Comodo anti-virus.] I have the most recent version of VIPRE v3 (Purchased on Black Friday w/discount) and also installed Comodo for first time on Windows XP, SP3. I submitted a tech report to Sunbelt via their WEB today (prior to submitting this post.) so have not yet received a reply. Has anyone totally removed Comodo to see if that resolves the problem? That will be my next step, but I am reluctant to do that since I would be left without a firewall. I will check back later for any further updates to this forum.
Here is my Comodo LOG (I’m not sure what, if anything, this shows):
Date/Time Application Action Target
11/28/2008 9:17:02 AM C:\WINDOWS\system32\drwtsn32.exe Access Memory C:\Program Files\COMODO\COMODO Internet Security\cmdagent.exe
11/28/2008 10:37:08 AM C:\Program Files\Sunbelt Software\VIPRE\sbamui.exe Access Memory C:\Program Files\COMODO\COMODO Internet Security\cmdagent.exe
11/28/2008 10:37:13 AM C:\Program Files\Sunbelt Software\VIPRE\sbamui.exe Access Memory C:\Program Files\COMODO\COMODO Internet Security\cfp.exe
11/28/2008 10:37:13 AM C:\Program Files\Sunbelt Software\VIPRE\sbamui.exe Access Memory C:\Program Files\COMODO\COMODO Internet Security\cmdagent.exe
11/28/2008 10:37:13 AM C:\Program Files\Sunbelt Software\VIPRE\sbamui.exe Access Memory C:\Program Files\COMODO\COMODO Internet Security\cmdagent.exe
11/28/2008 10:37:44 AM C:\Program Files\Sunbelt Software\VIPRE\sbamui.exe Access Memory C:\Program Files\COMODO\COMODO Internet Security\cmdagent.exe
11/28/2008 4:13:20 PM C:\Program Files\COMODO\COMODO Internet Security\cfp.exe Changes Defense+ Mode Training Mode
11/29/2008 7:37:00 PM C:\Program Files\COMODO\COMODO Internet Security\cfp.exe Changes Defense+ Mode Disabled
11/29/2008 9:19:31 PM C:\Program Files\COMODO\COMODO Internet Security\cfp.exe Changes Defense+ Mode Safe Mode
11/29/2008 9:19:54 PM C:\Program Files\COMODO\COMODO Internet Security\cfp.exe Changes Defense+ Mode Training Mode
11/29/2008 11:23:14 PM C:\Program Files\COMODO\COMODO Internet Security\cfp.exe Changes Defense+ Mode Disabled
I had to uninstall CIS and than reinstall without Defense +. It wasn’t enough to just disable it. It works fine for me now. Vipre has realtime protection which I think is basically the same as Defense +.
I love Vipre so it is not an option for me to remove it.
Is this the fix I am looking for?
'FIXED! Defense+ does not prevent process access in memory"
Everytime I perform scans with my security apps, I disable D+. You could try that, or does VIPRE also hangs while proactivily scanning (real time protection)?
I also don’t know if it has anything to do with it, but I do remember that VIPRE and Comodo Memory Firewall also do not get along. I do not remember any issues with CFP, though. But since we’re talking about CIS, well, I honestly can’t say much.
Best regards
If you read my previous posts, disabling it wasn’t enough - I had to completely uninstall and reinstall without defense+.
I just recieved a message that Vipre and Comodo are trying to resolve the conflict.
Yes, you have. My bad. 
Any chance this conflict will get fixed in the new version?
Melih, or any devs know the answer to this?
Anybody?
The new version came out today. Have you tried it?