Windows Server 2016 End of Support: Risks, Deadlines and Your Four Options
Microsoft has set the date in writing: extended support for Windows Server 2016 ends on January 12, 2027. Nothing dramatic happens that morning. Your server boots, your shares mount, your line of business application starts exactly as it did the day before. That is precisely what makes this deadline easy to ignore and expensive to miss.
This guide covers what actually stops, what you are accepting if you do nothing, and the four paths available, with the licensing you need for each.
What actually stops on January 12, 2027
Windows Server 2016 has been in extended support since January 2022. Extended support means one thing only: security updates. No new features, no design changes, no free support calls. On January 12, 2027, that last thread is cut.
After that date:
- No more security patches. The January 2027 Patch Tuesday is the last one. Every vulnerability discovered afterwards stays open on your server permanently.
- No technical support from Microsoft, paid or otherwise, for the operating system itself.
- Software vendors start dropping you. Backup agents, antivirus engines, database drivers and management tools set their own support matrices, and an unsupported host is usually the first thing removed from them. This is often what forces the migration, not the missing patches.
What does not change: the server keeps running, activation stays valid, and your existing licenses do not expire. Windows Server licenses are perpetual. End of support is the end of updates, not the end of the license.
The risk you are actually taking
"We are behind a firewall" is the most common reason companies give for staying put. It is worth being precise about what that argument does and does not cover.
An unpatched server is not exposed only to the internet. It is exposed to every device on the same network, including the laptop of the one employee who opened the wrong attachment. Domain controllers and file servers are the two roles where this matters most, because both are reachable from every workstation by design.
The second cost is compliance, and in the United States it is often the one that arrives first. Payment card requirements, healthcare rules and cyber insurance questionnaires all ask some version of the same question: are your systems receiving security updates from the vendor? After January 12, 2027, the honest answer for Windows Server 2016 is no. Insurers have become considerably more specific about this in renewals, and a failed audit or a declined claim tends to cost more than the upgrade would have.
The third cost is quieter. The longer a server sits on an unsupported version, the more the migration itself costs, because the application stack around it ages too. A 2016 to 2022 move is routine. The same move attempted in 2029 usually means replacing the application as well.
Your four options
| Option | What it costs | How long it buys you | Who it fits |
|---|---|---|---|
| Do nothing | Nothing up front | Zero. Risk starts January 13, 2027 | Nobody, beyond a short planned gap |
| Extended Security Updates via Azure Arc | Paid subscription, billed through Azure | A defined post-support window, security fixes only | Servers with a hard blocker and a dated exit plan |
| Upgrade to Windows Server 2022 | New server license plus CALs | Security updates into October 2031 | Most on-premises workloads |
| Upgrade to Windows Server 2025 | New server license plus CALs | Security updates into November 2034 | New hardware, longest runway wanted |
A word on the second row, because it is the one most often misunderstood. Extended Security Updates for Windows Server 2016 are delivered through Azure Arc, with updates flowing from the Azure portal rather than as a boxed product you buy once. That makes ESU a subscription with an Azure footprint attached, not a shrink wrapped extension. It is genuinely useful when a vendor application will not certify on a newer server until next year. It is a poor substitute for a plan, because the meter runs the whole time and you still have to migrate at the end.
Microsoft's own recommendation is Windows Server 2025 or moving the workload to Azure. That advice is honest but not complete, because it leaves out the option most small and midsize companies actually take.
Upgrading to Windows Server 2022: what the licensing looks like
Windows Server 2016 can move straight to 2022 as a supported in place upgrade from installation media. There is no intermediate hop required. Microsoft supports jumping up to two versions at a time for nonclustered systems on 2022 and earlier, and 2016 to 2022 is exactly two.
One caveat worth knowing before you plan: the Windows Update path to a newer version only exists for 2019 and 2022 moving to 2025. From 2016 you are using installation media, so plan for a maintenance window rather than an overnight patch cycle.
The licensing has three parts.
Core licenses. Windows Server is licensed per physical core, with a minimum of 16 cores per server and 8 per processor. A typical two socket box with eight cores per socket needs exactly the 16 core minimum, which is what Windows Server 2022 Standard covers. Above 16 cores you top up in pairs with a 2 core license. Count the cores in the hardware, not the cores you have assigned to virtual machines.
Client access licenses. Every user or device that touches the server needs a CAL. These are separate from the server license and are not included with it.
Remote Desktop licensing, if you use it. If people log into the server for full desktops or published applications, each of them additionally needs a Remote Desktop Services CAL on top of their regular CAL. Our Windows Server 2022 CAL range covers the RDS side, including five device RDS CALs for shift based setups where several people share the same workstation.
Two more practical notes on the upgrade itself. If the server uses NIC teaming, disable it before you start and re enable it afterwards. And you cannot switch between Server Core and Server with Desktop Experience during an in place upgrade, nor downgrade from Datacenter to Standard.
What about buying 2022 when 2025 exists?
A fair question, and the answer depends on how long the hardware has left.
Windows Server 2022 entered extended support in October 2026, which means it now receives security updates but no new features, through October 2031. That is five more years of patches on a version with a mature driver and application ecosystem, at a lower price than the current release. For a server that will be replaced within that window anyway, it is usually the better economics.
Windows Server 2025 runs on mainstream support until November 2029 and on security updates into November 2034. If you are buying new hardware you expect to keep for eight years, that longer runway is worth paying for.
What you should not do is repeat the 2016 mistake, which was not choosing the wrong version. It was choosing a version and then not looking at the calendar again for eleven years.
What to do this quarter
- Inventory what is actually running 2016. Not what the asset spreadsheet says. Query Active Directory or your management tool for operating system version, and expect to find at least one server nobody remembered.
- Sort the list by exposure, not by age. Domain controllers, file servers and anything reachable from user workstations move to the top.
- Check every application vendor's support matrix against Windows Server 2022 and 2025 before you pick a target version. This is where migrations stall, and finding out in December leaves no room.
- Count your cores and your users so the license quote is real. Sixteen core minimum per server, CALs for everyone who connects, RDS CALs on top for anyone using Remote Desktop.
- Book the maintenance window now, while January is still four months away. In place upgrades from 2016 need installation media and a reboot, not a patch cycle.
- Decide your fallback before you start. A tested backup you have actually restored once is the difference between a long evening and a lost weekend.
The companies that handle this well are not the ones with the biggest budgets. They are the ones that started while the deadline was still boring.
Related reading
- Migrating Windows Server 2016 to 2022: in-place upgrade vs clean install walks the actual procedure, including the prerequisites that stop an upgrade partway.
- Windows Server 2012 R2 is years past end of life is the same conversation three years further along, and it is where the 2016 estate is heading if nothing happens.
- The complete Windows Server 2022 licensing guide covers cores, CALs and virtualization rights in one place, with a worked example.