Support for Windows Server 2016 ends on 12 January 2027. After that date Microsoft stops shipping security updates for it — permanently. That is close enough that if you’re still running 2016 in production, this belongs on your roadmap now, not next year.
What changes on 12 January 2027
Nothing breaks on the day. Your servers boot, your services run, your users notice nothing. What stops is the steady stream of security patches. From that point on, every newly discovered vulnerability in Windows Server 2016 stays open on your machine forever.
That creates three practical problems:
- Security — unsupported server operating systems are a standard target precisely because the flaws become public while the fix never ships.
- Compliance — PCI DSS, HIPAA, ISO 27001 and most cyber-insurance policies require supported, patched systems. An out-of-support server can fail an audit by itself.
- Compatibility — backup agents, database engines and line-of-business apps progressively drop support for older server releases.
How much time do you actually have?
Less than the date suggests. A server migration isn’t a weekend job — inventory, application compatibility testing, hardware checks and a maintenance window all take real calendar time. Most teams should be starting a 2016 migration at least six months before the deadline, and sooner if Active Directory or SQL workloads are involved.
Your upgrade options
1. Move to Windows Server 2025 (recommended for most)
The newest release, and the one that buys you the longest runway — supported into the mid-2030s, so you won’t be repeating this exercise soon. It also brings meaningful security hardening, better storage performance and improved Hyper-V.
- Windows Server 2025 Standard — for most business workloads.
- Windows Server 2025 Datacenter — for heavy virtualization, with unlimited VMs.
2. Move to Windows Server 2022
Mature, extremely widely deployed, and supported until October 2031. If your applications are certified for 2022 but not yet for 2025, this is the pragmatic choice.
3. Step through Windows Server 2019
In-place upgrades move one major version at a time, so 2016 → 2019 is a supported single hop. Server 2019 Standard is supported until January 2029, which makes it a legitimate destination if you need a smaller jump — just know you’ll be planning the next move within a couple of years.
4. Migrate to a clean install
Frequently the better route for a server that’s been running since 2016. Build the new machine on a current release, migrate roles and data across, then retire the old box — nothing accumulated gets carried forward.
Standard, Datacenter or Essentials?
- Essentials — very small deployments (up to 25 users / 50 devices). See Server 2019 Essentials.
- Standard — the default for most businesses, with light virtualization.
- Datacenter — heavy virtualization and private cloud, with unlimited VM rights.
Full breakdown in Standard vs Datacenter vs Essentials.
Windows Server support dates
- Server 2012 / 2012 R2 — ended 10 October 2023 (paid ESU through October 2026). See your options for 2012 R2.
- Server 2016 — ends 12 January 2027
- Server 2019 — ends 9 January 2029
- Server 2022 — ends 14 October 2031
- Server 2025 — current release, supported into the mid-2030s
A migration checklist
- Inventory every role each 2016 server runs — AD DS, DNS, DHCP, file, print, IIS, SQL, backup targets.
- Confirm application support on your target release before buying licences.
- Check hardware — newer releases raise the bar on CPU, TPM and firmware.
- Test on a VM before touching production.
- Plan the maintenance window, and take a verified full backup first.
- Licence and activate — see upgrading an evaluation to full, or activating by phone if the server has no internet access.
Browse every edition in Windows Server. Keys are genuine, delivered instantly on your order confirmation page, and covered by our 7-day activation warranty. Not sure which edition you need? Open a ticket and we’ll help you choose.
Frequently Asked Questions
When exactly does Windows Server 2016 support end?
Extended support ends on 12 January 2027. After that date Microsoft no longer issues security updates for it.
Can I upgrade from Server 2016 straight to Server 2025?
In-place upgrades move one major version at a time, so a direct jump usually isn’t supported. Most administrators either step through an intermediate release or migrate to a clean install of 2025.
Should I upgrade to Server 2019 or go straight to 2022/2025?
If your applications support it, go to 2022 or 2025 — you get years more support and avoid repeating the migration. Choose 2019 only when a smaller jump is required.
What happens if I keep running Server 2016 after the deadline?
It keeps working but stops receiving security updates, which raises your risk over time and can put you out of compliance. If you must keep it running, isolate it from the internet and set a firm migration date.