← Blog

Windows Server 2016 end of life: what to do

Is Windows Server 2016 still supported? Yes, but only until 12 January 2027, when it receives its last security update. That’s about ten weeks away, with the holidays in between, so if you still run 2016 servers, the time to plan is now.

This post covers how to find them, where to move them, and the three realistic routes for each one.

Key dates

VersionMainstream supportSecurity updates end
Windows Server 2016Ended 11 January 202212 January 2027 (paid ESU possible until January 2030)
Windows Server 2019Ended 9 January 20249 January 2029
Windows Server 2022Ended 13 October 202614 October 2031
Windows Server 2025Until 13 November 202914 November 2034

Mainstream support means bug fixes and improvements as well as security updates. After it ends, a version gets security updates only, until the last date in the table.

What actually stops on 12 January

Microsoft calls it end of support; most people call it end of life. Either way, nothing switches off on the day. Your servers will keep booting, serving and running your applications.

What stops is the security fixes. From February, any new vulnerability in Windows Server 2016 stays open, and attackers know which versions are no longer patched. Software vendors also tend to drop a Windows version from their supported list once Microsoft does, which can leave you on your own when something breaks.

Find your 2016 servers

On a single server, this shows the version and build. Windows Server 2016 reports version 10.0.14393.

Get-CimInstance Win32_OperatingSystem | Select-Object Caption, Version, BuildNumber

In a domain, this lists every computer account running Server 2016, with the date each one last signed in (it can be up to about two weeks out of date), so you can spot stale entries. It needs the Active Directory PowerShell module, so run it on a domain controller or an admin machine with the management tools installed.

Get-ADComputer -Filter 'OperatingSystem -like "*Server 2016*"' -Properties OperatingSystem, LastLogonDate |
  Select-Object Name, OperatingSystem, LastLogonDate | Sort-Object Name

It only finds domain-joined servers, so check workgroup and DMZ servers separately. The list can also include Hyper-V Server 2016 and Windows Storage Server 2016. ESU only covers Standard and Datacenter, and Microsoft doesn’t list either product as an in-place upgrade path to Windows Server 2025, so plan to rebuild them.

For each 2016 server, note three more things, because they decide which route fits. First, the roles and features it runs:

Get-WindowsFeature | Where-Object Installed | Select-Object Name, DisplayName

Second, its edition and whether it’s Server Core or the full desktop version. An in-place upgrade keeps both, so you can’t use it to switch from one to the other.

Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' | Select-Object EditionID, InstallationType

Third, whether it uses NIC Teaming, which has to be removed before an in-place upgrade and rebuilt afterwards. No output means no teams.

Get-NetLbfoTeam

On a Hyper-V host, the virtual switch may sit on that team. When you rebuild the network after the upgrade, create a Switch Embedded Teaming (SET) switch rather than a new LBFO team, because from Server 2022 Microsoft no longer supports binding a Hyper-V virtual switch to an LBFO team. Then check that each virtual machine’s network adapter is connected to the new switch.

All of these commands only read information; none of them change anything. They’re general guidance, provided as-is.

Which version to move to

For most servers, the answer is Windows Server 2025. It’s supported until November 2034, so a move now buys you eight years before the next one.

What about Server 2022?

Upgrading Windows Server 2016 to 2022 is supported too, in place or by rebuilding, and plenty of guides still recommend it. But Server 2022 left mainstream support on 13 October 2026. It still gets security updates until October 2031, but no further improvements, and it gives you five years where 2025 gives you eight. Unless an application you depend on isn’t yet supported on 2025, there’s little reason to go through the work of an upgrade and land on the older version.

Three routes, server by server

1. Can you upgrade Windows Server 2016 to 2025 in place?

Yes. Since Server 2025, Microsoft supports skipping up to four versions in one go, so a 2016 server can upgrade directly to 2025 while keeping its files, settings and applications. It’s the quickest route when the server is fairly clean and its roles support it, but check the catches first:

  • You need a Server 2025 licence, and possibly new CALs. Unlike Windows on a PC, each Windows Server upgrade needs its own licence. A CAL covers its own version of Windows Server and earlier ones, so users and devices that connect need Windows Server 2025 CALs, unless your CALs have active Software Assurance; public websites don’t need them. A Remote Desktop session host needs Windows Server 2025 RDS CALs, installed on a licence server that also runs Server 2025. If a hosting provider licenses your server, CALs don’t apply, but ask them about licences for Remote Desktop users.
  • Check the processor. Server 2025 needs a CPU that supports SSE4.2 and POPCNT. Very old hosts can fail setup, and so can virtual machines running with Hyper-V’s processor compatibility mode or a low VMware EVC baseline. Microsoft’s Coreinfo tool shows what the processor supports. On a virtual machine, run it inside the VM, because that’s what setup sees.
  • The edition and installation type stay the same. Standard can move up to Datacenter, but not the other way, and Server Core stays Server Core.
  • Evaluation copies need converting first. If EditionID ends in Eval, the server is an evaluation copy. Microsoft’s guidance is to convert it to a licensed edition with DISM before upgrading. A domain controller can’t be converted, so replace it instead. A Server Core Standard evaluation copy can only become Datacenter, which costs much more.
  • Not every role upgrades in place. Check Microsoft’s role and feature migration matrix against your list from above.
  • Domain controllers and clusters are different. Microsoft advises against upgrading a domain controller in place (see route 2), and clustered servers use a rolling upgrade that moves one version at a time.
  • On a hosted server, ask your provider whether they support in-place upgrades. On Azure, for example, Microsoft’s installation-media method doesn’t apply, and Azure VMs have their own upgrade process.

Step by step

This follows Microsoft’s in-place upgrade instructions:

  1. Back up the server and test a restore. On a virtual machine, take a snapshot as well. Make sure you have console access, in case the upgrade stops partway and Remote Desktop isn’t available.

  2. Save the current system information, so you have a record of how the server was set up. An elevated PowerShell window starts in C:\Windows\System32, so switch to a working folder first, then copy the files somewhere off the server:

    New-Item -ItemType Directory -Path C:\Temp -Force | Out-Null
    Set-Location C:\Temp
    Get-ComputerInfo -Property WindowsBuildLabEx, WindowsEditionID | Out-File .\computerinfo.txt
    systeminfo.exe | Out-File .\systeminfo.txt
    ipconfig /all | Out-File .\ipconfig.txt
    Get-NetLbfoTeam | Format-List * | Out-File .\nicteam.txt
    # Hyper-V hosts only
    Get-VMSwitch | Format-List * | Out-File .\vmswitch.txt
    Get-VMNetworkAdapter -All | Format-List * | Out-File .\vmnics.txt
    Get-VMNetworkAdapterVlan -ManagementOS | Out-File .\hostvlans.txt
  3. Remove NIC Teaming if the server uses it. Do this from the console, because the server’s IP address goes with it; then give the same address to one of the physical adapters so you can reach the server again. On a Hyper-V host, the address usually sits on the virtual switch rather than the team: shut down or move any running virtual machines, remove the external virtual switch that uses the team, then remove the team (see the note on SET above).

  4. Mount the Windows Server 2025 media and run setup.exe. Let setup download updates, enter your product key, and pick the edition.

  5. Choose “Keep files, settings, and apps”. This is the option that upgrades without losing data, roles or installed applications. Then select Install. The server restarts several times.

  6. Check the result: confirm the new version with the first command from this post (Server 2025 reports version 10.0.26100), make sure your applications run and clients can connect, rebuild your network teaming if you used it (as a SET switch on a Hyper-V host), and install the latest updates.

If setup fails and rolls back, its logs are in C:\$WINDOWS.~BT\Sources\Panther and C:\$WINDOWS.~BT\Sources\Rollback; after a completed upgrade, they’re in C:\Windows\Panther. Microsoft’s SetupDiag tool reads them and points to the cause.

2. Clean build and migrate

Build a new Server 2025 machine, move the roles, data and applications across, then retire the old one. It takes longer, but you end up with a clean system instead of carrying years of accumulated changes forward.

It’s the better route for servers that have been modified many times over the years, and it’s Microsoft’s recommended route for domain controllers: promote a new Server 2025 domain controller, move the FSMO roles to it, then demote the old one.

3. Windows Server 2016 ESU: cost and requirements

If a server genuinely can’t move before 12 January, Microsoft sells Extended Security Updates (ESU) for Windows Server 2016. It isn’t free, and the details matter:

  • Mostly through Azure Arc. You connect the server to Azure with the Azure Arc agent (version 1.62 or later), enrol it in the Azure portal and pay through an Azure subscription. Microsoft also sells it through Enterprise Agreement, CSP and other licensing programmes.
  • Only for Standard and Datacenter editions, and only if the server is covered by Software Assurance, or licensed through a hosting provider (SPLA) or a server subscription.
  • The price is per core, per month. At Azure’s list price, Standard costs about $5.25 per core per month, with a minimum of 8 cores per virtual machine, or 16 per physical server. That’s about $42 a month for a typical small VM. Datacenter costs about $30 per core per month. The price is the same however you buy it and wherever the server runs; unlike Server 2012 R2, ESU isn’t free for servers running in Azure.
  • Billing starts on 13 January 2027. If you enrol later, Microsoft bills back to 12 January, so waiting doesn’t save anything.
  • Security fixes only, for up to three years, until January 2030. No new features, no non-security fixes and no technical support.

ESU buys time. It isn’t a plan in itself, and it gets more expensive the longer you rely on it.

A plan that fits before the holidays

  • This week: list your 2016 servers and their roles, and pick a route for each one.
  • By mid-November: test a restore from each server’s backup, and check your key applications’ supported versions for Server 2025.
  • Late November: do one low-risk server first, upgraded or rebuilt, and let it run for a week.
  • Early December: work through the rest, each with a fresh snapshot or backup and an agreed rollback window.
  • Anything left by mid-December: decide on ESU for it and set up Azure Arc before 12 January, rather than finding out in January that a server was missed.

What we did

Every server we manage was moved off Windows Server 2016 earlier this year, and every new Managed Windows VPS runs Windows Server 2025 by default.

Sources

This post is general information, not professional advice for your specific setup.

Rather not do this yourself?

If you'd rather hand this over, our Server Management service includes the upgrade or migration of a 2016 server we take on, as long as you hold a licence for the newer version.

See how it works →