Probable Conflict between Avast! 6.0.1125 and Comodo Firewall 5.4

You mean, if Comodo’s HIPS (D+) slows your system…?
No, it doesn’t.

You mean, if Comodo’s HIPS (D+) slows your system…?
No, it doesn’t.
[/quote]
That’s what I wanted to know. Thanks. :slight_smile:

You’re welcome…!

I know an easy fix…Uninstall Comodo, and use Windows FW.

Whom do you address…?

Nobody specific, just what I would do. :slight_smile:

SpeedyPC, have any suggestions for MBAM Pro that is loading 6-7 unencrypted signatures into memory? At least that is what Avast’s memory scanner is saying.

It is a bit odd that Avast’s memory scanner is not only flaging Comodo’s cmdagent.exe but also MBAM’s mbamservice.exe.

I am also curious as to why you are recommending that all Defense+ cloud settings be turned off. Know something amiss in that area?

BTW - cmdagent.exe is loading snxhk64.dll which is an Avast .dll. I was floored when I saw that. More so since Comodo really protects the hell out of cmdagent.exe.

The old Comodo FW v3.14 doesn’t work on Win7 just keep this in mind :wink:

@DonZ63 I cannot answer your question about MBAM Pro I only used the free version, I’m also aware that has extra features in the Pro version so I cannot fully answer your question along side with Comodo FW.

The Comodo FW cloud feature is a bit over kill when Avast free has so many extra feature that protecting your PC, Comodo cloud can cause to many FP if your not very careful with it. I also have other software for On-demand on my PC and I also have CCE :wink: All I’m saying is with all the extra security feature in Comodo FW is over killed while Avast free is almost doing the same the job, so why add more when you over killed the PC can create a lot problems. The only way to balance this problem out you either remove Avast to have all the CIS feature, and if you want to used Avast than cut down the feature running inside Comodo FW you can’t have both ways.

DonZ63 if you are getting memory detections about malwarebytes then you must be running a custom scan with memory scan included, as this scan tends to delve deeper into memory than the normal scans which is why your picking up MBAM signitures, there is no way round it but to either untick the memory scan section or to stick to the normal scans, or simply just ignore the detections of MBAM as there harmless anyway.

It also works on W7.

Are you 100% sure ??? I’m not trying to be a wise guy :-\

Yes. 100% :wink:

DonZ63 if you are getting memory detections about malwarebytes then you must be running a custom scan with memory scan included, as this scan tends to delve deeper into memory than the normal scans which is why your picking up MBAM signitures, there is no way round it but to either untick the memory scan section or to stick to the normal scans, or simply just ignore the detections of MBAM as there harmless anyway.

We are having a debate over in the Comodo firewall forum on this issue.

Individuals with identical security setups; Comodo ver 5.x firewall and Defense+ with Avast 6.x with web shield active are getting different results when Avast memory scanner is run. Most get the FakeVimes signature found result. However, others do not. This has more than a few people concerned. Note than none of these individuals every had Comodo’s AV installed including yours truly.

Comodo has admitted that Defense+ does do process hook injection to minimize Defense+ alerts. This however does not explain why Avast memory scanner is finding unencrypted signatures.

Then there is the MBAM Pro issue in the same area. As far as I know MBAM Pro does not do any process hook injection.

I dont know that much about comodo as i dont use it but i do know that defence + is not needed when running avast.
The issue with MBAM Pro signitures being discovered in memory by avast has been mentioned on this forum several times in the past and the only thing you can do is to not include the memory scan when running custom scans or ignore it as i have already mentioned there harmless.

Well… :-X :wink:

You are running quite an old version of comodo Asyn so maybe different to the newer version, all i see lately is conflict between avast and the new version of comodo, like i said i dont use it but there is something going on and defence + seems to be the cause with a few people.
I still dont think D+ is needed though ??? :-\

No problem with your opinion craig. :slight_smile: