Microsoft fixes bug behind Windows Server 2025 automatic upgrades

Microsoft fixes bug behind Windows Server 2025 automatic upgrades

1) Overview

• A long-standing bug caused some installations of Windows Server 2019 and Windows Server 2022 to “unexpectedly” upgrade to Windows Server 2025.
• The issue was first acknowledged by Microsoft in September 2024 after widespread reports from Windows admins about overnight upgrades to a newer server version for which licenses were not always in place.
• The upgrade path could appear as a banner in the Windows Update settings page, enabling in-place upgrades for eligible systems.
• Third-party update management tools were cited as a contributing factor, though Microsoft and software makers noted procedural or configuration issues could also play a role.
• After more than a year, Microsoft stated the problem was addressed and that customers could again check for upgrades via the Settings app.

2) Background and Context

• The phenomenon drew attention from system administrators who found servers unexpectedly running Windows Server 2025, sometimes without the corresponding license or support entitlement.
• Microsoft pointed to a Windows Update banner as a vehicle for in-place upgrades, highlighting that legitimate upgrade paths existed but could be triggered in ways admins did not anticipate or approve.
• The company also cited third-party update management software as a factor, while those software makers argued the underlying problem was a procedural and classification mismatch on Microsoft’s side, along with the speed of release.
• At the time, Microsoft did not immediately provide a detailed root-cause analysis beyond these high-level factors, and inquiries from news outlets were left with limited public commentary.
• The situation underscored the delicate balance between enabling timely feature upgrades and maintaining strict licensing and deployment controls in large, heterogeneous environments.

3) The Fix and Current Status

• In mid-April 2026, Microsoft announced that the known upgrade issue had been resolved and that the upgrade offer had been re-enabled via the Windows Update settings panel.
• A Windows release health update confirmed that customers could again manage and perform in-place upgrades to Windows Server 2025 through standard upgrade workflows.
• For organizations planning to upgrade, Microsoft Learn provides official guidance on performing an in-place upgrade from Windows Server 2019 or 2022 to Windows Server 2025, with emphasis on testing and licensing considerations.

4) How to Perform an In-Place Upgrade (If Applicable)

• Open the Settings app and navigate to Windows Update to check for feature updates.
• If the Windows Server 2025 upgrade is offered, follow the on-screen prompts to begin an in-place upgrade.
• Prior to upgrading, verify license eligibility and ensure appropriate licensing for the target Windows Server version.
• It is recommended to test the upgrade path in a controlled lab environment that mirrors production workloads before applying it to production servers.
• During the upgrade, monitor for any prerequisites or compatibility prompts and address them as directed by the upgrade wizard and official Microsoft guidance.

5) Related Updates and Context in the Same Period

• Microsoft had released out-of-band updates in March 2026 to address issues with a non-security preview update, which had been pulled due to installation problems.
• Another emergency out-of-band update resolved major sign-in issues triggered by March Patch Tuesday security updates, which affected sign-ins across Microsoft accounts in several apps (Edge, Teams, OneDrive, Microsoft 365 Copilot).
• Additional out-of-band updates addressed a Bluetooth device visibility bug on Windows 11 and mitigations for RRAS-related vulnerabilities affecting Windows 11 Enterprise devices.
• These related updates illustrate the broader pattern of rapid, non-scheduled fixes that frequently accompany large feature and security rollouts, underscoring the importance of monitoring release health communications from Microsoft during and after major upgrades.

6) Practical Takeaways for Administrators

• Stay current with Windows Release Health communications to verify when upgrade offers are enabled or re-enabled.
• Validate licensing implications before initiating an in-place upgrade to Windows Server 2025.
• Use authoritative upgrade guidance from Microsoft Learn to follow official steps and prerequisites.
• Test upgrades in a controlled environment to confirm compatibility with workloads, apps, and third-party tooling before broader deployment.
• Be aware that ancillary updates (Bluetooth, sign-in issues, RRAS vulnerabilities, etc.) can accompany major upgrade cycles and may require separate out-of-band remediation.

7) Summary

• The issue that caused Windows Server 2019 and 2022 to upgrade to Windows Server 2025 without explicit, consent-based deployment has been addressed.
• Microsoft has re-established the upgrade pathway via Windows Update settings and published formal guidance for in-place upgrades.
• In the broader context, a sequence of out-of-band fixes in early 2026 demonstrates the ongoing emphasis on reliability and compatibility as organizations navigate major server upgrades and patch cycles.