Windows 11-24H2 installations with certain update statuses can no longer install further updates. Only a manual correction will help.

Last Christmas, a problem with Windows 11 24H2 installations became known that they cannot install further updates if they were installed from an installation medium with certain update statuses. Microsoft has now given up looking for an automated solution to this problem or developing a fix-it tool – The only option available to those affected is manual correction.

Microsoft has confirmed this decision by setting the entry in the Windows Release Health announcements to “resolved”. Specifically, the problem description is that a Windows 11 installation on version 24H2, which was installed from a CD (sic) or USB drive with integrated October or November updates from 2024, can no longer install any further security updates. This also includes media created with the Windows Media Creation Tool at those times. However, installations that have downloaded the updates via Windows Update and applied them do not have this problem.

Windows update dropouts: only manual solution available

The entry on the problem from Microsoft has had the status “resolved” since the end of last week. However, it still only contains the previous workaround as a solution: The problem can be solved by overinstalling with an installation medium that contains at least the security updates from December 2024 – i.e. was created from December 10, 2024 –. Microsoft does not mention a fix-it tool, script or other options, such as registry changes.

Such an updated medium can be created with the Windows Media Creation Tool, which is available on Microsoft’s Windows 11 download website. This either downloads an ISO file that can be transferred to DVD or creates a bootable USB stick with the Windows installation; this should have at least 8 GB of space.

cross-posted from: https://lemm.ee/post/55122353

https://www.heise.de/en/news/Windows-11-24H2-update-problems-Microsoft-gives-up-on-finding-a-solution-10275962.html

  • andrew_bidlaw
    link
    fedilink
    English
    arrow-up
    3
    ·
    22 小时前

    MS Office’s lie of WYSIWYG and the idiotic requirements to follow absurdly complicated formatting guidelines and them not rendering the same from system to system or even correctly is the most brutal offender. If we used simplistic markdown without page-breaking in the GUI, there could’ve been no point to buy Office, but we don’t, and itso hsppens I had encountered many times where some arbitrary cosmetic request like ‘you can’t have less than X lines per page’ caused people toy with formatting or rewriting their documents… only for it showing differently on the other side >:ç Thus leading to even worse things like PDF.

    It being the most used piece of office software renders the voluntary switch close to impossible.

    • Obelix@feddit.org
      link
      fedilink
      English
      arrow-up
      7
      ·
      21 小时前

      Let’s be honest: That totally is a monopolistic tactic of Microsoft and regulators would do great to force this open. Force them to release a Linux Office. Force them to really make their file format transparent so that everybody can write working parsers

      • andrew_bidlaw
        link
        fedilink
        English
        arrow-up
        3
        ·
        21 小时前

        I agree. They need to be either pressured or abandoned.

        I feel like they would need to rewrite it completely in that case, partially because no one knows how their legacy code works and partially because it’s completely broken.

        Google with it’s billions and a promise of more free data did great with how office formats work. They set some little limits of what user can do compared to MS Word so ending up with a broken table or whatever is harder, and they aslo strong-armed their way into adoption with their obvious mechanics of real-time collaboration.

        I’m not sure about MS users coming to Linux, but their marketshare was already bled by Google. And if in some scenario Google releases their own internal XML format for these, I guess it’d work too.