Malwarebytes just deleted my Visual Studio 2015 Install

[LSmith1437]

While I was programming, I saw a flash notification at the bottom of the screen that said something about Malwarebytes blocking a ransomware attack.  I though it said something having to do with the path where my Visual Studio 2015 was installed.

When I went into the Malwarebytes interface, there was no log, no report, no quarantine...I could find nothing about what it had done.

When I closed and tried to re-open my development environment, I could not run it at all.  Malwarebytes has remove my devenv.exe, which is the main part of the development tool.

 

You're killing me, Malwarebytes!

How can I reverse this action?  Where can I find the logs of what it did?

[1PW]

Hello @LSmith1437 and

The logs needed by Malwarebytes staffers to assist you are obtainable with the following:

Obtain and post a copy of the Malwarebytes logs

1. Please zip the contents of "C:\ProgramData\Malwarebytes\MBAMService\logs".
   1. The ProgramData folder may be hidden. You may need to show hidden files, type the path manually or type “%programdata%” in the Run command.
2. Attach the ZIP file by clicking on the "Drag files here to attach, or choose files..." or simply drag the file to the attachment area.
3. Please advise the local date & the approximate time of the occurrence.

Thank you.

Edited April 23, 2017 by 1PW

[LSmith1437]

I have since moved on, reinstalled/repaired my visual studio and am back to work.

I do have a Feature Request:   Allow users to see the log of actions that Malwarebytes has taken.  I can find no place in the interface where I can see just what it's done, and when.

[1PW]

Hello @LSmith1437:

A very accurate log of worthy MB3 events is journaled within the MBAMSERVICE.LOG file in the archive (mb-check-results.zip) created by the mb-check-3.1.0.1002.exe support tool, or by directly reading the "%ProgramData%\Malwarebytes\MBAMService\logs\MBAMSERVICE.LOG" file.

HTH

[dcollins]

You can also see/undo the actions by going to the Reports Tab and it will show you what was detected and what actions were taken. If you still have the reports there, can you export the report for the Visual Studio issue so we can try to identify what's going on