How do you downgrade Windows 11 IoT Enterprise LTSC 2024 CSP to Windows 10 Enterprise 2016 LTSB?

Windows 11 IoT Enterprise LTSC 2024 cannot be changed in place to Windows 10 Enterprise 2016 LTSB; first confirm that the specific CSP agreement grants rights to the non-IoT 2016 edition, then clean-install it using authorized legacy media and activate it with the corresponding MAK or KMS infrastructure.

The screenshot already shows Windows 10 Enterprise 2016 LTSB as installed and activated. If that screenshot is from the intended device, no OS downgrade remains to be performed; verify that its existing activation is covered by the organization’s license agreement.

1. Confirm the exact downgrade entitlement

Windows 11 IoT Enterprise LTSC and ordinary Windows Enterprise LTSC are separate licensing products. Access to an ISO or product key does not by itself establish entitlement to use the non-IoT edition.

Ask the CSP provider or Microsoft Volume Licensing Support to confirm in writing that the purchased SKU permits running:

• Source: Windows 11 IoT Enterprise LTSC 2024 CSP
• Target: Windows 10 Enterprise 2016 LTSB, non-IoT
• Version: 1607
• Architecture: x64

Also request the authorized Windows 10 Enterprise 2016 LTSB media and applicable MAK/KMS activation rights. Volume Licensing customers can locate available downloads and keys under:

Microsoft 365 admin center → Billing → Your products → Volume licensing → View downloads and keys.

Viewing keys requires the VL Administrator or Product keys reader role. Microsoft documents that VL customers can use earlier-version keys for downgrade/reimaging purposes, but the product entitlement must still cover the requested edition.^1^

If the agreement covers only Windows 10 IoT Enterprise 2016 LTSB, do not deploy non-IoT Windows 10 Enterprise 2016 LTSB; obtain the matching IoT media and key from the CSP/OEM instead.

2. Verify hardware and driver support before wiping

The pictured computer uses an Intel Core i3-8100. The supplied Windows 10 LTSB 1607 processor-support documentation does not establish support for that processor.^2^

Before deployment, obtain confirmation from the computer or motherboard manufacturer that Windows 10 version 1607 supports its:

• Processor and chipset
• Storage controller
• Graphics
• Ethernet/Wi-Fi
• USB and attached peripherals

Download the 1607-compatible storage and network drivers before installation. Otherwise, Setup might not detect the disk, or the installed system could lack working networking and other devices.

3. Perform a clean installation

A product key cannot downgrade Windows 11 to Windows 10. Microsoft explicitly lists changing to an earlier Windows version by entering another key as unsupported; an unsupported path requires a clean installation.^3^

Warning: A clean installation removes installed applications, settings, domain configuration, and potentially all data on the selected disk.

1. Back up data, application installers, configuration, recovery keys, certificates, and required drivers.
2. Obtain the official, non-evaluation Windows 10 Enterprise 2016 LTSB x64 ISO through the authorized licensing channel.
3. Create bootable installation media using the deployment method approved by the organization.
4. Boot the device from that media.
5. Select Custom: Install Windows only.
6. Select the intended system partition and complete Setup.
7. Install vendor-approved chipset, storage, graphics, and network drivers.
8. Install all updates still available for the release, then rejoin the domain and restore applications/data.

Windows 10 Enterprise 2016 LTSB corresponds to Windows 10 version 1607.^4^

4. Activate the installation

Run Command Prompt as a local administrator.

For MAK, use the key supplied for Windows 10 Enterprise 2016 LTSB:

slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr.vbs /ato
slmgr.vbs /dlv
slmgr.vbs /xpr

For KMS, the documented Windows 10 Enterprise LTSB 2016 client setup key is DCPHK-NFMTC-H88MJ-PFHPY-QJ4BJ.^5^

slmgr.vbs /ipk DCPHK-NFMTC-H88MJ-PFHPY-QJ4BJ
slmgr.vbs /ato
slmgr.vbs /dlv
slmgr.vbs /xpr

That public KMS client key is not a license and will activate only when the device can reach an appropriately configured organizational KMS host.

Support status

Windows 10 Enterprise 2016 LTSB and Windows 10 IoT Enterprise 2016 LTSB reached end of support on October 13, 2026.^6^ Continued security updates now require an eligible paid Extended Security Updates (ESU) subscription. Microsoft documents ESU prerequisites for both 2016 editions; IoT ESU MAKs must be obtained from the OEM partner.^7^

References

1. Find and use product keys for volume licensing
2. Windows 10 LTSB 1607 Supported Intel Processors
3. Windows edition upgrade
4. Windows Enterprise LTSC
5. KMS client activation and product keys
6. Ending Support in 2026
7. Enable Extended Security Updates (ESU) for Windows 10 LTSB 2016 and Windows 10 Enterprise LTSC 2021