Microsoft gives up on users experiencing problems updating their Windows 11 machines. Now recommends a "manual correction"
Microsoft gives up on users experiencing problems updating their Windows 11 machines. Now recommends a "manual correction"
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
You're viewing a single thread.
I'm frequently told that Linux is hard and you need to be a tech guru to use it, yet every week I see 1-2 articles of issues in windows you need to do some bullshit to fix, and in my own use of it I've ran into issues (especially after doing an update) that I just don't run into on Linux or MacOS.
Windows is easy, bro, you just need to run this shady PowerShell script to get rid of ads, run this random EXE from github.ru to disable telemetry, install ClassicShell to make the UI actually usable, install a million utilities for basic features (each from a separate site, of course ; the centralized Windows Store is full of malwarei), then pray
sfc /scannowfixes your system after every update.BTW, don't bother searching for a solution to your problems other than "retry, reboot, reinstall" ; even certified MS professionals don't know how anything works.
I've been on Win10 for years, never had a single problem with any update whatsoever.
Still not subjecting myself to W11 though. As soon as Win10 support ends, I'll make the switch.
I recommend setting up whatever your alternative is a little before committing to ease the transition a bit. It's different, and it's good to fall back to something else for a bit if you get frustrated.
Windows 10 had an update that notoriously broke a lot of games a while back and the only solution was to manually roll it back.
It's been the same on win 11. The only experience i have had was at work. I work closely with the updating team, and there have been a few times where things would break like printers, and we would revert the updates to stop it from going to everyone and uninstall. Sometimes, that meant a help desk guy had to go to the pc or remote in to do it manually. I've been there 19 years now, and it's happened twice?
I've had my enterprise-distro linux machines updating by cron for 22 years. I had two glitches in those 20 years, too, just like you. But in addition to my two glitches - I had to bring in one unlisted dep for cobbler and also correct the smb.conf's old format on another box - in 20 years, I also got
- out-of-the-box
- do-nothing patch runs
- trivial back-out if I needed it
And while I know your numbers are excellent, I simply haven't had to DO ANYTHING since deploying some boxes. They patch, they bounce later on a weekend if they need it ('needs-rebooting' is centralized because ALL software installs are) and I can patch while under load because linux write-locks instead of read-locking. My effort is to check 'some time later' and ensure things are working in ways nagios doesn't catch.
Printer issues? Nah. Supply thing. App not working because java/perl/python/DLLs rug-pulled a dependency? Proper packages list hard dependencies, so that cobbler thing is a bug not an expectation. Network offline? nah. Reboots? timed at 3 minute downtime (1 min before systemd), or 7 minutes if I just updated 1gb of gitlab install because it starts like a manatee.
It's really a different world; and while I've teased the heck out of my windows peers, it's a true statement.
Absolutely, I don't disagree with your statement at all. I work heavily in systems administration and recently transitioned to networking. I deal with Linux systems, servers, vm's, Azure daily, and for stability nothing beats Linux. I just tend to agree with the statement above commenting on how you always see these Windows articles, yet almost none actually affect you in the end.
Same boat here.
The only issues I’ve ever personally run into with Windows are a missing driver for a software I was installing, like twice, and compatibility for gaming which was solved with admin mode and selecting a different compatibility. I’ve used Windows since 3.1
I’ve ran
I've run
You are wrong. Ran is past tense of run.
https://dictionary.cambridge.org/dictionary/english/run-into
run into something
present participle: running | past tense: ran | past participle: run
If you run into problems, you begin to experience them:
example: We ran into bad weather/debt/trouble.
If you're going to try to correct people, please make sure you're actually right first.
It's ran. Because I'm talking about past events.
I don’t mean to say that you’re completely wrong in your reasoning, but grammatically speaking, we use have + verb in past participle which we call present perfect no matter what verb is used.
In this case, you’re talking about something you’ve experienced, so the correct way would be “I’ve run” (as the past participle of run is run).
If you’d like to take a detailed look at it, here you have: Present Perfect - British Council and Using "have ran" or "have run".
Btw, It's completely normal to make mistakes! We're all human, and part of being human is learning and growing from our errors.
It’s either “I ran into…” or “I have run into…”, it’s never “I have ran into…”
So yeah, the one correcting you was right.
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.
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 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)
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.
At least that shit is somewhat documented.
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- 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.
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.
Something like this? https://devtutorial.io/how-to-configure-static-ip-address-on-debian-12-p3121.html
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.