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
So since you’ve clearly forgotten, let’s go back in time.
This is exactly what you wrote;
I mean Jesus Christ my guy.
Having never written Windows kernel code, you are in no position to judge the foundation.
No, you said you have been writing code longer before I was born.
I have been writing code since before you were born. Does that make my opinion more valid?
The source I lonked clearly explains in detail why code is misread. You handwaved it away with the premise that code might not be misread. With that attitude, memory safety isn’t needed either. Write perfect code and you don’t need to use structured programs. “Don’t do what everyone does because it is extremely hard.” isn’t a valid argument.
" It would be insane to claim that all of Linux (I’m also referring to all the gnu tools, window managers etc) should be thrown out and start fresh. "
I added that in the second sentence because I realized you have never used Linux without it being part of a distro. The first Linux I ran was compiled without being part of any distro. It was for a PRI Gateway when I was working for Vint Cerf on his side project.