LTSC 2021 vs. IoT LTSC 2021: tips on installations
Local Link | Content link | Reddit Link
r/Windows10LTSCu/etherealshatter (198) 18+

In this post, "Windows 10 Enterprise LTSC 2021" will be referred to as "non-IoT", and "Windows 10 IoT Enterprise LTSC 2021" will be referred to as "IoT".

Q: What's the difference between non-IoT and IoT?

A: They are essentially the same, except:

||non-IoT|IoT| |:-|:-|:-| |Lifecycle end date|Jan 12, 2027|Jan 13, 2032| |Generic key type|KMS|RTM| |Generic key embedded in the ISO file|M7XTQ-FN8P6-TTKYV-9D4CC-J462D|QPM6N-7J2WJ-P88HH-P3YRH-YY74H| |Activation method|KMS|Digital License (HWID)| |Languages available for ISO files|All native languages available, such like en-gb, fr-fr, de-de, etc.|Only en-us "English (United States)" is available.|

Q: If I want IoT, can I install with the ISO file of the IoT version, which is only available in en-us, then later on install language packs of my choice?

A: Yes. However, keep in mind that in some cases it will not be the same as installing from an ISO file in the native language. For exmaple, if you install with an en-us ISO, then install the en-gb language pack, then you could get the pesky "English (United States)" keyboard layout coming back again and again. It is recommended that you do a clean installation in the native language you want, e.g. install en-gb non-IoT, then switch to IoT (see below), so that you get IoT in native language "English (United Kingdom)".

Q: Can I switch between non-IoT and IoT after installation?

A: Yes. You can freely switch between these two at any time by changing the key (see generic keys in the table above). Right-click on Start menu, run "PowerShell (Admin)", type in the following command:

slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

Q: How can I activate?

A:

For genuine MSDN subscribers: you activate non-IoT with the KMS server of your institute, or activate IoT with the MAK key provided by your institute.

For home users: as per sub rules, no linking of pirated content, thus I will not provide any link here for activators. Just search for MAS.

================================================================================

Edit: MAS 1.5 may already support LTSC 2021. The section below were written for MAS 1.4 at the time of making this post and may be skipped:

MAS 1.4 will fail for IoT with the following error:

==== ERROR ====
[Windows 10 IoT Enterprise LTSC 2021 | 19044 | SKU:191] HWID Activation is Not Supported.
Press any key to exit...

However, simply modify the code for the SKU value in HWID_Activation.cmd:

Line 679:

191-IoTEnterprise

and lines 761-763:

:IoTEnterprise
set "key=QPM6N-7J2WJ-P88HH-P3YRH-YY74H"
exit /b

Then IoT activates permanently with HWID.

Comments (66)

For complete noobs like myself...

If you are activating Windows 10 IoT Enterprise LTSC 2021:

MAS 1.4 is an activator which contains a file called HWID_Activation.cmd, which fails if not modified.

Download Notepad++ which gives you numbered lines in txt files and edit the HWID_Activation.cmd at lines 679 and 761-763 as mentioned above.

​

Before: 679

188-IoTEnterprise

Modified:

191-IoTEnterprise

​

Before: 761-763

:IoTEnterprise
set "key=XQQYW-NFFMW-XJPBH-K8732-CKFFD"
exit /b

Modified:

:IoTEnterprise
set "key=QPM6N-7J2WJ-P88HH-P3YRH-YY74H"
exit /b

For anyone reading this in the future, newer versions of MAS fix this. I just used MAS 1.7 and it worked fine.

I am from the future, and I, thank you.

Would modifying the key for IoTEnterprise as shown above also fix the all-in-one script? Or is it a bit more complicated than a simple search-and-replace?

I'm not sure, I never tried it, I only used the HWID file in isolation. I presume it's using the code from that file when you implement HWID patch. I guess it should work all-in-one but if all the code is baked into the all-in-one, then you'd have to find the line code and change that for the all-in-one too.

do I have to edit in MAS 1.5 as well?

1.4 was the last official build at the time, so it needed to be updated. I presume 1.5 has been updated. I don't know though

I can add one thing about IoT. This may sound obvious to some, but LTSC IoT 2021 will not pickup during the installation and will not activate with the LTSC IoT 2019 license key embedded in your device.

I happen to have a Thin Client device with LTSC IoT 2019 license and it works fine with LTSC IoT 2019, but not 2021.

Windows 10 ltsc 2019 key not working on win 10 ltsc 2020? Where i can buy key for new version of ltsc?

Yes you'll need a new MAK key. My Microsoft reseller has not replied to me yet so I don't know the SKU number yet.

Microsoft reseller? I thought those only did home and pro keys.

You usually get volume license through Microsoft partners

Those keys are for LTSC 2019, are they valid?

KMS key for non-IoT is the same as 2019. RTM key for IoT is different from 2019.

How can I upgrade my current LTSC 1809 to LTSC 2021?

Some people have had success by simply downloading the LTSC iso, mounting it, running setup.exe and upgrading that way.

However I would recommend fresh installing the 2021 version of LTSC. That's what I did and it works flawlessly - just backup your files first of course ;)

Thanks! Just did a fresh install. Just checking, is the latest version 21H2 (19044.1288)?

your 1809 key worked on 21H2?

Old thread, but it did for me.

I just did `slmgr.exe /ipk KEY` with the generic key from the .iso and it let me upgrade in place from 2019 LTSC (winver 1809) to 2021 IoT LTSC (winver 21H2)

Sorry could you explain a bit more? Are you saying that you didn't have to reinstall windows, you just put the new 2021 IoT LTSC key in by typing that command in, and then it updated from 2019 to 2021 (assuming it downloaded the updated files form windows update?)

I believe I upgraded my old Windows 10 Enterprise 2019 LTSC install by running that command with the generic key from the 2021 IoT iso. Then I upgraded in place using the iso.

Ah great, thank you. I just did the same as you.

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

"In place" meaning I ran setup.exe and upgraded my existing install "in place"

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

AFAIK this should work for properly changing the "native" language of a Windows install (e.g. enables uninstalling the original language pack): https://winaero.com/upgrade-to-a-different-language-of-windows-10-from-the-installed-one/

So in other words, as a home user, you can't just buy a key for use on Non-IoT?

For anyone wondering about language of IoT: You can just install the normal LTSC in your language via iso, then use MAS with HWID activation and it will convert to IoT. The language will stay the same.

[deleted]

will using mas 1.6 be enough to activate it

Did you download an IOT version or a regular LTSC?
But either way, yes MAS should work. Try it.

thus I will not provide any link here for activators. Just search for MAS.

For anyone having trouble finding MAS (since it is pretty ambiguous) search instead for:

  • MAS Microsoft activation script

... which will take you to massgravel's github page.

Is there a legitimate iso download from MS or a KMS upgrade path that ends in either non-IoT or IoT ?

Tried going from Enterprise but that seems to fail.

Im having difficulties trying to find a download location for the IoT version. Is there somewhere it still exists?

Did you find the answer?

I did end up finding on google somewhere.

Im new to ltsc, which version should i install, non iot or iot

IoT, longer support date and hwid activation

[deleted]

Generic keys are not secrets. They're publicly available directly from Microsoft's website. They're embedded into the official ISO files. It's required for genuine license users. Genuine license users can switch between different editions by applying generic keys without having to re-install (supported by Microsoft's official docuemnt).

I've made changes to the OP to reflect this so people won't mistake it for piracy purposes.

You are correct; consider my objection withdrawn. Sorry!

caused a good discussion, so thanks!

[deleted]

Maybe there was a misunderstanding here, as there are both EnterPrise IoT and Enterprise LTSC IoT versions available. LTSC IoT is same as normal LTSC (no Store etc.), while IoT is the same as normal Windows Enterprise and comes with Store and other stuff.

May I ask for clarification on this statement: "Then IoT activates permanently with HWID."

What does 'permanently' mean? I was under the impression based on posts here & MDL that HWID constantly (relatively speaking) calling back to Microsoft to double check the HWID. Your post makes it seem like it's one and done. Anyone or /u/etherealshatter know the true answer?

  • HWID: Microsoft acknowledges and stores your hardware information in their database. Every time the system connects to the Internet, it checks the hardware information (e.g. the serial number of your motherboard) against the database at Microsoft. If it checks out, then it will not inactivate. If your device is disconnected from the Internet for many years, your system still retains the activated status. However, if major hardware change happens (e.g. motherboard replaced), activation status is lost until the system can find a valid entry in Microsoft's database for your new hardware.
  • KMS: By default the system loses activation if it cannot reach a KMS server for 180 days. The system needs to refresh its activation status by connecting to a KMS server. KMS38 forces the system not to check until a very long time later, but the deadline is bound by the technical limitation of the "Year 2038 problem".

"HWID: Microsoft acknowledges and stores your hardware information in their database. Every time the system connects to the Internet, it checks the hardware information (e.g. the serial number of your motherboard) against the database at Microsoft. If it checks out, then it will not inactivate. If your device is disconnected from the Internet for many years, your system still retains the activated status. However, if major hardware change happens (e.g. motherboard replaced), activation status is lost until the system can find a valid entry in Microsoft's database for your new hardware."

Thank you for the thoughtful response! If no hardware changes, Does Win10 IoT continuously do 'checks' to the MS servers? In other words, I install IoT LTSC 2021, it sends my Mobo SN#, no hardware changes -- does my system send pings back to tell MS everything is good?

I don't know whether it keeps checking, but it doesn't really matter, as HWID has been the standard method for Home and Pro editions for many years, and won't deactivate unless major hardware change happens.

KMS on the other hand would deactivate if you lose connection to the KMS server for a continuous 180-day period (or after year 2038 if you use KMS38).

TY sir very useful info

If I installed Non-IoT but wanted IoT (en-uk), at what point should I activate? After installing Non-IoT or after using the slmgr command to 'switch' ?

After you have switched

How can I get a license for Windows 10 ltsc 2021 officially?

You can't, they're only given out to corporations, so you could ask your employer.

Do LTSC 2019 license key work with LTSC 2021?

Short answer is no.

The purpose of LTSC is in it's definition: Long Term Service Channel.

These are aimed at devices that are always on, always available. Feature upgrading would cause too much downtime and negate the point of having LTSC. This is why you get a guaranteed 10 year license with it. (IoT only since LTSC 2021). These are aimed at ATM's/KIOSKS/POS or physically inaccessible devices.

I'm not sure why people are buying/using it when their use case is clearly more suited to Windows 10 Pro Enterprise.

Please compare Win 10 Enterprise vs Win 10 LTSC. The newer 2021 LTSC app loading and execution seems significantly faster than LTSC 2019. That's on m.2 main drive, i5 8265u, 16+gb laptop.

Because Pro isn't really Pro like 7 Pro used to be.

There are plenty of scripts out there to remove Windows Store, Cortana, and all the other Windows apps from Pro and it will become like Enterprise and you still get all the updates for the OS without having to worry about keys or re-installing the OS.
There are also plenty of tools out there to legitimately customise the Pro ISO to be more like LTSC OOBE. This saves a lot of cost on Pre-Built PCs.

You're mostly right, but a few minor quibbles that made (IoT) Enterprise LTSC marginally more attractive for me (and apparently others):

- Enterprise SKUs support a lower level of telemetry (0:Security [basically off] vs 1:Required [apparently it's not "required" then...]). While many telemetry services and tasks can be manually disabled, there's no exhaustive list of them and it can give more peace of mind to know that you've also disabled telemetry through the "front door" route.

- LTSC SKUs receive security updates for a longer period of time. IoT Enterprise 2021 LTSC is supported through 2032, which is another peace-of-mind feature.

- LTSC SKUs come with almost no bloat installed, and it's marginally more preferable to not have the bloat in the first place than to remove it through (sometimes) unapproved/unintended methods.

- IoT Enterprise has recently added a Soft Real-Time feature (still under development iirc) that can be handy for users who want to drive microcontrollers, run professional audio applications, etc. while staying on the Windows ecosystem.

​

Given that you can get an IoT Enterprise 2021 LTSC license code for like $15, and the ISO is readily available online, these are enough to persuade me and most others on this subreddit to go for an LTSC edition.

Is it still possible to activate these offline? I know for LTSC2019 I got a MAK key as well as a KMS key. I was able to call and activate the MAK key, but it was annoying.

There is one other caveat - you cannot use Windows Sandbox on the IoT edition of LTSC 2021. Windows Sandbox on non-IoT works fine, AFAIK.

Not so quite.While install "vclibs" via Powershell and restart your computer. After this Windows Sandbox works in Windows IoT...

Can you switch from LTSC N to IoT using slmgr or does slmgr work on non N LTSC only to switch to Iot?

.

Hello. I just recently found out that the keys for non-IoT and IoT are in fact different. I bought two legit Enterprise LTSC keys from a reseller and downloaded the IoT ISO but when I activate it it always switches to non-IoT. Can anyone help me out here?

try ask in MAS discord