Skip to main content
Guide, 6 minute read

Upgrading Windows Server 2016 to 2019, 2022, or 2025: Paths, Hardware Checks, and Support Runway

Which in-place upgrade paths Microsoft supports from Windows Server 2016, the hardware a newer release needs, what breaks an in-place upgrade, and how long each target version is supported.

Planning guidesInfrastructure managers and system administrators planning the move off Windows Server 2016By , Founder and CEO, Days Dynamics. Published November 9, 2026, updated November 10, 2026.

2016 can upgrade in place to 2019, 2022, or 2025, if the host and the applications allow it

Microsoft's upgrade matrix supports an in-place upgrade from Windows Server 2016 to Windows Server 2019, 2022, or 2025. Starting with Windows Server 2025, nonclustered systems can upgrade up to four versions at a time, so 2016 to 2025 is a supported single step. For Windows Server 2022 and earlier targets, nonclustered systems can upgrade up to two versions at a time, and a cluster OS rolling upgrade moves one version at a time. The upgrade itself is the easy part. Whether the hardware, the roles, and the applications on the server support the target release decides whether an in-place upgrade or a fresh install on new hardware is the better path.

How long each target version is supported

Pick the target by how long you want before the next migration. The dates are from Microsoft's Windows Server release information.

Target versionMainstream support endsExtended support endsRead
Windows Server 2019EndedJanuary 9, 2029Two years of runway after the 2016 deadline; only for an application that supports nothing newer
Windows Server 2022EndedOctober 14, 2031Reasonable when a vendor has certified 2022 but not 2025
Windows Server 2025November 13, 2029November 14, 2034The default target; Microsoft's own guidance points to 2025 or to Azure

See the replace your server or move to Azure comparison.

Hardware checks before any in-place upgrade

Microsoft's hardware requirements page covers Windows Server 2016 through 2025. Most processor minimums are shared, but Windows Server 2025 adds SSE4.2 and POPCNT and raises the Server Core memory minimum from 1 GB to 2 GB, so check each 2016 host against the 2025 list before planning an upgrade on it.

  • Processor: 1.4 GHz 64-bit with NX and DEP, CMPXCHG16b, LAHF/SAHF, PrefetchW, and Second Level Address Translation for every version. Windows Server 2025 also requires SSE4.2 and POPCNT. Microsoft points to the Sysinternals Coreinfo tool to check a processor.
  • A TPM and UEFI Secure Boot are listed as required only for certain features, not for a basic installation. Secured-core server (Windows Server 2022 and later) requires TPM 2.0, Secure Boot, and virtualization-based security to be enabled.
  • Firmware and driver support from the server manufacturer for the target release. A host that boots the installer is not the same as a host the manufacturer supports on that release.
  • Warranty or support contract status. A host leaving warranty in the next year is usually a better candidate for replacement than for an upgrade.

What blocks or complicates an in-place upgrade

  • Switching between Server Core and Desktop Experience during an in-place upgrade is not supported. The installation type stays as it is.
  • A domain controller cannot be converted to a retail version during an upgrade, and domain controllers follow their own upgrade guidance. Most teams promote a new domain controller instead.
  • Clustered servers upgrade one version at a time through cluster OS rolling upgrade, and nonclustered servers are the only ones eligible for a direct multi-version jump.
  • Roles and features that do not support in-place upgrade, and application vendors that have not certified the target release.
  • A full backup with a restore test, and a maintenance window: Microsoft lists both as prerequisites because downtime is required.

See the Windows Server 2016 replacement service.

Upgrade in place, or fresh install on new hardware

ChooseWhenWatch for
In-place upgradeHost is under warranty and supported by its manufacturer on the target release; roles and applications are certified; a tested backup existsAccumulated configuration drift carries forward; the server is down for the upgrade window
Fresh install on a new host, then migrate roles and dataHost is near the end of warranty, or the server has grown roles over the years that should be separatedTwo systems to run during cutover; application reinstall and data migration effort
Move the workload to Azure or another platformThe application suits a cloud or virtual platform and the data location allows itLicensing changes, network dependencies, and backup tooling that may change
Bridge with Extended Security UpdatesThe server cannot move before January 12, 2027 for a dated reasonCosts about a full license per year; buys time, not a destination

See the Windows Server 2016 Extended Security Updates guide.

Turning this into a plan

  • Record each 2016 server's host model, warranty date, installation type, roles, and application vendor support for 2022 and 2025.
  • Default to Windows Server 2025 and note the servers that need 2022 or 2019 because of a vendor.
  • Separate domain controllers and clusters into their own workstream.
  • Schedule the maintenance windows and the backup restore tests before January 12, 2027.

See the Infrastructure End-of-Support Assessment.

Get an upgrade or replace call for every 2016 server

Send us your server list with host models and warranty dates. We will mark each one upgrade, replace, migrate, or bridge, pick the target version, and sequence the maintenance windows. A planning call is planning support, not a quote, an audit, or a commitment on licensing, availability, or delivery dates.

Sources

Primary sources checked when this guide was written. Dates and product status can change, so confirm on the source before you rely on them.

Planning this project now?

Turn the checklist into a plan

The 2-minute IT quiz turns this checklist into ranked priorities for your situation, before any contact details.