ShowKeyPlus  

Interesting, any idea why is 2013 different? I can understand for lease versions but that does not need a key.

Was Office 2013 when Microsoft started providing Office 365? That may have changed some of the licensing.

cereberus said:

Interesting, any idea why is 2013 different? I can understand for lease versions but that does not need a key.

Not sure M, prolly 'cause of piracy - Office was MS' cash-cow for a long time - the key is stored now in encrypted format in the licence data file tokens.dat (like MAK's)

Berton said:

Was Office 2013 when Microsoft started providing Office 365? That may have changed some of the licensing.

Yep, oddly enough, on Click-2-Run installations the key is stored in the registry unencrypted.. 'suppose due to those being primarily preview versions so, no fuss, as opposed to retail.

cereberus said:

Interesting, any idea why is 2013 different? I can understand for lease versions but that does not need a key.

Starting with O2013, you had to login to your MS account, enter your key, and install (usually an online install, but if you clicked around enough, you could find the ISO for download). So, they had, your installs and your key stored in your profile. Good for people who need to reinstall and have lost their key, actually, as long as they know what MS account they used, they can get it.

simrick said:

Starting with O2013, you had to login to your MS account, enter your key, and install (usually an online install, but if you clicked around enough, you could find the ISO for download). So, they had, your installs and your key stored in your profile. Good for people who need to reinstall and have lost their key, actually, as long as they know what MS account they used, they can get it.

Yep. I purchased my keys cheap-cheap through HUP.. never used an MSA.

Superfly said:

Yep. I purchased my keys cheap-cheap through HUP.. never used an MSA.

Ah yes. No HUP here....

Yup .... I need to change that exception message ... what that is, is that the pk config does not recognise the key as it uses latest GA release files...Anything subsequent will be unrecognised. I will have to redirect to installed config files should that exception occur. Thanx for pointing this out

lx07 said:

Not sure if this is a bug but I activated 16257 ProfessionalWorkstation with generic key. This key is identified OK but when I check it using the "Check Product Key" option get the error message "Key not supported by this OS"

This should be working correctly now in new release v1.0.6477.

Superfly said:

This should be working correctly now in new release v1.0.6477.