Mindjet lost license key after update

  • 1
  • Question
  • Updated 3 years ago
  • Answered
  • (Edited)

Hi, I just checked for updates  (NOT Upgrades) and Mindjet found one. So, I decided to install the update.

Since than Mindjet lost my license key ... this is extremely annoying because now I have to search for a license key within our organization.

Please can someone repair this bug!

And while at it, it would be great to support touch on Windows 8 at least for navigating - or is there a trick for touch scrolling/ pinching on Windows Version?



Photo of Jenik


  • 1 Post
  • 0 Reply Likes
  • frustrated and annoyed

Posted 6 years ago

  • 1
Photo of Marian Kocmanek

Marian Kocmanek, Official Rep

  • 465 Posts
  • 102 Reply Likes
Hi Jenik, 

Please open a ticket with our support team here - https://secure.mindjet.com/app/support.aspx

Installing an update should not have removed the license key. 
Photo of Carl Lachmann

Carl Lachmann

  • 2 Posts
  • 0 Reply Likes
The same thing happened to me as I went to the latest version - 17.2.208. So the bug was probably never repaired. Mindjet support sends me to our IT department. So I spend time and they will spend time - all because Mindjet is perhaps not totally solid on their update process...
Photo of Ary Velstra, Expert Trainer

Ary Velstra, Expert Trainer

  • 1890 Posts
  • 339 Reply Likes
Strange... this could happen only if you Upgrade to a newer release e.g. from MM 2016 to MM 2017. It is obvious you should have a license key that fits the newer version when you do that.
But at least you can work with the newer version fully functional in the trial period

If you are Updating from an earlier MM2017 version, MindManager automatically uses the key you have for that release.

Most of the time, When and If your IT department is responsible for installs and licensing, -common- users are blocked from installing new versions, since they need System Admin authorization for that.
Photo of Carl Lachmann

Carl Lachmann

  • 2 Posts
  • 0 Reply Likes
Hi, thanks for the input. To me it is like a typical bug.