Jump to content

MBARW destroys (not Quarantines) bash, dpkg


Recommended Posts

I was updating the new bash tool that came with Windows 10 AU.  `bash` was Quarantined, or so MBARW said.  It was not in Quarantine, before or after a reboot.

I stop MBAWR to repair the bash tool.  I was going along fine, until `dpkg` was Quarantined -- again not really; it was destroyed like with `bash`.  This was really a surprise since my MBARW still said that Protection should be enabled -- with a red line!

I had to uninstall MBARW and I probably will wait for the next version.  I still managed to salvage logs from C:\ProgramData\Malwarebytes\Malwarebytes Anti-Ransomware\ , attached.






Link to post
Share on other sites

Hello ingber and welcome back:

As yours is the first report involving bash, dpkg and MBARW Beta after an upgrade with W10AU, the development team would benefit from the 3 archives that result when the False Positive reporting procedure is utilized.

Does any possibility exist that the C:\ProgramData\Malwarebytes\MBAMService\logs\ directory is still present within the system in question?  If so, please create a .zip archive of that directory and attach to your next reply to this topic.

Thank you kindly for your report.



Link to post
Share on other sites

Hi.  Sorry, I sent all the logs I have.  MBAMService/ does not exist anymore.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.