Windows Server 2016 End of Life: Your Options Before January 12, 2027

Home
/
Blog
/
Windows Server 2016 End of Life: Your Options Before January 12, 2027

Windows Server 2016 receives its last security update on January 12, 2027. Vulnerabilities keep arriving after that date. Patches do not. 

Windows Server 2016 end of life means Microsoft stops issuing security updates, bug fixes and technical support for the operating system on January 12, 2027, the closing date of its Fixed Lifecycle Policy. The servers keep running. Every vulnerability disclosed after that date stays open unless you buy Extended Security Updates, and whether you qualify for those depends on your licensing. For most organizations the answer is Windows Server 2025, with ESU as a short bridge for the servers that cannot make the date. 

Start with what is actually running

A security risk assessment inventories your environment, finds every server still on Windows Server 2016, shows what each one carries, and ranks them by exposure once patching stops. You get a triage list you can work from in week one.

When Does Windows Server 2016 Reach End of Life?

Extended support for Windows Server 2016 ends on January 12, 2027. Mainstream support ended on January 11, 2022. Extended support is the last phase of free security patching under the Fixed Lifecycle Policy, which makes January 12 the final Patch Tuesday this operating system will ever see. 

Windows Server 2016 Key Dates

MilestoneDate
General availabilityOctober 15, 2016
Mainstream support endedJanuary 11, 2022
Extended support endsJanuary 12, 2027
Paid Extended Security UpdatesUp to three years, running to January 2030

If you have seen January 13 quoted elsewhere, that comes from the timestamp on the Windows Server 2016 lifecycle page, which records the moment coverage lapses rather than the last covered day. Microsoft’s own announcement puts it plainly at January 12, 2027. Plan to January 12 and treat the morning of January 13 as unsupported. 

What Actually Stops on January 12, 2027?

Your servers keep running. What stops is everything that keeps them safe to run: monthly security updates through Windows Update, WSUS and Azure Update Manager, non-security fixes, and the ability to open a support case with Microsoft at all. Your other vendors follow shortly after. 

Security updates and Microsoft support

Microsoft discloses the vulnerabilities it has just fixed every Patch Tuesday. Where that code also sits in Windows Server 2016, you receive the disclosure without the fix, permanently. You also lose the ability to log a ticket. Microsoft is explicit that without ESU coverage, a customer on an out-of-support Windows Server version cannot open a support case even if they hold a support plan. 

According to CISA’s Bad Practices catalog, running unsupported or end-of-life software in service of critical infrastructure and national critical functions is dangerous and significantly elevates risk, and CISA lists it among the practices it calls exceptionally risky for any organization. That catalog was written with critical infrastructure in mind. Auditors and insurers have been applying the same reasoning to everyone else for years. 

Do your other vendors still support Windows Server 2016?

Some already do not. Backup agents, endpoint tools and line-of-business applications publish supported operating system matrices, and 2016 drops off them around Microsoft’s date. Check your three most important vendors this week rather than in January, because a backup agent that is no longer certified on 2016 is a restore you cannot count on. 

That distinction matters. An unpatched operating system is a risk you can partly contain with network segmentation. An unsupported backup agent is a recovery you only discover you lost on the morning you need it. 

The rest of your 2016 stack is probably already unsupported

Servers bought in one cycle tend to run software from the same cycle, and two of those products are already past their dates: 

  • Exchange Server 2016 reached end of support on October 14, 2025, and its short paid ESU window has closed too. The supported destinations are Exchange Online or Exchange Server Subscription Edition. 

A 2016 server running SQL 2016 is already half unsupported. Scope the operating system and the database as one project, or you will take the same outage twice. 

Can You Get Extended Security Updates for Windows Server 2016?

Yes, and you have two routes. Microsoft announced ESU for Windows Server 2016 on February 25, 2026, delivered through Azure Arc with monthly subscription billing. ESU is also sold as annual licenses through commercial licensing. Either route covers Critical and Important security updates only, for up to three years. Eligibility is the catch, and it is worth checking before you plan around it. 

How ESU works, and who actually qualifies

With the Arc route, you connect each server to Azure Arc, enable ESU, and pay monthly through an Azure subscription, with no keys to deploy. With the licensing route, you buy ESU licenses a year at a time, and Year 2 requires that you bought Year 1, the same annual cadence teams worked through during the Windows Server 2012 R2 transition.

With the Arc route, you connect each server to Azure Arc, enable ESU, and pay monthly through an Azure subscription, with no keys to deploy. With the licensing route, you buy ESU licenses a year at a time, and Year 2 requires that you bought Year 1. The terms worth reading before you build a budget sit in Microsoft’s Extended Security Updates FAQ: 

  • Eligibility. On-premises ESU requires active Software Assurance, active subscription licenses such as CSP, or Windows Server acquired as license-included through a SPLA partner. If you bought OEM licenses with the hardware and never added Software Assurance, on-premises ESU is not open to you, and moving the workload to Azure becomes the alternative. 
  • Your CALs need it too. Users connecting to an ESU-covered server must hold CALs with active Software Assurance or equivalent subscription coverage. 
  • Core minimums set the floor. Physical core licensing carries a 16-core minimum per server, virtual core licensing an 8-core minimum per VM. A four-core server is billed as sixteen. 
  • Enrolling late costs the same. Sign up in April and Microsoft back-bills January through March in your first invoice. Waiting does not save money, it just delays the patches. 
  • Azure destinations get it free. Azure VMs, Azure Dedicated Host, Azure VMware Solution, Nutanix Cloud Clusters on Azure and Azure Local carry ESU at no charge beyond running the VM. 
  • Arc needs a line home. An Arc-connected server tolerates intermittent connectivity but expects to reach Azure at least once in any thirty-day window. Genuinely isolated servers need the key-based route instead. 

Why isn’t ESU a long-term plan?

Because it patches the operating system and nothing else. ESU does not replace ten-year-old hardware, restore vendor support for your backup and security tools, or include technical support. Microsoft describes the program itself as a last resort and a temporary bridge rather than a long-term solution, which is a fair summary of what you are buying. 

Used well, it covers named servers with a retirement date already attached. Used badly, it becomes a line item you renew for three years and then face the same decision with older hardware and less goodwill. 

Which Version Should You Upgrade To?

Windows Server 2025 in most cases. It is the only current target still in mainstream support, and it carries the longest runway by several years. Choosing 2019 or 2022 now means repeating this project well before you need to. 

Where Each Upgrade Target Stands

VersionMainstream supportExtended support ends
Windows Server 2019Ended January 9, 2024January 9, 2029
Windows Server 2022Ended October 13, 2026October 14, 2031
Windows Server 2025Ends November 13, 2029November 14, 2034

Choose 2022 only when an application vendor has not certified 2025 yet, and ask that vendor for the date they will. Server 2025 also brings hotpatching to Arc-connected Standard and Datacenter machines, which Microsoft made available at no additional charge in May 2026. It replaces most monthly restarts with a quarterly baseline update, cutting planned reboots from roughly twelve a year to four. For a lean team, that is several weekends back. 

Should you upgrade in place or build clean?

Build clean for anything critical. Windows Server 2025 does accept a direct in-place upgrade from 2016 using installation media, because nonclustered systems can now move up to four versions at once, with no stop at 2019 or 2022. An in-place upgrade also carries a decade of drivers, dead software and registry drift onto the new system, while a clean build leaves the original server untouched as a rollback that actually works. 

Four restrictions apply whichever way you go: 

  • Failover clusters move one version at a time. Cluster OS Rolling Upgrade cannot jump 2016 straight to 2025, so a clustered workload needs an intermediate hop or a rebuild. 
  • Installation type is fixed. An in-place upgrade cannot switch Server Core to Desktop Experience, or back. 
  • Editions hold or move up. Standard upgrades to Standard or Datacenter. Datacenter cannot drop to Standard. 
  • NIC Teaming has to be off. Disable it before the upgrade and re-enable it afterwards, or the upgrade will not proceed cleanly. 

Decide each server’s path in one session

Bring your 2016 server list to a consultation and we will work through it by role: which to upgrade in place, which to rebuild, which to move, and which to bridge with ESU. You leave with a path, an owner and a date against every line.

What Is the Right Path for Each Server?

The role decides. Rebuild domain controllers rather than upgrading them, migrate file server data onto a fresh build, move databases and the operating system together, and segment the applications that genuinely cannot change this year. 

What to Do With Each Server

Server roleRecommended path
Domain controllersPromote new 2025 domain controllers, transfer the five FSMO roles, demote the old ones, then raise the domain functional level. No in-place upgrade.
File serversMove shares and permissions to a new 2025 server with Storage Migration Service, or relocate suitable shares to cloud storage.
Hyper-V hostsUpgrade or rebuild the hosts first, then raise the VM configuration version on the guests. Confirm the hardware supports 2025.
Remote Desktop ServicesRebuild on 2025 with 2025 RDS CALs, keeping the per-user or per-device model you already licensed, then cut users over.
SQL ServerMove to a supported SQL version on a fresh 2025 build, in the same project as the operating system.
Exchange ServerMove mailboxes to Exchange Online or Exchange Server SE. Do not upgrade the operating system underneath it.
Applications that cannot moveSegment on the network, enroll in ESU if you qualify, and assign an owner and a retirement date.

On remediation work, the inventory is the part that surprises people. The list an IT team hands over is rarely the list the scan returns, and the servers nobody wrote down tend to be the interesting ones: a print server quietly running a legacy scanning application, a utility box holding the scheduled task that writes a nightly finance export, a domain controller built as a temporary second DC during an office move and never decommissioned. None appear in the asset register. Each one has an owner, once you find the person who notices when the file stops arriving. That discovery work takes days rather than hours, which is why inventory comes before any upgrade decision rather than alongside it.

For a workload you would rather not buy hardware for again, managed cloud hosting hands the refresh cycle to someone else. Whatever you move, test a restore afterwards. Migrations break backup jobs quietly: new server name, new agent, old job still pointing at a machine that no longer exists. Nobody notices until the disaster recovery plan gets its first real test. 

When is the hardware the real deadline?

When the server shipped with 2016 and has never been replaced, which makes it about ten years old. Putting 2025 on out-of-warranty hardware with firmware that no longer receives updates moves the expiry date without removing it, and older boxes often lack the TPM 2.0 and Secure Boot support that current security baselines assume. 

Price the replacement now rather than in January, because lead times decide this more often than budgets do, which is where IT procurement earns its keep. If your team is also moving desktops off Windows 10, scope both refreshes together and order once.

What Licensing Checks Should You Make Before Upgrading?

Confirm three things before you touch a server: Windows Server 2025 licenses covering every core, client access licenses at the 2025 level, and an activation path for the new version. Microsoft states it directly on its own upgrade page, and it catches people every time: unlike Windows client, each Windows Server upgrade requires a separate license. 

  • 2016 licenses do not cover 2025 unless Software Assurance or a subscription grants rights to new versions. The same Software Assurance check that decides your ESU options decides this one. 
  • Core minimums apply. Windows Server licenses per physical core, with an 8-core minimum per processor and a 16-core minimum per server, whatever the hardware actually holds. 
  • CALs match the server version or exceed it. Users connecting to a 2025 server need 2025 CALs, and RDS CALs follow the same rule. 
  • Sort out activation. If you run a KMS host, it needs a Windows Server 2025 host key before any 2025 server will activate against it. 
  • Price the pay-as-you-go option. Windows Server 2025 can also be billed per core per month through Azure Arc, which can beat a perpetual license on a server you expect to retire within a couple of years. 

Bring finance in during week one. Ten weeks is not much runway for a purchase order. 

A 10-Week Plan to January 12

Two weeks on inventory and triage, three on the straightforward servers, two on the difficult ones, and the last three on a change freeze and segmentation. Starting the week of November 9, the calendar works out like this. 

Weeks 1 to 2, November 9 to 20. Inventory and triage. List every 2016 server with its role, workloads, hardware age and owner. Check your Software Assurance position in the same pass, because it decides whether ESU is even available to you. Assign each server a path, then place license and hardware orders. 

Weeks 3 to 5, November 23 to December 11. Straightforward servers. File servers, standalone application servers and anything with a clean path. Promote the new domain controllers early so replication settles while you work elsewhere. Thanksgiving week runs short, so plan around it. 

Weeks 6 to 7, December 14 to 23. Difficult servers. SQL, Remote Desktop Services, clusters and anything needing vendor involvement. Finish before the holidays, while the people you depend on still answer the phone. 

Weeks 8 to 10, December 28 to January 12. Freeze and segment. No new migrations. Enroll the remaining servers in ESU, segment them, and give each an owner and a retirement date. Verify backups and monitoring on everything you moved. 

Few lean teams can run four of those tracks at once, which is the usual reason to bring in outside server support for a quarter. The domain controller rebuild and the SQL move happen in parallel instead of in sequence, and the deadline stops being arithmetic. 

Frequently Asked Questions

Will Windows Server 2016 stop working after January 12, 2027?

No. It keeps booting, serving files and running applications. It stops receiving security updates unless you hold ESU coverage, and you lose the right to open a Microsoft support case, so every vulnerability disclosed after that date stays open on it. 

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

Yes. Nonclustered servers can upgrade up to four versions at once from installation media, so 2016 goes straight to 2025 with no intermediate hop. Failover clusters are the exception, because Cluster OS Rolling Upgrade advances one version at a time, and no in-place upgrade can switch between Server Core and Desktop Experience. 

Is it safe to keep running Windows Server 2016 after end of life?

Not without ESU coverage and network segmentation, and the position gets harder to defend each month. According to the PCI Security Standards Council, PCI DSS v4.0.1 requirement 12.3.4 asks you to review hardware and software technologies at least once every 12 months, confirm the vendor still supports them, and hold a remediation plan approved by senior management for anything at or approaching end of life. Requirement 6.3.3 separately sets a one-month window for patching critical vulnerabilities, which an unpatched server cannot meet. HIPAA requires a risk analysis that accounts for systems like these, and cyber insurance applications now ask directly whether you run end-of-life software.

Your Next Step

Ten years is a long life for a server operating system, and Microsoft gave five years of notice. What remains is a decision per server: 2025 by default, a clean build for anything critical, ESU only where you qualify and have already set a retirement date, and segmentation for the rest. Ten weeks rules out a perfect migration. It still leaves time for every server to have an owner, a path and a date, which is what an auditor, an insurer and your own team will ask for anyway. 

See the next deadline a year out

IT lifecycle management keeps a live record of every server, license, warranty and support date you run, mapped against your budget cycle. The next end-of-life date reaches you as a line in a roadmap instead of a headline ten weeks out.

Recent Posts

Essential Guides, Insights, and Case Studies for IT Solutions

Two IT professionals reviewing server upgrade graphic on monitor in data center, illustrating Windows Server 2016 end of life migration options

Windows Server 2016 receives its last security update on January 12, 2027.

Executives discussing MSP versus MSSP on conference room screen, illustrating the difference between managed service providers and managed security service providers

Your security dashboard has been green for six months straight. That’s either

Government officials reviewing city map and response plan at conference table, illustrating a ransomware response plan for local government

At 6:40 on a Friday morning, the desk phones at city hall