Which Windows Should You Put on an Industrial PC? — A Practical Guide to Windows IoT Enterprise / LTSC

“One morning, the inspection PC we delivered with the equipment suddenly had a different-looking desktop, and the camera capture software wouldn’t start.” — When we investigated this on behalf of an equipment manufacturer, the cause turned out to be the Windows 11 annual feature update. Because a commodity PC with Windows 11 Pro had been built into the equipment, a major update was applied overnight, leaving the equipment software running on an OS version nobody had validated. We also get the opposite enquiry: “we left feature updates blocked for a few years, and at some point support ran out and the security updates stopped arriving too.”

A PC built into a piece of equipment is expected to keep running through the same roughly ten-year lifecycle as the equipment itself. Ordinary Windows 11 (GAC: General Availability Channel), however, gets a feature update every year, and each version goes out of support in two to three years. This mismatch between “equipment time” and “OS time” is the first problem to get straight when choosing Windows for an industrial PC.

This article is aimed at equipment manufacturers and manufacturing engineers selecting the Windows PC to embed in industrial cameras, inspection equipment, and production machinery. It organises the LTSC (Long-Term Servicing Channel) and IoT Enterprise options in terms of the edition line-up, support periods, licensing routes, functional differences, and the points developers need to watch — backed by Microsoft’s official documentation.

1. The Bottom Line First

• The first choice for a PC embedded in equipment is Windows 11 IoT Enterprise LTSC 2024. It is supported for ten years, until 10 October 2034, and during that time no feature updates arrive — only the monthly quality updates (security fixes).¹²
• Windows 11 Enterprise LTSC 2024 — the one without “IoT” — gets five years (until 9 October 2029). Even for the same LTSC 2024, the fact that only IoT Enterprise LTSC comes with ten years of extended support is the single biggest fork in the road.³⁴
• Windows 11 on the General Availability Channel (GAC) gets a feature update every year. Each version is supported for 24 months on the Home/Pro line and 36 months for Enterprise/Education/IoT Enterprise (GAC). Keeping a machine running for ten years means going through major updates and re-validation many times over.⁴
• LTSC does not include the Microsoft Store or the standard apps that evolve through feature updates. It is a configuration for special-purpose devices and is not intended for rollout across general-purpose office PCs.⁵
• For IoT Enterprise licences, new devices mean procuring an OEM licence through an authorised distributor (an embedded distributor). Volume licensing is available as a route only for upgrading existing devices. Always confirm the terms with your distributor.⁶⁷
• On the Windows 10 generation, Windows 10 IoT Enterprise LTSC 2021 can be used until 13 January 2032. It is also a realistic destination for extending the life of hardware that does not meet the Windows 11 requirements. Note, though, that the minimum requirements for the IoT edition of Windows 11 are substantially more relaxed than for general-purpose PCs (TPM and Secure Boot optional, 2 GB/16 GB), so check the requirements table before giving up.⁸⁹
• On the equipment software side, three things are essential: don’t create dependencies on features LTSC lacks, manage the .NET runtime support period separately, and design the operational handling of quality updates and reboots. .NET Framework 4.8 is supported for the same period as the OS, but modern .NET gets three years even on LTS.¹⁰¹¹

2. Why Ordinary Windows 11 Doesn’t Suit Equipment — The GAC Timeline

On the General Availability Channel (GAC), Windows 11 receives a feature update in the second half of each year (24H2, 25H2, and so on), and each version is supported for 24 months on Home/Pro/Pro Education/Pro for Workstations and 36 months on Enterprise/Education/IoT Enterprise/Enterprise multi-session.⁴

In concrete numbers, that looks like this.⁴

Note that 26H1 is an exceptional first-half-of-the-year release, limited to new devices brought to market in the first half of 2026, and is not offered as a feature update (an in-place update from 24H2/25H2) to existing devices. Furthermore, it is stated explicitly that the IoT Enterprise edition does not support 26H1, so if you choose GAC for equipment use, the relevant versions remain the 24H2/25H2 line.⁴

In other words, building a commodity PC running Windows 11 Pro into your equipment leaves you with a choice between “accepting an annual-to-biennial feature update and re-validating the equipment software every time” and “blocking updates and going out of support in two years”. The former runs against the fundamental principle on the shop floor of never changing a working configuration, and because a feature update is a major update that replaces the internals of the OS, compatibility problems with drivers and resident software really do occur. The latter means placing equipment that receives no security updates on a customer’s network, which in recent years gets rejected during the purchaser’s security audit.

Temporarily deferring feature updates (deferral by policy or pinning a version) is possible on GAC too, but it does not extend the support deadline itself, so it is not a fundamental fix. The right answer is to choose a channel that matches the equipment’s timeline from the outset.

3. Making Sense of the Edition Line-Up — How Pro / Enterprise / LTSC / IoT Relate

Windows client editions become much clearer when you organise them along three axes: the “feature set” (Pro / Enterprise), the “servicing channel” (GAC / LTSC), and the “licensing route” (general retail / volume licensing / OEM embedded). IoT Enterprise is, in substance, a derivative of Enterprise, characterised by a licensing model for fixed-purpose devices and long-term support.⁷

⁴³¹⁶

There are two key points.

• LTSC exists only on the Enterprise line. There is no “Pro LTSC”, so if you want long-term fixed operation it is either Enterprise LTSC or IoT Enterprise LTSC.
• Even for the same LTSC 2024, the support period differs by a factor of two depending on whether “IoT” is in the name. Windows 11 Enterprise LTSC 2024 gets five years; Windows 11 IoT Enterprise LTSC 2024 gets ten. Microsoft’s release information states explicitly that “Enterprise LTSC 2024 has no extended support, and only IoT Enterprise LTSC 2024 is extended to 2034”.⁴

Incidentally, the “IoT” in IoT Enterprise LTSC does not mean a cut-down version for sensors. Under the hood it is full Windows, equivalent to Enterprise, and kiosk mode (Restricted User Experience) and other lockdown features are available.⁷²

4. Pinning Down the Support Periods in Numbers

So you can use it directly in a selection meeting, here is a list of the LTSC support deadlines. All dates are the values from Microsoft’s lifecycle pages.

¹³⁸⁷

Some notes on how to read this.

• Ten-year support for LTSC without “IoT” ended with the LTSC 2019 generation. From 2021 onwards, if you want ten years, IoT Enterprise LTSC is the only choice.
• New LTSC releases are announced as arriving roughly every three years (the timing does vary).⁷ That means there is a good chance the next LTSC will appear around 2027, and the question “do we ship the equipment we’re designing now on the 2024 release, or wait for the next one?” comes up periodically. If you do decide to wait, factor into your estimate that upgrading between LTSC releases requires a new licence.²
• Windows 11 IoT Enterprise LTSC 2024 is equivalent to Windows 11 24H2 under the hood, and has been available to OEMs since 22 May 2024.² From this generation it supports Arm64EC, allowing x64 applications to run under emulation on Arm64 processors without modification, which brings Arm-based low-power, fanless industrial boards into consideration as well.²

The options after the end of mainstream support for Windows 10 (ESU, re-platforming onto LTSC, migrating to Windows 11) are organised in detail in the sister article published the same day, “Practical Options After Windows 10 End of Support”.

5. Licensing Routes — OEM Licences and Embedded Distributors

The acquisition route for the IoT Enterprise line differs considerably from ordinary Windows. It is not on the shelves of retailers nor on Microsoft’s own direct sales site, and the Microsoft Learn licensing page sets out the following two routes.⁶

In practice, this breaks down as follows.

• When an equipment manufacturer puts it on equipment it newly manufactures, an OEM licence is the only choice. You procure it through a Microsoft authorised distributor (what is generally called an embedded distributor), complete activation before the unit leaves the factory, and transfer the licence to the end user along with the equipment.⁶
• If you are only replacing the OS on an existing equipment PC with LTSC, a volume licensing upgrade licence can be used. It is offered through programmes such as the Microsoft Customer Agreement and MPSA, but it is limited to “upgrading a device running an eligible existing OS” and cannot be transferred.⁶
• For evaluation purposes, a 90-day evaluation edition is available at no cost. It is quite sufficient for running the full equipment software stack on real LTSC hardware during the selection phase to confirm compatibility.²

Note that OEM licence minimum order quantities, pricing, support contacts, and the kind of development assistance offered all vary from distributor to distributor and over time. We deliberately avoid quoting specific figures in this article, but some distributors will accommodate orders of a single unit, so before concluding “we only build a few units a year, so it’s out of the question”, talk to an embedded distributor first. IoT Enterprise also carries conditions of use as a fixed-function device (usage restrictions under the EULA), so it is safest to confirm at the same time whether your intended use fits the licence terms.⁶

6. What LTSC Doesn’t Provide — Store, Standard Apps, and Compatibility Caveats

In exchange for “not changing the features for ten years”, LTSC excludes from the outset those elements that evolve through feature updates. Microsoft’s official description states that LTSC receives only the monthly quality updates and does not include things that keep getting updated with new features, such as the standard (in-box) apps.⁵ Note that the official description also lists Microsoft Edge as an example of something “not included”, but that refers to the Windows 10-generation LTSC; as covered in the next point, the 2024-generation LTSC does ship with Edge.

The points most likely to bite in practice are these.

• There is no Microsoft Store. Because you cannot use the Store’s distribution and update route, you cannot depend on codecs or runtimes distributed only via the Store, or on in-house tools distributed through the Store. The winget package manager is not installed by default either, so if you need it, arrange separate distribution of the installer.
• The UWP standard apps such as Mail, Calendar, and Photos are not included. For equipment use they are almost always unnecessary — indeed it becomes an advantage that “no superfluous apps change behaviour after an update”.
• The browser differs by generation. Windows 11 Enterprise LTSC 2024 / IoT Enterprise LTSC 2024 ship with Microsoft Edge as the default browser. Internet Explorer and WordPad, on the other hand, were removed in this generation (IE mode is still available).¹²²
• LTSC support from third-party tools is not guaranteed. Microsoft itself cautions that “LTSC support for apps and tools designed for GAC may be limited” and that “because the feature set does not change, some third-party tools may drop legacy support over time”.⁵¹² Whether the antivirus software, asset-management agents, and other software your customer mandates support LTSC is something to check before deployment.

For that reason, it is more accurate to think of LTSC not as “an OS that is missing features” but as “an OS whose features have been frozen for special-purpose devices”. Microsoft also states plainly that it is not intended for rollout across an organisation’s PCs generally, but is an option for special-purpose devices that perform a single critical task.⁵

7. Points for Equipment Software Developers — .NET, Windows Update, and Long-Run Design

Being able to fix the OS for ten years is meaningless unless the design and operation of the equipment software running on it can keep pace. Here are four issues developers need to get right.

Don’t create dependencies on features LTSC lacks

If the development machine is ordinary Windows 11 Pro while the delivery target is LTSC, you will get incidents where something that worked on the dev machine doesn’t work on the real hardware. Typical culprits are components that rely on automatic distribution from the Store, integration with standard UWP apps (invoking the default mail client, for example), and dependencies on new APIs added by a feature update. Verifying behaviour on the 90-day LTSC evaluation edition in a CI-like fashion from early in development lets you detect this class of dependency mechanically.

The .NET runtime support period is a separate account from the OS

• The .NET Framework 4.8 line is defined as a component of Windows and is supported for the same period as the OS it is installed on.¹⁰ On Windows 11 IoT Enterprise LTSC 2024, that works out to security updates arriving at no additional cost until 2034 — an outstanding match for equipment software that has to run for a decade.
• Modern .NET goes out of support after three years, even on LTS releases. For instance, .NET 8 (LTS) runs to 10 November 2026, and .NET 10 to 14 November 2028.¹¹ On equipment running for ten years, you will need to swap the runtime at least three times, each requiring re-validation and on-site update arrangements.
• Which one to choose comes down to “can you maintain a process for updating the runtime after delivery?” Equipment on a closed network that is expected to be maintenance-free suits .NET Framework 4.8; if you can update on a regular cycle under a maintenance contract, modern .NET is a realistic option.

Design how Windows Update is controlled

With LTSC there are no feature updates, but the monthly quality updates — and the reboots that come with them — still arrive.² It is far from unusual for inspection equipment running around the clock to stop during the night shift because of a monthly-update reboot. Design active hours and reboot policy settings, separate validation rings for updates (internal test machine → customer standby system → production), and, for closed environments, documented procedures for WSUS or offline application — and treat all of that as part of what you deliver. It only works in practice when combined with a mechanism for the equipment software to come back automatically after an update (running it as a service, or automatic start-up and monitoring via reliable operational design for Task Scheduler).

Fixing the OS doesn’t solve long-run bugs

When we get an enquiry along the lines of “we moved to LTSC and the equipment still becomes unstable after a few weeks”, the cause is usually not the OS but resource leaks or power settings on the equipment software side. Cases we have investigated are written up in separate articles.

• Long-run crashes caused by handle leaks: Investigating Long-Run Crashes of an Industrial Camera App - The Handle Leak (Part 1)
• Intermittent stalls with a network cause: Why TCP Retransmissions Stall Industrial Camera Communication, and How to Isolate Them
• Power and sleep settings: Sleep, Hibernation, Modern Standby, and Long-Running Apps — Designing Around ‘It Stopped Overnight’
• Throttling of background processing: What Is Windows Efficiency Mode? - The Green Leaf Icon and How to Turn It Off, Windows Processor Scheduling Settings - Background Services and P/E Cores

OS selection (this article) and long-run design (the above) are independent problems, and you only get a “PC that runs for ten years” when both are in place.

8. Practical Rules of Thumb (Decision Table)

One additional point: before you conclude that a board “doesn’t meet the Windows 11 requirements”, always check the minimum requirements table for IoT Enterprise. The requirements for general-purpose Windows 11 are TPM 2.0, UEFI + Secure Boot, 4 GB of memory, and 64 GB of storage, but Windows 11 IoT Enterprise LTSC defines a separate set of OPTIONAL minimum requirements for special-purpose devices, relaxed to TPM and Secure Boot optional, BIOS firmware permitted, and 2 GB of memory / 16 GB of storage.⁹ An industrial board that fails the general-purpose compatibility check may still be able to run LTSC 2024, usable until 2034 (there is a separate supported-processor requirement, so check that too).

9. Summary

• Selecting a PC to embed in equipment is a matter of aligning two timelines: “the equipment’s ten years” and “the OS support period”. Ordinary Windows 11 (GAC) gives 24 months on the Pro line and 36 months on the Enterprise line and assumes annual feature updates, so it does not suit equipment with a fixed configuration.
• The prime candidate for long-term fixed operation is Windows 11 IoT Enterprise LTSC 2024 (ten years, to October 2034). The biggest trap is that Enterprise LTSC 2024 — the one without “IoT” — gets only five years.
• On the Windows 10 generation, IoT Enterprise LTSC 2021 can be used until January 2032. It is a destination for extending the life of hardware and assets that cannot move to Windows 11.
• For the IoT Enterprise line on new devices, you procure an OEM licence through an embedded distributor. Quantities, pricing, and terms are all subject to confirmation with the distributor.
• LTSC does not include the Microsoft Store or the update-driven standard apps. For equipment use this is if anything an advantage, but eliminate any dependencies by testing on real hardware with the evaluation edition.
• Even with the OS fixed, the .NET runtime support period, the operational handling of monthly updates and reboots, and long-run bugs such as resource leaks all need to be designed for as separate problems.

Related Articles

• Practical Options After Windows 10 End of Support
• Investigating Long-Run Crashes of an Industrial Camera App - The Handle Leak (Part 1)
• Why TCP Retransmissions Stall Industrial Camera Communication, and How to Isolate Them
• Sleep, Hibernation, Modern Standby, and Long-Running Apps — Designing Around ‘It Stopped Overnight’
• What Is Windows Efficiency Mode? - The Green Leaf Icon and How to Turn It Off
• When Task Scheduler Tasks Don’t Run or Exit with 0x1 — Isolating the Cause and Designing for Reliable Operation

Related Consulting Areas

KomuraSoft LLC provides support for selecting the OS for Windows PCs embedded in industrial cameras, inspection equipment, and production machinery, porting equipment software to LTSC environments and verifying compatibility, and designing and troubleshooting equipment-integration software intended for 24-hour operation. You are welcome to consult us from the “which Windows will last us ten years?” stage.

• Soft Real-Time Windows Application Development
• Windows Application Development
• Technical Consulting & Design Review
• Contact Us

References

Related Articles

Recent articles sharing the same tags. Deepen your understanding with closely related topics.

Related Topics

These topic pages place the article in a broader service and decision context.

Frequently Asked Questions

Common questions about the topic of this article.

What is the difference between Windows 11 Pro and Windows 11 IoT Enterprise LTSC?

The biggest differences are the support period and how feature updates are handled. Pro exists only on the General Availability Channel (GAC), where each version is supported for just 24 months, on the assumption that you keep taking the annual feature updates. IoT Enterprise LTSC is an edition for fixed-function devices that receives no feature updates: Windows 11 IoT Enterprise LTSC 2024 receives only the monthly quality updates (security fixes) for ten years, until October 2034. Because the feature set does not change for a decade, it suits uses such as inspection and production equipment where the rule is "don't change a configuration that works". On the other hand, note that the Microsoft Store and some of the standard UWP apps are not included.

Where can I buy a Windows IoT Enterprise LTSC licence?

If you are preinstalling it on equipment you manufacture, the standard route is to procure an OEM licence through a Microsoft authorised distributor (an embedded-systems distributor). It is not sold individually through electronics retailers or the Microsoft Store. Purely for replacing the OS on an existing device, there is also a volume licensing route (an upgrade licence), but it cannot be applied to new devices. Minimum order quantities, pricing, and contract terms vary by distributor and over time, so always check with an embedded distributor.

I hear LTSC has no Microsoft Store. Is that a problem in practice?

For equipment use it is rarely a problem, but you do need to check in advance. LTSC does not include the Microsoft Store, nor the standard apps such as Mail and Calendar that evolve through feature updates. You will get stuck if you depend on codecs or runtimes distributed only via the Store, or on in-house tools distributed as Store apps. If the equipment software is an ordinary desktop application (Win32/.NET), there is unlikely to be any impact — but the reliable approach is to build in a step early in development where you run all the functionality on real LTSC hardware (a 90-day evaluation edition is available at no cost).

Is it acceptable to newly adopt Windows 10 IoT Enterprise LTSC 2021 now?

Support runs until 13 January 2032, so it is a realistic option if you want to keep using Windows 10-generation drivers and equipment software assets as they are. In practice it is still being adopted for extending the life of industrial boards that simply cannot meet the Windows 11 supported-processor requirement, and for equipment using SDKs whose operation is only guaranteed on Windows 10 (if the only shortfall is TPM or Secure Boot, the relaxed requirements for the IoT edition of Windows 11 may solve it, so check that first). Bear in mind, though, that around five and a half years remain, so if the equipment is expected to run for ten years the maths says you will need an OS update partway through its lifecycle. If this is a new design and you can also select new hardware, we recommend making Windows 11 IoT Enterprise LTSC 2024 — usable until October 2034 — your first choice.

How should I choose the .NET version for equipment software running on LTSC?

The .NET Framework 4.8 line is defined as a "component of Windows" and is supported for the same period as the OS itself, which makes it the best match for LTSC operation where the OS is fixed for ten years. Modern .NET (.NET 8/10 and so on), by contrast, goes out of support after three years even on LTS releases, so for equipment running for a decade you need to build several runtime updates into the operational plan. The practical framing is: .NET Framework 4.8 for equipment you want to remain maintenance-free for a long time; modern .NET if you prioritise development productivity and performance and can put a runtime-update process in place. In either case, it is important to settle at the contract stage who will handle runtime vulnerability remediation after delivery.

Author Profile

Profile page for the article author.

Go Komura

Representative of KomuraSoft LLC

Focused on Windows software development, technical consulting, and investigations into failures that are difficult to reproduce.