Andy2No

I was about to make the same complaint, then found this thread. I was trying to search for "xxx.exe" (a trojan, which mbam failed to detect), so I concluded the thing to do was to replace the dot with a space - no good, because the forum also refuses to let me search for three letter words. Darn those three letter words. So much more offensive than the four letter ones.Was the search function designed by an incompetent control freak?

I've finally rebooted, allowing the installation of 1.60.1.1000 to complete. I unticked "Start with windows" though, for the protection module, and started it manually, just in case. So far, so good - that's on my old Windows 2000 SP4 machine, with the older ZA free though, and I haven't had the problems on this one. I haven't been using the XP machine for a few days, so I haven't tried it on that yet. I'll report back if there are any problems with either. I guess they're now rare, so there's little point in filling this thread up with posts about not having a problem

When using XP, I'd agree with that. Windows 2000 was stable enough to not need restarting unless there was a good reason to. It's still a superior product, you just can't get the software for it any more.

I haven't rebooted in days, and I'm still not ready to - I'll leave it til after a meeting I'm preparing for, in case something goes wrong with the update. I still see MBAM updates as an unexploded bomb, at the moment. I wish there was an option to disable automatic updates all together and just have it notify me there was one available, once in a while. Yes, I can cancel the update, but it's too easy to press the wrong button if it pesters me when I'm in the middle of doing something more important. I thought this machine still had 1.51.2.1300 on it, but that's the other one (this is my Windows 2000 PC - old, but reliable). I certainly didn't install 1.60.0.1800 manually, so it was offered as an automatic update, at some point.

Ah. Okay. Apparently, it was just sitting there doing nothing. It's now offered to install 1.60.1.1000, and wants to restart. The horror! There's no way I'm letting it do that til I've had some sleep. I don't want a repeat of that scenario.

Oops. Where's the edit in this forum? That should have said "assuming it would be to 1.60.1.1000 but it now identifies itself as 1.60.0.1800"

daledoc1, No, he's right. Mine just asked to update itself so I decided to let it, assuming it would be to 1.60.1.1800 but it now identifies itself as 1.60.0.1800

@davidy46 I certainly am. I've had enough stress already Actually, I'm waiting for reports of the next FULL release. I'm fine with what I have, for now.

No problem, Firefox. I didn't realise that. I've just looked, and they're on the right hand side of the page, here: http://filehippo.com/download_malwarebytes_anti_malware/

I forgot to mention, both 1.51.2.1300 and 1.60.0.1800 work on the Windows 2000 PC, so I'm using the latest one one to avoid having the annoying update pop-ups all the time, as I now do on the XP machine. Possibly the reason is that 1.60 doesn't conflict with the older version of ZA Free.

Does malwarebytes.org have an archive of older versions to download? It certainly needs one. If there's no objection, I could upload the working version I have to oldversion.com. I have mbam-setup-1.51.2.1300.exe and that's working fine for me, with XP Pro SP3, Aviria Antivir Free and ZoneAlarm Free, also on Windows 2000 SP4 + the final roll up updates, with Avast! 6.0.1203 (an older version than the current one as they no longer support Win2k) and ZoneAlarm Free 7.0.483.000 (the last verison I know of that supports Win2k). If for some reason the admins don't want me to do that, let me know soon because I don't think I can take it off again once I put it on there. I paid for MBAM Pro (for both PCs) but as I understand it, it's the same download either way. Someone correct me if I'm wrong.

I see. Thanks for clarifying that, HiSpeed. I think I'll just stick with 1.51 until a new release appears, and has been tested by a few other people I hate automatic updates in general. You never know what to expect. It's good that you can cancel it when MBAM wants to update itself, but it's still too easy to click the wrong thing. I've done it with Opera too. I never want to update Opera til I've made a backup of my settings because it has a habit of wiping all my bookmarks. On the whole, I'd rather let other people try it first and wait for the complaints

B1z, Did you get 1.6 to work, or just uninstall it? HiSpeed, What fix is that? The thread LDTate linked to refers to one, but doesn't give a link to download it, as far as I can see.

Almost? I'm pretty sure this qualifies as a full sized boo boo. For a lot of people, this year, and a few days of last year, their first experience of trying MalwareBytes AntiMalware was that it stopped their computer working all together. A large proportion of those people probably didn't have the faintest idea what to do about it and weren't able to fix it for themselves. Some will have pestered the usual friends and relatives, some will have handed over good money to an alleged IT professional get it sorted out. How many of those people are going to want to pay to use MBAM Pro after that? Okay, some of them will be dumb enough to fall for the idea that it happened because they had a virus. I can see that. What amazes me most, having read the "Possible Updating Issues" thread that LDTate has just kindly linked to, is that the MalwareBytes team has now been aware of the severity of the problem for a while, and the causes, but the plan has been to just let the situation continue until the next version's ready. Seriously, why not just pull this version and direct people to the last known good one instead? Is it for legal reasons - i.e. you just don't want to admit the mistake, or is it just because you're all too busy panicking? I could certainly understand if it was the second one but the fact that there's absolutely nothing on the main pages of www.malwarebytes.org to warn new users of the problem makes me wonder if it's the first. Sure, it takes a while to sort these things out but while that's going on, more people who haven't updated in a while (like I hadn't) and many more people trying MBAM and the protection module for the first time, are getting their PCs turned into large air cooled, LED lit paperweights. I'm no business expert, but I'm inclined to think that's going to have a negative effect on sales.

Update: I found I still had mbam-setup-1.51.2.1300.exe so I installed that on my XP Pro SP3 machine. That seems to be working fine, except for downloading 1.60 as part of the first set of updates and announcing that it was about to install it. Pressing cancel stopped it so now there's just the balloon that pops up from the system tray icon to deal with. Presumably, if I miss the close button and hit the main part of the balloon, I'm back to square one, but at least I'll know how to fix it. I see that 1.60 is still on the cnet download page. May I strongly suggest that you withdraw it before someone tries to start a class action against you? Possibly there's a clause in the EULA that says "I accept that by using this software my PC may, quite likely will, become completely inoperable"?