Microsoft is giving Windows Server administrators a long-awaited convenience: an opt-in upgrade through Windows Update that can take a server running Windows Server 2019 or 2022 directly to Windows Server 2025. The feature, which eliminates the need for installation media, represents a major shift in how IT professionals deploy the latest version of Microsoft’s server operating system.

A New Path to Windows Server 2025

Traditionally, upgrading a Windows Server instance from one major release to another involved downloading an ISO image, mounting it, and running the setup wizard—or building a new server and migrating workloads. While that method is still supported, Microsoft is now offering a much simpler alternative. With the upcoming update, eligible servers will see the Windows Server 2025 upgrade appear as an optional update in Windows Update. Administrators can initiate the in-place upgrade with a few clicks, much like a feature update on Windows 11.

The capability is being delivered through a servicing stack update and a special enablement package that will be offered via Windows Update for systems running Windows Server 2019 and Windows Server 2022. Once those prerequisites are installed, the upgrade option will be visible under Settings > Windows Update, or within the SCONFIG tool for Server Core installations.

Opt-In Only—No Forced Upgrades

Crucially, the upgrade is entirely opt-in. Unlike some consumer updates that download automatically, this server upgrade will not be forced on any system. It will appear as an optional update that requires manual approval and explicit action from the administrator. Microsoft designed this to prevent inadvertent upgrades on production servers, where stability is paramount. You must deliberately choose to install it, and you can even set policies to hide it if needed.

This opt-in model respects the critical nature of server workloads. Admins can evaluate timing, test in a sandbox, and schedule the upgrade during maintenance windows without worrying about unexpected reboots or compatibility issues triggered by an automatic download.

Supported Editions and Scenarios

The in-place upgrade path supports both Windows Server Standard and Datacenter editions, covering the most common deployments in enterprise and cloud environments. Whether you are running the full Graphical User Interface (Desktop Experience) or a headless Server Core installation, the upgrade will function. For Server Core, the SCONFIG utility receives a new menu item—likely under option 6 for updates—that allows initiating the process. This brings parity with the GUI-based upgrade experience.

Windows Server 2012 R2 users, unfortunately, are not included. The path is limited to versions that share a similar servicing architecture: Windows Server 2019 and Windows Server 2022. This means organizations on older platforms will still need to perform a clean installation or a media-based upgrade if they wish to reach 2025.

What Makes Windows Server 2025 Worth the Upgrade?

Windows Server 2025 introduces a raft of enhancements designed for modern hybrid environments. Among them are:

  • Advanced security with Secured-core server and improved Credential Guard, making it harder for attackers to steal credentials.
  • Hotpatching support, available through Azure Arc, allowing installation of security updates without rebooting—a massive gain for uptime.
  • GPU integration and improved AI workload support with GPU-P (GPU paravirtualization) for virtual machines.
  • Enhanced storage with NVMe over Fabrics support, accelerating storage area network performance.
  • Software-defined networking improvements including better load balancing and network virtualization.
  • Subscription-based activation that simplifies licensing in hybrid cloud setups.

For organizations still on Windows Server 2019 or 2022, these innovations offer tangible benefits, from reduced downtime to better protection. The new upgrade method lowers the barrier to adopting them.

Step-by-Step: How the In-Place Upgrade Will Work

While exact screenshots are not yet public, the process is expected to mirror the experience of installing a Windows feature update:

  1. Ensure your system is up to date. Install the latest cumulative update and the special servicing stack update that enables the upgrade detection.
  2. Open Settings > Windows Update (or run SCONFIG on Server Core). You will see a new option: “Upgrade to Windows Server 2025” under optional updates.
  3. Click “Download and install.” The upgrade payload will be fetched in the background.
  4. Review the license terms and begin installation. The server will restart several times, preserving installed applications, roles, and data (assuming compatibility is met).
  5. Post-upgrade verification. Once completed, the server will report itself as Windows Server 2025, and you can proceed with any needed configuration changes.

Administrators should perform thorough testing before deploying this on critical infrastructure. Although the upgrade retains roles and settings, certain legacy applications or drivers may not be compatible. Microsoft recommends checking the Windows Server Catalog for hardware and software certifications.

How the Enablement Package Works

The enablement package at the heart of this upgrade is a small, lightweight file that essentially flips a switch to activate Windows Server 2025 components already present in the system. Over the past several months, cumulative updates for Windows Server 2019 and 2022 have been seeding the necessary code into the operating system. The enablement package simply toggles the license state and activates the new features, drastically reducing download size and installation time compared to a full-fledged ISO upgrade.

This approach, first popularized with Windows 10 feature updates, means the actual upgrade payload could be just a few megabytes, while the bulk of the bits have already arrived through normal patches. For administrators with limited bandwidth or large server fleets, this is a significant logistical win.

Enterprise Deployment Considerations

For organizations managing dozens or hundreds of servers, the new upgrade mechanism opens up streamlined deployment opportunities. Key considerations:

  • Group Policy and Update Rings: IT admins can use Group Policy or Configuration Manager to manage whether the upgrade option appears. \"Enable Optional Updates\" policies can be tweaked to hide the upgrade until after testing.
  • Bandwidth Management: With the enablement package being small, network impact is minimal, but the initial cumulative updates containing the Windows Server 2025 components may consume several gigabytes over time. Delivery Optimization can be configured for peer-to-peer sharing within the network.
  • Windows Server Update Services (WSUS): For disconnected or regulated environments, the upgrade enablement package will be publishable through WSUS, allowing offline deployment after approval.
  • Virtual Machine Templates: In virtualized environments, the upgrade can be tested on a cloned VM to verify application compatibility before rolling out to production.

Risks and Best Practices

In-place upgrades on servers always carry risk. Even with the simplified path, IT teams must adopt the same discipline they would with a media-based upgrade. Key best practices include:

  • Full backup: Create a system image backup or snapshot before starting.
  • Check compatibility: Run the Microsoft Assessment and Planning Toolkit or equivalent to identify compatibility issues.
  • Test in a staging environment: Mirror your production setup and attempt the upgrade first.
  • Have a rollback plan: Know how to revert to the original OS if something goes wrong. Because this is an in-place upgrade via Windows Update, the rollback period is typically 10 days, during which you can go back from Settings > Update & Security > Recovery, but that may change.
  • Disable or update non-essential drivers and software that could interfere.

Because the upgrade mechanism relies on Windows Update, ensure your firewall and proxy settings permit access to Microsoft’s update servers.

A Nod to Cloud and Modern Management

This move aligns with Microsoft’s broader strategy of treating servers more like Windows clients—where in-place feature updates have been the norm since Windows 10. It also complements Azure Stack HCI and hybrid management tools. Organizations managing fleets of servers through Windows Admin Center or Microsoft Intune/ConfigMgr will find the update channel easier to orchestrate at scale. Policies can be used to control which updates appear, and deployment rings can manage rollout.

Moreover, for customers using Azure Arc–enabled servers, the cloud dashboard could eventually trigger the upgrade remotely, though that functionality has not been announced.

The Evolution of Server Upgrades

Windows Server in-place upgrades have a checkered history. Early versions of Windows Server often required a clean install when moving between major releases. Starting with Windows Server 2012 R2 to 2016, in-place upgrades became supported but were cumbersome, requiring the installation media and a manual setup.exe invocation. Many admins avoided them, preferring clean builds to avoid inheriting stability issues.

Over time, feature update tooling improved, and by Windows Server 2019, the process was more robust. The new Windows Update–based method represents the culmination of a decade-long effort to make server OS upgrades as painless as possible.

Community Reaction and Expert Advice

Early feedback from Windows Server forums and IT communities has been largely positive, with many admins praising the reduced complexity. \"No more hunting for ISOs or burning DVDs—just click and go,\" one participant remarked. However, some have raised valid concerns about storage space: even a small enablement package might trigger a large cleanup of previous installation files, and the Windows.old folder generated during upgrade can consume over 20 GB. Microsoft’s Disk Cleanup tool can reclaim that space afterward.

Veteran administrators also caution that third-party antivirus, backup agents, or monitoring tools might need updates to work with Windows Server 2025. The general advice is to check with all software vendors before proceeding.

How to Get the Upgrade Option

The upgrade option is expected to begin rolling out as an optional update alongside a forthcoming cumulative update for Windows Server 2019 and Windows Server 2022. The exact date hasn’t been confirmed, but it is likely to appear in early 2025, around the same time Windows Server 2025 reaches general availability or shortly after. Insiders can test it now by enrolling in the Windows Server Insider Program.

Server administrators should watch for KB articles and Windows Server blog posts detailing the prerequisites. The enablement package will likely be listed as a “Feature update to Windows Server 2025” in the update history.

Licensing and Activation

The upgrade preserves the existing activation state. Servers running genuine, activated copies of Windows Server 2019 or 2022 will remain activated after moving to Windows Server 2025. However, be aware that licensing rules apply: if you are using downgrade rights or have specific license agreements, verify with your Microsoft representative that an in-place upgrade doesn’t violate terms.

Final Thoughts

Microsoft’s new Windows Update–based in-place upgrade for Windows Server 2019 and 2022 is a welcome change that simplifies lifecycle management. By making the leap to Windows Server 2025 as straightforward as clicking “Install,” the company reduces friction and encourages adoption of its most secure and capable server OS yet. As with any major change, careful planning is essential, but the path forward has never been clearer.

For detailed guidance, see Microsoft’s official Windows Server upgrade documentation once updated for this feature.