It's a dynamic update DU for Sources/Setup, it's for the ISO:\Sources folder. When updating the ISO with the LCU the DU content is used to update the sources folder. Here you can safely download all the applicable and needed updates: https://forums.mydigitallife.net/posts/1571109 And why not just use W10UI, no extra steps needed other then shoving the listed updates next to the script and run the script.
Sure, but even the same process which is used by W10U to apply KB5032906 breaks the installer. Even with just the KB5032906 installed, the OS can no longer be installed. Without it, with every other update it works fine. en-us_windows_10_iot_enterprise_ltsc_2021_x64_dvd_257ad90f as the base (i.e., 19044.1288). A pre-requisite missing, despite I couldn't find anything stated as a requirement?
BTW: Good to know uupdump.net is a legit successor, was on the search. (mkuba™ my friend, we'll meet in next life, there are things i would like to talk about) Have a Stalker™, cool, is my first, 2 times reported, let's see... aaaaaand disapeared, won't be missed.
It isn't just the KB5032906 which is causing it, but all of the previous DUs as well: e.g., KB5007402. There must be some sort of a pre-requirement, which isn't fulfilled. Otherwise it makes no sense. So a simple question, what else needs to be added to 19044.1288 ISO, besides the DU (e.g., KB5032906 or KB5007402) because it is obvious that something is missing?
I'm not doubting that, rather I am trying to understand what I am doing wrong. According to everything I've found, extracting the files inside the DU to the "sources" folder of the ISO should work (e.g., W10U uses expand + xcopy). However, for whatever reason it doesn't.
Then extract the cab using 7zip and copy paste or drag the content to the ISO:\Sources folder manually and save the ISO. You probably need a driver not an update for your problem or the setup.exe from "ISO:\boot.wim\2\sources" doesn't match setup.exe from "ISO:\Sources", which won't happen when W10UI is used with the correctly listed updates.
Likely the mismatch then. Since the default 19044.1288 ISO doesn't ask or require any additional drivers. Yeah, replacing the setup.exe (in ISO /sources/) with the one from boot.wim (Index:2) /sources/ does the trick.
I used the specified updates. The updates themselves have no issues nor is there anything really missing.
my dear friend, do as you were advised to do by @Enthousiast Make sure you use the script to integrate the update and that is it, okay?
I did, but I initially never used the resulting image to install it Instead, I used the same exact updates, in the same exact order of installation, with the known results. So it makes me wonder, what's the actual issue here. Is it the IoT LTSC being somehow incompatible with the DUs, or what. Because I wouldn't expect even Microsoft release multiple updates that are not intended and cannot be used. Since to my understanding, the contents of the DU are intended to replace the files on the installation media, not inside the WIMs (install, boot, winre). So what gives
you can't just drop the content of DU for Sources update to sources folder, it never worked that way and never will be just use W10UI
This time this was a bigger rebuild (pre 24H2 and after). It was on hold (shortly) for a reason. The created the base for Copilot(+) System Integration this time and inbetween outsorced the GUI as Store App --- that prevents lots of problems in EU --- tricky move. So question is what was restructured to allow Copilot(+) global System Access --- System Packages and The GUI(s) ....?
That Dev Experience appeared early and seems part of that, besides other stuff, is my educated guess. Preparation ....than activating feature with command or small KB. .......????????
I've been getting this error on any driver I try to update since 19045.4717 Very little out there in terms of solutions. Anyone else have it?