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"/>