Jump to content

MWB 2.0.2.1012 Crashing when clicking Scan or Fix Now


Recommended Posts

When I upgraded to Malwarebytes 2.0.2.1012, it opened without problems.  I would run it and get an error stating that the program stopped working (like the one in the picture).  I tried the uninstall and clean method more than once with no working result.  I am running Windows 7 32-bit edition.  I have 1 administrator account and 2 standard user accounts.  I installed MWB 2.0 while logged in under the administrator account.  This is where I would get the crash issue.  I logged out of the administrator account and logged in under one of the standard accounts.  Then I ran MWB 2.0.  Amazingly it worked fine without crashing.  Then I logged back into the administrator account and MWB 2.0 has been working fine ever since.  I have no idea how this corrected the issue, but it did for me.  Hope this helps others in their plight.

post-168197-0-56468100-1404354442_thumb.

Link to post
Share on other sites

Yes, Maurice, that is correct.  I don't know why there was an issue in the beginning.  I installed it as usual under the administrator account.  I even did the clean your system and re-install method under the administrator account.  It would not work until I went into one of the standard user accounts and ran the program.  I will run the diagnostic tests and upload the files when I get time to.  I will also try to recreate the symptoms and  upload those files as well.

Link to post
Share on other sites

Yes, 1PW, this method worked for me.  Why is it that net.conf is not operating properly?  I see that the batch file replaced net.conf inside the Malwarebytes program folder.  Was this file corrupt with the new release?  Also, what made it work after changing user accounts?

Link to post
Share on other sites

Hello ricknorris_1:

 

Thank you for the good news feedback!

 

I am merely a volunteer forum helper, and I can only relate what we believe is the best path for you to follow to success. Because Malwarebytes' products are not open-source, and revealing details might give competitors or purveyors of badware unwanted insight, we may never know more than what we know now. However, near future updates to MBAM2 likely will correct this issue

 

If Malwarebytes staffers weigh-in, more information might be available.

 

Please let us know if we can help you further. :)

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
 Share

  • 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.