★ First page of Microsoft's 100,000-partner directory, sorted by responsiveness✓ Microsoft Solutions Partner — Security, Modern Work, Infrastructure, App Innovation, Data & AI● Microsoft partner since 2006◆ 1,100+ organizations under management

The One Server You Cannot Replace: Keeping a Legacy Application on Windows Server 2016 or Windows 10 Supported with ESU Through Arc, Windows IoT Enterprise LTSC, or Isolation

Every estate has one: an application whose vendor will not certify anything newer than Windows Server 2016 or Windows 10, on a machine nobody may switch off. Windows Server 2016 and Windows 10 Enterprise LTSC 2021 both leave support on 12 January 2027. Here are the four supported ways to keep that one box, with October 2026 list prices and what an auditor will accept.

The four options, answered first

Four paths keep a legacy application supported, and the right one turns on one question for the vendor: is the application supported on a client edition of Windows? If yes, a rebuild on Windows 10 IoT Enterprise LTSC 2021 or Windows 11 IoT Enterprise LTSC 2024 buys a perpetual $295 license supported until 13 January 2032 or 10 October 2034 (Microsoft list price, October 2026 price list). If not, Windows Server 2016 Extended Security Updates (ESU) buy up to three years from 12 January 2027, monthly per core through Azure Arc or annually through volume licensing. If neither is possible, isolation behind written controls with an exit date. Replacement is the only permanent path.

Option Supported until List price Needs from the vendor An auditor will accept
ESU year one, Azure Arc or volume licensing Three years from 12 January 2027; Arc bills from 13 January 2027 Per core: Standard $124 per 2-core pack, $496 per 8-core pack, per year; Datacenter $720 or $2,880; Software Assurance, Server Subscription or SPLA required Nothing Yes, with the license record and patch report
Rebuild on Windows IoT Enterprise LTSC 2021 or 2024 13 January 2032 or 10 October 2034 $295 per device, perpetual, plus the rebuild A support statement naming a client edition; fixed-function use Yes: a supported operating system
Isolation with compensating controls No vendor support; the controls carry the risk until the exit date No license; firewall, vault, EDR and backup, plus engineering time Nothing, but no inbound connections from users Only as a documented exception with an owner and an exit date
Replacement The new platform's lifecycle A new release or product; Windows Server 2025 Standard is $1,176 per 16-core pack plus CALs A supported release Yes

ESU for the one box: Azure Arc or volume licensing

Windows Server 2016 ESU delivers the updates Microsoft rates Critical and Important for up to three years after 12 January 2027, through January 2030. It needs Software Assurance, a Server Subscription or SPLA licensing and comes through two channels.

Through Azure Arc, the server runs the Connected Machine agent and you provision an ESU license in the Azure portal by edition and core count. Billing starts on 13 January 2027 and runs monthly per core; a license provisioned later is back-billed to the end-of-support date, and a deactivated one bills for up to five more days. For one box the appeal is the exit: drop the cores and the meter stops.

Through volume licensing, ESU is an annual key per core. At the time of writing, Microsoft's lifecycle FAQ prices each of the three years at the full license price, and years two and three are sold only to customers who bought the earlier years. On the October 2026 price list, Windows Server Standard ESU is $124 per 2-core pack and $496 per 8-core pack; Datacenter is $720 and $2,880; the list carries the same figures for all three years. Moving from volume licensing to Arc is not supported for 2016. The ESU calculator prices both channels per year; our Windows Server 2016 end-of-support article covers eligibility.

The LTSC path: when the vendor supports a client operating system

Microsoft describes Windows IoT Enterprise as a binary equivalent of Windows Enterprise for fixed-function devices: ATMs, point-of-sale terminals, industrial automation, medical devices and digital signage. Each Long-Term Servicing Channel release is supported for ten years with security updates and no feature updates. It is licensed for fixed-function use, not as a general desktop, and is sold pre-installed by an OEM or as an upgrade license through volume licensing and the Cloud Solution Provider program.

Windows 10 IoT Enterprise LTSC 2021 is supported until 13 January 2032. Windows 11 IoT Enterprise LTSC 2024 has mainstream support until 9 October 2029 and extended support until 10 October 2034. Both are $295 per device, perpetual, Microsoft list price, October 2026 price list.

The non-IoT Windows 10 Enterprise LTSC 2021 ends on 12 January 2027 with no extended phase; its Extended Security Updates are $61 per device for year one, $122 for year two and $244 for year three (October 2026 price list), cumulative, so three years of ESU cost more than one IoT LTSC license. Windows 10 Enterprise LTSB 2016 left support on 13 October 2026. A vendor accepts the LTSC path when its support statement names a client edition and the application has no server role.

Isolation done properly

Isolation is for a machine that cannot take ESU, cannot be rebuilt and cannot yet be replaced. The documentation is most of the work.

  1. Network. Its own VLAN or host, no inbound connections from the user network, administrators through a jump host with multifactor authentication.
  2. Outbound. Only to the destinations and ports the application needs; no general internet access.
  3. Identity. No domain membership where the application allows it; otherwise its own organizational unit with no domain administrator logons. Local accounts with unique passwords in a vault.
  4. Detection. Microsoft Defender for Servers through Defender for Cloud, or the EDR you already run, with alerts routed to a named person.
  5. Backup. A nightly image, with a restore tested and dated each quarter.
  6. Exit. A written retirement date and an owner, reviewed each quarter until the machine is gone.

The sentence an auditor wants to read, in your register: "This system runs an operating system that no longer receives vendor security updates. It is isolated with no inbound access from the user network, monitored by EDR, backed up and restore-tested, owned by a named manager, and scheduled for retirement on a stated date." Insurers ask whether every system receives vendor updates; that sentence answers the question after the "no". Our Windows Server 2012 R2 post-ESU plan applies the same controls.

A worked example: the signage server in a practice being acquired

A medical practice of about 200 users is being acquired by a hospital group, with a possession date about four weeks out and an acquirer's checklist requiring central management of every server. About a dozen servers are being rebuilt on Windows Server 2022 and connected to Azure Arc. One machine does not fit: a digital-signage system on a Windows Server 2016 virtual machine the vendor will not move to a newer server release.

The plan treats it as a device rather than a server. The vendor's support statement names Windows 10 Enterprise and the application has no server role, so the practice orders one Windows 10 IoT Enterprise LTSC 2021 license at $295 (October 2026 list price) instead of ESU, once the licensing desk confirms the upgrade and virtual-use terms. The signage player is rebuilt on a fresh LTSC 2021 virtual machine; the 2016 machine stays off for ninety days. On the acquirer's inventory it is a fixed-function device supported until 13 January 2032, on its own VLAN with outbound only to the vendor's content service, EDR and nightly backup.

ESU stays on the plan as the fallback: if the rebuild slips past 12 January 2027, the 2016 machine is enrolled through Arc for the months it needs.

What not to do

Unsupported in production with "we'll get to it". A server with no security updates and no written controls is not an accepted risk but an undocumented one, and an assessor records it as a finding.

Moving the server to Azure for ESU at no additional charge. That entitlement applied to Windows Server 2012 and 2012 R2 and ended on 13 October 2026. Microsoft's pricing-consistency notice of 27 March 2026 states that ESU offerings released from 1 April 2026, Windows Server 2016 among them, carry the same list price regardless of deployment location or purchasing channel.

A consumer or general-purpose edition. Windows 10 Home and Pro left support on 14 October 2025, and Microsoft excludes organization-managed devices from the consumer ESU program. Windows 10 Enterprise LTSC 2021 ends on 12 January 2027 and is not a rebuild target either.

An annual volume-licensing key for a server retiring mid-year. The key is paid for the year; the Arc meter stops when cores are removed.

What it costs on our side

Microsoft's charges (the ESU meter, the IoT license, Arc add-ons and Azure consumption) are billed to you by Microsoft.

Frequently asked questions

We have an old system on Windows Server 2016 that the vendor won't move; what is the cheapest supported way to keep it?

Ask whether the application is supported on Windows 10 or Windows 11 Enterprise. If yes, a Windows IoT Enterprise LTSC rebuild at $295 per device, perpetual and supported to 2032 or 2034, costs the least. If no, Windows Server 2016 ESU through Azure Arc, monthly per core from 13 January 2027, costs the least for a box retiring within the year.

What does Windows 10 IoT Enterprise LTSC cost and when can we use it?

Windows 10 IoT Enterprise LTSC 2021 and Windows 11 IoT Enterprise LTSC 2024 are each $295 per device, perpetual, Microsoft list price, October 2026 price list, for fixed-function devices such as signage players and kiosks. LTSC 2021 is supported until 13 January 2032, LTSC 2024 until 10 October 2034.

What does "supported" mean to an auditor or an insurer?

That the operating system still receives vendor security updates, or, when it does not, that a written exception names the owner, the compensating controls and the exit date. ESU and an LTSC rebuild pass the first test; isolation passes the second only with the paperwork.

Can we just isolate it?

Yes, for a defined period, if the application works with no inbound connections from the user network. It needs its own VLAN or host, outbound limited to named destinations, local accounts in a vault, EDR, tested backups and a dated exit, all written down.

Can we move the server to Azure and get ESU at no additional charge?

Not for Windows Server 2016. ESU at no extra charge in Azure applied to Windows Server 2012 and 2012 R2 and ended on 13 October 2026. Since 1 April 2026 Microsoft prices new ESU offerings the same wherever the server runs.

Sources

  • Microsoft Learn, "Windows 10 IoT Enterprise LTSC 2021" (lifecycle/products/windows-10-iot-enterprise-ltsc-2021) and "What's new in Windows 10 IoT Enterprise LTSC 2021" (windows/iot/iot-enterprise/whats-new/windows-10-iot-enterprise-ltsc-2021), retrieved October 2026
  • Microsoft Learn, "Windows 11 IoT Enterprise LTSC 2024" (lifecycle/products/windows-11-iot-enterprise-ltsc-2024) and "Windows IoT Enterprise release history" (windows/iot/iot-enterprise/whats-new/release-history), retrieved October 2026
  • Microsoft Learn, "What is Windows IoT Enterprise?" (windows/iot/iot-enterprise/overview) and "Windows IoT Enterprise LTSC in Volume License" (windows/iot/iot-enterprise/deployment/volume-license), retrieved October 2026
  • Microsoft Learn, "Windows message center" and "Supported versions of Windows client" (windows/release-health), Windows 10 Enterprise LTSC 2021 end of updates on 12 January 2027, retrieved October 2026
  • Windows IT Pro Blog, "Plan for Windows 10 Enterprise LTSC 2021 end of support" (techcommunity.microsoft.com), retrieved October 2026
  • Windows IT Pro Blog, "Plan for Windows Server 2016 and Windows 10 2016 LTSB end of support" (techcommunity.microsoft.com), retrieved October 2026
  • Microsoft Learn, "Prepare to deliver Extended Security Updates for Windows Server through Azure Arc" (azure-arc/servers/prepare-extended-security-updates), retrieved October 2026
  • Microsoft Learn, "Billing service for Extended Security Updates for Windows Server through Azure Arc" (azure-arc/servers/billing-extended-security-updates) and "License provisioning guidelines for Extended Security Updates for Windows Server" (azure-arc/servers/license-extended-security-updates), retrieved October 2026
  • Microsoft Learn, "Product Lifecycle FAQ - Extended Security Updates" (lifecycle/faq/extended-security-updates), retrieved October 2026
  • Microsoft, "Microsoft Services: Pricing Consistency Update" (licensing/news/services-pricing-consistency-update), 27 March 2026, retrieved October 2026
  • Microsoft Support, "Support for Windows Server 2016 will end in January 2027", retrieved October 2026
  • Microsoft, "Windows 10 Consumer Extended Security Updates (ESU)" (windows/extended-security-updates), retrieved October 2026
  • IT Partner Microsoft deadlines page; Microsoft NCE Software price list (US, Commercial), October 2026

Key takeaways

  • One vendor answer decides the path: an application supported on a client edition of Windows moves to Windows IoT Enterprise LTSC at $295 per device, perpetual, supported to 2032 or 2034.
  • Windows Server 2016 ESU runs up to three years from 12 January 2027: monthly per core through Azure Arc, back-billed to 13 January 2027, or annually through volume licensing at $124 per Standard 2-core pack.
  • Isolation is a documented exception: no inbound access, limited outbound, vaulted local accounts, EDR, tested backups and a written exit date.
  • A 2016 server moved to Azure gets no ESU at no additional charge; since 1 April 2026 the list price is the same wherever the server runs.

Which of the four fits your one box? Put its edition and core count into the Extended Security Updates Calculator to see ESU through Azure Arc and volume licensing priced per year at Microsoft's list price, and if ESU is the answer, Windows Server ESU Enrollment through Azure Arc ($35 per server plus a $1,450 tenant fee, one week) provisions and links the license before 12 January 2027. Microsoft's ESU charge is billed to you; our work is quoted in writing before it starts.

Didn’t find your question?

Ask it here. A real engineer answers by email within one business day — and if it’s a good one, it becomes part of this page so the next person finds it.

Answered by a person, one time, to your inbox. Nothing you type here is published without a human reviewing and anonymizing it first.

Questions this article didn’t answer?

Thirty minutes with Mike — our CEO, not a sales rep. Bring the hard version of the question.