Possible Product Key problem?

K

kosmo

Member
Messages
82
Reaction score
27
I'm attempting to install a NTL-modded copy of W10-Iot-LTSC-21 to a Dell Optiplex 5070. I initialized the new SSD as GPT and then let setup configure the disk and install the OS. It coppied all the files but then choked at what appears to my (very inexperienced view) to be a possible Product Key issue. Here's the error:

View attachment 12269

and here's the section of the unattended install script that it seems to be pointing at:

<settings pass="specialize">
<component name="Microsoft-Windows-Security-SPP-UX">
<SkipAutoActivation>true</SkipAutoActivation>
</component>
<component name="Microsoft-Windows-Shell-Setup">
<ComputerName>Opti5070</ComputerName>
<CopyProfile>false</CopyProfile>
<ProductKey>KBN8V-HFGQ4-MGXVD-347P6-PDQGT</ProductKey>
</component>
</settings>

Note that the Product Key in the UI script is the KMS key that M$ specificies for the "IoT LTSC 21". But as garlin pointed out in this post setup checks the computer firmware for an embedded Product Key. Suppose that it found an existing key - almost certainly for W10 Pro - and was also presented with a different version of the OS that a user was attempting to install. Would it refuse to finish the install? (even though the presented key was correct for the OS being installed)

And if this is true is there any way to to install W10-iot-LTSC-21 to this computer? Can the embedded key be removed? Or hidden? Or am I on the wrong track?
 

Attachments

Unattended mode provides two different fields for a Product Key:
- WindowsPE for installation​
- Specialize pass for Windows activation​

LTSC/LTSB is a volume-licensed product, there are no individual keys because you will use a KMS license server or a MAK key.

KBN8V-HFGQ4-MGXVD-347P6-PDQGT is the generic key to get through a Windows install. It doesn't belong in the specialize pass. Legitimate LTSC/LTSB systems are normally licensed by enterprises using some form of scripted action.

We do not discuss KMS activation methods on this forum, especially since most of the methods involve software piracy.

Retail product keys (not a Generic install key) can be entered once, or twice, since it fulfills the activation role. Generic install keys can never be used for activation, and should not be entered in specialize. Windows can always be installed without activation, as the built-in SPP service will begin nagging you to activate shortly after installation.
 
You must log in or register to reply here.
Back
Top