Jump to content
  • Microsoft: Yes, Windows 11 24H2 update fails download on 23H2 / 22H2 with 0x80240069 error


    Karlston

    • 172 views
    • 2 minutes
     Share


    • 172 views
    • 2 minutes

    Windows 11 version 24H2 is nearly eight months old, and despite that, Microsoft is still blocking the feature update on systems owing to compatibility issues. The latest such incident was announced last month under the safeguard hold ID 56318982. And sometimes it can take a long while before these compatibility blocks are removed, as it happened, for example, in the case of ID 52754008.

     

    However, updates can be blocked as a result of bugs in the Windows Update service itself. As it turns out, Microsoft's Windows Server Update Services (WSUS) is currently bugged out such that it is unable to receive the 24H2 feature update on Windows 11 23H2 and 22H2 devices.

     

    When an attempt is made to download version 24H2, the error code "0x80240069" is displayed. Microsoft says that the problem started with the April Patch Tuesday update KB5055528.

     

    The company has explained the issue in some detail below:

     

    Devices which 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".

    The tech giant has not provided any workaround in this case and has only mentioned that it is " presently investigating and will provide an update when more information is available." You can view the issue here on Microsoft's official Windows health dashboard site.

     

    Looking around the internet, it appears that SCCM (System Center Configuration Manager) is also affected by this problem, and it is not exclusive to WSUS.

     

    Microsoft has dedicated documentation for Windows Update-related error codes. However, the page does not provide any information about the 0x80240069 error, unfortunately.

     

    Source


    Hope you enjoyed this news post.

    Thank you for appreciating my time and effort posting news every day for many years.

    News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of March): 1,357

    RIP Matrix | Farewell my friend  :sadbye:


    User Feedback

    Recommended Comments

    There are no comments to display.



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...