Jump to content

3.0.6 "ransomware protection" bug (March 21, 2017)

Recommended Posts

I just mandatorily updated to 3.0.6.  It ran OK for a day, now Malwarebytes Ransomware Protection is broken.

This is not the first - or even the second - time that I have encountered some hard-to-fix bug in Malwarebytes "protection."

This is getting old, guys...

Link to post
Share on other sites

Hello @Phurry:

1) Please consider using the guidelines within Having problems using Malwarebytes? Please follow these steps: to give the Malwarebytes' developers/staffers the data they require to analyze your system's issue.  Please separately attach the four (4) data files from steps 6, 7, and 8 in a reply to this topic.

2) Also, please consider left-clicking the "Follow" button, near the upper-right corner of your topic, to receive timely notifications about updates to your topic.

Thank you.

Link to post
Share on other sites

@Phurry I've had this issue on two of my Windows 10 computers so far. Seems to have happened after the last Windows 10 update.

I was able to fix it pretty easily.

1. I ran Ccleaner (Cleaner and Registry Cleaner)

2. Ran Kaspersky Privacy Cleaner (Dunno if running both is important, I just did)

3. Restarted computer

4. Turn on the Ransomware Protection (Still spins and spins trying to start it)

5. Restarted computer again with it trying to start Ransomware Protection

6. Upon 2nd restart all protections are on and have stayed that way.

Edited by Technicalpep
Forgot to include OS
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.