Microsoft has opened a new, streamlined path to Windows Server 2025: an in-place upgrade delivered through Windows Update. For the first time, administrators can transition eligible Windows Server 2019 and 2022 systems to the latest release without booting from installation media, marking a significant shift in how server operating systems get updated.

This feature update appears as an optional entry in Windows Update settings, much like the feature updates for Windows client. For IT teams managing fleets of servers, this change promises reduced downtime and simpler deployment logistics. But the new mechanism also raises critical questions about control, compatibility, and the risks of unplanned upgrades in production environments.

How the In-Place Upgrade Works

The in-place upgrade leverages the same servicing technology used for Windows 10 and 11 feature updates. When a server is configured to receive updates, Microsoft’s deployment engine downloads the full Windows Server 2025 image and launches a setup process that migrates the operating system, installed roles, applications, and data—all without manual intervention beyond the initial approval.

Administrators can check for the offer under Settings > Update & Security > Windows Update, then Check for updates. If the device meets the hardware and licensing requirements, an option labeled “Feature update to Windows Server 2025” appears. Clicking Download and install initiates the upgrade sequence.

Under the hood, the upgrade process uses a staged approach:
- Compatibility checks validate drivers, applications, and server roles.
- The system downloads a 4.7 GB (approximate) package in the background.
- Installation runs through SafeOS phases, preserving Windows Server roles like Active Directory, DNS, and Hyper-V.
- After multiple reboots, the server boots into Windows Server 2025, retaining all prior configurations.

Microsoft maintains a dedicated support article, KB5037782, detailing the upgrade path, though that document evolves as the company refines the rollout.

Which Servers Are Eligible?

At launch, the in-place upgrade offer targets two source operating systems:
- Windows Server 2019 Standard and Datacenter
- Windows Server 2022 Standard and Datacenter

Additionally, the source installation must have the latest cumulative update applied—specifically, the June 2024 or later monthly quality update. Devices running earlier builds won't see the feature update offer until patched.

The target edition is automatically matched: Standard upgrades to Standard, Datacenter to Datacenter. Servers configured as Server Core can be upgraded to Server Core only; a desktop experience upgrade requires a clean installation or additional post-upgrade configuration.

Notably, Windows Server 2016 and earlier releases are excluded. Microsoft plans no direct upgrade path for those versions, recommending a migration to newer hardware or a fresh installation of Windows Server 2025.

Prerequisites and Compatibility Checks

Before hitting install, IT teams must verify several technical prerequisites:
- Hardware: Windows Server 2025 demands processors that support SSE4.2 and NX/XD bit, plus TPM 2.0 for certain security features. Most hardware purchased after 2017 meets these requirements, but older Intel Xeon E5 v2 or AMD Opteron systems might fail.
- Driver Compatibility: Server-class drivers for storage controllers, network adapters, and management firmware must have signed Windows Server 2025 versions. Microsoft’s Setup compatibility checker scans for known issues and blocks the upgrade if incompatible drivers are found.
- Role and Application Readiness: Roles like Hyper-V require specific CPU virtualization extensions (Intel VT-x or AMD-V). Applications relying on deprecated components (e.g., Internet Explorer, Windows Server Update Services 3.0) may break and need remediation beforehand.
- Disk Space: The installer requires at least 32 GB of free space on the system drive for the temporary download and migration files.

Administrators should also confirm that management tools—backup agents, monitoring software, and security solutions—officially support Windows Server 2025. Major vendors like Veeam and SolarWinds have released updated agents, but older versions might fail during the upgrade.

Step-by-Step Upgrade Process

For those performing the upgrade manually on a single server, the workflow is straightforward:

  1. Back up the server and its system state. Ensure a full bare-metal recovery image is available.
  2. Install all pending Windows updates from Windows Update to meet the cumulative update baseline.
  3. Open Windows Update in Settings and check for updates.
  4. Look for the “Feature update to Windows Server 2025” option. If not visible, use the manual enablement commands in PowerShell or Group Policy to unblock the offer.
  5. Click Download and install. The server will download the package and begin the unattended upgrade.
  6. Monitor the process through the Windows Setup logs (%windir%\Panther) or remotely via RSAT tools.

The entire operation typically takes 40 to 90 minutes, depending on hardware speed and role complexity. Servers with many roles (Domain Controller, DHCP, etc.) may take longer due to post-upgrade configuration steps.

Managing Upgrades at Scale

For enterprises, pushing the in-place upgrade to hundreds of servers requires orchestration. Microsoft offers several control mechanisms:

  • Safeguard Holds: Microsoft can block the feature update on specific hardware or software combinations where known issues exist. These holds appear in Windows Update for Business reports.
  • Group Policy: Administrators can use the Select the target Feature Update version policy (Computer Configuration > Administrative Templates > Windows Components > Windows Update > Manage updates offered from Windows Update) to specify the desired version (e.g., “Windows Server 2025”) and prevent accidental upgrades.
  • Windows Server Update Services (WSUS) and Configuration Manager: The feature update package is published to WSUS as a stand-alone update (ID 3012973). IT teams can approve it to pilot groups and schedule deployments during maintenance windows.
  • Azure Arc and Azure Update Manager: Cloud-managed servers can receive the upgrade through Azure’s update management tools, providing compliance reporting and phased rollout capabilities.

Microsoft also supports a command-line trigger: running SetupPrep.exe /auto upgrade /compat ScanOnly from the extracted media previews the compatibility report without initiating the upgrade.

Some organizations have reported that the feature update offer does not appear immediately even on eligible systems. Microsoft explains that the rollout is gradual, and impatient administrators can force detection by executing:

$WU = New-Object -ComObject Microsoft.Update.Session
$Searcher = $WU.CreateUpdateSearcher()
$Searcher.Search("IsInstalled=0 and Type='Driver' or Type='Software'").Updates | Where-Object { $_.Title -match "Windows Server 2025" }

If the update is found but hidden, using the Show or hide updates troubleshooter or the USOClient command often resolves the issue.

Rollback and Recovery Options

Understanding the rollback window is crucial. After an in-place upgrade, Windows Server 2025 retains the previous version’s files in the Windows.old directory for 10 days. During this period, administrators can revert to the prior OS via Settings > Update & Security > Recovery > Go back to the previous version of Windows Server.

This rollback restores the server exactly to its pre-upgrade state—including system state and applications—but it will not revert Active Directory schema extensions or other forest-wide changes if the server acted as a Domain Controller during the upgrade. Microsoft recommends demoting domain controllers before upgrading to avoid irreversible forest modifications.

For recovery beyond 10 days, a bare-metal restore from backup is the only path. Testing the rollback process in a lab environment is non-negotiable before touching production servers.

Licensing and Activation Considerations

A common source of confusion: the in-place upgrade does not automatically grant a new license. Servers upgrading from Windows Server 2019 or 2022 must already be licensed for the target edition. In practice, this means organizations with active Software Assurance or those who have purchased Windows Server 2025 licenses can perform the upgrade; those covered solely by OEM licenses for the older version must buy a new license.

After the upgrade, Windows Server 2025 activates using the same activating mechanism as the source OS. If the server was activated via OEM or volume licensing, activation carries over. However, some users have reported activation failures when moving from an OEM-licensed 2019 Standard to 2025 Standard; in such cases, re-entering the volume license key resolves the issue.

Microsoft clarified the licensing rules in a partner readiness document, emphasizing that the upgrade “right” comes from the license, not the installation bits.

Community Feedback and Early Adopter Experiences

Though no vibrant forum thread accompanied this article, early reports from IT communities on Reddit and TechCommunity highlight mixed experiences:

  • Smooth Upgrades: Many users with modern hardware and up-to-date drivers report seamless transitions, with roles like IIS, File Server, and Hyper-V functioning immediately post-upgrade.
  • Gotchas: Several administrators encountered failures when upgrading Domain Controllers with Active Directory Certificate Services role installed due to a compatibility check timeout. A workaround using the /DynamicUpdate disable setup flag circumvented the issue.
  • Performance Regressions: A minority of upgraders noted increased CPU usage on virtualized SQL Server instances until they updated the Hyper-V integration components.
  • WSUS Integration: IT pros managing through WSUS initially struggled because the feature update was not classified properly; Microsoft rectified this by reclassifying the update under the “Upgrades” category.

These anecdotes underscore the need for thorough pre-flight testing and staged rollouts.

Security Enhancements Worth the Upgrade

Beyond the deployment mechanism, Windows Server 2025 introduces compelling security and performance features that justify the upgrade for many organizations:

  • SMB over QUIC now supports client access control via certificates, making it a viable VPN replacement for file shares.
  • Hotpatching is available for Datacenter Azure Edition (and Standard Edition via Azure Arc), allowing security updates without restarts.
  • Secured-core server capabilities protect credentials from theft via firmware attacks.
  • Credential Guard and System Guard runtime attestation are enabled by default, reducing the attack surface.

These improvements, combined with a 10‑year lifecycle (mainstream support through 2029, extended through 2034), make the upgrade strategically valuable.

Potential Pitfalls and Risk Mitigation

Despite its convenience, the Windows Update-based upgrade path introduces risks that IT governance must address:

  1. Accidental Upgrades: An administrator could inadvertently approve the feature update on a critical server. Deploy the Group Policy template mentioned earlier to prevent this.
  2. Incomplete Compatibility Checking: The built-in checker does not cover all third-party applications. Maintain an inventory of installed software and verify vendor support before attempting the upgrade.
  3. Network Bandwidth: Downloading 5 GB per server over remote site links can saturate WAN connections. Use Delivery Optimization configured to peer-only mode within the local network, or pre-stage the content via a local WSUS server.
  4. Post-Upgrade Overhead: Windows Server 2025 optimizes its servicing stack over the first 24 hours after upgrade, which can increase disk I/O and CPU load. Schedule upgrades to conclude at least one day before the server must handle peak workloads.

Alternatives to the In-Place Upgrade

For organizations that prefer a more traditional approach, the classic in-place upgrade via mounted ISO remains fully supported. This method offers more granular control, including offline servicing and the ability to inject drivers during setup. It also bypasses the gradual rollout restrictions.

Clean installations—while more disruptive—remain the gold standard for servers where configuration drift or accumulated cruft might undermine the upgrade’s integrity. Microsoft provides a Server Migration Tool to move roles and data to a freshly installed Windows Server 2025 instance.

Looking Ahead

Microsoft’s decision to deliver a server operating system feature update through Windows Update signals a maturation of its servicing pipeline. Future cumulative updates for Windows Server 2025 will also flow through this channel, and the company hints at eventual support for upgrade-in-place from Windows Server 2022 Azure Edition to Windows Server 2025 Azure Edition entirely via cloud update management.

IT teams should treat this new capability as a tool, not a mandate. With careful planning, the in-place upgrade can slash migration timelines and reduce the manual toil of server fleet management. Without proper guardrails, it can just as easily cause unplanned outages. The difference lies in how thoroughly organizations test, pilot, and policy-enable the feature before clicking “Download and install.”