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
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.
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.
At least set it outside your DHCP range.
I have my DHCP set to use from
.100and up, and my static addressee are in the.1-99range.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.
Too bad when the DHCP server is down with the proxmox host ;)
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 withBut 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:
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 :)
No worries. Hopefully you have things sorted.