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.comEnglish
    619·
    1 day ago

    At least that shit is somewhat documented.

    If you are so sure about the way Linux is fully usable and understandable: Please tell me the proper way to set a static IP via terminal on Raspberry Pi OS and/or Debian bookworm.

    Because last I checked (about 4 weeks ago) it was basically impossible.

      • Appoxo@lemmy.dbzer0.comEnglish
        32·
        1 day ago

        I believe I tried the exact raspberry forum entry but it didnt catch on even with reboots and whatever I tried.
        Saved for the future though.

        • femtech@midwest.socialEnglish
          10·
          1 day ago

          If you can I would set static IPs from the router though. That’s what I do as another device can still take the IP and cause issues.

          • sugar_in_your_tea@sh.itjust.worksEnglish
            3·
            1 day ago

            At least set it outside your DHCP range.

            I have my DHCP set to use from .100 and up, and my static addressee are in the .1-99 range.

            I still set it through my router so I have a place to look up which one is which (they’re piling up), but they’re all in that range.

        • sugar_in_your_tea@sh.itjust.worksEnglish
          5·
          1 day ago

          How you set it can vary depending on what you’re running. Linux is all about choice, and choice means multiple ways to do a thing. Places to look:

          • raspi-config - catchall CLI tool on Raspbian, not sure if it covers both of the following, but it’s a good option to start with
          • /etc/network/interfaces - the Debian way to do things
          • Network Manager - usually used for desktops, but can be used by servers; if the first two don’t work, try this

          But you could also have installed something different. If you post your OS and version and what you’re running on it, I can give better advice.

          That said, normal networking rules apply:

          • don’t set a static lease in your DHCP range, or you could get conflicts, which can look like it’s not working
          • consider using DHCP and setting the static lease through your router; use the MAC address and you’ll never need to mess with network settings on the Pi
          • if you set on the pi, make sure everything is correct (netmask, gateway, interface)
          • Appoxo@lemmy.dbzer0.comEnglish
            2·
            18 hours ago

            I will remember it for next time I need to set a static IP in Linux. Comment is saved and hopefully I can reference it.

            I appreciate the effort you took to help me and anyone that is still looking for help :)

      • Appoxo@lemmy.dbzer0.comEnglish
        45·
        1 day ago

        Somewhat. That means partially.

        At least there arent 500 different ways to set a static IP.
        Don’t get me wrong. I like Linux but I can’t get warm witg it as a desktop OS besides SteamDeck.
        But I like it very much as a server OS.

        • sugar_in_your_tea@sh.itjust.worksEnglish
          81·
          1 day ago

          So you’re saying you don’t like the choice in Linux? On a given distro, there’s usually one right way and maybe 2 other ways. Learn the right way for your setup and you’re good.

          If you’re using Network Manager, do it the Network Manager way. If you’re using Debian as a server, do it the Debian way (`/etc/network/interfaces). If you’re using SUSE, do it the SUSE way (YaST).

          If you don’t want to deal with it, use DHCP (usually default) and set the static lease on your router using the MAC address. That’s better anyway because you can change all of your static leases in one spot if you ever need to.

          • Appoxo@lemmy.dbzer0.comEnglish
            1·
            21 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.worksEnglish
              1·
              21 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.comEnglish
                1·
                21 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.
        • MonkderVierte@lemmy.mlEnglish
          1·
          19 hours ago

          I do like the diversity. You learn a few patterns and you can do them all. In the end basically the same but more flexible.

      • Appoxo@lemmy.dbzer0.comEnglish
        3·
        1 day ago

        If I remember correctly that didnt work despite following the instructions.
        Either I did it wrong or something changed. Oh well. I will keep that for future reference and maybe it’ll work then.