Mbam displays out of date notice, but won't update.

[Noehl]

I have been having this issue constantly where my mbam will display a notice at the bottom right of my screen every 30 mins or telling me to update mbam, and a green button to update. I click the button, and nothing happens. I open the  mbam interface, and attempt to manually update it by clicking the green update button there aswell, and nothing ever happens. The only way i've managed to get around this and make it finally update is by restarting my computer, and running the update check first thing once my windows is loaded. I am on premium mbam. 

 

I'm using windows 7 64b home premium, and it's running alongside avast (non-free version)

 

The annoyance continues as the windows seem to stack if i'm away from the computer for several hours. Like it's queuing the update notice. I x out the update notice window and it will pop up again until the number of queue'd notices has been displayed and closed...

[daledoc1]

Hello and :
 

Like it's queuing the update notice.

Yes, that is a known issue on some systems with certain scheduler settings.

 

First: please be sure your system date and time are correct.

Also: Open the dashboard > click "Scan" and make sure there are no PUPs or PUMs awaiting your action. That will prevent updating, as well.

 

You may wish to try the new public Release Candidate build of 2.0.3. It does fix many different issues for some users - this includes changes to the default outdated database notifications settings.
Information and download link are here: Malwarebytes Anti-Malware 2.0.3 Release Candidate 1
Known issues are here: Malwarebytes Anti-Malware 2.0.3 RC 1 - Known Issues

If you do, it might be a good idea to cleanly upgrade, following the basic sequence here: MBAM Clean Removal Process 2x (you would substitute the version 2.0.3 RC1 installer instead of the 2.0.2 installer at the appropriate step).

And if the clean upgrade doesn't resolve your issue, it would greatly help us to see some diagnostic logs: Diagnostic Logs (the 3 logs are: FRST.txt, Addition.txt and CheckResults.txt)

Thanks,

[Noehl]

There was indeed one item in the list that was waiting for an action! Taking care of that solved the issue. 

 

I'm not one to mind participating in experimental/betas for things, but in regards to a security measure as needed as this, I'd rather avoid "do everything to break it", and potentially doing so, along with my computer... Aside from that, i'm not the most technical and computer literate of people, so i'll leave that to those who are 

 

[daledoc1]

Great!

I'm glad you're all set now.

To make sure it doesn't happen again, you might want to please check to be sure your Detection and Protection settings look like the screen shot.

 

Cheers,