Error 0x80240069: Microsoft acknowledges a problem upgrading to Windows 11 24H2 with WSUS

Microsoft Confirms Error 0x80240069 Blocks Windows 11 24H2 Upgrades via WSUS and SCCM Windows Forum+2GinjFo+2Windows Forum+2

Microsoft has officially acknowledged a critical issue affecting enterprise environments attempting to upgrade to Windows 11 version 24H2 using Windows Server Update Services (WSUS) or System Center Configuration Manager (SCCM). The problem, identified by error code 0x80240069, causes the Windows Update service (svchost.exe_wuauserv) to crash during the upgrade process. TugaTech+4Windows Forum+4Windows Latest+4

---

🛠️ Issue Overview

The error manifests when devices running Windows 11 versions 22H2 or 23H2, managed via WSUS or SCCM, attempt to upgrade to version 24H2. After installing the April 2025 security update (KB5055528), these systems encounter an access violation fault, leading to the crash of the Windows Update service and the appearance of error code 0x80240069. Windows Forumroosho. – Jack of all IT Trades+9BleepingComputer+9Windows Report+9

Event logs typically show messages such as “Service wuauserv has unexpectedly stopped,” indicating the failure of the Windows Update service. Windows Latest+6Windows Forum+6Windows Forum+6

---

🧪 Root Cause

The issue appears to stem from a conflict introduced by the April 2025 Patch Tuesday update (KB5055528). This update seems to interfere with the Windows Update service’s ability to process the 24H2 feature update packages when deployed via WSUS or SCCM. GinjFo+11Windows Forum+11Windows Forum+11

Microsoft has acknowledged the problem and is currently investigating the root cause to develop a fix.

---

🔄 Workarounds

While awaiting an official fix from Microsoft, administrators can consider the following temporary solutions:

• In-Place Upgrade: Use the Windows 11 Installation Assistant to perform an in-place upgrade to version 24H2. Microsoft Learn+1Sysnative Forums+1
• Manual Deployment: Deploy the 24H2 update manually using ISO files, bypassing WSUS/SCCM. Windows Forum+4Windows Forum+4GinjFo+4
• Registry Modification: Some administrators have reported success by applying specific registry changes to mitigate the issue. Windows Forum+1GinjFo+1

It’s important to note that these workarounds may not be suitable for all environments and should be tested thoroughly before widespread implementation.

---

📅 Next Steps

Microsoft has not provided a timeline for a permanent fix but has indicated that they are working on resolving the issue. Enterprises relying on WSUS or SCCM for updates should monitor Microsoft’s official channels for updates and consider implementing temporary workarounds to maintain update compliance.

For more detailed information and updates, refer to Microsoft’s official documentation and support forums.