Windows Server 2016 reaches the end of extended support on 12 January 2027 (Microsoft's lifecycle page, read on 4 November 2026, lists the cut-off as the early hours of 13 January, Pacific time). After that date Microsoft ships no security updates for it, and a server that is still running it becomes a finding in every audit that asks whether software is supported. Mainstream support ended in January 2022, so for almost five years the product has received security fixes only. This guide covers what actually stops, what the risk is, the four options Microsoft leaves you, the supported in-place upgrade paths, and a migration checklist for the roles most 2016 servers still carry.
What stops on 12 January 2027
Extended support is the phase in which Microsoft publishes security updates and paid support but no new features or non-security fixes. When it ends:
- No more security updates through Windows Update, WSUS or the Update Catalog, including for vulnerabilities rated critical.
- No technical support from Microsoft for the operating system, even paid.
- Dependent products follow. Microsoft 365 Apps and current versions of SQL Server Management Studio, Defender and other agents drop support for the platform on their own schedules; Microsoft's "Windows Server end of support and Microsoft 365 Apps" page tracks these.
- Containers too. Windows Server 2016 container base images share the same lifecycle dates.
What does not stop: the server keeps booting, activation stays valid, and nothing in the software disables itself. That is the problem. A 2016 server in January 2028 looks exactly as healthy as it did in January 2026, except that a year of published vulnerabilities applies to it with no patch.
Why running past the date is a compliance problem, not just a security one
Most frameworks do not name Windows versions, but all of them require supported software or a documented exception. PCI DSS requirement 6 asks that system components be protected from known vulnerabilities by installing applicable security patches; an unsupported operating system cannot meet it without compensating controls that an assessor accepts. The HIPAA Security Rule's risk analysis and patch management expectations point the same way. ISO 27001's Annex A controls on technical vulnerability management (A.8.8 in the 2022 edition) and on change management treat end-of-life software as a vulnerability to be addressed. Cyber-insurance questionnaires now ask the question directly.
Extended Security Updates are the usual exception path, and here Windows Server 2016 is different from 2012 and 2012 R2. Microsoft's ESU overview page, read on 4 November 2026, lists ESU programmes only for Windows Server 2012 and 2012 R2 (which ended on 13 October 2026). No ESU programme for Windows Server 2016 was published on that page at the time of writing. Check the page again before you plan on buying time; if nothing appears, there is no paid extension to fall back on, and the date is the date.
Your four options
- In-place upgrade on the existing server. Windows Server 2016 can upgrade directly to Windows Server 2019, 2022 or 2025 using installation media (Microsoft's upgrade-path table, read on 4 November 2026). Settings, roles and data stay. Fastest, but it carries every misconfiguration forward, and some roles do not support it (check Microsoft's role migration matrix for Active Directory Certificate Services, Hyper-V clusters and anything third-party).
- New server, migrate the roles. Build Windows Server 2025 clean, move the roles and data, cut over, retire 2016. More work, cleanest result, and the only option that also changes where the server runs: this is the moment many teams move a server from an office rack or an old VPS to a hosted Windows Server on an HA cluster.
- Isolate and run on. Keep 2016 for an application that cannot move, behind a firewall with no internet exposure, no browsing, no mail, and a documented exception with an end date. Acceptable for a legacy line-of-business box for a few months; not acceptable for anything public.
- Retire the workload. Many 2016 servers run a file share, a print server or an application that has since become a SaaS product. The cheapest upgrade is the server you switch off.
Skipping to 2025 rather than 2022 is worth the small extra testing. Windows Server 2022 left mainstream support on 13 October 2026 and its extended support ends on 14 October 2031; Windows Server 2025 is in mainstream support until 13 November 2029 and extended support until 14 November 2034 (both from Microsoft's lifecycle pages, same date). Upgrading to 2022 buys five years; 2025 buys eight.
The supported upgrade paths
| From | To Windows Server 2019 | To Windows Server 2022 | To Windows Server 2025 |
|---|---|---|---|
| Windows Server 2012 R2 | Yes | No | Yes |
| Windows Server 2016 | Yes | Yes | Yes |
| Windows Server 2019 | n/a | Yes | Yes |
| Windows Server 2022 | n/a | n/a | Yes |
Microsoft's rules, as read on 4 November 2026: non-clustered servers can jump up to two versions when the target is 2022 or earlier and up to four versions when the target is 2025; cluster rolling upgrades move one version at a time. An in-place upgrade keeps the edition (Standard to Standard) and can move Standard to Datacenter but not back. Server Core cannot switch to Desktop Experience during the upgrade, NIC Teaming must be disabled first, and a licensed installation cannot be upgraded to an evaluation copy. Back up before you start; Microsoft says so in bold and so do we.
Licensing: each Windows Server version needs its own licence. On your own hardware that means a new licence or active Software Assurance. On a hosted server the licence is the provider's problem: a MassiveGRID Windows server rents Windows Server Standard per vCore under our SPLA agreement ($6.00 per vCore a month on the managed server, $6.31 per vCPU on a Windows VPS), and the version you install is your choice from 2016 to 2025. Our SPLA hosting page explains how that works.
Migration checklist by role
IIS and web applications
- Export the IIS configuration (Web Deploy or
appcmd list site /config /xml), note application pool identities, .NET versions and bindings. - .NET Framework 4.8.1 and .NET 8 and 9 run on Windows Server 2025; .NET Framework 3.5 is still installable as a feature. Older ASP.NET sites usually run unchanged.
- Re-issue or export certificates with private keys; HTTP/2 and TLS 1.3 are on by default in 2025, so test old clients.
- Cut over by changing DNS with a short TTL, keeping the 2016 server running read-only for a week.
File servers
- Use Storage Migration Service (in Windows Admin Center) to copy shares, permissions and even the server name and IP to the new server. It was built for 2012 and 2016 retirements.
- Check for SMB 1.0 dependencies first; it is off by default on new installs and old scanners and NAS devices still try to use it.
Domain controllers
- Never upgrade a domain controller in place if you can avoid it. Promote a new 2025 server, move the FSMO roles, let replication settle, demote the 2016 one.
- Raise the forest and domain functional levels only after the last old controller is gone.
SQL Server hosts
- Check the SQL Server version first. SQL Server 2016 left extended support on 14 July 2026 and SQL Server 2017 leaves it on 12 October 2027, so an old Windows server often carries an old SQL Server too; the SQL Server 2016 and 2017 end-of-support guide covers that half.
- Back up, restore onto the new server, run the Data Migration Assistant, then switch the application's connection string. A side-by-side move also lets you change edition and licensing in one step.
Remote Desktop Services
- RDS CALs are version-bound upwards: 2016 CALs do not cover a 2025 session host. Budget for new CALs, or rent RDS user licences monthly on a hosted server ($8.90 per user a month at MassiveGRID).
Where a hosted Windows Server 2025 fits
A retirement is the natural moment to stop owning the hardware. On a hosted server the operating system is one of the templates on the order form, so the new Windows Server 2025 machine exists in minutes; the old 2016 box becomes the migration source rather than the thing you are trying to upgrade without breaking. Three tiers cover most 2016 workloads:
- A Windows VPS on shared cores from $3.99 a month for a file server, a small IIS site or a utility box, on the 180-day evaluation or with the licence at $6.31 per vCPU.
- A Windows Dedicated VPS with reserved cores from $18.84 a month for a domain controller, an RDS session host or a busy application server.
- A Managed Cloud Dedicated Server from $69.34 a month with Windows Server Standard included, where we patch and back up the operating system, for the server you would rather not administer again.
All three run on a Proxmox HA cluster that restarts a virtual machine on another node within about two minutes of a hardware failure, which is the other thing most 2016 servers never had. Pick New York, London, Frankfurt or Singapore to keep the data where it is today, and migrate at no extra charge with our team if the server is managed.
Frequently Asked Questions
When exactly does Windows Server 2016 support end?
Extended support ends on 12 January 2027; Microsoft's lifecycle page lists the cut-off as 6:59 AM Pacific time on 13 January 2027. Mainstream support ended in January 2022. After the extended date Microsoft publishes no security updates for Windows Server 2016.
Will there be Extended Security Updates for Windows Server 2016?
As of 4 November 2026 Microsoft's Extended Security Updates overview page lists ESU programmes only for Windows Server 2012 and 2012 R2, which ended on 13 October 2026. No ESU for Windows Server 2016 was published there. Check the page before relying on an extension.
Can I upgrade Windows Server 2016 directly to Windows Server 2025?
Yes. Microsoft's supported in-place upgrade paths allow Windows Server 2016 to upgrade to 2019, 2022 or 2025 using installation media. The edition is kept (Standard to Standard), Server Core cannot be switched to Desktop Experience during the upgrade, and you need a licence for the new version.
Do my Windows Server 2016 CALs and RDS CALs work on 2025?
No. CALs must be the same version as the server or newer, so 2016 CALs do not cover a Windows Server 2025 host. On a hosted server rented under SPLA the Windows licence is per vCore and RDS users can be rented monthly instead of buying CALs.
What is the cheapest way to replace a Windows Server 2016 box?
Often to retire it, if the workload has moved to a SaaS product. Otherwise a hosted Windows Server 2025 VPS starts at $3.99 a month on shared cores with Microsoft's 180-day evaluation, and the licence adds $6.31 per vCPU a month when you need it permanently.
A Windows Server 2025 host, ready before the old one is switched off
MassiveGRID runs Windows Server 2016 to 2025 on a Proxmox HA cluster in New York, London, Frankfurt and Singapore: a Windows VPS from $3.99 a month, reserved cores from $18.84, or a managed server with the Windows Server Standard licence included from $69.34. Rent the licence under our SPLA agreement or bring yours with Software Assurance.
Compare Windows Server hosting tiers