A Stupid Question About Windows 10 Product Keys

Hello All,
So I am happily running Windows 10 build 10240, and I' m loving it. There is so much talk here at The Windows Ten Forum regarding exactly what will happen on July 29th, and how each person is going to receive and activate their public release version of Windows 10, that I decided to use a program called Magical Jelly Bean Key Finder to find out exactly what is the product key of my Windows 10. I found out that the product key that is shown is vastly different than any in this list:
Download Windows 10 Insider Preview ISO File - Windows 10 blog

or this list;

How to activate the latest Windows 10 build - Microsoft Community

Also, the key is different than the product key of my original Windows 8 (and 8.1) OS that I have installed on my machine. It is important to note that I do not run Windows 10 in a virtual machine, it is primary OS. Also, I did not do a clean install of Windows 10, I went the upgrade route over my Windows 8.1. So what gives? Where did this new and different product key come from?

Hello All,
So I am happily running Windows 10 build 10240, and I' m loving it. There is so much talk here at The Windows Ten Forum regarding exactly what will happen on July 29th, and how each person is going to receive and activate their public release version of Windows 10, that I decided to use a program called Magical Jelly Bean Key Finder to find out exactly what is the product key of my Windows 10. I found out that the product key that is shown is vastly different than any in this list:
Download Windows 10 Insider Preview ISO File - Windows 10 blog

or this list;

How to activate the latest Windows 10 build - Microsoft Community

Also, the key is different than the product key of my original Windows 8 (and 8.1) OS that I have installed on my machine. It is important to note that I do not run Windows 10 in a virtual machine, it is primary OS. Also, I did not do a clean install of Windows 10, I went the upgrade route over my Windows 8.1. So what gives? Where did this new and different product key come from?

I don't know.

I'd bet, however, that you could not use that key to clean install 10240 from an .iso. If you learn otherwise, please let us know.

Thanks. I am going to do some more research into this enigma.

Has anybody else investigated their product key? I am curious to find out if everybody is experiencing the same thing as I am.

Build 10162

Did a clean install and skipped all the points where I was asked for a product key. Windows activated itself anyway, lol? So, I changed the product key to the officail one: 8N67H-M3CY9-QT7C4-2TR7M-TXYCV.

Just had a look in the registry (HKLMSOFTWAREMicrosoftWindows NTCurrentVersionDigitalProductId) and I too have a completely different product key.

I upgraded my VM from 10166 to 10240, key is as expected: Windows 10 Build 10240 for PC is now available

Windows 10 Pro build 10240 - VK7JG-NPHTM-C97JM-9MPGT-3V66T

Same key on my Toshiba laptop that was upgraded from 10166 to 10240.

I upgraded my VM from 10166 to 10240, key is as expected: Windows 10 Build 10240 for PC is now available

Windows 10 Pro build 10240 - VK7JG-NPHTM-C97JM-9MPGT-3V66T

Same key on my Toshiba laptop that was upgraded from 10166 to 10240.

Today I upgraded a W7 machine using that key.

It installed without hitch but would not activate. There was a message to use the key that is printed on the box the DVD came in.

Maybe I should try a clean install?

Build 10162

Did a clean install and skipped all the points where I was asked for a product key. Windows activated itself anyway, lol? So, I changed the product key to the officail one: 8N67H-M3CY9-QT7C4-2TR7M-TXYCV.

Just had a look in the registry (HKLMSOFTWAREMicrosoftWindows NTCurrentVersionDigitalProductId) and I too have a completely different product key.

It seems like that key is for 32bit OS, and HKLMSOFTWAREMicrosoftWindows NTCurrentVersionDigitalProductId4 is for 64bit OS. I'm running 64bit; regardless, the key under that location is different as well.

OP, is the Jelly Bean software you used checking for 32bit or 64 bit keys?

Anyway, I assume Microsoft is just assigning unique keys to the preview builds during activation or something similar.

I also have had all sorts of keys that I didn't recognize! I am just quietly confidant that MS will sort out my system, updated from 8.1, come 29 Jul.

Try Showkey as I think that is better at finding keys.

Thanks to everybody that posted to help me sort this riddle out. Mine is 64 bit and I will try Show Key, but as was pointed out upthread, I am sure that Microsoft knows what it is doing.