Mayidunk

I just tried, no joy! No updates available.

Malicious website protection just stopped working for me as well, and I have not yet updated to 2.0.3.. FYI...

Self protection of Malwarebytes program files is definitely a very, very good thing!

These are the types of instabilities that I am referring to! There is absolutely no reason why the update manager should not be able to detect that these settings are in force, and either change them accordingly, or notify the user that they need to be changed before continuing with the update. To instead allow the update manager to indiscriminately update a user's installation without regard to its current self-protection status, is a rather serious oversight!

I, too, would like to be able to turn off the nag message. With the problems that occurred with previous updates, coupled with the "scorched Earth" nature of their current "delete it, and reinstall it" troubleshooting method, I'm a bit gun shy about installing this update, or any other update until I can be sure that it is indeed stable, and won't clobber my installation in some way! I currently own two lifetime licesnses for Malwarebytes, because I believe that it's currently the best anti-malware software out there! However, I'm chagrined at having to take this kind of "wait-and-see" attitude about updates. Malwarebytes is complex, and has a lot of hooks in our systems, so it's understandable that "stuff" will happen from time to time. However, given some of the current design choices that were made for version 2, we have no choice but to be vigilent to ensure that the integrity of our systems are not compromised because choices that were made resulted in instabilities being introduced into the product. My hope is that past issues with version 2 were only growing pains, and that moving forward, version 2 will prove to be as robust, and stable as version1 was. However, until that is proven beyond a reasonable doubt, we must continue to be careful with updates to version 2, and unfortunately, wait for early adopters to report back with their experiences before comitting to updating our installations. Towards that end, IMO, as long as the basic functionality of the prodect is not disrupted by delaying the installation of an update, then the user should be able to acknowlege the update notification, and then turn it off. At the very least, perhaps the nag screen could be redisplayed afterwards, once every 24 hours, until the user decides that it's safe to proceed with the update?

Thank you for chiming in on that. I believe this is a good example of why Shakespeare advocated doing away with all the lawyers! Perhaps it might not be a bad idea for Malwarebytes to create a sticky explaining this, especially with the changes made to the EULA from the previous version as pointed out by Stem in their post, above. This way, there are no surprises that could end up biting you in the end, in the end. These kinds of "Weasel words" are what many people are starting to complain about. As written, the end user is placed between a rock and a hard place as soon as they begin the process of updating to ver. 1.51, specifically due to the fact that merely disagreeing with the EULA requires them to stop using the software, and delete any copies they may have! Either that, or change the EULA so that disagreeing with it will not make pirates of your end users.

I'm bumping this because, if you read the EULA, the wording of that provision definitely requires the end user to accept any and all subscription fees that the provider decides to levy. I am not at all averse to paying for a good product that is so well supported as Malwarebytes, however I am averse to having things like this surreptitiously added to the EULA that few people actually read. BTW, what is legally binding is what you agree to each time you click through a EULA. regardless of what you agreed to prior to that. Please note the following: The Preamble of the EULA contains the following statement: "By installing or running this software, you are agreeing to the terms of this License. If you do not agree to abide by the terms of this Agreement, you may not install or run the Malwarebytes Anti-Malware Software (the "Software") and must delete any copies of that Software in your possession." Clause number 14 states the following: "Malwarebytes reserves the right to designate any updates, additional content or features as requiring separate payment or purchase of a separate subscription at any time without notice to you." Therefore, according to clause 14, any changes or updates they make to the software allows them to require you to pay either a separate one-time payment, or to purchase an on-going subscription. Furthermore, according to the wording of statements made in the preamble, this EULA effectively supersedes all previous agreements made, and stipulates that, if you do not agree to the terms of the EULA, you not only cannot install the update, but you must then uninstall, and delete, any copies of the software! Notice that it does not stipulate you must delete the update software only, but rather that you must delete "any" copy of the software in your possession! Does that mean they'll start requiring you to pay a subscription any time soon? Maybe not. However, it does allow them to put you over a barrel if they suddenly decide to require it. Whether or not Malwarebytes is seen as one of the "good guys" in the battle against malware and such things, the plain fact is that they thought it necessary to add this kind of thing to their EULA without making it abundantly clear to their users. BTW, this is not a troll. You may read the EULA for yourselves when you attempt to install the update, and decide for yourself at that point whether or not you want to accept it. And, BTW, according to the way they worded it, if you decide not to accept it, you must then delete any copy of the software in your possession! For me, the bottom line is to never click through a EULA without reading it thoroughly.

While reading the EULA for the latest version of Malwarebytes Pro, I saw a provision that will allow Malwarebytes.org to start charging an annual subscription fee without prior warning to, or approval by the user. I ask because I purchased a copy of Webroot Window Washer about a year ago. I installed it, and subsequently updated it to the latest version. After the update, Window Washer started tossing messages saying that I had to start paying an annual software subscription fee by a certain date, otherwise the software would stop working! Needless to say, having the previous version installation disk, I immediately uninstalled the update, and reverted the software to the previous version. If I did not have the previous version's installation files on a CD ROM, I would have been stuck with either having to start paying the annual fee, or uninstall and stop using the product that I had previously purchased! Malwarebytes has always maintained that once a user purchases a copy of their software, they then own it, and would not be required to pay any additional fees. However, I now find that if I update my copy of Malwarebytes Ver. 1.5 to 1.51, I open myself up to possibly becoming locked into an annual subscription payment plan at some future point in time. This contradicts the notion that if I purchase a copy of the software, I then own it. I checked the info and news portions of the fora, and did not see any mention of this change to the EULA. Now, is this provision in the EULA new with this version, or has it always existed? If it was in the EULA of previous versions, then I guess maybe I just didn't see it. However, whether or not it is a new provision, why would it even exist in the EULA in the first place? If this provision existed beforehand, then why would Malwarebytes assert that once we purchase a copy, that would be the last time we would have to pay any money to use it? Am I missing something, here?