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

  • Appoxo@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    1
    ·
    24 hours ago

    I tried doing it the debian way and (I believe) followed the instructions of one of the debian manuals.
    Problem: Most assume (like you) that the DHCP server is always on and able to give out adresses. But sometimes life is in the way (and in my case: offline for maintenance) and it doesnt work with the DHCP option.

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      23 hours ago

      Usually the DHCP server is the same as the router, so if the router is offline, you can’t access it anyway. Right?

      Or are you saying you’d plug in directly with a patch cable?

      Could you explain more about your network setup?

      • Appoxo@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        23 hours ago

        My router is just that: A gateway
        This follows a HW firewall (I intend to replace)
        Behind that is

        • My proxmox host with a bunch of VMs (including the DHCP/DNS server)
        • A raspberry PI (which I reformatted and had the trouble with getting a static IP)
        • Bunch of other stuff like servers, NAS and stuff.