Microsoft Patches Windows Server 2025 Auto-Upgrade Issue
Microsoft addressed a significant configuration flaw on April 15, 2026, that was triggering unplanned operating system upgrades across enterprise Windows Server deployments. The issue affected systems running Windows Server 2019 (build 17763) and Windows Server 2022 (build 20348), causing them to automatically initiate upgrade sequences to Windows Server 2025 without administrator intervention or approval.
The problem first surfaced in enterprise environments during routine Windows Update cycles starting in late March 2026. System administrators reported that their production servers began downloading and installing Windows Server 2025 upgrade packages during scheduled maintenance windows, despite having no explicit upgrade policies configured. The upgrade process consumed significant bandwidth and storage resources, with some organizations reporting multi-terabyte downloads across their server fleets.
Microsoft's engineering teams traced the root cause to a misconfigured Windows Update policy that was incorrectly classifying the Windows Server 2025 upgrade as a critical security update rather than an optional feature update. This classification bypass allowed the upgrade to proceed through automated patch management systems that were configured to install critical updates automatically. The Microsoft Security Response Center confirmed that the issue originated from a server-side configuration change deployed on March 28, 2026.
The upgrade process typically took between 45 minutes to 2 hours per server, depending on hardware specifications and installed roles. During this time, affected servers experienced service interruptions as the upgrade required multiple reboots and role reconfiguration. Organizations with clustered environments reported cascading failures as multiple nodes attempted to upgrade simultaneously, overwhelming failover mechanisms and causing extended downtime periods.
Microsoft's initial response involved temporarily disabling the problematic Windows Update classification on April 10, 2026, which prevented new unwanted upgrades from starting. However, servers that had already begun the upgrade process continued to completion, leaving administrators to manage mixed-version environments until a permanent fix could be deployed.
Windows Server 2019 and 2022 Enterprise Deployments Hit
The unwanted upgrade issue specifically targeted Windows Server 2019 systems running build 17763.1 through 17763.4889 and Windows Server 2022 systems with builds 20348.1 through 20348.2322. Both Standard and Datacenter editions were susceptible, regardless of whether they were deployed as physical servers, virtual machines, or cloud instances. The problem was most prevalent in environments using Windows Server Update Services (WSUS) or System Center Configuration Manager (SCCM) for automated patch deployment.
Enterprise customers with large server fleets experienced the most significant impact, particularly those in financial services, healthcare, and manufacturing sectors where unplanned upgrades could trigger compliance violations or disrupt critical business processes. Organizations running domain controllers, Exchange servers, SQL Server instances, and other mission-critical workloads reported service degradation during the upgrade windows. The issue also affected Azure Stack HCI deployments and Windows Server containers, where the upgrade process could corrupt container images and require rebuilding of containerized applications.
Small and medium businesses using Windows Server Essentials editions were largely unaffected, as these versions follow different update channels that weren't impacted by the misconfiguration. Similarly, organizations that had disabled automatic updates or implemented strict change control processes were able to avoid the unwanted upgrades, though they still needed to manually review and block the problematic updates from their approval workflows.
Microsoft Deploys Permanent Fix and Recovery Guidance
Microsoft released the permanent resolution through Knowledge Base article KB5037592, which is automatically delivered via Windows Update to all affected Windows Server 2019 and 2022 systems. The fix modifies the Windows Update client behavior to properly categorize major version upgrades as optional updates that require explicit administrator approval. System administrators can verify the fix installation by checking the installed updates list for KB5037592 or running the PowerShell command 'Get-HotFix -Id KB5037592' on affected servers.
For organizations that experienced unwanted upgrades to Windows Server 2025, Microsoft provides several recovery options depending on the upgrade completion status. Servers that completed the upgrade can be rolled back using the Windows Recovery Environment if the upgrade occurred within the past 10 days and the Windows.old folder remains intact. The rollback process requires booting from Windows installation media and selecting the 'Go back to the previous version of Windows' option from the recovery tools menu.
Organizations needing to prevent future unwanted upgrades can implement additional safeguards through Group Policy settings. The 'Configure Automatic Updates' policy should be set to 'Notify for download and notify for install' or 'Auto download and notify for install' rather than fully automatic installation. Additionally, administrators can use the 'Select when Preview Builds and Feature Updates are received' policy to defer feature updates for up to 365 days, providing time to evaluate major upgrades before deployment.
Microsoft recommends that affected organizations review their Windows Update deployment rings and implement staged rollouts for future server updates. The company has also committed to improving its update classification processes to prevent similar incidents and will provide advance notification for major version upgrades through the Microsoft 365 Admin Center and Azure Service Health dashboards.
