WSUS blocks downloading Windows 11 24H2 update on 23H2 & 22H2 devices, leaving 0x80240069 error

Microsoft just confirmed that Windows 11 24H2 feature updates are being blocked if you’re using Windows Server Update Services (WSUS). Users on Windows 1123H2 and 22H2 are getting the 0x80240069 error code after installing the April 2025 security patches.

Microsoft warns WSUS blocks Windows 11 24H2 update on 23H2 and 22H2 devices with the 0x80240069 error code

WSUS, first introduced as Software Update Services (SUS) almost 20 years ago, is a lifesaver for IT admins. It allows managing updates for Microsoft products from one central server, so you can control what gets rolled out, when, and to whom, without every device pinging Microsoft’s servers directly.

The company has confirmed that the issue with Windows Server Update Services (WSUS) has blocked the receipt of the 24H2 feature update on Windows 11 23H2 and 22H2 devices. If you’re trying to download the Windows 11 24H2 update through Windows Server Update Services (WSUS), you might fail.

Microsoft says an error code “0x80240069” pops up, blocking the download. The issue reportedly started after the April 2025 Patch Tuesday KB5055528 update. Microsoft has detailed this issue and noted:

Devices that have installed the April Windows monthly security update, released April 8, 2025, or later (starting with KB5055528) might be unable to update to Windows 11 24H2 via Windows Server Update Services (WSUS). WSUS allows Servers with the WSUS role to defer, selectively approve, and schedule updates for specific devices or groups across an organization.

As part of this issue, the download of Windows 11 24H2 does not initiate or complete. Windows updates log can show error code 0x80240069, and further logs might include text similar to “Service wuauserv has unexpectedly stopped”. Home users are unlikely to experience this issue, as WSUS is designed for use across business and enterprise environments.

Also read: Windows 11 25H2 spotted in the wild; likely to be a smaller update

No workaround is available for the time being

Microsoft didn’t provide any workaround this time around, but noted that it is “presently investigating and will provide an update when more information is available.” Interestingly, the tech giant hasn’t provided any details about the 0x80240069 error code. For now, we can only hope that the issue gets resolved as soon as possible.