New
#460
Tweet
— Twitter API (@user) View on Twitter
@simrick Hello. Nice to hear from you again. Something that might be of interest about Malwarebytes Premium. Have used the lifetime licence without issue for quite some time on the old laptop that eventually failed. Usually while upgrading or clean install on the same PC I had no issues activating the licence. This time the motherboard failed so the laptop went to the 'dumpster'. Right word?
Installed on another old Tosh laptop still running IP on the old laptop's log in details and activation failed. Raised a ticket with Malwarebytes and after a few days they were very helpful. They've reactivated it and this is their reply;
"Dee S. (Malwarebytes Support)
Jul 20, 16:35 PDT
Hello,
My name is Dee and I'm from Malwarebytes Consumer Support. I will be helping you with your ticket # 2019128.
The issue with the license is that the number of times the license has been activated has exceeded the threshold it’s set for. You mentioned that you run Windows 10 Insider evaluation copies, and had to do clean installs; this likely caused your license to reach its activation limit.
The license is a single PC system lifetime license and should not be activated to more than 1 system at a time.
I’ve cleared the activation history for the license so you should be all set to activate the license without issue now.
I would recommend that in future, you should deactivate your license before doing any work on your PC's operating system or hardware, before reformatting your hard drive, or before moving your license from one PC to another.
Please continue to use the license key that begins with xxxx, as that was a replacement license for one that was not in our records. "
'Not in our records' was a puzzle?
Anyway, hope the information is of some value.
Last edited by Fabler2; 21 Jul 2017 at 10:58.
This build is continuing to work well on my machine, keep up the good work.
Yes!
Nice of them to reset the activation history for you. I can see where deactivating could help with Insider builds and multiple clean installs. Perhaps she was using a canned response, and forgot to edit that part out about the license not being in the system? Anyways, glad you've got it sorted! :)