Anti randsome sometimes occupies excel files

[Hal7]

Yesterday I could not fully open certain excel files in one particular folder.

Another user would had the file in use (write protected message).

After emptying my system files temp folders and rebooting I got full access so I blamed the cluttered temp folders.

Today however again an excel file in another folder was occupied.

I discovered Anti-Randsomeware was the one, occupying the files. After I switched off Anti-Randsomeware, the problem was gone.

 

[Hal7]

Now also MsWord is involved. With Anti-Randsom on, I get the message that my file cannot be saved.
So I think I will abandon A-R until this is solved.

[1PW]

Hello Hal7 and

If MBARW has not already been uninstalled, please create the following files for developer analysis:

Create a ZIP file of the directory C:\ProgramData\Malwarebytes\Malwarebytes Anti-Ransomware\

Create another ZIP file of the directory C:\ProgramData\Malwarebytes\MBAMService\logs\

Please attach the above zipped files to your next reply.

Thank you.

[Hal7]

Here are the zip files

A-R 2.ZIP

A-R 1.ZIP

[1PW]

Hello Hal7:

 

The developer team may be able to make good use of the data.

 

Thank you.

[Hal7]

Additionally: Even with A-R switched off I have some access problems. To open my files not "write protected" I have to swicht A-R on and off.

[Hal7]

I reïnstalled A-R, following the procedure 1PW posted in "Cannot save Word files - Office 2010" from March 13.
It seems a better procedure. At this moment at least, using it one day, I did not meet any problem.
(Bit strange to me, because I only use my PC with full admin rights, so why not just follow standard install?)

[1PW]

Hello Hal7:

 

Thank you for the good news feedback.

[Decrypterfixer]

We are currently aware and working hard on the issues MBARW has with office currently. Thanks for the great feedback.

[Hal7]

Unfortunately the faulty condition is back, so re-installing did not solve the issue.
But just before the faulty condition reappeared, I emptied my temp folders. Maybe that's a clue!!

(I also ran cccleaner, but without making modifications)