danburrito

So, six plus months later I see this reply... (again? maybe?) I suppose I had read it while at work and forgot about it later that day. And here we are. Thanks, @Arthi and @Porthos for all your help.

You may have misunderstood - I never added (or removed to my knowledge) any checkmarks myself. Those checkmarks in the screenshot I provided were added when I reset the settings to default.

@Porthos Thank you for your continued efforts to help. I appreciate it. Sadly, this did not work. Penetration Testing was already toggled OFF. A reset of the advanced settings added a few checkmarks, as indicated in the attached screenshot (also checkmarks for the 64-bit equivalent of the CALL ROP gadget detection, albeit not reflected in the image) - this did not make a difference regarding my issue. Furthermore, I do not recall to ever have messed with those specific settings. I am following following the troubleshooting steps given by @Arthi via DM as I am writing this. Thanks again.

Neither Malwarebytes v4.6.1.280 or LibreOffice v7.6.0.3 solved this issue.

That's the thing: There was no Malwarebytes notification whatsoever about a block. Only on LibreOffice's side about not being able to create a lock file. Scouring LibreOffice community help sites, I couldn't find anything specific (and recent), so I tried disabling Malwarebytes' protection modules one by one to see if that would do anything. It started working when I disabled the Exploit Protection module. After that I started to look into the Exploit Protection settings attached in the original post.

Thanks for the quick reply, @Porthos, but this setting was already disabled.

Trying to open an existing file with LibreOffice v7.5.4.2_x64 on Windows 10_b19045 I get the following notification: The workaround to this is to disable LibreOffice in the Protected Applications settings:

I had experienced the same issue as OP for the last day and a half, but upon coming to this forum and seeing the first pinned thread annoucing the release of MB v3.3.1, I downloaded and installed it over the top of the old installation and it runs just fine so far.

Ran a scan and left computer for an hour, returned to my system (Win10 x64 v1607 build 14393.576) severely lagging. Used task manager to end Malwarebytes Service (see attached image). Also attached MBAMSERVICE log. MBAMSERVICE.zip

Installed over the top of previous version, and so far no problems on Win 8.1_X64.

WinRAR v5.11 came out of beta today. After installation, I do not experience issues with it and MBAE x.1012.

Could always change the name of the executable in question to chrome.exe.

Thanks, Pedro.

You know, I haven't even thought about that. In fact, I forgot that I added the custom shield for WinRAR. It does work when I disable the shield, although it worked in previous versions.

Since installing version .1012 of MBAE, WinRAR v5.11 beta 1 will not function properly anymore. I.e. open/extract/create archives via the right-click menu or open the application itself. However, extracting sfx archives does still work. Proper function of WinRAR is restored upon closing MBAE. Logs are attached. mbaelogs.zip