Outlook exploit protection shut down problem

[mightaswell]

I am using mbam3.  Recently while I was in Outlook and browsing an email, the exploit protection module activated and mbam3 shut down Outlook as I added it to the protected list.

I was most grateful for the intervention preventing me from opening the email.

However I then had a problem that every time I tried to open outlook mbam immediately shut it down as Outlook  is set to open at the inbox on opening and of course the offending email. So I had to stop the exploit protection module to be able to access Outlook.

This defeats the purpose of the exploit protection for Outlook.

Does anyone have suggestions about the merits of removing Outlook from the custom list to avoid this issue or is there an alternative I can’t see which is not cumbersome like reinstalling a back up Outlook PST file? 

 

Exploit: 1

Malware.Exploit.Agent.Generic, , Blocked, [0], [392684],0.0.0

 

-Exploit Data-

Affected Application: Outlook

Protection Layer: Application Behavior Protection

Protection Technique: Exploit payload process blocked

File Name: C:\Program Files\Microsoft Office 15\root\vfs\ProgramFilesCommonX86\Microsoft Shared\OFFICE15\FLTLDR.EXE C:\Program Files (x86)\Common Files\Microsoft Shared\GRPHFLT\GIFIMP32.FLT

[1PW]

Hello @mightaswell:

Thank you for reporting the system's Outlook issue.  The Malwarebytes' staffers/helpers must have good log data for a quality fault analysis to begin.

1. Please save your work and close all running user applications for your convenience. applications for your convenience.

2. Please follow the steps within the locked/pinned topic at Having problems using Malwarebytes? Please follow these steps.

3. In your next reply to your topic, please only attach the three (3) separate files that are developed above: mb-check-results.zip, FRST.txt, and Addition.txt.

Thank you.

[mightaswell]

Thanks @1PW for your reply however I don't see this as a fault in Mbam.  I believe mbam worked exactly as intended when it closed Outlook.

I am asking 

6 hours ago, mightaswell said:

Does anyone have suggestions about the merits of removing Outlook from the custom list to avoid this issue or is there an alternative I can’t see which is not cumbersome like reinstalling a back up Outlook PST file?