Share via

Had to reload windows 10 IoT Ent 2021 LTSC

TM 0 Reputation points
2026-03-13T17:38:03.43+00:00

Asking for windows activation keys. Keys were not provided by supplier but I have a tag on my

server for Win 10 IoT Ent 2021 but its not a Win license but it does have some numbers that may reference a windows key.

Thanks

Windows for business | Windows for IoT
0 comments No comments

2 answers

Sort by: Most helpful
  1. Sean Liming 4,811 Reputation points Volunteer Moderator
    2026-03-13T17:42:56.1933333+00:00

    The numbers on the sticker are for tracking only. The sticker is used by the OEM to track where systems are shipped too. The numbers are not the product key required to activate the system.

    Typically, Windows 10 IoT Ent 2021 LTSC is for OEMs building devices like and ATM machine, industrial controls, medical device, etc. The OEMs should supply support for system recovery. I would recommend that you go back to the manufacturer to get assistance on recovering the OS.

    Can you explain what your device is?

    0 comments No comments

  2. Q&A Assist
    2026-03-13T17:38:16.27+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Windows 10 IoT Enterprise LTSC 2021 requires a valid product key from the appropriate licensing channel; it cannot be activated using numbers printed on a generic hardware tag or device label that is not explicitly a Windows product key.

    For Windows IoT Enterprise LTSC, activation is done using one of these models:

    1. Volume Licensing (Enterprise/IT scenarios)
      • Requires either a Multiple Activation Key (MAK) or activation via Key Management Service (KMS).
      • The KMS client setup key for Windows IoT Enterprise LTSC 2021 is: KBN8V-HFGQ4-MGXVD-347P6-PDQGT This is a generic KMS client key only; it does not itself grant a license. It is used when activating against an existing KMS host in the organization.
      • Licensing assets (media and MAK/KMS keys) must be obtained from the organization’s Volume License Administrator via programs such as MPSA, MCA, or Select Plus. If the supplier did not provide a key, the Volume License Administrator or Microsoft Account Manager must be contacted to obtain the correct key.
    2. OEM / Device-maker scenarios (PKEA, ePKEA, OA 3.0)
      • OEMs building specialized devices must enable activation before the device leaves the factory using one of:
        • PKEA (unique 5×5 key per device),
        • ePKEA (embedded key with a fixed activation count), or
        • OA 3.0 (key stored in firmware, discovered automatically by Windows).
      • If the device was originally shipped by an OEM with Windows IoT Enterprise preinstalled, the OEM is responsible for providing or embedding the activation key. If the reloaded image no longer activates automatically, the OEM or Windows IoT Distributor must be contacted to obtain the correct key or recovery media.

    If no product key was provided and there is no access to a Volume License key, KMS infrastructure, or OEM activation key, activation cannot be completed. In that case, the next step is to contact:

    • The Volume License Administrator or Microsoft Account Manager if the device is licensed via Volume Licensing, or
    • The Windows IoT Distributor/OEM that supplied the device if it is an OEM IoT device.

    The numbers on the server tag alone are not sufficient unless they are explicitly documented as a Windows product key or are tied to an OEM activation mechanism (such as OA 3.0) that the reinstalled image is configured to use.


    References:

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.