Windows 10 LTSB 2016 and LTSC 2021 on Lab, Clinical and Shop-Floor Machines: A Guide to What Ends on October 13, 2026 and January 12, 2027, and the Path for Each Device

By Michael Branson

Quick answer. As of September 2026, Windows 10 Enterprise LTSB 2016 and Windows 10 IoT Enterprise LTSB 2016 end support on October 13, 2026 and Windows 10 Enterprise LTSC 2021 ends support on January 12, 2027, according to Microsoft, while Windows 10 IoT Enterprise LTSC 2021 moves to Extended Support that day and stays in support through January 13, 2032; Microsoft states that these releases are “NOT covered via the Windows 10 ESU program.” Microsoft Learn and Microsoft’s posts give each release its own options, among them a newer LTSC release if the device meets the hardware requirements, a release-specific Extended Security Updates offer where one exists, which Microsoft calls a temporary bridge, and, for Windows 10 Enterprise LTSC 2021 on fixed-function devices, an upgrade license to Windows 10 IoT Enterprise LTSC 2021. On a device its maker certifies, the maker decides first: Microsoft says to check with the device maker before an upgrade, and, according to Microsoft, the Extended Security Updates for Windows IoT Enterprise LTSB 2016 are sold only through the device’s manufacturer.

A vulnerability scan or an auditor flags Windows 10 machines that your Windows 10 Extended Security Updates plan did not cover, and those machines turn out to run a long-term servicing release: the lab analyzer, the imaging workstation, the test stand, the line PC, the kiosk. Two things you may have been told are each only partly true. That LTSC means ten years of support holds for the IoT edition: Microsoft’s Windows IoT Enterprise Release History says “Windows IoT Enterprise LTSC releases follow the Fixed Lifecycle Policy where each release is supported for 10 years and requires a separate license.” The Enterprise edition of LTSC 2021 ends on January 12, 2027, as the table below shows. That Extended Security Updates will cover these machines fails too, because the Windows 10 ESU program does not. This guide sets out what Microsoft’s and the FDA’s own pages, read on 2026-09-24, say for Windows 10 LTSB 2016 and LTSC 2021 on lab, clinical and shop-floor machines, edition by edition, and where the i3solutions recommendation sits beside them.

Before Any Date Applies, Find Out Which Edition Each Machine Runs

If the inventory says only “Windows 10”, it cannot tell you which date applies, because the dates differ by edition and release. Microsoft’s Windows Enterprise LTSC page on Microsoft Learn says “The long-term servicing channel was previously called the long-term servicing branch (LTSB).”, so LTSB 2016 and LTSC 2021 are two releases of the same channel. Its release table maps Windows 10 Enterprise LTSC 2021 to “Windows 10, Version 21H2” and Windows 10 Enterprise LTSC 2016 to “Windows 10, Version 1607”, and it advises: “Always check your individual LTSC release to verify its servicing lifecycle.”

The edition matters as much as the release. Microsoft’s Windows IoT Frequently asked questions page shows how to recognize an IoT Enterprise LTSC machine: in the Settings app, under System and About, the Edition field says “Windows 10 IoT Enterprise LTSC”, and the command dism /online /get-currentedition reports “IoTEnterpriseS”. Record the edition and release for every machine, never just “Windows 10”.

Some machines will turn out to be ordinary desktops that someone put on LTSC. Microsoft’s Windows Enterprise LTSC page says “The long-term servicing channel isn’t intended for deployment on most or all the PCs in an organization.” and “The LTSC edition of Windows provides a deployment option for special-purpose devices and environments.” Microsoft’s Windows IoT Enterprise LTSC in Volume License page adds that the IoT edition “is intended for use for fixed-function specialized devices only and cannot be used as a replacement of Windows desktop for general purpose computing.” A general-purpose PC on LTSC belongs in the organization’s Windows 10 fleet decision, not in this guide. Desktops already on Windows 11 version 23H2 Enterprise reach end of updates on November 10, 2026, and Windows 11 23H2 End of Updates and WSUS sets out the feature-update path and update channel for a regulated fleet.

What Ends on Each Date, and What Does Not

If two machines both show Windows 10 LTSC, they can still face different dates. Microsoft’s plain-text lifecycle pages give these dates, one row per edition:

Microsoft’s Ending Support in 2026 page lists the first row’s edition as “Windows 10 2016 LTSB”. The row to read twice is the fourth. On January 12, 2027 the Enterprise edition of LTSC 2021 ends, and the IoT edition of the same release only changes support phase. Microsoft’s Ending Support in 2027 page lists the IoT edition under “Products moving to Extended Support” and says “Extended Support includes security updates at no cost, and paid non-security updates and support.”

End of support is not a soft date. Microsoft’s Ending Support in 2026 page says “Upon retirement or end of support, there will be no new security updates, non-security updates, free or paid assisted support options or online technical content updates.” For the LTSB 2016 releases, Microsoft’s post Plan for Windows Server 2016 and Windows 10 2016 LTSB end of support says “your devices will receive a final monthly security update” on the end date, and Microsoft’s Windows IoT Enterprise Release History says “Windows 10 IoT Enterprise 2016 LTSB reaches end of support with a final monthly update on October 13, 2026.” For LTSC 2021, Microsoft’s post Plan for Windows 10 Enterprise LTSC 2021 end of support says “This release reaches end of support (EOS) on January 12, 2027.”

Why the Windows 10 ESU Program Does Not Apply, and What Microsoft Offers Instead

If the budget assumed these machines would ride on the Windows 10 Extended Security Updates plan, that assumption fails on Microsoft’s own words. Its Enable Windows 10 Extended Security Updates (ESU) for physical machines page says “Windows 10 Long Term Servicing releases (LTSB/LTSC) have their own lifecycles and are NOT covered via the Windows 10 ESU program.” Each release has its own terms instead:

• Windows 10 Enterprise LTSB 2016. Microsoft’s Plan for Windows Server 2016 and Windows 10 2016 LTSB end of support post says “Windows 10 Enterprise 2016 LTSB ESUs are available as of April 1, 2026.” and “Temporary solution: You can purchase Extended Security Updates for Windows 10 Enterprise 2016 LTSB for up to three years if you can’t upgrade to a newer version by October 13, 2026.” It adds “Extended Security Updates are now available for purchase through Volume Licensing or a Microsoft Cloud Solution Provider.”
• Windows 10 IoT Enterprise LTSB 2016. The same Plan for Windows Server 2016 and Windows 10 2016 LTSB end of support post says “Extended Security Updates for Windows IoT Enterprise LTSB 2016 are only available through IoT original equipment Manufacturers (OEMs).” Your route to them runs through the device’s manufacturer.
• Windows 10 Enterprise LTSC 2021. In a post dated August 5, 2026, Plan for Windows 10 Enterprise LTSC 2021 end of support, Microsoft wrote “ESU coverage for Windows 10 Enterprise LTSC 2021 will be available for purchase starting September 1, 2026.” The same post says “For Windows 10 Enterprise LTSC 2021, that means ESU coverage can run through January 8, 2030.”
• Windows 10 IoT Enterprise LTSC 2021. That Plan for Windows 10 Enterprise LTSC 2021 end of support post says “This Extended Security Update offer isn’t for Windows 10 IoT Enterprise LTSC. These devices remain in support through January 13, 2032.”

Read every one of those offers with its limits. Microsoft’s Plan for Windows Server 2016 and Windows 10 2016 LTSB end of support post says “The ESU program is not intended to be a long-term solution but rather a temporary bridge.” and “The ESU program offers critical and important security updates only (as defined by the Microsoft Security Response Center).” It also says the ESU program does not extend technical support for Windows 10 Enterprise LTSB 2016 or Windows IoT Enterprise LTSB 2016, and Microsoft’s LTSC 2021 post says “The ESU program doesn’t extend technical support for Windows 10 Enterprise LTSC 2021.” This guide states no price for any of these offers.

Choosing the Path for Each Machine

Once each machine’s edition and date are known, the decision is which of four paths it takes, and by when. Work through them in this order:

• A newer LTSC release of the same edition family. For LTSB 2016, Microsoft’s Plan for Windows Server 2016 and Windows 10 2016 LTSB end of support post names “Windows 11 Enterprise LTSC 2024 (if your devices meet the hardware requirements)” and Windows 10 Enterprise LTSC 2021, which itself ends on January 12, 2027, for the Enterprise edition, and “Windows 11 IoT Enterprise LTSC 2024 (if your devices meet the hardware requirements)” and Windows 10 IoT Enterprise LTSC 2021 for the IoT edition. Treat Windows 10 Enterprise LTSC 2021 as a destination only with its January 12, 2027 date written beside it. For Windows 10 Enterprise LTSC 2021, Microsoft’s LTSC 2021 post says “Upgrade to Windows 11 Enterprise LTSC 2024 for the latest security capabilities for these devices.”
• A change of edition, for Windows 10 Enterprise LTSC 2021 on a fixed-function device. Microsoft’s Windows IoT Enterprise LTSC in Volume License page says “Windows IoT Enterprise LTSC is now available as an upgrade license for fixed-function, specialized devices through Volume Licensing programs” and describes how “you install Windows 10 Enterprise LTSC 2021 then transform it into Windows 10 IoT Enterprise LTSC 2021 using a 5-by-5 volume activation key associated with the activation model that best suits your needs.” Its prerequisite: “The activation keys for Windows 10 IoT Enterprise LTSC 2021 require the installation of 2023-05 Cumulative update (10.0.19044.2905) or a more recent successor.” The same page limits it to “fixed-function specialized devices only”, so in Microsoft’s terms Windows 10 Enterprise LTSC 2021 can be changed to IoT Enterprise LTSC 2021 on that kind of device and no other. Whether a given machine qualifies is read from Microsoft’s terms by whoever owns your licensing; this guide does not decide it.
• An Extended Security Updates bridge, where the previous section shows Microsoft offers one. Put a written exit date on it, because Microsoft calls it a temporary bridge.
• A machine that stays past its date with no Extended Security Updates. This is the i3solutions recommendation, not a Microsoft or FDA statement: write a risk acceptance with a named owner and a review date, plan reduced network exposure with the device maker, and put the machine on the retirement list.

Microsoft sets two more conditions on the IoT Enterprise LTSC paths. Its What is Windows IoT Enterprise? page says “Upgrading from one version of Windows IoT Enterprise LTSC to the next version requires a new license.” and “When you utilize the LTSC, you must factor hardware into your decision, making sure you have a long-term supply of components for the expected life of your devices.” For the newer releases, Microsoft’s Ending Support in 2029 page lists October 9, 2029 as the end of support for Windows 11 Enterprise LTSC 2024 and as the date Windows 11 IoT Enterprise LTSC 2024 moves to Extended Support, and its Ending Support in 2034 page lists October 10, 2034 for Windows 11 IoT Enterprise LTSC 2024. Long-lived devices like these also need the Secure Boot certificate update, and Secure Boot Certificate Expiration in 2026 sets out how to update every Windows device and what goes on the exception list.

Whether the application on the device is worth extending at all is a separate question, covered in Are Our Current Systems Stable Enough to Extend, or Too Fragmented to Build On?.

On a Device Its Maker Certifies, the Maker Decides First

If the machine is part of a certified instrument or medical device, changing its operating system without the maker can break the certification you depend on. Microsoft’s Windows IoT Frequently asked questions page says “First, check with your device maker to determine what upgrade options are offered for the device.” and, on whether an upgrade to the newer LTSC is supported on your device, “Due to the specialized nature of Windows IoT devices, check with your device maker first for guidance”. Its What is Windows IoT Enterprise? page says “Devices that require regulatory certification and devices that perform a critical business function can’t accept feature updates for years at a time.” Microsoft’s Lifecycle FAQ – Windows says LTSC “is designed to be used only for specialized devices” and gives as examples “those that control medical equipment or automated teller machines (ATMs)”.

For medical devices, the FDA’s words are addressed to the device’s manufacturer, not to the hospital or lab that owns it. According to the FDA’s Cybersecurity in Medical Devices Frequently Asked Questions (FAQs), section 524B(c) of the FD&C Act defines a cyber device as one that includes software validated, installed or authorized by the sponsor as a device or in a device, has the ability to connect to the internet, and contains any such technological characteristics validated, installed or authorized by the sponsor that could be vulnerable to cybersecurity threats. The same page lists requirements on the maker, including “Design, develop, and maintain processes and procedures to provide a reasonable assurance that the device and related systems are cybersecure, and make available postmarket updates and patches to the device and related systems” and “Provide a software bill of materials, including commercial, open-source, and off-the-shelf software components”. It also says “As provided by the Omnibus, the cybersecurity requirements do not apply to an application or submission submitted to the FDA before March 29, 2023. If a cyber device was previously authorized, and the manufacturer is making a change to the device that requires premarket review by the agency, the law applies to the new premarket submission.”

The FDA’s guidance Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions says “Document issued on February 3, 2026.” and every page is headed “Contains Nonbinding Recommendations”. Its labeling recommendations ask manufacturers for “Information, if known or anticipated, concerning device cybersecurity (including components) end of support and end of life.” They note “At the end of support, a manufacturer may no longer be able to reasonably provide security patches or software updates.” and “If the device remains in service following the end of support, the manufacturer should have a pre-established and pre-communicated process for transferring the risks highlighting that the cybersecurity risks for end-users can be expected to increase over time.” Its software bill of materials elements include each component’s “end-of-support date”. On changes, it says “In general, changes that may impact cybersecurity and may require premarket submission could include changes to authentication or encryption algorithms, new connectivity features, or changing software update process/mechanisms.” Whether an operating-system move on a given device needs a submission is the manufacturer’s call, and this guide does not make it.

For industrial, lab and energy equipment, this guide cites no regulator; Microsoft’s What is Windows IoT Enterprise? page lists “industrial automation systems” among the fixed-purpose devices Windows powers, and the same maker-first rule applies. Ask each maker in writing for:

• the supported operating-system path for the device model, and its date;
• whether it offers the Extended Security Updates for Windows IoT Enterprise LTSB 2016;
• its end-of-support statement for the device;
• the operating-system entry in the device’s software bill of materials.

Change nothing on a certified device until that answer is on file.

The Record an Assessor Can Ask For, Machine by Machine

If an assessor asks what you are doing about these machines, the answer is a record with one row per machine, not a policy statement. Each row carries:

• the edition and release, read from the machine;
• Microsoft’s end date for that edition, from the table above;
• the chosen path and its date;
• the maker’s written statement, where the device is certified;
• for a machine that stays, the risk acceptance with its owner and review date.

Microsoft’s own advice on the Windows Enterprise LTSC page applies to every row: “Always check your individual LTSC release to verify its servicing lifecycle.”

When This Guide Is the Wrong Starting Point

If the machine in front of you does not fit the situation above, start somewhere else:

• If it is a general-purpose PC that happens to run LTSC, it belongs in the Windows 10 fleet decision for the rest of your desktops.
• If it is a shared or kiosk workstation that only presents an application and is not bound to an instrument, it may be a cloud desktop question rather than a device question.
• If it runs Windows 10 Enterprise LTSC 2019 or its IoT edition, it is not on these dates; Microsoft’s Ending Support in 2029 page lists January 9, 2029.
• If the question is about servers, that is a separate decision, and this guide states no server fact.
• If the question is about Office on these machines, that is a separate decision and is not covered here.

What to Ask of Whoever Does the Work

If you bring in outside help for these machines, hold the work to these criteria:

• Build the inventory by edition, release and maker, not by “Windows 10”.
• Name a path and a date for every machine.
• Collect the makers’ written statements before any change on a certified device.
• Have your licensing owner read eligibility for any edition change from Microsoft’s terms.
• Treat Extended Security Updates as a dated bridge with an exit.
• Expect senior, US-based people on the work.

Be plain about what stays with you. Patching and running these machines after the project remains your team’s work, or the device maker’s, as ongoing work; i3solutions does not take it on as an ongoing managed service. An i3solutions engagement does not produce managed-service ownership, a replacement for the internal team, open-ended scope expansion, or vendor lock-in.

How i3solutions Answers

If you want an outside architect on this decision, i3solutions takes on this planning as project work, with embedded specialists available where your team needs them. Delivery is senior and US-based. i3solutions plans and runs Intune migrations for enterprises moving domain-joined Windows devices off on-premises Group Policy. Designing Intune enrollment profiles for shared and kiosk devices is part of i3solutions’ Microsoft Intune Technology Readiness Services work. i3solutions has performed IV&V on software subject to FDA design-control expectations, including requirements traceability from controls through delivered functionality. That work is described in Third-Party Software Validation (IV&V) for FDA and ISO Regulated Software: What It Involves and What It Costs. The wider practice is governed, scalable enterprise modernization. For moving Windows devices off Group Policy more broadly, see the Intune migration checklist.

Key Takeaways

• On Microsoft Learn, Windows 10 Enterprise LTSB 2016 and Windows 10 IoT Enterprise LTSB 2016 end support on October 13, 2026, and Windows 10 Enterprise LTSC 2021 on January 12, 2027.
• On Microsoft Learn, Windows 10 IoT Enterprise LTSC 2021 moves to Extended Support on January 12, 2027 and stays in support through January 13, 2032.
• Microsoft Learn states that LTSB and LTSC releases are not covered by the Windows 10 ESU program; each release has its own terms, the Windows 10 Enterprise LTSC 2021 offer is not for the IoT edition, and, according to Microsoft, the offer for Windows IoT Enterprise LTSB 2016 comes only through the device’s manufacturer.
• On a certified device, the maker decides first; the FDA’s guidance on end of support is a set of nonbinding recommendations to manufacturers.
• Keep one record row per machine: edition, date, path, the maker’s statement and, for a machine that stays, a named owner.

Frequently Asked Questions

Does the Windows 10 ESU program cover Windows 10 LTSC or LTSB?

No. Microsoft Learn says “Windows 10 Long Term Servicing releases (LTSB/LTSC) have their own lifecycles and are NOT covered via the Windows 10 ESU program.”

When does support for Windows 10 IoT Enterprise LTSC 2021 end?

Windows 10 IoT Enterprise LTSC 2021 moves to Extended Support on January 12, 2027 and, according to Microsoft Learn, is supported through January 13, 2032. Microsoft’s blog post on LTSC 2021 says “These devices remain in support through January 13, 2032.”

Can we buy Extended Security Updates for Windows 10 LTSB 2016?

Yes, with conditions. Microsoft’s blog post on LTSB 2016 says “Windows 10 Enterprise 2016 LTSB ESUs are available as of April 1, 2026.” and that they can be bought “for up to three years if you can’t upgrade to a newer version by October 13, 2026,” while “Extended Security Updates for Windows IoT Enterprise LTSB 2016 are only available through IoT original equipment Manufacturers (OEMs).”

Can Windows 10 Enterprise LTSC 2021 be changed to IoT Enterprise LTSC 2021?

On fixed-function devices, yes. Microsoft Learn says “Windows IoT Enterprise LTSC is now available as an upgrade license for fixed-function, specialized devices through Volume Licensing programs” and it “is intended for use for fixed-function specialized devices only and cannot be used as a replacement of Windows desktop for general purpose computing.”

What does the FDA say about a medical device’s operating system reaching end of support?

The FDA’s guidance is written for device manufacturers and headed “Contains Nonbinding Recommendations”. It recommends that labeling include “Information, if known or anticipated, concerning device cybersecurity (including components) end of support and end of life.” and notes “At the end of support, a manufacturer may no longer be able to reasonably provide security patches or software updates.”

Planning the Decision

If your LTSB and LTSC machines need an inventory by edition and maker, a path and date for each one, or an Intune enrollment design for the shared and kiosk devices among them, the next step is a conversation about your estate.

Contact a senior architect