Thanks for the replies.
I was asking because EMET 5.52 was released in November, and MS announced that they will not support the use of EMET on any version of Windows 10 beyond 1607 (it's also noted in the EMET 5.52 user's guide), and at the same time they also pushed back the cutoff date for support to July 2018 for EMET for Windows 10 1607 and earlier, as well as all earlier Windows, back to Vista SP2.
I don't know if you've seen this -
https://blogs.technet.microsoft.com/srd/2016/11/03/beyond-emet/
When it came out there was one dissenting opinion from a normally reliable source -
https://insights.sei.cmu.edu/cert/2...tect-insecure-applications-like-emet-can.html, and then the herd of parrots jumped on the bandwagon repeating what he said without anything new added. (well it did generate a lot of hits for their sites)
MS hasn't responded so it's hard to judge who is right.
But apparently something changes after version 1607 since MS will only support the use of EMET up to 1607, but obviously that's not a factor for either of you.
I don't have EMET installed here because EMET's not supported in Server 2016 either, so apparently something is different in it (even though it was released before Win 10 1607), as MS did/does support EMET in prior versions of Server.
Maybe an interaction with defender or other built-in safeguards in the OS that are triggered by Malwarebytes' AE running?
As I said, absolutely no problems in Server 2016, so the difference in the OS's must be where the "rub"
lies.
Hopefully Malwarebytes can sort it out.
Does your Event Viewer offer any clues?