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
Uhm, Windows? No.
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.
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.
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.
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?
My router is just that: A gateway
This follows a HW firewall (I intend to replace)
Behind that is
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.