Windows 7 -> Windows 10 key, getting a Microsoft Account, etc

[King_V]

Alright, so, something of an odd situation here.

I was given an old PC back in October, a Dell XPS 630i. It was originally a Vista machine downgraded to XP. However, the original owner, some time later, was part of MSDN, and had purchased a Windows 7 Pro license.

I'm not clear if she never installed it on this machine, or tried to install it but the machine went kaput before finishing, or if it was completely installed at one point, and then things went sour afterward.

In any case, the partitions on the hard drives were hosed, so I used some 3rd party partitioning tool on a bootable USB to delete and recreat the partitions.

I then used the Windows 10 installer on a bootable USB to install the OS. It accepted the Windows 7 Pro license key, and installed Windows 10 Pro for me. All is well and happy.

HOWEVER.... at this time, I do not have a Microsoft account. There's a possibility that, at some point, I may want to build my own PC, and then use this license to install Windows 10 Pro on the new machine, and removing the OS from the 630i (I assume this would be required).

What do I have to do, exactly? I mean, I'm not even clear what Microsoft knows/thinks about the current install - if they have this license key tagged as still being owned by the original owner of the 630i or with her (maybe no longer valid) MSDN account, or what.

I want to make sure that whatever I do, I do legitimately. Any suggestions on what steps I should take here?

 

[Dark Lord of Tech]

I doubt the MSDN key will activate.

 

[Jwpanz]

Was the old license on the old computer a pre-installed license? Or, was the license bought separately and installed onto the old system? A pre-installed version can not be transferred between two different machines. If you have a full retail version then you can. Take a look at this article: https://www.howtogeek.com/261053/when-can-you-move-a-windows-license-to-a-new-pc/

You would have to deactivate Windows on your old system before activating Windows 10 on your new system using the installer tool.

 

[captaincharisma]

this is the procedure to reactivate windows 10 after a major hardware change like replacing a motherboard although i am not sure if this would work if you are trying to use the same licence(if its OEM) to reactivate it on a completely new computer

http://www.windowscentral.com/how-re-activate-windows-10-after-hardware-change

 

[King_V]

Ah, yes, let me clarify - to the best of my knowledge, the Windows 7 Pro license key was purchased separately by the original owner subsequent to purchasing the Dell 630i, and was a full license, not OEM. The Dell 630i in question originally came with Windows XP.

I do not know if that Windows 7 Pro license had ever been successfully installed, though, prior to my using it.

 

[Dark Lord of Tech]

Contact Microsoft support they will gladly give you the status of the key.

 

[captaincharisma]

Ah, yes, let me clarify - to the best of my knowledge, the Windows 7 Pro license key was purchased separately by the original owner subsequent to purchasing the Dell 630i, and was a full license, not OEM. The Dell 630i in question originally came with Windows XP.

I do not know if that Windows 7 Pro license had ever been successfully installed, though, prior to my using it.

if the key has never been used then you can enter it in settings after the windows install. if it has been used then you have to find out what type of licence an MSDN key has. it could act either as a retail or volume licence

 

[Dark Lord of Tech]

You will need the MSDN account info too.

 

[King_V]

Well, it installed successfully when I did it in October, but might still be associated with the previous owner. I'm now curious to see if this is a volume license or not.

I'll have to see what I can do, as, erm, well, unfortunately, the previous owner and I are currently on less than amicable terms. That could potentially get "interesting" and not in the fun way.

 

[captaincharisma]

if you already have windows installed with that key then you can check what key it is by going to "run" and type in this command

slmgr.vbs /dlv al

it will say something like retail or OEM channel in the info that appears

http://www.thewindowsclub.com/view-licensing-status-activation-id-windows-slmgr

 

[King_V]

Ok, when I do it without the "all" option, it's definitely retail, and it says this:

Name: Windows(R), Professional edition
Description: Windows(R) Operating System, RETAIL channel
...
Product Key Channel: Retail
...
Remaining Windows rearm count: 1001
Remaining SKU rearm count: 1001

Not sure exactly what that all means...

With the "all" option, there's like 28 entries, the one I showed above, which has a Partial Product Key, and 27 others. The 27 others all have these 4 lines in common:

This license is not in use.
License Status: Unlicensed
Remaining Windows rearm count: 1001
Remaining SKU rearm count: -1


But the descriptions vary for each of them, and for each entry, is among one of these:
Description: Windows(R) Operating System, OEM_DM channel <--- 8 of these
Description: Windows(R) Operating System, VOLUME_KMS_W10 channel <--- 4 of these
Description: Windows(R) Operating System, OEM_COA_NSLP channel <--- 3 of these
Description: Windows(R) Operating System, VOLUME_KMSCLIENT channel <--- 3 of these
Description: Windows(R) Operating System, VOLUME_MAK channel <--- 4 of these
Description: Windows(R) Operating System, RETAIL channel <--- 6 of these (including one in use)


What the heck does all that mean? I can't possibly have over 2 dozen licenses, can I?

 

[King_V]

Additionally, the Names are varying as well from that list:

Name: Windows(R), Professional edition <--- 19 of these
Name: Windows(R), Enterprise edition <--- 4 of these
Name: Windows(R), ProfessionalEducation edition <--- 5 of these


And, finally, one of each of the above names, all three of which are the VOLUME_KMSCLIENT type, say the following at the end:

Configured Activation Type: All
Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.