https://www.displayfusion.com/Discussions/RSS/?TopicID=7db86c9b-9cb9-4b67-8eb4-a276d103045a DisplayFusion RSS: Conflict between Malwarebytes Anti-Exploit and DisplayFusion Pro V8.1 Beta 2 Fri, 22 May 2026 12:42:06 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=7db86c9b-9cb9-4b67-8eb4-a276d103045a https://www.displayfusion.com/Discussions/View/conflict-between-malwarebytes-anti-exploit-and-displayfusion-pro-v81-beta-2/?ID=7db86c9b-9cb9-4b67-8eb4-a276d103045a#4 Fri, 28 Oct 2016 18:26:37 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/conflict-between-malwarebytes-anti-exploit-and-displayfusion-pro-v81-beta-2/?ID=7db86c9b-9cb9-4b67-8eb4-a276d103045a#4 DisplayFusion Phew! Glad to hear it's not a DF issue

Thanks for the update! ]]> https://www.displayfusion.com/Discussions/View/conflict-between-malwarebytes-anti-exploit-and-displayfusion-pro-v81-beta-2/?ID=7db86c9b-9cb9-4b67-8eb4-a276d103045a#3 Thu, 27 Oct 2016 07:29:16 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/conflict-between-malwarebytes-anti-exploit-and-displayfusion-pro-v81-beta-2/?ID=7db86c9b-9cb9-4b67-8eb4-a276d103045a#3 DisplayFusion Tried the suggestion of adding MBAE into DF Conflict. It did not make any difference. The problem still exists.

I removed DF entirely from my system and the problem still occurs; therefore, I suspect this is not a conflict with DF but some other issue with MBAE. I have posted over on the Malwarebytes forum and the developers are looking into it. ]]> https://www.displayfusion.com/Discussions/View/conflict-between-malwarebytes-anti-exploit-and-displayfusion-pro-v81-beta-2/?ID=7db86c9b-9cb9-4b67-8eb4-a276d103045a#2 Wed, 26 Oct 2016 17:49:14 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/conflict-between-malwarebytes-anti-exploit-and-displayfusion-pro-v81-beta-2/?ID=7db86c9b-9cb9-4b67-8eb4-a276d103045a#2 DisplayFusion That's really strange! I run MBAE on my system as well and I'm not able to reproduce that. I wonder if it's hook related. Could you try creating a Compatibility rule in the DF Settings for MBAE, and in the rule, enable the "Disable Application Hooks" option? ]]> https://www.displayfusion.com/Discussions/View/conflict-between-malwarebytes-anti-exploit-and-displayfusion-pro-v81-beta-2/?ID=7db86c9b-9cb9-4b67-8eb4-a276d103045a Sat, 22 Oct 2016 18:54:18 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/conflict-between-malwarebytes-anti-exploit-and-displayfusion-pro-v81-beta-2/?ID=7db86c9b-9cb9-4b67-8eb4-a276d103045a DisplayFusion This applies to Windows 10x64 Pro Build 14393.321, Malwarebytes Anti-Exploit Premium V1.09.1.1225(and earlier versions) and DisplayFusion Pro V8.1 Beta 2.

There appears to be a conflict between DisplayFusion and MBAE on my system with 3 monitors. If I open MBAE and select "Stop Protection", it results in the Start Menu becoming inoperable on all monitors. In addition the Taskbar on the primary monitor becomes inoperable as well. The taskbar is fully operational on monitors 2 and 3. The desktop on all monitors remains active. The notification message that MBAE attempts to issue stating that protection has been stopped is not issued at the time I stop protection.

To get things back to normal, I can go to the notification tray on monitor 2 or 3, enable protection via the right click menu of the MBAE icon in the notification tray. After a few seconds, things will go back to normal.

This issue does not occur if Displayfusion is not running. ]]>