Jump to content

Recommended Posts

This is quite normal. The service mbamservice.exe is not supposed to be stopped after the protection module has been enabled, even if the protection module is later disabled. The reason being that it uses a kernel mode filter, and killing it can cause system instability, such as the system freeze you mention (I've seen similar behavior on my own systems, even with several previous versions of Malwarebytes in testing).

If you do not want the service to be using CPU/RAM (but still wish to use the Scheduler), then I would recommend unchecking Start protection module with Windows. in the Protection tab.

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.