Enterprise Windows 11 Deployments Blocked by April Update—Microsoft Issues Workaround
Microsoft has confirmed a newly uncovered conflict triggered by its April 2025 security update that disrupts the rollout of Windows 11 version 24H2 via Windows Server Update Services (WSUS), a tool widely used by IT teams in corporate environments.
The bug, introduced through update KB5055528 on April 8, 2025, is halting feature update installations across managed devices in enterprise networks. Organizations relying on WSUS to push the latest version of Windows 11 are seeing installations stall or fail outright.
The issue came to light after IT professionals began sharing symptoms across forums such as Reddit and Microsoft’s official community hub. According to Microsoft’s Windows Release Health Dashboard, impacted systems may produce update errors with code 0x80240069 and log entries noting the ‘wuauserv’ service crashing unexpectedly.
Critically, this glitch does not affect home users, as WSUS is exclusive to business-grade IT infrastructure.
To address the problem, Microsoft introduced a Known Issue Rollback (KIR) on May 5, 2025, which allows enterprises to undo the specific problematic change without removing the entire update. The rollback is deployed via a downloadable Group Policy configuration, tailored separately for Windows 11 versions 22H2 and 23H2.
Once installed, admins can navigate to Computer Configuration > Administrative Templates to find and apply the appropriate fix.
For those preferring not to use Group Policy, Microsoft has also acknowledged a registry-based workaround. This approach involves modifying system settings via a .reg file, which must be executed with administrative rights.
While a longer-term solution is still under investigation, Microsoft is encouraging affected organizations to implement the KIR or registry patch while awaiting a potential permanent fix, which may arrive in the next Patch Tuesday update on May 13, 2025.
It’s important to note that only Windows 11 client versions are currently impacted—no server editions are affected.
