Microsoft has reintroduced an optional in-place upgrade to Windows Server 2025 via Windows Update, offering a streamlined path for Windows Server 2019 and 2022 systems. The feature reemerged in late January 2025 after the company yanked it from automatic delivery channels in December 2024 when a faulty implementation caused unsolicited server upgrades and reboots. This second attempt arrives with stricter opt‑in controls, but the earlier chaos shows why IT teams must immediately audit their update configurations.

A Quick Recap: Why the Upgrade Was Pulled

Windows Server 2025, the latest Long‑Term Servicing Channel (LTSC) release, launched on November 1, 2024. Alongside it, Microsoft began offering the new OS as an optional feature update through Windows Update for machines still running Server 2019 and Server 2022. The idea was convenient: qualifying servers could upgrade without a manual ISO or media, directly through the same monthly servicing pipeline.

But the rollout turned dangerous almost immediately. Instead of appearing only as an optional, user‑initiated action, the upgrade landed on some systems classified as a regular monthly quality update. Servers configured to automatically download and install security patches ingested the full OS replacement without any admin prompt. Restarting those servers triggered the entire upgrade process—unannounced and unapproved.

By early December 2024, Microsoft acknowledged the blunder. The company issued an out‑of‑band update to block the feature update from further automatic installation and yanked the offering from the Windows Update catalog. The pause lasted roughly seven weeks while Microsoft rewired the detection and targeting logic.

Now, as of January 2025 (rolling out alongside the January 14 cumulative update cycle), the feature update reappears for WSUS, Configuration Manager, and Windows Update for Business. It carries the same name—“Feature update to Windows Server 2025”—but it will only download and stage if an administrator explicitly selects it.

The Upgrade Paths at a Glance

Two server versions can take this shortcut:

  • Windows Server 2019 (Standard or Datacenter)
  • Windows Server 2022 (Standard or Datacenter)

Both require the Desktop Experience installation variant. Server Core editions cannot perform an in‑place upgrade retaining Core; they must migrate to Desktop Experience first or use a fresh installation. Moreover, the upgrade only supports the same language and hardware architecture—no x64‑to‑ARM64 jumps, and no en‑us to fr‑fr transitions mid‑stream.

Microsoft also warns that domain controllers require special care. An in‑place upgrade of a DC is supported, but best practice is to demote the server, upgrade, and then promote again to avoid metadata inconsistencies.

What Changed Technically?

The critical change is in the update’s applicability rules. The pre‑December version incorrectly evaluated servers with the “Windows Server 2022” product name but no upgrade flag as eligible. The revised detection logic adds two layers:

  1. The feature update now appears exclusively under the “Feature update to Windows Server 2025” banner, not mixed into the security updates list.
  2. It requires a manual “Download and install” click from an administrator, even on servers configured for automatic updates.

For domains using Group Policy, a new administrative template setting controls whether the feature update is offered at all. The policy “Do not include drivers with Windows Updates” does not affect this change; instead, a dedicated “Select the target Feature Update version” policy (introduced in Windows Server 2022’s September 2024 cumulative update) lets admins pin a maximum version. Setting it to “Windows Server 2022” blocks the Server 2025 offer entirely.

Steps IT Must Take Immediately

The risk of another accidental rollout—however diminished—demands a proactive stance. Recommendations follow three stages.

1. Audit Update Policies

Confirm how servers obtain updates today. Check:

  • Windows Update for Business ring configurations. If a ring is set to “Auto install at maintenance time,” the feature update won’t self‑start under the new rules, but double‑check.
  • Group Policy Objects controlling automatic update behavior. Look for “Configure Automatic Updates” and ensure it’s set to “3 – Auto download and notify for install” or lower.
  • WSUS approval rules. Do you have an “All Critical Updates” auto‑approval? That rule may inadvertently approve the feature update classification if you add it to WSUS. By default, feature updates are a separate classification and shouldn’t be auto‑approved.
  • Microsoft Configuration Manager (formerly SCCM) software update points. Feature updates published to WSUS can sync to ConfigMgr. Verify that any automatic deployment rules exclude the “Upgrades” category.

2. Test the Upgrade in Isolation

Set aside a representative lab that mirrors production workloads. Key test points:

  • Is every installed role and feature supported on Server 2025? The Windows Server Catalog lists compatible applications, but custom or legacy line‑of‑business software may break.
  • Storage and memory requirements: Server 2025 demands at least 32 GB of free disk space for the in‑place process (plus another 10 GB for temporary files).
  • Third‑party antivirus, backup agents, and monitoring tools: Test each with Server 2025’s January 2025 baseline update.
  • Upgrade duration: Expect 45–90 minutes on modern hardware. Scale your maintenance window accordingly.

3. Stage the Rollout

Even though the update is optional, treat it like any significant platform change. Use rings:

  • Ring 1: IT infrastructure servers (print servers, jump hosts).
  • Ring 2: A departmental application server.
  • Ring 3: Broader production systems, monitored closely.

For each ring, capture baseline performance metrics and validate functionality for at least one week before progressing. Prepare a rollback plan—either via the built‑in “Go back to the previous version” option (available for ten days after upgrade) or a bare‑metal recovery from backup.

How to Block the Upgrade Entirely

Organizations that want to stay on Windows Server 2019 or 2022 for the foreseeable future can block the feature update through any of these methods:

  • Group Policy: Enable “Select the target Feature Update version” and enter “Windows Server 2022” (or “2019”) in the product version field. This hides the Server 2025 upgrade from Windows Update.
  • Windows Update for Business: Set the target version in the deferral policy to “Windows Server 2022.”
  • WSUS/Configuration Manager: Decline the feature update from the WSUS console or avoid syncing the “Upgrades” classification.
  • Local Group Policy on workgroup servers: The same administrative template applies.

All techniques are also documented in Microsoft’s official guidance for controlling feature updates.

Known Issues and Limitations

Even with the corrected delivery, several known issues persist:

  • Mixed‑language upgrades fail: Both OS and language pack versions must match. English‑only servers upgrade without issue; multilingual servers may require a fresh install.
  • BitLocker: If the system drive is encrypted, suspend protection before the upgrade. Failure to do so can lock the drive post‑reboot, requiring a recovery key.
  • Small footprint: Servers running with less than 32 GB free on the system volume may see the upgrade fail late in the process.
  • iSCSI targets: The iSCSI Target Server role has new configuration requirements in Server 2025; test carefully if you rely on it.
  • Hyper‑V: Guests must be at configuration version 9.0 or higher. Older VMs may not start after the host upgrade; update integration services and configuration versions first.

Microsoft updates the known‑issues list at Windows Server 2025 known issues. Bookmark it and consult it before initiating any upgrade.

Why Move to Windows Server 2025?

Despite the hiccup, Server 2025 delivers tangible improvements. Hotpatching—applying security fixes without restarts—arrives for Azure Arc‑connected servers, cutting downtime. The new SMB over QUIC secures file access over the internet, and NVMe storage performance jumps due to a revamped storage stack. Credential Guard and Hyper‑V secured‑core strengthen the default security posture.

Support timelines also matter. Mainstream support for Windows Server 2019 ended in January 2024, though extended support continues until 2029. Windows Server 2022 mainstream support runs until October 2026. Migrating to Server 2025 grants full support through at least 2029 (mainstream) and 2034 (extended), aligning with typical hardware refresh cycles.

What’s Next?

Microsoft’s botched first attempt left many admins jaded. Resentment aside, the corrected optional upgrade remains the easiest path to a current OS for servers that can’t be rebuilt from scratch. The safeguards now in place—mandatory manual selection plus granular policy control—give IT the power that was missing in November.

Still, no one should click “Download and install” on a production server without thorough validation. Download the feature update manually, run it in a sandbox, and mandate rigorous change management. The tooling works; the onus now falls on planning, not on patching.

For detailed step‑by‑step instructions, refer to Microsoft’s upgrade documentation. Check the Windows Server 2025 update history page for cumulative update details that may affect post‑upgrade stability.