Windows 10: How does Microsoft store activation credentials?

NavyLCDR said:

Not always. Windows 10 setup will only pick the version to install for you if it finds a pre-existing indication on the computer itself as to which version should be installed. The order of preference Windows setup uses to predetermine which version should be installed is a PID.txt file (or other answer file) in the \sources folder of the install media, a product key stored in UEFI/BIOS, or a product key input by the user. If Windows setup does not find a product key or specified version to install by any of those methods, it does NOT default to Windows 10 Home. It will ask the user which version they want to install after clicking on "I don't have a product key".

On my two desktop PC's with legacy BIOS and no OEM embedded key, I get prompted to enter a key. If I click "I don't have one" the menu to select Home or Pro comes up. It does not auto install Home. That used to happen on my laptop. It has a Windows 8.0 Core OEM embedded key. If I didn't modify my install media with a PID.txt file, 10 Home was auto installed with no prompt for a key and no selection menu. Happily, the CU now ignores Windows 8 OEM keys. I get prompted for a key and can install what ever I want from the selection menu.

OK gonna get a bit technical now, but bear with me ...

Windows stores the licence details in database files called tokens.dat (in addition to registry dependencies for hash checks etc)... Legacy (non-DL) in the spp folder under system32... digital licences are classified as a store licence (gets lumped together with the apps downloaded from there and subject to renewal at certain intervals.. according to event log, anyway)
... and stored in the tokens.dat in programdata\microsoft\windows\clipsvc folder - each also uses their own services to activate as well...

@SIW2
I recall a post of yours @ EF regarding Jim's CAPS thingy.. he's still got it LOL

Back to topic...

Why the need for an efi.cfg when installing CU?

jimbo45 said:

Hi there
@NavyLCDR

I always LIKE your posts and agree usually 100% of the time - but in this case unfortunately you are INCORRECT --just try wiping your HDD and installing the CU edition FROM SCRATCH after first having done an update via the usual methods.

Your windows update edition needs to be AT LEAST version 1703 -- any earlier versions then of course what I'm posting here is BONKERS. I.E use a CU 1703 ISO or rufus bootable USB with 1703 on it - and install after an initial update from a previous version of Windows . (I mean here that your CURRENT running edition should be the 1703 version after you did an UPGRADE -- not a clean install -- from a previous version). If you aren't already running 1703 then do the upgrade FIRST before the clean install.

So to update to 1703 from a previous version of windows do the following :

a) take backup of existing installation so you don't have to re-do after the next step. (Macrium etc -- so you can restore if it doesn't work).

b) wipe HDD and install clean the 1703 ISO

Please try a CLEAN update and see what happens -- even a VM should be a good enough test. The default always is HOME unless you fix the ei.cfg file like I've posted previously.



Cheers
jimbo

I've done numerous clean installs with stock install media, AU and CU, and they DO NOT auto install the Home edition as default. You first prompted for a product code. Enter one and the matching edition is installed. Click "I don't have one" and you'll get a selection menu. If its an MSDN ISO the options are Home or Pro. If its the MCT ISO your options are Home, Pro Education, and I think Home SL. If yours is installing Home maybe its because you added an ei'cfg?

EDIT: Home may be highlighted, pre selected in the selection menu but you can easily change that with one mouse click. Unless your just blindly clicking every yes button that comes up.

Superfly said:

@SIW2
I recall a post of yours @ EF regarding Jim's CAPS thingy.. he's still got it LOL

Back to topic...

Why the need for an efi.cfg when installing CU?

You don't need it.

jimbo45 said:

...@Comp Cmndo

I'm not sure I want a TPM module in my computer --Who knows --CIA / Trump / N.Korea or whatever -- that type of chip could really sink any computer privacy FOREVER....

You might have one now & you never would know.
Earlier TPM versions did less. Had one a couple years ago on a used Dell laptop, where the BIOS (not UEFI) had many settings locked. Needed the proprietary Dell software to unlock it. It can also be cleared by shorting the correct pins of the TPM & there is more than one variation of the chip.