Key takeaways
Extended support for Windows Server 2016 ends on 12 January 2027. After that date Microsoft stops releasing security updates unless the server is covered by Extended Security Updates.
Windows Server 2022 left mainstream support on 13 October 2026. Windows Server 2025 is the only release with mainstream support until 2029.
Starting with Windows Server 2025, non-clustered in-place upgrades can skip up to four versions, so a 2016 server can be upgraded directly.
Microsoft describes Extended Security Updates as a last-resort option. They buy time for servers that cannot move by January; they are not a plan.
The date
Windows Server 2016 was released in October 2016 under Microsoft’s Fixed Lifecycle Policy. Mainstream support ended in January 2022, and extended support, which includes security updates, ends on 12 January 2027.1 From that date, a server that is not covered by Extended Security Updates will receive no further security fixes.
Note: Dates are the last day of each support phase, Pacific Time.
Source: Microsoft Lifecycle1–4.
The choice of target matters. Windows Server 2022 left mainstream support on 13 October 2026, so a server moved to 2022 today receives security updates but no further non-security fixes.3 Windows Server 2025 has mainstream support until November 2029 and extended support until November 2034.4
Five options for each server
Every Windows Server 2016 machine ends up in one of five places. The work of the next ten weeks is deciding which, based on what the server actually runs.
| Option | Suits | Main risk |
|---|---|---|
| Retire | Servers with no active users, duplicated roles or applications already replaced | A dependency nobody documented |
| Upgrade in place to 2025 | Stable, non-clustered servers whose applications support 2025 | Application compatibility; needs a tested rollback |
| Rebuild on 2025 and migrate | Servers with configuration drift or that need resizing | Time; each migration needs a cutover window |
| Rehost in Azure | Workloads that can move as they are and gain from managed hosting | Network, licensing and latency assumptions |
| Extended Security Updates | Applications that cannot move before January | Cost each year; it postpones the decision |
Source: Corvx. Upgrade paths per Microsoft documentation5.
Starting with Windows Server 2025, non-clustered in-place upgrades support up to four versions at a time, so a Windows Server 2016 server can be upgraded to 2025 directly.5 That makes in-place upgrade a realistic option for many servers, provided the applications on them are supported on 2025 and a rollback has been tested.
Extended Security Updates
Microsoft describes its Extended Security Update program as a last-resort option for customers who need to run a product past the end of support. The updates cover security issues rated critical and important, with no new features or non-security fixes. For earlier releases, Microsoft provided them at no extra charge for servers hosted in Azure and sold them for servers elsewhere.5
Extended Security Updates buy time for the servers that cannot move by January. They are not a plan for the ones that can.
Terms and prices for Windows Server 2016 should be confirmed with Microsoft or a licensing partner before they are relied on. The budget case is usually clear once the inventory is done: paid updates for a handful of difficult servers, and migration for the rest.
Ten weeks of triage
With little time left, the order of work matters more than the speed of any single migration.
- Inventory every 2016 serverInclude virtual machines, appliances and servers outside central IT. Record the role, owner and applications on each.
- Retire what is unusedCheck logins, connections and scheduled tasks. Switch off candidates for two weeks before deleting them.
- Confirm application supportFor each remaining server, confirm the application vendor supports Windows Server 2025, or note why not.
- Upgrade the simple casesUpgrade or rebuild servers with supported applications, starting with the least critical, with a tested rollback.
- Cover the rest, with an exit dateBuy Extended Security Updates only for named servers, each with an owner and a date by which it will move.
References
- 1.Microsoft Learn. “Windows Server 2016 – Microsoft Lifecycle.” learn.microsoft.com
- 2.Microsoft Learn. “Windows Server 2019 – Microsoft Lifecycle.” learn.microsoft.com
- 3.Microsoft Learn. “Windows Server 2022 – Microsoft Lifecycle.” learn.microsoft.com
- 4.Microsoft Learn. “Windows Server 2025 – Microsoft Lifecycle.” learn.microsoft.com
- 5.Microsoft Learn. “Overview of Extended Security Updates for Windows Server.” Updated April 2026. learn.microsoft.com
