Thank you. You experience confirms mine except I managed to make SBIE work with CF.I tested COMODO with EMET, MBAE, and HMPA. At that time, they all worked fine with it. If you have a lot of vulnerable softs or are just plain paranoid about exploits, then any one of them should still work fine.
COMODO worked fine with Malwarebytes, but I never tested it with Zemana. Theoretically, Zemana should work fine along side COMODO too.
I could never get Sandboxie to work well along side COMODO since version 6.
I tested COMODO with NVT ERP and Voodooshield and both worked fine - but I removed them because they are not needed since COMODO has HIPS and the sandbox can be set to block any Unrecognized applications.
In default settings D+ is like anti-exec + AutoSandbox I prefer to enable HIPS as it gives more control over the system. And yes, FW in ask mode is safer. Though these tweaks make CIS more vociferous.My opinion is based on Comodo default settings with little tweaks (slight tweaks). Coz for me default settings are good with little tweak. And I never faced any major or unacceptable prob with Comodo with default settings.
Cant comment on custom settings, HIPS, etc... as mentioned above I have used only default settings with little tweaks & no probs.
Some say Comodo default is not good. I dont agree, Comodo default provides strong protection with good usability. Default is strong And not maximum protection.
I suggest default settings with little tweaks like Firewall set to ask, you may want to set sandbox rules from "Internet" to "Any", etc...
But as mentioned above, you need to know how CIS works.
Actually ESET support is right unless you have direct inconveniences of such RAM usage. If you PC goes slow for instance.High RAM usage, particularly ekrn.exe which averaged around 150 MB for me but often went much higher....
ESET support forums staff say 200 MB is quite acceptable, but not for me.