Windows Server 2019 can be upgraded directly to Windows Server 2025. Microsoft currently supports Windows Server 2019 as a source for an in-place upgrade to Windows Server 2025, so you do not have to install Windows Server 2022 as an intermediate step on a qualifying nonclustered system.
The fact that the path is supported does not make an in-place upgrade the safest answer for every 2019 server.
Windows Server 2019 has been available since 2018, which means many production installations now sit on hardware, drivers, applications and management agents that have accumulated years of dependencies. Microsoft extended support for Windows Server 2019 ends on January 9, 2029, while Windows Server 2025 receives extended support until November 15, 2034. That makes migration planning increasingly important, but it also makes compatibility testing more important than simply getting Setup to run.
For a simple member server with current applications and healthy hardware, an in-place upgrade can be efficient. For an aging file server, domain controller, specialized application server or machine already due for replacement, building a clean Windows Server 2025 system and migrating the workload can provide a much safer transition.
This runbook covers both decisions.
Yes.
Microsoft’s current Windows Server upgrade matrix supports a direct in-place upgrade from Windows Server 2019 to Windows Server 2025 using installation media. Windows Server 2019 is also now an eligible source for the Windows Server 2025 feature update through Windows Update when the required prerequisites are installed.
That is important because older Windows Server upgrade planning often involved moving only one or two releases at a time. With Windows Server 2025, Microsoft expanded the supported version gap for nonclustered systems.
There are still restrictions.
An in-place upgrade cannot switch between Server Core and Server with Desktop Experience. You cannot change the operating-system language as part of the upgrade. The existing edition is retained by default, although Standard can move upward to Datacenter where appropriate; Datacenter cannot be downgraded to Standard during the upgrade. Systems configured to boot Windows Server from a VHD are also not supported for this in-place path.
If the Windows Server 2019 machine uses NIC Teaming, Microsoft also instructs administrators to disable the team before the in-place upgrade and re-enable it afterward.
For Windows Server 2019, this decision deserves more attention than it often does for a comparatively young Windows Server 2022 deployment.
An in-place upgrade installs Windows Server 2025 over the existing operating system while preserving settings, installed applications, server roles and data. A migration moves the workload to another Windows Server installation instead. Microsoft supports both approaches, but individual roles differ in what they support.
A useful starting point is:
| Server situation | Usually safer approach |
|---|---|
| Current hardware, simple member server, supported applications | In-place upgrade can be reasonable |
| Hardware is due for replacement | Side-by-side migration |
| Application vendor has not certified Windows Server 2025 | Stay on 2019 temporarily and test first |
| Active Directory domain controller | Deploy a new 2025 DC and demote the old DC |
| Failover cluster | Use the supported cluster upgrade process |
| Old file server with years of accumulated configuration | Consider Storage Migration Service / clean target |
| Server Core to Desktop Experience change | Clean deployment or migration |
| Critical workload requiring an easy fallback | Side-by-side migration is usually safer |
The important distinction is that “supported” describes what Microsoft permits technically. It does not determine which method gives your organization the best recovery path.
The upgrade gap is not the problem by itself. The age of the surrounding environment is.
A Windows Server 2019 installation may have an application installed in 2019, an old SQL or middleware component, a backup agent added several years later, endpoint-security software, printer drivers, an HBA utility, monitoring software and custom scheduled tasks that nobody has revisited since deployment.
Windows Setup can preserve all of those components and still leave you with an application that its vendor does not support on Windows Server 2025.
Before changing the OS, inventory the complete workload:
Microsoft specifically advises checking both Microsoft server-application compatibility and the requirements of non-Microsoft application vendors before an in-place upgrade.
Do not interpret “the application starts” as equivalent to “the vendor supports it.”
A Windows Server 2019 domain controller needs a different modernization plan.
Although an in-place operating-system upgrade can technically be possible, Microsoft’s current guidance recommends a clean Windows Server installation for new domain controllers, followed by promotion of those servers and demotion of the older DCs. Microsoft specifically advises against the normal in-place approach for servers running Active Directory Domain Services because a clean deployment provides the full Active Directory performance and feature improvements associated with newer Windows Server releases.
A typical production sequence is therefore:
If you deliberately choose to perform an in-place upgrade of an existing DC, additional Active Directory preparation applies. Microsoft’s domain-controller guidance states that adprep /forestprep and adprep /domainprep must be handled for that process. Promoting a new Windows Server 2025 DC integrates the necessary preparation into the supported deployment tools, which is another reason the clean-DC approach is preferable.
Do not raise domain or forest functional levels simply because the operating systems have been upgraded. Functional-level changes should be treated as a separate, planned Active Directory change.
Not every role should be moved in the same way.
Microsoft’s role matrix currently allows in-place upgrades for roles such as DHCP, DNS, IIS, File and Storage Services and WSUS, subject to their specific requirements. Other roles have more restrictive guidance. Print and Fax Services, for example, should be migrated rather than treated as a normal in-place role upgrade. Failover Clustering and clustered Hyper-V workloads require the supported cluster process instead of the generic standalone-server procedure.
An in-place upgrade can work well for a straightforward file server on hardware you intend to keep.
If the Windows Server 2019 machine is already old, however, moving the data to a clean Windows Server 2025 system can solve two problems at once: operating-system lifecycle and hardware lifecycle.
Microsoft identifies Storage Migration Service as the migration path for applicable file and storage workloads.
IIS can be upgraded in place, but the web application is the real compatibility question. Check the required .NET runtime, PHP version, ISAPI components, certificates, authentication configuration, application pools and vendor support before assuming the OS migration is safe.
For a business-critical web application, building a parallel Windows Server 2025/IIS instance can make testing and rollback much cleaner.
Both roles have supported migration options as well as upgrade paths. Where multiple DNS or DHCP servers already provide redundancy, moving the role to a new Windows Server 2025 machine often creates less risk than changing the OS under the active service.
A standalone Hyper-V server and a clustered Hyper-V environment require different thinking.
Microsoft requires cluster-specific procedures such as Cluster OS Rolling Upgrade for applicable clustered Hyper-V workloads rather than treating cluster nodes as ordinary standalone servers. The generic in-place-upgrade guidance assumes the target server is not clustered.
For a standalone Hyper-V host, shut down or migrate running VMs and include them in the backup plan before performing the host upgrade. Microsoft specifically instructs administrators to make sure no VMs remain running during the in-place operation.
Before scheduling downtime, complete the readiness work.
The rollback decision should not be invented at 2:00 a.m. while users are waiting for the application to come back.
Before changing Windows Server 2019, save enough information to compare the old environment with the upgraded system.
Open an elevated PowerShell prompt and record the build and edition:
Get-ComputerInfo -Property WindowsBuildLabEx,WindowsEditionID |
Out-File .\computerinfo.txt
Record general system information:
systeminfo.exe | Out-File .\systeminfo.txt
Record the current network configuration:
ipconfig /all | Out-File .\ipconfig.txt
Microsoft recommends storing these diagnostic files somewhere outside the server so they remain available even if the upgrade fails.
For a production machine, also export or record information such as:
The objective is not paperwork. It is to make post-upgrade troubleshooting deterministic.
Microsoft’s current prerequisite for an in-place upgrade is a full server backup covering the operating system, applications, data and any VMs, together with a restore test to confirm that recovery actually works.
For a Windows Server 2019 system, pay particular attention to how old the hardware and backup configuration are.
If you discover during planning that the only recovery mechanism is a backup job nobody has restored in three years, that is a reason to delay the OS change.
Set explicit rollback triggers. Examples include:
For a side-by-side migration, the old Windows Server 2019 system itself can often form part of the rollback architecture because it remains intact until the Windows Server 2025 target is validated.
That is one of the biggest advantages of migration over in-place upgrade for an older production workload.
For a nonclustered Windows Server 2019 member server that has passed compatibility testing, installation media provides a straightforward upgrade route.
Install applicable Windows Server 2019 updates and restart the machine if required.
Confirm that no pending restart or unfinished application update remains.
Verify the backup one final time. If the machine hosts Hyper-V VMs, shut them down or migrate them away before proceeding.
If NIC Teaming is configured, disable it as required for the in-place upgrade and document the team configuration so it can be restored afterward.
Mount the Windows Server 2025 ISO while logged into the running Windows Server 2019 operating system.
From the root of the mounted media, launch: setup.exe
For an in-place upgrade, start Setup from within Windows Server 2019. Do not boot the server from the installation media and expect the same preserve-applications workflow. Microsoft’s documented procedure launches setup.exe from the existing Windows installation.
By default, Windows Server Setup can retrieve installation updates.
Whether you allow that during the maintenance window should match your organization’s change-control process. Some administrators prefer the latest applicable installation updates; highly controlled environments may use prevalidated media and apply updates afterward.
Do not change the plan during the maintenance window without a reason.
Depending on your media and licensing channel, Setup may request a Windows Server 2025 product key.
A technically supported upgrade path does not itself grant licensing rights to Windows Server 2025. Microsoft treats the target license and activation method as prerequisites to the upgrade.
Make sure the licensing decision has already been made rather than trying to resolve it after production downtime begins.
Windows Server normally retains the edition during an in-place upgrade.
A Windows Server 2019 Standard machine therefore normally moves to Windows Server 2025 Standard, while Datacenter remains Datacenter. An upward move from Standard to Datacenter can be supported, but Datacenter cannot be downgraded to Standard as part of the in-place process.
Do not use the migration itself as an excuse for an unplanned edition change.
For the in-place path, select the option to Keep files, settings, and apps.
This is what preserves the current applications, roles, data and Windows configuration while Setup replaces the operating system.
If Setup does not offer that option when you expected it, stop.
Do not continue with an alternative installation mode because it appears to be the only available button. Investigate the source/target edition, media language, Server Core versus Desktop Experience configuration and media type first.
Before selecting Install, verify three things in particular:
Also make sure your recovery files, backup console and documentation remain accessible from another machine.
Select Install only after those checks pass.
The server restarts multiple times during the upgrade.
As of Microsoft’s current Windows Server 2025 guidance, eligible Windows Server 2019 machines can also receive Windows Server 2025 as a feature update through Windows Update.
For Windows Server 2019, Microsoft currently requires the March 2026 cumulative update KB5078752 or later before using this Windows Update path.
The Windows Server feature-update policy must also be enabled before the offer appears. Microsoft’s documented PowerShell configuration uses:
New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AllowWindowsServerFeatureUpdate"
New-ItemProperty `
-Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AllowWindowsServerFeatureUpdate" `
-Name "AllowWindowsServerFeatureUpdate" `
-PropertyType DWord `
-Value 1
Once the prerequisites are satisfied, Windows Update can present the Windows Server 2025 feature update for download and installation. Server Core can use the corresponding Windows Update flow through SConfig.
The delivery method changes; the migration risk does not.
You still need the same backup, compatibility testing, maintenance window and post-upgrade validation that an ISO-based upgrade requires.
For a critical Windows Server 2019 workload, many administrators will prefer installation media because it can be staged and tested as part of a controlled change. Either route can be valid when its prerequisites are met.
A successful Windows login does not mean the migration is complete.
First verify the installed Windows Server product:
Get-ComputerInfo -Property WindowsProductName
Microsoft includes this check in its post-upgrade procedure and also instructs administrators to verify that applications are running and client connections succeed.
Then validate the server in layers.
Confirm:
Compare the active configuration against the baseline you collected before the migration.
Check:
Test the workload from a user or application perspective, not just from the server console.
For example, an IIS server should serve its actual application from a client. A database-backed application should complete a real transaction. A file server should be tested using its normal UNC path and permissions. A middleware server should communicate with upstream and downstream systems.
Confirm that:
Keep the rollback option available until these checks are complete.
If the installation fails, avoid immediately making unrelated changes.
Microsoft identifies the Windows Setup logs in:
C:\Windows\Panther
Microsoft also recommends SetupDiag to help analyze Windows Setup logs after an unsuccessful or problematic upgrade.
Compare what you find with the pre-upgrade diagnostic information.
That can quickly reveal whether the problem is associated with Windows Setup itself, a driver, application compatibility, networking, services or another dependency.
If the agreed rollback threshold has already been reached, restore service first and investigate afterward. Production recovery should not become an open-ended troubleshooting session simply because the OS technically finished installing.
For many Windows Server 2019 systems, side-by-side migration is the more attractive option.
Consider migration when:
Windows Server Migration Tools can move supported roles, features, settings, data and shares to a newer Windows Server system, while Storage Migration Service is designed for appropriate file and storage migrations.
A clean Windows Server 2025 deployment also removes years of operating-system residue. That can be worth the extra migration effort when the Windows Server 2019 instance has lived through multiple application versions, driver packages and administrative changes.
A Windows Server 2019 Standard machine runs a supported internal application. The hardware has several years of useful life left, the application vendor supports Windows Server 2025 and the recovery process has been tested.
An in-place upgrade is reasonable.
Document the configuration, back up the server, run Windows Server 2025 Setup from within 2019, preserve files/settings/apps and validate the application afterward.
A Windows Server 2019 file server is six years old and both storage and hardware need replacement.
An in-place OS upgrade would modernize the software while leaving the organization on aging infrastructure.
A clean Windows Server 2025 file server followed by a controlled file/storage migration is normally the better architectural choice. The old server can remain available during validation, providing a cleaner fallback.
The organization has multiple healthy domain controllers and wants to move its DC estate to Windows Server 2025.
Rather than performing a generic in-place upgrade, deploy a fresh Windows Server 2025 server, promote it to a domain controller, verify Active Directory and DNS health, transfer responsibilities where necessary, and then demote the Windows Server 2019 DC.
That follows Microsoft’s preferred modernization model for AD DS.
Do not decide the target edition only from what the old Windows Server 2019 machine is running.
The migration is an opportunity to reassess the target architecture.
A primarily physical server or an environment with relatively low Windows Server VM density may naturally lead toward Windows Server 2025 Standard Core-Based.
A virtualization-heavy host or infrastructure design where Datacenter capabilities and virtualization rights are the better fit should instead evaluate Windows Server 2025 Datacenter Core-Based.
Before buying, determine the physical host configuration, edition requirements, expected VM density and any applicable access licensing. Do not assume that the existing Windows Server 2019 license, product key or edition automatically determines the correct licensing for the Windows Server 2025 target.
A direct Windows Server 2019 to Windows Server 2025 in-place upgrade is now supported for qualifying systems, so there is no technical requirement to migrate through Windows Server 2022 first.
For a healthy, nonclustered member server on supported hardware with fully compatible applications, that direct path can save substantial rebuilding work.
For an older production server, however, the more important question is whether preserving the existing installation is actually desirable.
If the hardware is aging, the application needs extensive testing, the server is a domain controller, the workload has a specialized migration path or rollback needs to be simple, use the move to Windows Server 2025 as an opportunity to build a clean target and migrate the workload instead.
Whichever method you choose, complete the same four tasks before declaring the project ready: verify compatibility, prove the backup, define rollback criteria and document how the workload will be validated after the move.
That is what turns a technically supported Windows Server upgrade into a production-safe migration.
Upgrade Windows Server 2022 to Windows Server 2025 with a practical runbook covering compatibility, backups, in-place upgrade steps, rollback and post-upgrade checks.
Compare Windows Server 2019, 2022 and 2025 by support lifecycle, security, Hyper-V, compatibility and upgrade path to choose the right version.
Compare Windows Server 2025 vs 2022 across security, Hyper-V, Active Directory, lifecycle and compatibility to decide whether to upgrade now or wait.