Microsoft is officially putting a clock on several 2016‑era Windows releases, and IT teams now have a clear deadline to get migration plans off the whiteboard and into production. Over the next 12–18 months, Windows 10 Enterprise 2016 LTSB, Windows 10 IoT Enterprise 2016 LTSB, and Windows Server 2016 will all reach end of support (EOS), meaning no more security patches, bug fixes, or technical assistance once their final updates ship. For organizations that still rely on these platforms, Microsoft is offering a paid Extended Security Updates (ESU) program as a temporary safety net, but the company’s guidance is unmistakable: treat ESU as a bridge, not a destination.
In a recent Windows IT Pro Blog post, Microsoft lays out the key dates and upgrade recommendations for these products, while positioning ESU as what it calls “the gift of time” for complex environments that can’t move quickly enough. The article confirms that Windows 10 Enterprise LTSB 2016 and Windows 10 IoT Enterprise 2016 LTSB will hit EOS on October 13, 2026, with Windows Server 2016 following on January 12, 2027. On those dates, devices will receive a final monthly security update; after that, they’re effectively frozen in time from a support perspective.
What actually ends in 2026 and 2027
Three specific SKUs are in scope for this wave of lifecycle changes: Windows 10 Enterprise LTSB 2016, Windows 10 IoT Enterprise 2016 LTSB, and Windows Server 2016. The desktop and IoT editions share the same end‑of‑support date—October 13, 2026—while the server counterpart remains supported until January 12, 2027. After those dates, Microsoft will no longer ship security updates, non‑security updates, or bug fixes for these versions, and official technical support and online content updates will cease as well.
These releases sit in the Long‑Term Servicing Branch (LTSB), now called the Long‑Term Servicing Channel (LTSC), a servicing model Microsoft positions for specialized devices that require minimal feature churn, such as medical systems, industrial controllers, embedded kiosks, and dedicated line‑of‑business endpoints. That original stability promise is one reason many organizations have stayed on 2016 builds for so long, especially when hardware refreshes or app certification cycles lag behind mainstream Windows development.
ESU: a bridge, not a strategy
To reduce the shock of a hard cutoff, Microsoft is extending its ESU program to cover these products for up to three years beyond their EOS dates. ESU for these SKUs provides only critical and important security updates as defined by the Microsoft Security Response Center; it does not deliver new features, quality fixes, design changes, or extended technical support beyond help with activating ESU licenses, installing ESU updates, and troubleshooting issues caused by those patches. Put simply, ESU keeps the lights on from a security standpoint while you finish migrating, but it does not evolve the OS in any other way.
For Windows 10 Enterprise 2016 LTSB, ESU will be available through Volume Licensing and Microsoft Cloud Solution Providers starting in the second quarter of 2026. Year one pricing is set at 61 USD per device, with a discounted rate of 45 USD per device for systems managed via Microsoft Intune or Windows Autopatch. The cost doubles each consecutive year for up to three years, and ESU is cumulative: enrolling in year two requires paying for year one as well, and joining in year three triggers charges for all three years. That structure is intentionally punitive—it buys time, but it gets increasingly expensive the longer you stay behind.
Windows 10 IoT Enterprise 2016 LTSB follows the same high‑level pattern but uses a different sales channel. ESU for IoT devices will only be available through IoT original equipment manufacturers (OEMs), meaning organizations must work directly with their device vendors or distributors for pricing and purchasing. The same cumulative, doubling‑every‑year model applies, though exact per‑device costs will be set by each OEM. For many customers, hardware constraints or tightly integrated embedded solutions will make ESU a necessary short‑term option while device replacement programs ramp up.
For Windows Server 2016, Microsoft is again offering up to three years of ESU coverage post‑EOS, but detailed server pricing and licensing mechanics have not yet been published and are expected in a later communication. The company’s preferred path is clear: customers should plan to upgrade to Windows Server 2025 wherever possible and reserve ESU for scenarios where migration cannot be completed by January 2027.
Recommended upgrade destinations
On the server side, Microsoft recommends treating Windows Server 2025 as the primary target for customers coming off Windows Server 2016. That move not only restores full support and feature innovation but also aligns organizations with current security baselines, virtualization improvements, and hybrid cloud integrations that are not available on older versions. For many shops, this will coincide with broader refreshes of Hyper‑V, Active Directory, and on‑premises workloads that integrate tightly with Azure.
For desktop and specialized endpoints, the recommended landing zone depends heavily on hardware capabilities. Where devices meet modern hardware requirements, Microsoft advises upgrading to Windows 11 Enterprise LTSC 2024, the newest long‑term servicing option for enterprise deployments. If hardware limitations block a move to Windows 11, Windows 10 Enterprise LTSC 2021 remains a viable intermediate step that keeps devices on a supported, stable branch without forcing them into the rapid feature cadence of general Windows 10 releases.
Similarly, for IoT scenarios, Microsoft points customers toward Windows 11 IoT Enterprise LTSC 2024 on compatible hardware, or Windows 10 IoT Enterprise LTSC 2021 when a full platform jump is not yet feasible. This is especially relevant for industrial control systems, medical equipment, and embedded kiosks, where validation cycles and regulatory certifications can make OS upgrades far more complex than a typical PC refresh.
How IT should respond now
With end‑of‑support dates and ESU pricing finally on the table, organizations running 2016‑era Windows should start by performing a thorough inventory: identify which devices are still on Windows 10 Enterprise 2016 LTSB, Windows 10 IoT Enterprise 2016 LTSB, and Windows Server 2016, and categorize them by criticality, hardware readiness, and application dependencies. From there, teams can segment their estate into three buckets: systems that can be upgraded before EOS, systems that require ESU as a temporary stopgap, and systems that should be targeted for retirement or replacement.
Budget planning is another urgent step. Because ESU costs double each year and are cumulative, waiting to enroll can have a significant financial impact, especially at scale. Organizations that expect to need the full three‑year ESU runway for certain devices should model the total per‑device cost—up to 427 USD over three years for non‑discounted Windows 10 Enterprise 2016 LTSB systems, or roughly 315 USD for Intune/Autopatch‑managed endpoints—and weigh that against the capital and operational expenses of accelerating hardware and OS upgrades instead.
Finally, Microsoft is encouraging customers to stay plugged into its lifecycle communications channels, including the Windows message center, Tech Community, and official ESU FAQ pages, for evolving details on pricing, availability, and best practices. For organizations that are still living in the 2016 generation of Windows, the message is straightforward: the “gift of time” is real, but it’s limited and increasingly expensive, and the smartest move is to use it to get onto modern LTSC releases as quickly as possible.
Recent Posts You Might Like
- Japan Raids Microsoft Japan Over Massive Alleged Azure Anti‑Monopoly Violations
- MWC 2026: Microsoft Supercharges Telecom AI with Powerful Azure Local and Sovereign Edge
- Windows 11 KB5077239: What’s New in the February 24, 2026 Preview Update
- Microsoft Pushes ‘Agentic SOC’ with Defender Autonomous Defense and Expert‑Led Security Services
Discover more from Microsoft News Now
Subscribe to get the latest posts sent to your email.
