![]() Ironically, it's showing up as being used on two other systems that I had installed it on, but NOT on my current/primary system! But the second/MBAE license was accepted, and is now formally registered to me. The first/MBAM license was rejected, indicating that someone else had already registered that license. Today, I tried to register/store my license information online. So I then tried to enter my second "lifetime" license, which I got for beta-testing very early versions of MBAE. When I tried to re-enter the same license information, it was no longer accepted. Then, a few months ago, it happened again. and so they reactivated it on my system(s). I contacted MBAM, and was able to offer them "proof" of the license that I had been awarded. Everything worked fine for a few years, until one day, I noticed my MBAM had reverted to "free" from "premium". at least 5 people were offered the same license/registration information. ![]() If I'm not mistaken, that particular license was issued to us beta testers as a "shared" license. The first was for beta-testing very early versions of MBAM 1.x. In my case, I had two "lifetime" licenses. ![]() It's probably for the best to set up an MBAM account, where you can register/store your license. It is permitted to transfer that license from one system to another, by deactivating the license on the first, before activating it on the second. but version 3.8 started checking and enforcing the one-machine license as it was intended. Versions of MBAM prior to 3.8 "overlooked" this. It seems the problem is that people were purchasing a license that was valid for a single machine, but then applying it to multiple machines, concurrently.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |