Malwarebytes 2.x database constantly goes out of date

[nascent]

I'm having the Same issue as here.

 

And before the 'Problems that seem "the same" most often are not' comment. this is happening with 3 of my machines, and all of my friends' and family's machines,

 

'A reboot should fix it' isn't a fix.  Most people don't shutdown or reboot any more.  They just close their laptop lids.  If your security product cannot cope with running without interruption then there is a severe flaw.

 

I bought many lifetime licenses because I trust in MalwareBytes and know the detection rate is pretty much unbeatable.  But if a simple thing such as definition updates can't work properly something needs to be done.

 

None of us had issues before the new 2.0 update, and now we all do.

 

The database will fail to update giving "database out of date" errors and it will never fix itself.  I've found machines haven't been updated for a month on a regular basis.

 

This issue really needs to be fixed, an out of date security tool is not a security tool.

 

Some specs:

Issue occurs on Windows 7 and 8/8.1 machines. 32 bit and 64 bit.

Premium lifetime licenses.  Hard drives with plenty of space, and always on connections.

 

Sometimes rebooting will trigger the auto update, sometimes exiting and reopening the client will allow auto update, sometimes reinstalling malwarebytes or installing a slightly newer minor version of the client will allow autoupdate, but in all cases it breaks again within a short time.

 

Some of my friends and my girlfriend keep asking me to uninstall it, because "it's rubbish and doesn't work".  They see the updated warnings and get frustrated.  I keep telling them I trust in it's detection and find it better than larger competitors, but honestly, when they ask why those can auto update and this can't I have no answer for them.

For the ones that live near me I can usually fix it temporarily for them but no all are technologically savvy enough to troubleshoot.  My parent's have zero technological understanding and need things to just work.

This is why I bought premium licenses, because I needed auto update, I needed things to just work.  Currently MalwareBytes is not accomplishing this.

 

log:

 

<record severity="debug" LoggingEventType="1" datetime="2014-07-26T10:26:59.648088+01:00" source="Scheduler" type="Update" username="SYSTEM" systemname="NASCENT"fromVersion="2014.5.27.11" last_modified_tag="5dbec93a-3164-478d-b76e-a928b04e375c" name="Malware Database" toVersion="2014.7.26.4"/><record severity="debug" LoggingEventType="1" datetime="2014-07-26T10:34:54.590701+01:00" source="Manual" type="Update" username="SYSTEM" systemname="NASCENT"fromVersion="2014.3.4.9" last_modified_tag="c67c175c-757f-4c33-8241-f3afb3725595" name="Malware Database" toVersion="2014.7.26.4"/>

 

[daledoc1]

Hello and :

A couple of easy things to check:

>>First, please be sure your system date/time are correct.

>>Then, please be sure that your AV and firewall both give MBAM full permissions. It's possible that your AV or firewall might be treating the new build as a new program and may be blocking it -- the files that need to be excluded can be found HERE (just the one reply -- not the entire thread). Please post back if you need help with that.

>>Also, please check to be sure there are no "Detected Threats" that need to be dealt with first, as this can prevent the program from updating: Click the "Scan" button at the top of the dashboard and verify that there are no detected threats (especially PUPs or PUMs) awaiting your actions.

>> Finally, you might want to start with the advice in this pinned topic >>HERE<< -- we don't have enough info about your system yet to know if it will work for you (but it won't hurt).

If those suggestions don't resolve your issue:

• Please follow the steps in this pinned topic to uninstall your current version of MBAM and reinstall the latest build - MBAM Clean Removal Process 2x
• If that does not correct the issue, then please read the following and post back attached to your next reply the 3 requested logs - Diagnostic Logs (the 3 logs are: FRST.txt, Addition.txt and CheckResults.txt)
• NOTE: There is an FAQ section with valuable information located here - Common Questions, Issues, and their Solutions

As you mention multiple machines, if you DO end up needing to perform step #2 (diagnostic logs), it will be most helpful to start with a log set from only ONE computer at a time.  Otherwise, it's likely to become overly confusing for everyone.

 

Please let us know how it goes.

Thanks,

[nascent]

Hello and :

 Hi.

 

A couple of easy things to check:

>>First, please be sure your system date/time are correct.

It is.  Across all machines.

 

A couple of easy things to check:

>>Then, please be sure that your AV and firewall both give MBAM full permissions.

They do.

 

 

A couple of easy things to check:

>>It's possible that your AV or firewall might be treating the new build as a new program and may be blocking it

It's not.

 

>>Also, please check to be sure there are no "Detected Threats" that need to be dealt with first, as this can prevent the program from updating: Click the "Scan" button at the top of the dashboard and verify that there are no detected threats (especially PUPs or PUMs) awaiting your actions.

This is interesting to me.  Why would the program refuse to update for this reason?

There aren't Detected Threats on all the machines.

 

 

>> Finally, you might want to start with the advice in this pinned topic >>HERE<< -- we don't have enough info about your system yet to know if it will work for you (but it won't hurt).

What is the Net Conf Fix and what 'specific situation' is meant to be causing it?

I shall try it on my girlfriend's machine first and see if it makes a difference long-term.

 

 

If those suggestions don't resolve your issue:

• Please follow the steps in this pinned topic to uninstall your current version of MBAM and reinstall the latest build - MBAM Clean Removal Process 2x

As mentioned I have done that multiple times.

 

 

If that does not correct the issue, then please read the following and post back attached to your next reply the 3 requested logs - Diagnostic Logs (the 3 logs are: FRST.txt, Addition.txt and CheckResults.txt)

 

As you mention multiple machines, if you DO end up needing to perform step #2 (diagnostic logs), it will be most helpful to start with a log set from only ONE computer at a time.  Otherwise, it's likely to become overly confusing for everyone.

I'll start with the machine I'm using now.

 

CheckResults.txt attached.  FRST64.exe is blocked by SmartScreen.

CheckResults.txt

[1PW]

Hello nascent:

Please disable SmartScreen® for the time it takes to download FRST64.exe to your system's desktop. Then you can re-enable.

The FRST.txt and Addition.txt report files go hand-in-hand with the mbam-check tool and are crucial in proper and complete diagnosis of your system.

Thank you for your patience and understanding.