Upgrade Windows Server 2019 to 2025: In-Place Step by Step – LicenceHouse guide

Yes, you can upgrade Windows Server 2019 to 2025 directly with an in-place upgrade, keeping your settings, roles and data. Microsoft supports it from installation media or as a feature update through Windows Update. You need a Windows Server 2025 licence, a tested backup and a maintenance window. Below is the step-by-step process, plus the cases where a clean install is the better route.

Stage What you do Typical time
1. Check eligibility Confirm edition, hardware, roles and apps support Server 2025 1–2 hours
2. Back up and test restore Full backup of OS, apps, data and VMs; prove it restores Varies with data size
3. Collect diagnostics Save system, edition and network info off the server 10 minutes
4. Prepare the server Install latest updates, disable NIC Teaming, stop VMs 30–60 minutes
5. Run the upgrade setup.exe from media, or the Windows Update feature update 1–2 hours, several restarts
6. Verify and activate Check version, edition, activation, roles and apps 30–60 minutes

Can you upgrade Windows Server 2019 to 2025 directly?

Yes. Microsoft lists Windows Server 2019 as a supported direct in-place upgrade source for Windows Server 2025, using either installation media or a Windows Update feature update. Starting with 2025, non-clustered servers can jump up to four versions at once, so you do not need to stop at Server 2022 on the way.

There are firm exceptions. Microsoft's Windows Server upgrade overview rules out in-place upgrades that change language, switch between Server Core and Desktop Experience, start from an evaluation or preview build, run on a server that boots from VHD, or come from Windows Storage Server editions.

Failover clusters are different again. A cluster OS rolling upgrade can only move one version at a time, so a 2019 cluster has to pass through 2022 before reaching 2025.

Do I need a new licence to upgrade Windows Server 2019 to 2025?

Yes. Unlike Windows 10 to 11 on the desktop, every Windows Server version upgrade needs its own licence for the target version. Microsoft states this directly in its upgrade guidance. A Server 2019 product key will not activate Server 2025, so buy the 2025 licence, and any CALs your users or devices need, before you schedule the work.

By default, an upgrade keeps the same edition: Standard stays Standard and Datacenter stays Datacenter. You can move from Standard to Datacenter during the upgrade, but not from Datacenter down to Standard.

For most single-host businesses, Windows Server 2025 Standard is the matching licence for an existing 2019 Standard server; see the current price on the product page. Remember that Windows Server 2025 CALs are also needed for users or devices connecting to the upgraded server, as our guide to Windows Server CALs explains.

Blue network cables plugged into a patch panel with status lights, like a server being prepared for an in-place upgrade

Should I upgrade in place or do a clean install?

Upgrade in place when the server runs roles that support it, the hardware is staying, and you want the shortest path with the fewest reconfigurations. Choose a clean install or migration when you are moving to new hardware, the server is a domain controller, or years of accumulated software and configuration drift make a fresh start attractive.

Scenario Recommended route
File server, print server or line-of-business app on supported hardware In-place upgrade
Hyper-V host on supported hardware In-place upgrade, with all VMs shut down first
Active Directory domain controller New 2025 DC, transfer roles, demote the old DC
Failover cluster node Cluster OS rolling upgrade, one version at a time
Ageing hardware or a server with years of clutter Clean install on new hardware and migrate roles

What we commonly see: in-place upgrades fail less often because of Windows itself than because of third-party software: old antivirus agents, backup agents, and hardware management tools with kernel drivers. Uninstalling or updating those before setup removes the most common cause of rollbacks.

What should I check before upgrading Windows Server 2019 to 2025?

Before upgrading, confirm the server meets the Windows Server 2025 hardware requirements, that every installed role supports in-place upgrade, that your applications and their vendors support Server 2025, and that you hold a valid Server 2025 licence. Then take a full backup and prove it restores, because Microsoft lists a tested backup as a prerequisite.

  • Hardware: the processor must support SSE4.2 and POPCNT, and the server needs at least 2 GB of RAM and 32 GB of disk. Our Windows Server 2025 system requirements guide shows how to check with Coreinfo.
  • Roles: check each role against Microsoft's role and feature upgrade matrix.
  • Applications: confirm vendor support, especially for SQL Server, Exchange, accounting and backup software.
  • Edition and media: match the language and installation option (Core or Desktop Experience) of the existing server.
  • Free space: leave generous room on C: for setup files and the rollback copy of the old installation.
  • Evaluation copies: an evaluation install cannot be upgraded in place; see our guide to converting Windows Server Evaluation.

How do I upgrade Windows Server 2019 to 2025 with installation media?

Mount the Windows Server 2025 ISO on the 2019 server, run setup.exe, enter your 2025 product key, choose the same edition and installation option, accept the licence terms and select Keep files, settings, and apps. Setup then checks compatibility, installs and restarts the server several times before you can sign in again.

  1. Collect diagnostics first. In an elevated PowerShell prompt run Get-ComputerInfo -Property WindowsBuildLabEx,WindowsEditionID | Out-File .\computerinfo.txt, systeminfo.exe | Out-File systeminfo.txt and ipconfig /all | Out-File ipconfig.txt, then copy the files off the server.
  2. Shut down or migrate any running virtual machines, and disable NIC Teaming if the server uses it.
  3. Right-click the Windows Server 2025 ISO and select Mount, then open setup.exe from the new drive and accept the User Account Control prompt.
  4. Leave the default to download updates during setup, or choose Change how Setup downloads updates if the server has restricted internet access, then select Next.
  5. Enter your Windows Server 2025 product key and select Next.
  6. Select the matching edition, for example Windows Server 2025 Standard (Desktop Experience), then Next.
  7. Review the notices and licence terms and select Accept.
  8. Select Keep files, settings, and apps, then Next.
  9. On the Ready to install screen, select Install and let the server restart as needed.

The full procedure, including Azure VM exceptions, is in Microsoft's perform an in-place upgrade of Windows Server guide. For downloading the correct media, our Windows Server 2025 Standard download and installation guide covers ISO options.

Can I upgrade Windows Server 2019 to 2025 through Windows Update?

Yes. Windows Server 2019 and 2022 can receive Windows Server 2025 as a feature update through Windows Update, without mounting any media. The server first needs the March 2026 cumulative update (KB5078752 for Server 2019) or later, plus a registry value that allows the feature update offer to appear.

  1. Install the latest cumulative update for Windows Server 2019 and restart.
  2. In an elevated PowerShell prompt, create the policy key: New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AllowWindowsServerFeatureUpdate"
  3. Add the value: New-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AllowWindowsServerFeatureUpdate" -Name "AllowWindowsServerFeatureUpdate" -PropertyType DWord -Value 1
  4. Open Settings > Windows Update and check for the Windows Server 2025 feature update banner.
  5. Select Download and install, review the important information on licensing, then select Accept and install.

On Server Core, use SConfig option 6 to search for and install the feature update. The Windows Update route still requires a valid Windows Server 2025 licence; it changes the delivery method, not the licensing.

Cause and effect: the feature update is convenient for remote servers, but it does not give you a chance to type a product key during setup. Have the 2025 key ready to enter immediately afterwards so the server does not sit unactivated.

Can I upgrade a Windows Server 2019 domain controller in place?

Technically yes, but Microsoft advises against it. Its guidance says not to use in-place upgrade on servers running Active Directory Domain Services, because it does not deliver the AD performance and feature improvements in Windows Server 2025. Instead, build a new 2025 server, promote it to a domain controller, move the FSMO roles and demote the old DC.

The process involves extending the schema with adprep, which happens automatically when you promote the first 2025 domain controller, and then checking replication before decommissioning the 2019 DC. Our step-by-step domain controller migration guide covers the whole sequence, so it is not repeated here.

What should I do after upgrading to Windows Server 2025?

After the upgrade, confirm the version and edition with Get-ComputerInfo -Property WindowsProductName, check that Windows is activated, re-enable NIC Teaming if you disabled it, start your virtual machines and test every application and client connection. If anything fails, Microsoft points to the setup logs in C:\Windows\Panther and its SetupDiag tool.

  1. Run slmgr /dli to confirm the Windows Server 2025 licence is active; enter the key under Settings > System > Activation if it is not.
  2. Install the latest Windows Server 2025 cumulative update and restart.
  3. Check Event Viewer for role-specific errors in the first 24 hours.
  4. Update drivers and firmware from your hardware vendor's Server 2025 support pages.
  5. Run a fresh full backup now that the server is on the new version.

Advanced nuance: once on Server 2025, you can enrol the server in hotpatching through Azure Arc to cut security-update restarts. It requires UEFI with Secure Boot and virtualization-based security, so a server upgraded from a legacy BIOS installation will not qualify without a rebuild.

Frequently asked questions

How long does an in-place upgrade from Server 2019 to 2025 take?

On typical SSD-based hardware, the setup phase usually takes one to two hours, including several automatic restarts. Allow a longer maintenance window for the backup, preparation and post-upgrade testing, which often take more time than setup itself. Servers with slow disks or many installed roles take longer.

Can I roll back if the Server 2025 upgrade fails?

If setup fails before completion, it normally rolls back to Windows Server 2019 automatically. Once the upgrade completes, there is no supported one-click route back to 2019, which is why Microsoft lists a full, tested backup as a prerequisite. Restoring that backup is the reliable way to return to the previous version.

Does the upgrade keep my Hyper-V virtual machines?

Yes, an in-place upgrade keeps the Hyper-V role and VM configurations, but Microsoft says no VMs should be running during the upgrade. Shut them down or migrate them first. Afterwards, you can update each VM's configuration version to unlock newer Hyper-V features once you are sure you will not move it back to an older host.

Can I switch from Standard to Datacenter during the upgrade?

Yes. Microsoft allows an edition change from Standard to Datacenter, or to Datacenter: Azure Edition, as part of an in-place upgrade, provided you enter a matching key. The reverse is not supported: a Datacenter server cannot be upgraded down to Standard. Choose the edition before you start, because changing later needs a separate conversion.

When does Windows Server 2019 support end?

Windows Server 2019 left mainstream support on 9 January 2024 and reaches the end of extended support on 9 January 2029, according to Microsoft's lifecycle page. Security updates continue until then. Windows Server 2025 is supported until 14 November 2034, which gives an upgraded server roughly five more years of updates.

Related guides

Links in this guide

Link Type Why it helps
Windows Server upgrade overview (Microsoft Learn) External Supported upgrade paths and restrictions
Role and feature upgrade matrix (Microsoft Learn) External Which roles support in-place upgrade
Perform an in-place upgrade (Microsoft Learn) External Official media and Windows Update procedures
Windows Server 2025 Standard Internal Licence required for the target version
Windows Server CALs explained Internal Access licences for users and devices
Windows Server 2025 system requirements Internal Hardware checks before upgrading
Convert Windows Server Evaluation to full Internal Fix for evaluation installs that cannot upgrade
Windows Server 2025 Standard installation guide Internal Getting the right installation media
Migrate a domain controller to Server 2025 Internal Recommended path for domain controllers
How-to, Licensing, Upgrade, Windows server, Windows server 2025