Microsoft has resolved a significant issue that hindered the delivery of Windows 11 24H2 feature updates via Windows Server Update Services (WSUS) following the installation of the April 2025 security updates. This situation arose after the company acknowledged widespread reports of upgrade problems from users on various online platforms, including Reddit and its community forums.
WSUS, originally introduced as Software Update Services (SUS) nearly two decades ago, serves as a vital tool for IT administrators. It allows them to manage updates for Microsoft products across extensive enterprise networks from a centralized local update server, eliminating the need for individual endpoints to connect directly to Microsoft’s servers for updates.
In late April, Microsoft confirmed the upgrade issues affecting users attempting to transition from Windows 11 23H2 or 22H2. Those impacted encountered Windows Update Service (wuauserv) errors, specifically error code 0x80240069, during their update attempts.
Fortunately for home users, these update complications are unlikely to arise, as WSUS is primarily intended for business and enterprise environments. Microsoft noted in a Windows release health update that devices installed with the April monthly security update, released on April 8, 2025, or later (beginning with KB5055528), may face challenges when trying to update to Windows 11 24H2 via WSUS.
As part of the issue, users found that the download of Windows 11 24H2 either did not initiate or failed to complete, with the Windows updates log displaying error code 0x80240069 and additional logs indicating that the wuauserv service had unexpectedly stopped.
Fix available via Known Issue Rollback
While the fix is not yet available to all customers through Windows Update, Microsoft is currently rolling it out automatically via Known Issue Rollback (KIR) for all enterprise-managed devices. To rectify the situation on affected Windows enterprise-managed devices, IT administrators must implement the Known Issue Rollback Group Policy on endpoints running Windows 11 22H2 and 23H2.
To deploy this policy, administrators can utilize the Group Policy Editor to select the targeted Windows version within the Local Computer Policy or the Domain policy on the domain controller. A restart of the affected device(s) will be necessary to apply the group policy setting. Microsoft has provided further guidance on deploying and configuring KIR Group Policies on its documentation website.
In addition to addressing the WSUS update issue, Microsoft is also working to resolve a “latent code issue” that has led to some PCs being upgraded to Windows 11 despite existing Intune policies meant to prevent such upgrades. This situation is not unprecedented; in November, Microsoft acknowledged that certain Windows Server 2019 and Windows Server 2022 devices were upgraded to Windows Server 2025 without user consent.