Windows Server 2016 End of Life

When Windows Server 2016 reaches end of life

Windows Server 2016 reaches end of life on January 12, 2027. Microsoft's lifecycle page shows the product started support on October 15, 2016, left mainstream support on January 11, 2022, and ends extended support on January 12, 2027 ¹. Microsoft repeated the date when it announced paid updates for the product: "extended support for Windows Server 2016 will end on January 12, 2027" ².

Several products built on the same base end the same day, so check for them while you take stock. Microsoft's 2027 list includes Hyper-V Server 2016, IIS 10 on Windows Server 2016, Windows Server Update Services for Windows Server 2016, Windows Storage Server 2016, .NET Framework 4.6.2 and Windows 10 Enterprise LTSC 2021, all on January 12, 2027 ⁴. SQL Server 2017 follows on October 12, 2027 ⁴.

Every other Microsoft cutoff, with days left and the source for each, is in our Microsoft end of support dates table.

What stops after January 12, 2027

After January 12, 2027, Windows Server 2016 keeps running, but Microsoft stops fixing it. Microsoft's wording for any product at end of support: "there will be no new security updates, non-security updates, free or paid assisted support options or online technical content updates" ⁵.

In practice that means three things for a business:

• Security holes stay open. New flaws found in Windows Server 2016 after the cutoff are not patched unless you pay for Extended Security Updates.
• Microsoft support is gone. You cannot open a support case for the product, so a stubborn problem becomes your provider's problem alone.
• Software vendors move on. Line-of-business apps, backup agents and security tools drop support for old operating systems over time, which can leave you stuck on old versions of those too.

It also shows up in paperwork. Marsh lists replacing or protecting end-of-life systems among its twelve key cyber controls and notes that insurers now treat certain controls as a minimum requirement ⁹, and our cyber insurance requirements guide covers the rest of that list. A cybersecurity risk assessment will flag an unsupported server on the first scan.

Extended Security Updates for Windows Server 2016

Microsoft offers paid Extended Security Updates (ESUs) for Windows Server 2016, announced on February 25, 2026 ². The terms Microsoft has published:

• Coverage: "Critical and Important security updates for up to three years, through 2030" ³. No new features and no customer-requested non-security fixes ³.
• How you buy: through Azure Arc, which connects your on-premises server to the Azure portal. Setup opened August 3, 2026 and billing begins January 13, 2027 ³.
• Editions: Standard and Datacenter ³.
• Eligibility: Software Assurance through a volume licensing program is required, unless the servers are licensed through SPLA or a Server Subscription ³.
• In Azure: Microsoft says Windows Server and SQL Server ESUs are available "for 3 more years in Azure" across its Azure destinations ⁸. The pages we checked do not say whether 2016 ESUs are free in Azure, so confirm that before you count on it.

Microsoft had not published a Windows Server 2016 ESU price on the pages we checked in October 2026. For a sense of scale, Windows Server 2012 ESUs bought outside Azure cost 100% of the full license price every year ¹². Microsoft also calls ESUs "a last resort paid option" and "a temporary bridge" ¹², which is the right way to budget them: a year or two of cover while an upgrade finishes, not a plan.

Upgrading Windows Server 2016 to Windows Server 2025

Windows Server 2016 can be upgraded directly to Windows Server 2025. Microsoft says that starting with Windows Server 2025, "nonclustered in-place upgrades support up to four versions at a time" ⁶, so a 2016 server does not need to step through 2019 and 2022 first. Clustered servers and domain controllers usually call for a different approach, so let whoever runs the move confirm the method for each machine.

Windows Server 2025 is the target that buys the most time. Its mainstream support runs to November 13, 2029 and extended support to November 14, 2034 ¹³. Moving to Windows Server 2019 instead only buys two years, because 2019 reaches end of life on January 9, 2029 ¹⁴; our Windows Server 2019 end of life guide covers that date.

Licensing is the part people forget. Microsoft lists Windows Server 2025 Standard at $1,176 and Datacenter at $6,771, both priced for 16 cores, and requires a client access license for every user or device that connects ⁷. For servers connected through Azure Arc, Microsoft also offers pay-as-you-go licensing at $33.58 per CPU core per month ⁷.

What a Windows Server 2016 replacement costs

A Windows Server 2016 replacement costs licenses, possibly hardware, and project labor, and the labor usually decides the total. The published pieces:

• Licenses: $1,176 for Windows Server 2025 Standard or $6,771 for Datacenter, 16 cores, plus client access licenses ⁷.
• Hardware, if the server is old: Dell lists its PowerEdge T160 tower server from $4,330.76 with a 12-month basic warranty ¹⁰. A Standard license plus that server is $5,506.76 before client access licenses and labor, by our arithmetic.
• Labor: one IT buyer's guide lists project engineers at $135 to $195 an hour and senior engineers for server, cloud or security work at $195 to $275 an hour ¹¹.

What pushes the total up or down. Datacenter licensing costs far more than Standard, $6,771 against $1,176 for 16 cores ⁷. New hardware adds the server price ¹⁰, while an in-place upgrade on a machine with warranty left avoids it ⁶. Work that needs a senior engineer runs $195 to $275 an hour, against $135 to $195 for a project engineer ¹¹.

Hours depend on what the server does. A file server with a few shares is a small job; a domain controller, an old line-of-business app or SQL Server on the same box is a larger one. If SQL Server 2016 is on the machine, it has its own deadline that already passed, covered in our SQL Server 2016 end of life guide.

Upgrades are usually priced as fixed-fee projects rather than inside a monthly agreement. Our IT project management guide explains how those are quoted, and our managed IT price index lists published hourly rates. If you would rather not buy hardware at all, hardware as a service spreads the server cost into a monthly fee, and cloud migration removes the server from your office.

A plan for the months before January 12, 2027

With less than three months left as of October 2026, work in this order:

1. List every server and what runs on it. Include virtual machines, the operating system version, and the roles each one holds (domain controller, file, print, applications, SQL Server).
2. Ask each app vendor which Windows Server versions they support. This is the step that most often forces a delay.
3. Pick a path per server: in-place upgrade, replacement, cloud, or ESUs for the few that cannot move in time.
4. Back up and test a restore before anything changes. Our backup and disaster recovery guide covers what a tested restore looks like.
5. Set up ESUs as a fallback now for any server you are not sure will finish. Configuration has been open since August 3, 2026, and billing does not start until January 13, 2027 ³.
6. Schedule cutovers after hours and keep the old server available until users confirm everything works.

If you do not have someone in house to run this, a managed IT provider or a co-managed IT arrangement can take the project alongside your staff.