@Ahsan instructions here : https://forums.mydigitallife.net/th...1-22h2-vb_release.80763/page-543#post-1820847
I installed the December updates on W10 "IoT" Enterprise in Canada and didn't see any signs of Copilot, so maybe we're not getting it here yet. By "á la edge", I meant that properly uninstalling Edge requires the use of a ridiculous script and it's 50/50 whether I have to re-uninstall after any monthly update. I'm assuming that Copilot will be similar (although raptorddd suggests that it may not be possible at all). Has anyone tried the update on a system with NO WinRE partition? Does it simply not even attempt to install that part of the update? Or does it error out the same as if the partition was too small? And if it errors out, does this cause the entire LCU to fail, or only the WinRE/BitLocker patch?
@Human_3829416057 If you disable WinRe using command "reagentc /disable", still the same error. If you delete WinRe partition, NO more KB5034441 offered. No LCU errors.
LOL, this WinRE update is such a royal screwup. The update package itself is only 22.7 MB in size, and WinRE partitions are sized to have around 80 MB free. Well, the problem is that WinRE lives as a WIM inside the WinRE partition. And the update tries to update individual files inside the WIM. Which means... Mount the WinRE WIM Apply the servicing stack update to the WinRE WIM (yes, the bulk of the 22.7 MB package is actually just the servicing stack update from 2023) Apply the actual fix to the WinRE WIM (only several MB) Commit changes, unmount, etc. And of course, all this requires a lot of temporary space, and there's not nearly enough of it in the WinRE partition. The final result doesn't take that much space. It's just that it requires a ton of temporary space in order to mount and update WinRE as an offline image. Clearly the better solution is to just provide a fresh new WinRE.wim to drop in. This would be way less work, it would go way faster (everyone here knows how slow it is to mount, do dism stuff, etc.), and have way fewer points of failure. "Oh no, but this means that the update will be a 500MB download instead of 23MB!" Yea, so what? The monthly LCU is well over 700MB in download size. Okay, let's say that you do prefer an overly complicated update method that is slow and has multiple points of failure, just so that you can get a small download size for the update. Then the solution would be to do all that temporary scratch work on the main OS partition and only drop the final result into the WinRE partition. But instead, it's all being done on the WinRE partition, which means you need it to be way, way bigger than it needs to be, just to be able to handle this temporary work. So, everyone: just ignore this update. Microsoft screwed up. Wait for them to come up with a better solution that doesn't require a gigantic WinRE partition to work. It can be done. They're just too f**king incompetent to get it right the first time.
Won't following M$ guidance at kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf nuke the OEM RE anyway?
Is there an alternate set of instructions? It lists "delete partition override" and format quick fs=ntfs label=”Windows RE tools”
That's why it's manual instructions if you don't know how or don't want to lose the current config, set WinREVersion registry and ignore the update https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-729#post-1820918
Sorry, yes, I mean 21h2 LTSC. I'd like to pick 22h2 for a long run, got tired of experimentation, but 21h2 ltsc is supported longer. So, I think, if it's definitely not possible to put 21h2 upgrades on 22h2, I'll choose 21h2, and if updates possible, I'll choose 22h2. Any chance, that it will be possible?