- Dec 27, 2014
- 3,423
Would be interested, too.It's possible that Emsisoft Anti-Malware and HitmanPro.Alert may conflict, especially if you don't white-list both software in each product. However if anyone uses both in combination, let me know if it works well.
The reason I suspect it may potentially cause conflict is because since Emsisoft Anti-Malware has a Behaviour Blocker feature, it will work the same way other BB/HIPS systems work, usually via API hooking (so it can monitor the actions and intercept when necessary). Depending on how HitmanPro.Alert works, this may cause a conflict, since I believe HitmanPro.Alert will most likely attempt to detect hooks and repair them/notify the user of the manipulation (e.g. especially for browser processes to identify the browser becoming compromised).
Therefore, if Emsisoft does set hooks and then HMA starts detecting these and alerting the user about them = conflict. Even worse if it tries to repair them, and then Emsisoft tries to put them back in place, and it can continue in a loop.
However this is all just guesses, of course it would be a good idea to test and see if there is a conflict (I'd be interested in hearing about this), maybe if I get the chance I will test it myself if no one else currently uses both in combination to provide the feedback.
I had EIS v11 running next to HMP.A, they didn't conflict, however I did not throw any malware on them. For HUB purposes, I uninstalled HMP.A to not need to shut it down multiple times by the TaskManager (it used to restart). HMP.A is currently running on my main PC only, next to CF, without any conflicts. It even did not conflict when Q360 TSE joined the party.
As for the HUB results, I agree, take everything with a grain of salt, CIS managed to not sandbox a ransomware once, however, this could not be repeated, and has never appeared again yet. For sure something wrong with the PC or a conflict with other ransomwares / malwares sitting in the sandbox as well, which can even cause BSODs.
I've not whitelisted CF in HMP.A and the other way around, I only turned off Control-Flow integrity in HMP.A (stops ROP attacks due to it's description - please don't ask me what it does, I only know it conflicts with legit Photoshop Elements v12+13).