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
My age isn’t important to the argument. That’s not an opinion.
I noticed now that I posted my age you didn’t respond with yours.
You can’t get past personal attacks. First it was I’m too young. When that attack didn’t work, it’s now I’m too old.
Unless you work at Microsoft on the code, you have absolutely no basis for your claim that the entire code base should be thrown out. I use Linux. There are frequent bugs that require me to type in a command manually to work around. 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 didn’t bring up your age to make an argument about it. I simply pointed out that I’ve likely been developing software longer than you’ve been alive and to my credit this statement is almost always true, especially given that very few in their 60s would use a federated social platform, it’s a reasonable assumption. You’re the one who made it about age–and you keep doing so in your replies.
Why do you feel entitled to know my age?
You’re the one fixating on age, and you clearly misread my initial post. You’re counter-arguing against the source you provided, misrepresenting and misunderstanding what your own source said. You’re only arguing against those points because you mistakenly thought I had made them. So, I responded in kind. In typical boomer fashion, you entered this thread dismissive of others, framed everything around your age as if it automatically makes you right, and now blame others for your misunderstandings. Truly a sight to see.
It’s objectively true that building on a poor foundation is a bad idea and it’s also objectively true that sometimes if the foundation is bad enough it’s easier to simply rebuild the whole damn thing from scratch than to attempt to patch bad code. As I said, I’ve been a developer for decades. I’m a subject matter expert here. Just because I don’t work for Microsoft doesn’t mean my critique of their monolithic software is invalid.
It’s an opinion backed by decades of expertise with the product. I’ve not only used every single version of Windows extensively, but I also write software for Windows. That’s not experience you can casually dismiss. I don’t need to work at Microsoft to recognize that its poorly designed from the ground up and that each new version builds on a flawed foundation.
Calling your operating system “Linux”–when Linux is just the kernel and not the OS–doesn’t really help your argument here.
Moreover, the various Linux distributions have a strong foundation around the linux kernel. Windows does not. I don’t understand how anyone could seriously argue otherwise.
There was absolutely no reason to bring up that you were coding longer than I was alive other than to imply that your age is a reason why the argument is invalid.
Funny how you use your age as an argument but see it as entitled when I point out the reverse.
I specifically referenced Gnu tools, window managers, etc. What is wrong with you?
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.