Windows Server 2016 End of Life: Cost Comparison of the Four Options

The short answer: Extended support for Windows Server 2016 ends on January 12, 2027. After that, there will be no more security updates unless Extended Security Updates are purchased. There are four ways forward: buy ESUs, new hardware with Server 2025, in-place upgrade on existing hardware, or migration to Azure. For a typical medium-sized business with one physical server and 25 employees, the five-year costs range from approximately €2,300 to around €22,000, depending on the path taken. The cheapest option is not the one most guides recommend.

Four Months, and a Hardware Market in an Exceptional State

If you're reading this in September 2026, you have about 17 weeks left. Sounds like a lot. It's not, because in between lies the year-end business and, new to this, a procurement market for server hardware that has completely turned around within a year.

The numbers for this are not subtle. DRAM contract prices, according to market observers, rose by 80 to 95 percent in the first quarter of 2026 compared to the previous quarter. Server memory was hit hardest because the three manufacturers that control over 95 percent of global DRAM production have redirected their capacities towards HBM for AI accelerators. A 64 GB DDR5 RDIMM that cost around $255 in contract in the third quarter of 2025 cost over $900 a year later.

RAM accounts for up to a quarter of the material costs in a typical server, and significantly more in virtualization hosts with 256 or 512 GB. If RAM quadruples, it pulls the entire server with it. Add to that delivery times: what used to arrive in two to three weeks in 2024 now takes eight to twelve weeks for some configurations, and several months for Intel CPUs in some cases.

This is the real reason why this article calculates differently from typical migration guides. The standard advice for years has been "new server, current version, done." In 2026, that happens to be the most expensive option of all.

What Really Happens on January 12, 2027

Nothing dramatic at first. The server will continue to boot, shares will be accessible, Active Directory will do its job. What stops is the monthly update supply.

Specifically, this means:

• No more security updates. Not even for critical vulnerabilities. Newly discovered vulnerabilities will continue to be publicly documented, but no longer patched. Your attack surface will grow every month from this day on.
• No technical support. No support cases, no hotfixes, no documentation maintenance.
• This applies to all roles. Not just the kernel. IIS, Active Directory, DNS, DHCP, Hyper-V, print services, everything running on the machine will no longer receive updates.
• All editions. Standard, Datacenter, Essentials, no difference.

Mainstream support, by the way, already expired on January 11, 2022. Server 2016 has been operating in pure security mode for over four years.

The point business owners should understand: Cyber insurers now explicitly ask about systems without vendor support in their risk assessment forms. If, after an incident, the log shows that the encrypted file server has not received patches for 14 months, that is no longer a technical detail, but an issue for claims adjustment. In addition, NIS-2 requires the use of state-of-the-art systems.

The Trap That's Missed in Almost Every Guide

Before we do the math, one point that is overlooked in virtually every migration plan and regularly adds four-figure sums afterwards.

Windows Server CALs are backward compatible, not forward compatible.

A 2025 CAL can access a Server 2016, 2019, and 2022. A 2016 CAL may not access a Server 2019, 2022, or 2025. Without active Software Assurance, there is no upward path.

In practice, this means: If you upgrade your Server 2016 to 2025, you will need a new access license for every user or device. For 25 employees, that's 25 CALs. For 60, it's 60.

And because the calculation would otherwise be wrong: Anyone using Remote Desktop needs additional RDS CALs, not instead. These are extra. This is the mistake almost everyone makes in practice, and it becomes more expensive with each version increase because the RDS CAL is the most expensive single item in the entire license stack.

Anyone who only budgets for the server license typically forgets half of the actual licensing costs for 25 users.

Option 1: Buy ESUs and Buy Time

Microsoft offers Extended Security Updates for Server 2016 after the deadline, for three years, until January 2030. This is an emergency brake, not a plan.

How ESUs work for servers:

Unlike Windows 10, where ESUs are a fixed price per device ($61 in the first year, then doubling to $122 and $244), Server ESUs are charged per core, as a percentage of the current Windows Server list price. Here are three details that mess up the calculation:

• Core minimum. At least 8 cores per processor and 16 cores per physical server. For virtual machines, at least 8 cores per VM. Your small 8-core server will still be billed for 16 cores.
• Cumulative. If you start in the second year, you pay for year one retroactively. There is no skipping.
• Moving target. The percentage refers to the current list price, and that increases. With Server 2025, Microsoft has increased list prices by approximately 10 percent for Standard and 20 percent for Datacenter compared to 2022. Your Year 3 price is not only a higher percentage, but a higher percentage of a higher number.

Then there's the operational part: ESUs for on-premises servers are booked via Azure Arc. So you need an Azure connection for servers that you actually intended to run locally. And the first bill will include back-billing for all months in which ESUs were not yet activated.

What ESUs cost: Microsoft has not released official prices for Server 2016 as of press time. Based on the established model (75 percent of list price in the first year, then increasing) and a list price of around €1,100 net for a 16-core Standard license, you end up with roughly €3,000 to €3,500 over three years for a single 16-core server. This figure is a model calculation, not a price list. As soon as Microsoft publishes, we will update it here.

And after that? After that, you've spent €3,300 and are still running Windows Server 2016, now with no prospects whatsoever. ESUs buy time, nothing else.

When ESUs are still the right choice: If industry software is demonstrably only certified for Server 2016 and the vendor has announced an update for Q3 2027. Then ESUs for one year are a sensible bridge. In all other cases, you're paying rent for a house that's going to be demolished.

Option 2: New Hardware Plus Windows Server 2025

The classic path, and in 2026 the most expensive one. Not because of the license, but because of the hardware.

What comes together:

So you're paying approximately 25 to 55 percent more for the same task than two years ago, and that delta is almost entirely due to memory.

When this path is still correct: If the hardware is due for replacement anyway. A server from 2016 or 2017 with expired warranty, aging power supplies, and disk wear is a risk in itself, regardless of the operating system. If you would have had to replace the machine in 2027 anyway, you can combine the two projects. But the decision should then be made consciously and not because a guide defaults to "new hardware."

If you go this route: buy now, not in December. Analysts do not expect significant new DRAM capacity before the end of 2027. Distributor quotes have shrunk from 30 days to sometimes four to seven days. If you inquire in November, you'll be negotiating against a wall.

Option 3: In-Place Upgrade on Existing Hardware

The option that few guides seriously calculate because there's the least money to be made from it.

What has technically changed: For a long time, the leap from 2016 to a current version was considered a staged model via 2019 or 2022. Since Windows Server 2025, Microsoft explicitly documents the direct path. Non-clustered systems can skip up to four versions at once via installation media, with 2016 to 2025 listed as a supported source. Server 2016 to 2019, to 2022, and to 2025 are all three officially supported in-place paths.

What the in-place upgrade achieves: It replaces the operating system files while preserving roles, settings, installed applications, and data. A weekend window is often sufficient for a clean file server.

What it doesn't achieve: It's not a panacea. Field reports on success rates vary widely. A German service provider reports about 250 supervised terminal server upgrades with exactly one failure, while other sources cite success rates around 60 percent for mixed environments. The difference almost always lies in the condition of the source machine: someone upgrading a domain controller installation that has grown over ten years with legacy drivers faces different challenges than someone with a clean application server.

The hard exclusion criteria:

• Failover clusters require a Cluster OS Rolling Upgrade, where only one version step at a time still applies.
• A Server 2016 with SQL Server 2016 cannot be directly upgraded. First, upgrade SQL to a compatible version, then the operating system. SQL Server 2016, by the way, has been out of support itself since July 14, 2026.
• Domain controllers belong in a side-by-side migration, not an in-place upgrade.
• Check each software vendor individually beforehand. If your ERP provider has not approved Server 2025, Server 2025 is not an option, no matter what Microsoft documents.

The cost side: This is where it gets interesting. The hardware remains, the service is a weekend instead of a project, and the licenses can be used volume licenses. Trading them is permissible within the EU, as ruled by the European Court of Justice in the UsedSoft judgment (C-128/11) and followed by the German Federal Court of Justice with I ZR 129/08. Legally, this has been settled for over a decade.

We sell server cores in 2-core packs, access licenses in 5-packs. For our example with 25 users:

For comparison: This is barely more than what ESUs alone cost over three years, and you end up with a system with security updates until October 14, 2031.

Option 4: Migration to Azure

The path Microsoft would prefer, and the right one for some businesses.

The one real argument: Windows Server instances running in Azure (Azure VM, Azure Local, Azure VMware Solution) receive ESUs without licensing costs. If you won't finish in time anyway, you get the extension there for free instead of paying per core. Plus, there's the Azure Hybrid Benefit, which allows existing licenses with Software Assurance to be credited.

The counter-argument is the operating cost. A file server in your basement with depreciated hardware costs practically nothing except electricity. The same machine as an Azure VM with comparable configuration, storage, and backup, depending on size, ends up costing roughly €3,000 to €4,000 per year, permanently. Over five years, that easily amounts to €20,000, plus the migration itself.

This can pay off if you get rid of a server room, a UPS, air conditioning, and a maintenance contract. For a single file server in a 25-person business, it usually doesn't pay off.

The middle ground many overlook: Not the entire server has to move. If the machine only runs file shares, print services, and a domain controller, the file shares can often be moved to SharePoint or OneDrive and identity to Entra ID, without a server remaining. Then the end of support is not a migration project, but a decommissioning project.

Cost Comparison at a Glance

Assumptions: one physical server, 16 cores, 25 employees with User CALs, file and domain services, hardware built in 2018 and technically sound, consideration period five years from January 2027. All amounts net. ESU prices are a model calculation, see Option 1.

The order surprises many: ESU, the "we'll do nothing for now" option, is more expensive than a complete upgrade to Server 2022 with used licenses. And at the end of the three ESU years, you're back at square one.

Server 2022 or Server 2025? The Answer Changes in Four Weeks

If you've decided on an upgrade, the second question arises. And here's a piece of information that hardly anyone will be aware of in September 2026.

Windows Server 2022 leaves mainstream support on October 13, 2026. Microsoft sent out the 90-day reminder in late July 2026. The October update is the last in mainstream. After that, 2022 will continue in pure security mode for five years, until October 14, 2031.

What that practically means:

Server 2022 makes sense if your industry software is not yet approved for 2025, the hardware is older and driver compatibility becomes an issue, or the budget is tight. You get monthly security updates until October 2031 at no extra cost, and for a file server, that's all you need. The price difference to 2025 is significant with used licenses: €81.99 versus €109.99 per 2-core package, a difference of about €224 for 16 cores.

Server 2025 makes sense if the machine is intended to run beyond 2031, you want hotpatching without a reboot, or you're buying new hardware anyway. Support runs until November 14, 2034. For a new purchase, it would be senseless to immediately go for a version that is already out of mainstream support.

What is not an argument: "Newer is better." A branch office file server that will be replaced in 2029 anyway does not need to be on 2025. It needs to be on something supported, and Server 2022 fully fits that bill until 2031.

What I notice in the inquiries

Since spring, we have been regularly receiving inquiries that all follow the same pattern: Someone has an offer from a system house, finds the price high, and wants to know if it can be done cheaper. When I look at the offers, they are usually calculated correctly. They just answer a different question than the one the customer actually has.

The offer answers: "What does the modern target architecture cost?" The customer asks: "What does it cost for this one server to still receive updates in February?"

I keep seeing three things:

First: CALs are missing from the mind. Almost everyone who asks us about a server license only thinks about the server license. The question "and how many people access it" regularly leads to a pause on the phone. That's why we've put a CAL configurator on the hub page that calculates the correct combination from three pieces of information, because the explanation in the running text is apparently not enough.

Second: User CALs are chosen reflexively, even though Device CALs often fit. If you have 20 people working shifts on six computers, you pay more than three times as much with User CALs. Conversely, the same applies: If you use a desktop and a notebook in the office, User CALs are cheaper. The question is not what is more common, but which number is smaller.

Third: Hardware is replaced without anyone checking if it's failing. A 2018 server with healthy storage, sufficient RAM, and current firmware has no technical reason to be replaced in 2026. The only reason is the operating system, and that can be solved for a fraction of the cost. With current storage prices, this is the difference between 2,000 and 11,000 euros.

The Roadmap to January

What you should do in the next four months, in this order:

Immediately: Inventory. Which machines are running on Server 2016? Which roles and applications are on them? How many cores does each physical machine actually have? How many users and how many devices access them? Without these four figures, any cost calculation is guesswork.

September: Obtain manufacturer approvals. Ask each software manufacturer in writing which Windows Server version is approved. This is the step that can derail projects, and it can take weeks for some providers.

September: Evaluate hardware. SMART values of the storage, age of power supplies, firmware status, warranty status, RAM expansion. Decision: stay or go. If it goes, order now, not in November.

October: Determine target version and licenses. Only here, not before. And include the CALs in your calculation.

November: Test run. Snapshot or backup, upgrade on a copy, click through applications. If you don't have a hypervisor, at least make a full bare-metal backup and a documented rollback path.

December or January: Conversion. On a weekend of your choice, not on January 11th.

Anyone who follows this process makes decisions calmly and negotiates without pressure. Anyone who starts in December will pay ESU surcharges or migrate during the year-end stress.

A good starting point for the migration is our range of Windows Server licenses, along with the corresponding access licenses. If you want to read the details on core licensing, you can find them in the Server Guide.