Skip to content
audiotale.net
Sign in
NewsNews

Windows Server 2016 end of support 12 January 2027: ESU, upgrade paths and what to do

Microsoft will stop security updates for Windows Server 2016 on 12 January 2027; here is who is affected, which in-place upgrades are supported and what Extended Security Updates are known to cover.

audiotale.net team

· 6 min read

Written by AI from the sources linked below. How we use AI

On this page
  1. Key points
  2. What to do
  3. What happened
  4. Background
  5. How it works
  6. What it means
  7. What we don't know yet
  8. What to watch next
  9. Sources

Windows Server 2016 reaches the end of extended support on 12 January 2027, less than three months from now. After the January 2027 security update, servers still running it receive no more monthly security fixes unless they are enrolled in Microsoft's paid Extended Security Updates (ESU). Microsoft's guidance is to upgrade to Windows Server 2025; the in-place path from 2016 is supported, but it needs planning because roles, clusters and licences each change what is allowed.

Key points

  • Windows Server 2016 extended support ends on 12 January 2027 (Pacific Time), per Microsoft's lifecycle page; mainstream support ended in January 2022.
  • The affected editions are Datacenter, Essentials, MultiPoint Premium and Standard, and containers released with Windows Server 2016 follow the same dates.
  • Microsoft's Windows Server team has announced ESU for Windows Server 2016, delivered through Azure Arc; the post we read does not give duration or price.
  • Microsoft's documentation lets Windows Server 2016 upgrade in place directly to 2019, 2022 or 2025 using installation media.
  • Windows Server 2025 has mainstream support until November 2029 and extended support until 14 November 2034, according to BleepingComputer's report.

What to do

Who is affected: every server running Windows Server 2016 in the Datacenter, Standard, Essentials or MultiPoint Premium editions, on-premises or in a hosted environment, plus Windows containers built on 2016 base images. The Essentials features, including Remote Web Access, also lose support on the same date, BleepingComputer reports.

How to check: run winver or Get-ComputerInfo | Select WindowsProductName, OsVersion on each server, or query your inventory tool. Do not forget lab, backup, print and branch-office servers that nobody owns any more.

Pick a route before January:

  1. Upgrade in place. Microsoft's upgrade-path table shows 2016 to 2019, 2022 and 2025 as supported with installation media. Back up first. Check that every role supports in-place upgrade in Microsoft's role and feature matrix, and note the restrictions: no switching between Server Core and Desktop Experience during the upgrade, no in-place upgrade for servers booting from a VHD, NIC Teaming must be disabled beforehand, and a domain controller cannot be converted to a retail version this way.
  2. Clean install or migrate roles to a new server running a supported version, which gives a fresh environment and suits hardware that is also ageing.
  3. Move the workload to Azure. For the previous generation, Microsoft's ESU FAQ states that ESU are free for VMs in Azure. Microsoft's 2016 announcement points customers to its Azure migration programme; confirm whether the same free-in-Azure terms apply to 2016 before relying on them.
  4. Buy ESU as a bridge. Microsoft says ESU are a last-resort paid option, not a long-term solution.

Licensing: each Windows Server upgrade needs its own licence, Microsoft's documentation notes, unlike Windows client upgrades. Confirm you hold a valid key and activation method for the target version before you start.

What happened

Microsoft's lifecycle page lists Windows Server 2016 under the Fixed Lifecycle Policy with a start date of 15 October 2016, a mainstream end date of January 2022 and an extended end date of 13 January 2027 at 06:59:59 UTC, which is the end of 12 January in Redmond. BleepingComputer reported on 23 October 2026 that Microsoft is reminding customers of the deadline, that the January 2027 security update will be the last for the product, and that Microsoft tells customers to "plan to upgrade to Windows Server 2025".

Microsoft's Windows Server blog, in a post dated 25 February 2026, had already said extended support for Windows Server 2016 would end on 12 January 2027 and announced ESU for it, with updates delivered through Azure Arc and managed in the Azure portal. For on-premises workloads, the post lists licensing flexibility, Azure management features and flexible subscription billing as benefits, and it refers readers to Microsoft's ESU page for details. It does not state the duration or the price.

Background

Windows Server 2016 was announced at Microsoft Ignite in September 2016 and became generally available in October 2016. BleepingComputer gives general availability as 12 October 2016, while Microsoft's lifecycle page gives a start date of 15 October 2016. The two dates differ, and we have used Microsoft's listing for the support schedule.

The most recent precedent is Windows Server 2012 and 2012 R2. Their extended support ended on 10 October 2023, and Microsoft sold ESU for up to three years. According to Microsoft's ESU FAQ, the third and final year of those ESU ends on 13 October 2026, which means that program has just run out. The FAQ shows how Microsoft handled that program:

  • ESU was free for VMs in Azure, including Azure Virtual Machines, Dedicated Host, Azure VMware Solution and the Azure Stack portfolio.
  • On-premises, ESU was available through volume licensing or Azure Arc, with a requirement of active Software Assurance or an equivalent subscription (or service-provider licensing).
  • Pricing for on-premises customers was 100% of the full licence price in each of the three years.
  • Customers who enrolled late were back-billed for the months they missed.

This history does not tell us what the Windows Server 2016 terms will be. The FAQ's availability table, as we read it, lists only Windows Server 2012/R2 and Windows 10, so the 2016 dates are not yet shown there. The general rule it states is that ESU can run for up to three years after the end of extended support, which for 2016 would run to January 2030, but that is an inference from the general rule and not a Microsoft announcement for this product.

How it works

Support ending does not stop the server booting. It means Microsoft stops issuing fixes for newly found vulnerabilities, so every new flaw found in the Windows Server code after January becomes a permanent exposure unless you buy ESU or leave. ESU include security updates rated Critical and Important only; no new features, no non-security fixes on request, and no general technical support, according to the FAQ.

Which in-place upgrades are allowed depends on the source and target versions. From Microsoft's installation-media table, a server on 2016 can go straight to 2019, 2022 or 2025. A server on 2012 R2 can reach 2016, 2019 or 2025, and Microsoft says that from Windows Server 2025 onward, non-clustered systems can jump up to four versions at once, so 2012 R2 and later can upgrade directly to 2025. Clusters are different: a cluster operating-system rolling upgrade advances one version at a time. Servers on Windows Update can only upgrade this way from 2019 or 2022 to 2025, so a 2016 server needs media.

What it means

For administrators, the deadline is a project, not a patch. The slow parts are rarely the operating system: they are application compatibility, third-party agents and drivers, domain controller replacement, and the licence purchase. Starting in November leaves little time for testing before the last patch.

For organisations that cannot finish in time, ESU buys time, but Microsoft stresses it is a bridge, and its history shows the cost can equal the full licence price each year for on-premises servers. Whether 2016 follows the same pricing is not stated in the sources we could open.

For security teams, an unsupported Windows Server is also a compliance finding: auditors and cyber-insurance questionnaires commonly ask about unsupported operating systems. That point is general industry practice, not something drawn from the sources below.

What we don't know yet

  • The ESU price, duration and eligibility rules for Windows Server 2016. Microsoft's February post defers to its ESU page, and we could not open a page with those numbers.
  • Whether ESU for 2016 will be free for VMs in Azure as it was for 2012/R2.
  • Whether Microsoft will publish additional guidance, such as a Windows Server 2016 entry in its lifecycle FAQ, before January.

What to watch next

Watch Microsoft's lifecycle FAQ and the Windows Server blog for the 2016 ESU terms, and the January 2027 Patch Tuesday, which will be the last security release for 2016 on the standard track. If you manage servers, run an inventory this week and put the oldest and least-documented machines first.

Sources

SaveStart the discussion

Written by

audiotale.net team

The official account of the people who run audiotale.net: announcements, conversation starters and the newsroom's drafts. Posts written with AI say so. Every other account here is a real person.

Read next