Gonzo: It wasn't a fresh install. I'm thinking that will be of interest to the program developers and one of the reasons I started this thread. To post / make known things that are different that past updates. Past updates would install overtop of my existing license and carry on without any licensing issues. The install of 2.1.8 was prompted by MalwareBytes from within the program telling me there was an update. That happens ok on past upgrades. So the problem is that it over wrote my registry keys or wherever my license key was stored. If that happened to me, then it will probably happen to a lot of other people, which will create an administrative nightmare for the people at MalwareBytes from all the people who misplaced their keys. ( Unless this is an "ooops - we meant to do that" so that we can clear a lot of people's lifetime licenses by wiping the registry key on the 2.1.8 install and hope you didn't keep track of the key, heh heh ) So, the 2.1.8 didn't roll out with the same results as prior updates. That is what I want to be known to the developers. My choice was to uninstall the whole thing, and start with an old version and go to 2.1.6 and "activate" at that point. At least I'm back where I started. My blue MBAM system icon has a red exclamation on it saying there is an update to 2.1.8 but I'm not doing it because I think it will not recognize my license even if I punch it in. Just my thought. Might be wrong on that one. But I'll wait and see how many other posts crop up on how 2.1.8 won't recognize a lifetime license before I ruin this machine. Hopefully, there will be NONE, and I will have no problem moving forward trying to activate. Personally, I have 13 Malwarebytes licenses that I use for test machines that I create / tear down. I bought them years ago via CleverBridge online from MalwareBytes. I have all the receipts and keys etc. LOL. I would hate to think that the $$ I spent on those licenses ends with 2.1.8. Again, I'm waiting to see what other people experience during this upgrade... maybe nothing. But in anycase, the developers should know that in this auto update, it wiped out my license, which prior updates did not do. cheers.
