Step-by-Step Guide · Resource Center

Windows Server 2016 End of Life: Key Dates, ESU, and Migration Options

By Los Angeles ITUpdated October 9, 20269 min read

Quick answer

Windows Server 2016 reaches end of extended support on January 12, 2027, after which it gets no security updates unless you buy Extended Security Updates. Windows Server 2019 follows on January 9, 2029. Most small businesses should upgrade to Windows Server 2025, move the workload to Azure, or replace the server with cloud services.

Key takeaways

  • Windows Server 2016 extended support ends January 12, 2027. Mainstream support already ended in January 2022.
  • Windows Server 2019 extended support ends January 9, 2029, so plan for it in the same budget cycle.
  • Paid Extended Security Updates for Server 2016 are available through Azure Arc, as a bridge of up to three years.
  • Windows Server 2025 supports a direct in-place upgrade from 2016, but a clean migration to new hardware is often safer.
  • Many small offices can retire the server entirely by moving files, email and identity to Microsoft 365 or Azure.

Windows Server 2016 has been a workhorse for small businesses, running file shares, Active Directory, print servers and line-of-business databases. Microsoft's support for it ends on January 12, 2027. After that, the server will keep working, but it will stop receiving security updates unless you pay for Extended Security Updates.

If you also have Windows Server 2019, it is not far behind. This guide lays out the exact dates, what ESU does and does not cover, and the realistic migration options for a small or mid-sized business.

Windows Server end of support dates

Microsoft's Fixed Lifecycle Policy gives each Windows Server release five years of mainstream support and five years of extended support. Here are the dates that matter in 2026, from Microsoft's lifecycle pages.

Version Mainstream support ended or ends Extended support ends
Windows Server 2012 / 2012 R2 October 9, 2018 October 10, 2023 (ESU only after that)
Windows Server 2016 January 11, 2022 January 12, 2027
Windows Server 2019 January 9, 2024 January 9, 2029
Windows Server 2022 October 13, 2026 October 14, 2031
Windows Server 2025 November 13, 2029 November 14, 2034

During extended support, servers still get monthly security updates at no extra cost, but no new features. After extended support ends, there are no security updates, no bug fixes and no Microsoft technical support.

Warning

Windows Server 2016 is the base for some older appliances and vendor-supplied servers, such as phone systems, camera recorders and building systems. Check with each vendor about their own support plans, not just Microsoft's.

What end of support means for your business

An unsupported server is a bigger risk than an unsupported laptop. Servers usually hold your shared files, run Active Directory, and are reachable from every PC on the network. Ransomware operators specifically target unpatched servers because one compromise can encrypt the whole company. Our guide on how to prevent ransomware explains why.

There are practical costs too:

  • Compliance. HIPAA risk assessments, PCI DSS and most cyber insurance applications ask whether systems run supported, patched software.
  • Software support. Accounting, practice management and ERP vendors drop support for older server operating systems, and newer versions of their software may refuse to install.
  • Hardware age. A server installed with 2016 is often seven to ten years old, and its hardware warranty has likely expired.

Extended Security Updates for Server 2016

Microsoft made Extended Security Updates for Windows Server 2016 generally available through Azure Arc in August 2026. Arc is an agent that connects on-premises servers to Azure for management and billing, so you do not have to move the server to Azure to get patches.

What to know about ESU, as of 2026:

  • Coverage. Critical and important security updates only. No new features, no non-security fixes, and no general technical support.
  • Length. Up to three years beyond January 2027. Treat it as a bridge, not a plan.
  • Eligibility. Past Windows Server ESU programs have required Software Assurance or subscription licenses, and reports indicate the same for 2016. Confirm your eligibility with a Microsoft licensing partner.
  • Billing. ESU through Azure Arc is billed through your Azure subscription. Per-core pricing should be quoted for your specific servers, and enrolling late typically means paying back to the end-of-support date.
  • Azure-hosted servers. Microsoft has included ESU at no extra charge for some older versions running in Azure. Ask whether that applies to Server 2016 before assuming it does.
Tip

ESU only makes sense for a server you cannot replace before January 2027, such as one running specialized software awaiting a vendor update. For a plain file and domain server, the cost of ESU usually goes further toward a replacement.

Migration options

Most small businesses land on one of four paths. Many use a mix, for example moving files to the cloud and keeping a small on-premises server for one application.

Option Best for Main considerations
In-place upgrade to Server 2025 Newer hardware that meets Server 2025 requirements Fastest, but carries over old configuration. Back up first
New server with Server 2025 Aging hardware, or many roles on one box Clean build, new warranty, supported until 2034
Move workloads to Azure Apps that must stay on Windows Server, remote-heavy teams Monthly cost, internet dependence, needs good design
Retire the server (Microsoft 365 / cloud) Offices using the server mainly for files, email and logins Files to SharePoint and OneDrive, identity to Entra ID, devices to Intune

Upgrade to Windows Server 2025

Microsoft supports an in-place upgrade from Windows Server 2016 directly to 2025 on non-clustered servers. Failover clusters must use a rolling upgrade, one version at a time. Each upgrade needs a new Windows Server license plus the right client access licenses (CALs). Server 2025 also requires a processor that supports the SSE4.2 and POPCNT instruction sets, which rules out some very old hardware.

For a server that is already six or more years old, a clean installation on new hardware is usually the better choice. You avoid carrying years of configuration drift, and you get a fresh hardware warranty.

Move to Azure

If an application must run on Windows Server, you can host it on an Azure virtual machine running Windows Server 2025 instead of buying hardware. This suits businesses with multiple locations or mostly remote staff. Budget for compute, storage, backup and a site-to-site VPN, and get a monthly estimate before committing.

Retire the server

Many offices with under 50 people no longer need a server at all. Shared files move to SharePoint and OneDrive (see OneDrive vs SharePoint for how to split them), logins move from Active Directory to Microsoft Entra ID, and PCs are managed by Intune. Printing can move to direct IP printing or Universal Print.

LA business note

An on-premises server in a small LA office is exposed to summer heat waves, utility outages, and in some Southern California Edison service areas, public safety power shutoffs. If you keep a server, put it on a UPS with automatic shutdown and make sure the room is cooled. If those risks keep coming up, that is a point in favor of the cloud.

How to plan a Windows Server 2016 migration

Whichever path you choose, the planning steps are similar:

  1. Inventory. List every 2016 and 2019 server, its roles (domain controller, DNS, DHCP, file, print, SQL, line-of-business apps), and its hardware age. Run winver or check Server Manager > Local Server to confirm the version.
  2. Check application support. Ask each software vendor which Windows Server versions they support today.
  3. Back up and test a restore. Before any change, confirm you can actually restore the server. A business continuity plan should cover what happens if a migration goes wrong.
  4. Pick a target and a date. Schedule well before January 12, 2027, and leave time for a second attempt.
  5. Decommission properly. After migration, demote old domain controllers cleanly and wipe or destroy the old drives.

Since Server 2019 support ends in January 2029, fold those servers into the same plan rather than starting over in two years.

When to call an IT professional

Server migrations touch everything: logins, file permissions, printers, backups and line-of-business software. A careful plan avoids a Monday morning where nobody can sign in. Los Angeles IT handles Windows Server assessments, Server 2025 upgrades, Azure moves and server retirements for LA businesses at $95/hr with no long-term contract. Visit our managed IT services page to see how we keep servers supported long term.

Disaster Recovery Plan Template

Restore your systems after an earthquake, wildfire, outage, or cyberattack

Free download

FAQ

Windows Server 2016 End of Life: FAQ

When does Windows Server 2016 reach end of life?

Windows Server 2016 extended support ends January 12, 2027, according to Microsoft's lifecycle page. Mainstream support ended January 11, 2022. After January 2027, Microsoft stops releasing security updates, bug fixes and technical support for the product unless the server is covered by paid Extended Security Updates.

When does Windows Server 2019 reach end of life?

Windows Server 2019 mainstream support ended January 9, 2024, and extended support ends January 9, 2029. Until then it still receives monthly security updates at no extra cost. If you are replacing a 2016 server now, skip 2019 and go straight to Windows Server 2025 to get the longest support runway.

Can I buy Extended Security Updates for Windows Server 2016?

Yes. As of August 2026, Microsoft offers Extended Security Updates for Windows Server 2016 through Azure Arc, which works for on-premises servers without moving them to Azure. ESU provides critical and important security patches only, for up to three years. Pricing and eligibility, including Software Assurance or subscription licensing, should be confirmed with a Microsoft licensing partner.

Can I upgrade Windows Server 2016 directly to Windows Server 2025?

Yes. Microsoft supports an in-place upgrade from Windows Server 2016 to 2025 for non-clustered servers, skipping 2019 and 2022. You need a Windows Server 2025 license, a full backup, and a check of every role and application. Failover clusters must step up one version at a time, and the server hardware must meet Server 2025's processor requirements.

What happens if I keep running Windows Server 2016 after 2027?

The server keeps running, but every new vulnerability stays unpatched. Servers hold the most sensitive data and often run domain controllers, so they are prime ransomware targets. Unsupported servers can also cause problems with cyber insurance applications, HIPAA and PCI DSS assessments, and vendor support for line-of-business software.

Rather have an engineer handle it?

Talk to a Los Angeles IT engineer today. $95/hr, onsite or remote, no contracts.