Windows Server 2016 Support Ends January 12, 2027: What to Do Now
Extended support for Windows Server 2016 ends on 12 January 2027. As of 5 October that leaves roughly 99 days. The window also contains year-end closing, stocktaking and budget meetings, so finding a quiet week for a server migration will not be easy. The plan has to exist now.
What actually happens on 12 January?
Nothing breaks on the day. Files stay where they are and users keep signing in. What changes is that Microsoft stops publishing security patches by default. New vulnerabilities turn up every month, and your server simply stays exposed to them.
The bigger problem is contractual rather than technical. Cyber insurance policies, customer audits and certifications such as ISO 27001 all trip over “software past end of support”. When an auditor asks for your server list and sees 2016, a finding gets written. (In Türkiye the same logic applies to KVKK, the personal data protection law, which expects “appropriate technical measures”.)
| Version | End of extended support | Status |
|---|---|---|
| Windows Server 2012 / 2012 R2 | 10 October 2023 | Ended |
| Windows Server 2016 | 12 January 2027 | 99 days left |
| Windows Server 2019 | 9 January 2029 | Plan ahead |
| Windows Server 2022 | 14 October 2031 | Safe |
Start with what runs where
The first step is not counting servers but listing workloads. In the audits I run, the company that says “we have two servers” usually turns out to have four or five virtual machines, one of them hosting an accounting program nobody remembers installing.
Answer these in order:
- Which application sits on which server, and does its vendor support Windows Server 2022 or 2025?
- Where do Active Directory, file, print, DHCP and DNS live? Are they separate?
- Which SQL Server version is behind the apps? SQL Server 2016 extended support also ended in July 2026, so the database may need to move at the same time.
- Does your backup software support the new version?
- Licensing: is Software Assurance in place, and do your core counts fit the licence model?
Four options, four different costs
1. In-place upgrade. Windows Server 2025 supports upgrading directly from 2012 R2 and later. It looks fast, but you also carry over years of accumulated settings and old drivers. Use it on servers that are simple to rebuild if it goes wrong, and take a full backup plus a restore test first.
2. Side-by-side migration to a new server. Clean install, move roles one by one, keep the old machine around as a fallback. Slower, but the safest route. If the hardware is five or six years old, it was due for replacement anyway.
3. Move to Azure or another cloud. Sensible if the application is happy running there. A file server can also be split into pieces: SharePoint for documents, Entra ID for identity. Do the latency, bandwidth and monthly cost sums before you commit.
4. Extended Security Updates (ESU). Microsoft has announced an ESU programme for Windows Server 2016, delivered through Azure Arc. Treat it as a bridge, not a fix. I am not quoting prices because the terms change; confirm duration and cost on Microsoft’s current announcement. If you have a legacy production application that cannot be touched, this may be the only realistic path.
A 90-day calendar
| Week | Task |
|---|---|
| 1-2 | Server and application inventory, licence status, vendor compatibility letters |
| 3-4 | Pick the method (upgrade, new server, cloud, ESU) and get budget approved |
| 5-6 | Order hardware or prepare the cloud tenant, build a test server |
| 7-9 | Trial migration, application validation, user testing |
| 10-12 | Production cutover over a weekend, keep the old server powered off, verify backups |
| 13 | Decommission the old server, update the inventory |
Hardware is the riskiest line in this calendar. Lead times on some models run to several weeks, so place the order well before week 5.
Frequently asked questions
Can a Windows Server 2016 machine stay on the internet after 12 January? It should not. If it exposes remote desktop, VPN or file sharing to the outside, move that role first or restrict it at the firewall.
Does it matter if the server is virtual? No. Support follows the operating system version, physical or virtual.
Is Windows Server 2025 worth moving to? Microsoft highlights hotpatching and hybrid management. But if your application vendor has not certified it, 2022 is a perfectly reasonable target, and for most workloads you will not feel the difference.
What if I buy ESU, or just do nothing? In the first month you will notice nothing. But vulnerabilities pile up, and your position with insurers and auditors weakens. Even accepting the risk in writing is better than leaving it unrecorded.
To map your server inventory, choose the path that fits and build the migration calendar, get in touch. An inventory review usually takes one working day and leaves you with a concrete roadmap.
Related Posts
What Happens to Servers and Switches in a Power Cut? UPS Sizing and Care
When the office power drops for one second, what happens to the server, switches and NAS? A walk through UPS types, how to size capacity, when to replace the batteries and the yearly load test that tells you the truth before an outage does.
Read more: What Happens to Servers and Switches in a Power Cut? UPS Sizing and Care
Is It Time to Replace Your Server? Seven Signs to Check
Age alone does not decide it. Software support dates, warranty, disk health, backups and capacity tell you whether to replace the server, move to the cloud or safely wait another year.
Read more: Is It Time to Replace Your Server? Seven Signs to Check
IT Infrastructure Audit: What It Covers and What Turns Up in Week One
What an infrastructure audit actually looks at, from backups and admin accounts to servers nearing end of support, how long it takes, and how to rank the findings so the report leads to action instead of a drawer.
Read more: IT Infrastructure Audit: What It Covers and What Turns Up in Week One