Jump to content

Updating issues with new mbam; stuck on 12/31/2011 database


Recommended Posts

After installing the .1000 update the database is from 12/31/2011 and can't be updated with newer version.

I deleted the rules.ref and MBAM succesfully did update the database but again with the 12/31/2011 version. For some buggy reason the program can't get the 2012 update and is stuck with the one from past year. So it's not the fact it can't get the updates, it's downloading always the same old one...

Dutch language / Pro version / Win7 starter / Avast FW-AV

(updated, mbam excluded and even shut down to test)

Link to post
Share on other sites

  • Root Admin

Please do the following and let us know if that corrects it.

  • Download and run mbam-clean.exe from here
  • It will ask to restart your computer, please allow it to do so very important
  • After the computer restarts, temporarily disable your Anti-Virus and install the latest version of Malwarebytes' Anti-Malware from here
    • Note: You will need to reactivate the program using the license you were sent via email if using the Pro version
    • Launch the program and set the Protection and Registration. Then go to the UPDATE tab if not done during installation and check for updates.
      Restart the computer again and verify that MBAM is in the task tray if using the Pro version. Now setup any file exclusions as may be required in your Anti-Virus/Internet-Security/Firewall applications and restart your Anti-Virus/Internet-Security applications. You may use the guides posted in the FAQ's here or ask and we'll explain how to do it.

Link to post
Share on other sites

AdvancedSetrup, with all respect but it's always easy to copy and paste a drastic workaround which is in most cases not necesaraly, can't you guys see what a hassle it is to do this procedure every time there is a bug in your system (and yes it was)?

(Caused by other programs or not, but that should be tested before a major release imho).

Today mbam did download the right database file from today so I suppose your technical department addressed and solved the problem. And Yes, I did reboot yesterday so it wasn't the reboot today which corrected the update.

For my and other's sake, PLEASE backtalk to the engineers of the program before copy and paste a "reinstall program" solution.

Maybe for some people this will help but the most only find it annoying and time wasting...

I'm working since 1990 with computers and thousands programs later you're still the only company I jknow who always suggest to do a full clean in first place before trying something else.

Thx.

Link to post
Share on other sites

  • Root Admin

Thanks wijllie

If you've been working with computers since 1990 then perhaps you also realize that it can potentially take days to track down specifically the exact cause on a specific computer. Then when the average computer user does not know how to use the computer very well in the first place that makes customized answers you're looking for almost impossible when there are only a few support techs.

I realize it's not an optimal solution but if you have experience it takes less than 3 minutes to do on a modern computer.

We are investigating issues such as this though behind the scenes and have corrected a few issues that we no longer see anymore because the code was fixed. We don't like having to offer this solution anymore than you do and hope to find and squash all of these issues.

Thank you for your understanding.

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.