Windows 11 24H2 Update Fails on WSUS/SCCM: Troubleshooting & Official Advice

Here’s a detailed summary—including current status, official acknowledgments, and available advice—on the Windows 11 24H2 update failure via WSUS for enterprise and business users:

The Issue​

• Scope: Devices running Windows 11 22H2 or 23H2, managed via Windows Server Update Services (WSUS) or System Center Configuration Manager (SCCM), cannot upgrade to Windows 11 24H2 after installing the April 2025 Update (KB5055528).
• Symptoms:
• Update fails to download/install.
• Logs show error code 0x80240069 and “Service wuauserv has unexpectedly stopped.”
• This does not affect Windows 11 Home users, as WSUS is not used there.
• Depth: The issue affects both feature updates (24H2) and some monthly cumulative updates. WSUS/SCCM environments are primarily impacted.

Microsoft’s Official Response​

• Acknowledgment: Microsoft has confirmed the bug and says it is under active investigation.
• Root Cause: The problem began after the April 8, 2025 Patch Tuesday update (KB5055528). Certain cumulative updates (also including KB5055629 and KB5058919) disrupt WSUS update mechanisms.
• Current Advice: There is no official workaround or patch as of now. Microsoft is advising IT administrators to watch the Windows Release Health Dashboard for updates.

Recommendations for IT/Admins​

• Pause Upgrades: Delay the deployment of Windows 11 24H2 in WSUS- or SCCM-managed environments until Microsoft issues a fix.
• Do Not Attempt Manual Workarounds: At this stage, no registry, group policy, or local fix is recommended unless specifically advised by Microsoft.
• Monitor Communications: Keep checking Microsoft’s official channels for solutions.
• Community: Stay in touch with professional forums to exchange the latest news and unofficial troubleshooting ideas.

Possible (Unofficial) Workarounds​

• Manual ISO Upgrades: For critical cases, manually upgrading using the official ISO might work—but is not scalable or generally advised for fleet deployments at this time.
• Delaying April Patch: For machines not yet updated with KB5055528, consideration could be given to deferring this update for a short time (though this means missing out on April security patches).
• Registry Script (Experimental): One community-discussed registry fix was mentioned to "override problematic variant logic" introduced by the cumulative updates. However, this is not documented by Microsoft as an official remediation and should not be considered production-ready except in lab/test environments.

How Long Will This Last?​

• As of now, there is no ETA for a fix. Previous bugs of this scale have sometimes taken weeks or months to resolve in WSUS/SCCM-heavy environments.
• Microsoft has also placed a compatibility hold on some devices to prevent the update from being delivered in problematic scenarios, referenced as "Safeguard ID: 54762729" (mainly devices with USB eSCL scan protocol devices attached).

Summary Table​

References​

• Neowin, The Windows Release Health Dashboard
• Multiple forum posts and technical summaries

Bottom Line: If you manage enterprise machines with WSUS and are blocked by error 0x80240069, delay upgrades to 24H2 and monitor Microsoft’s channels. Do not expect an instant solution; history shows such bugs can take time to resolve.
Let me know if you would like a full-text copy of the registry workaround mentioned, or if you require additional step-by-step troubleshooting tips for WSUS!

---

Source: Tom's Hardware Windows 11 update failure stops machines from updating to version 24H2 using WSUS