Mr_Burnz

Sorry I meant to also add if Comodo's devs can also figure it out, it takes two to tango

Nps pbust, glad I could help, as I know how frustrating it can be when things don't work as you want them to. Pretty much every conflict I've had between CIS and MBAE since the update can be resolved by that method, just adding the programs installation folder to the Detect shellcode injections exclusion list in CIS, I found another conflict as well, with DNSCrypt, if you add that to the MBAE shields list, the same thing happens, you get the Anti-HeapSpraying Enforcement (this thing loves popping up it would seem, LOL!) going bananas, so just add it to the exclusions list, seems to solve everything at this point, until hopefully your devs can figure it out with a update, anyway if I find more issues I will let you know but for now that is the workaround

OK I found another problem (feel free to move this or start another thread if it's considered cross posting) I tried watching a few vids on You Tube and MBAE lost it's (insert expletive here) it's goes bonkers with the Anti-HeapSpraying Enforcement pop ups but this is mainly due to using the No Script add-on and having "Apply these restrictions to whitelisted sites too" and the "show placeholder icon" ticked I do believe, as when I disabled those or the actual add on itself the videos played with no trouble. The workaround for this is exactly the same as for Mozilla FF, you need to find where Flash is located on your computer so either: 32 Bit Windows: C:\Windows\system32\Macromed\Flash or 64 Bit Windows: C:\Windows\system32\Macromed\Flash C:\Windows\syswow64\Macromed\Flash Then just add the entire folder to the Detect shellcode injections exclusion list and hit OK, then everything should play as normal

OK well while you're doing that I will give everyone else the workaround, here's what to do (for CIS that is, I dunno about other AV's but if they have something similar it may do the job) you need to add the entire Mozilla Firefox folder from your C: Drive > Program Files directory (or where ever you installed it to) to the HIPS (just left click it on the main interface) > Detect shellcode injections > Exclusions list, then hit OK. FF should open with no problems, mind you it will be a little bit slower than normal but it's better than nothing at this point! Hope this helps everyone pulling their hair out trying to get the 3 to play nicely with each other

I just noticed this as well, the only way to get Firefox to run is by disabling Anti-HeapSpraying Enforcement (which sort of defeats the purpose), uninstall MBAE (not really an option is it?) or CIS (once again, I'd rather not, LOL). So is anyone actually looking into this to try and fix this conflict/issue? Only one bright spark over at the Comodo forums has picked up on it so it would seem?