The Windows Server 2016 end of support date is 12 January 2027. After that day Microsoft stops releasing security updates, fixes and technical support for every edition, including Standard, Datacenter and Essentials. Mainstream support already ended on 11 January 2022. With less than two months to go, most organisations should be finishing a move to Windows Server 2025 or 2022, or arranging paid Extended Security Updates as a short bridge.
What Is the Windows Server 2016 End of Support Date?
Windows Server 2016 extended support ends on 12 January 2027, according to Microsoft's Windows Server 2016 lifecycle page. The product follows Microsoft's Fixed Lifecycle Policy, which gives five years of mainstream support followed by five years of extended support.
| Version | Released | Mainstream support ended / ends | Extended support ends |
|---|---|---|---|
| Windows Server 2016 | 15 October 2016 | 11 January 2022 | 12 January 2027 |
| Windows Server 2019 | 13 November 2018 | 9 January 2024 | 9 January 2029 |
| Windows Server 2022 | 18 August 2021 | 13 October 2026 | 14 October 2031 |
| Windows Server 2025 | 1 November 2024 | 13 November 2029 | 14 November 2034 |
Two things stand out. Windows Server 2019 is already in extended support and has a little over two years left, so moving to it only buys time. Windows Server 2022 left mainstream support in October 2026, which means it now receives security fixes but no new features. Windows Server 2025 gives the longest runway by a wide margin.
What Happens After Windows Server 2016 End of Support?
After 12 January 2027, Windows Server 2016 keeps running, but it receives no more security updates unless you pay for Extended Security Updates. Every new vulnerability discovered after that date stays open on your servers.
- Security risk: servers are often the most exposed machines on a network, handling file shares, remote access and authentication. Unpatched servers are a common entry point for ransomware.
- Compliance: standards such as PCI DSS and cyber-insurance questionnaires typically ask whether systems are supported and patched.
- Software support: vendors steadily drop support for older server versions, so line-of-business apps and backup agents may stop being certified.
- Related products: roles that ran alongside 2016 are also ageing. Exchange Server 2016, for example, has already reached its end of life, which our Exchange Server 2016 and 2019 end-of-life guide covers.
Can You Get Extended Security Updates for Windows Server 2016?
Yes. Microsoft offers Extended Security Updates (ESU) for Windows Server 2016, delivered through Azure Arc. According to Microsoft's Azure Arc ESU documentation, ESUs provide Critical and Important security updates for up to three years after end of support.
- You could configure Windows Server 2016 ESUs in the Azure portal from 3 August 2026; billing starts on 13 January 2027.
- Servers stay on-premises but must be connected to Azure through Azure Arc.
- On-premises servers need Software Assurance through a volume licensing programme, or an equivalent server subscription.
- ESUs include security fixes only: no new features and no non-security fixes.
ESU is a bridge, not a destination. It suits a server running an application that can't be moved in time, and it costs money every month. For most small businesses without Software Assurance, upgrading is simpler and cheaper.
Should You Upgrade to Windows Server 2025 or 2022?
For most organisations, Windows Server 2025 is the better upgrade target because it is supported until November 2034 and is still in mainstream support. Windows Server 2022 makes sense only if an application vendor hasn't yet certified 2025.
Windows Server 2025 also brings security changes worth planning for, such as Microsoft's move away from the older NTLM authentication protocol; our post on NTLM changes in Windows Server 2025 explains what to test.
Standard or Datacenter?
The choice depends on virtualisation. Microsoft's Windows Server 2025 licensing guidance states that Standard covers two operating system environments (physical or virtual) when all physical cores are licensed, while Datacenter covers unlimited virtual machines. If you run Hyper-V hosts with many VMs, Datacenter is usually the better value; our article on what Hyper-V really costs with Windows Server explains the maths.
How Do You Migrate From Windows Server 2016?
You migrate from Windows Server 2016 either by upgrading the existing server in place or by building a new server and moving roles and data across. Microsoft's Windows Server upgrade documentation confirms that non-clustered servers can upgrade directly from Windows Server 2016 to Windows Server 2025.
- Inventory. List every 2016 server, its roles (domain controller, file server, RDS, SQL, IIS) and the applications on it.
- Check compatibility. Confirm each application vendor supports Windows Server 2025, and check hardware drivers and firmware.
- Back up. Take a full, tested backup or a VM snapshot before you change anything.
- Choose the method. In-place upgrade suits simple servers. A fresh build with role migration suits domain controllers and older servers carrying years of configuration changes.
- Keep the installation type. You can't switch between Server Core and Desktop Experience during an in-place upgrade, so choose the same type or do a clean install.
- Upgrade licences and CALs. Buy the new server licence, and check your Client Access Licences. Microsoft's licensing guidance states that CALs permit access to the same or earlier versions, so 2016 CALs don't cover a 2025 server.
- Test and cut over. Test logins, file access, printing, backups and applications, then decommission the 2016 server.
If the server hosts Remote Desktop Services, plan the RDS CALs at the same time; our guide on applying and activating RDS CALs walks through the licensing server setup.
A Common Mistake We See
The most common mistake is upgrading the server and forgetting the CALs. The new server runs, users connect, and the problem stays hidden until an audit or until Remote Desktop sessions start being refused after the grace period.
The second is leaving an old 2016 domain controller in place "just in case". Demote and remove old domain controllers once the new ones are healthy, so your directory isn't relying on an unsupported server. Treat the upgrade as a project with a checklist, not a weekend job.
Frequently Asked Questions
What is the Windows Server 2016 end of support date?
Windows Server 2016 reaches end of extended support on 12 January 2027. Mainstream support ended on 11 January 2022. After January 2027, Microsoft stops releasing security updates for Standard, Datacenter and Essentials editions unless the server is enrolled in paid Extended Security Updates through Azure Arc.
Will Windows Server 2016 stop working after January 2027?
No. Windows Server 2016 keeps running after end of support, and existing activations remain valid. What stops is security updates, bug fixes and Microsoft technical support. Running it without updates leaves new vulnerabilities unpatched, which is a serious risk for any server connected to a network or the internet.
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 must keep the same installation type (Server Core or Desktop Experience). You can move from Standard to Datacenter during the upgrade, but not the other way round.
How long are Windows Server 2016 Extended Security Updates available?
Microsoft offers Windows Server 2016 ESUs for up to three years after end of support, delivered through Azure Arc with monthly billing that starts on 13 January 2027. On-premises servers need Software Assurance or an equivalent subscription. ESUs include security updates only, not new features or other fixes.
Do I need new CALs when upgrading from Windows Server 2016?
Yes. Microsoft's licensing rules say CALs allow access to the same or earlier versions of Windows Server. Windows Server 2016 CALs therefore don't cover users or devices connecting to a 2025 server. Windows Server 2025 CALs cover 2025 and earlier versions, which helps during a phased migration.
Conclusion
The Windows Server 2016 end of support date of 12 January 2027 is close, so finish your inventory, pick a target and schedule the cut-over now. For most businesses that means Windows Server 2025, which is supported until 2034. Compare editions in our Windows Server 2025 collection, where Windows Server 2025 Standard starts at $99.99 at the time of writing.
Useful Links
| Resource | Link |
|---|---|
| Windows Server 2025 licences | Windows Server 2025 collection |
| Windows Server 2025 Standard | Buy Windows Server 2025 Standard |
| Hyper-V licensing costs | Hyper-V cost with Windows Server |
| RDS CALs | How to apply and activate RDS CALs |
| Lifecycle dates (Microsoft) | Windows Server 2016 lifecycle |
| ESU via Azure Arc (Microsoft) | Prepare for Extended Security Updates |
Leave a comment