You dont integrate LP stuff without updating, you have to let the script update the ISO with latest LCU/SSU also. VM blocking ram?
existing ISOs are just prepended with random number to avoid overwrite W10MUI only distinguish Client <> Server, it's doesn't check or identify editions
Generally you are right, its better this way, but I separate those steps in case something goes wrong with updates, so I just need to start over from LP-integrated-isos (extracted folders) instead of whole new. Yea, removing stuff I plan later with NTLite, but Ill take a look in this one too, thanks.
W10MUI integrates the Language files and updates in the correct way, what why would it be better to do it your way? Nothing goes wrong with updates when the script is used properly and the updates provided correctly.
I never said my way is better, I literally said, his/official way is better: 2 different things. And I have my reasons why I'm doing it different. There is a lot what could go wrong, even in best conditions either. In the end it does not matter how much and many times I explaining it to you, you will/let delete the post anyway, once again... for no any reasons at all.
It makes no difference as long as everything went alright and files are good. Even if something went wrong you woundnt even know what went wrong
What I mean is, look the file name: 10240.20766.240830-2256.TH1_CLIENT_X86FRE_EN-US_DE-DE Version Build Number, Sub-Build-Number (Update-State), Date, Time, Code-name (threshold 1 or smth like that), edition (no idea why "client", its enterprise LTSB), FRE (no ideal.. any free retail?), architecture, first/main L(P), added LPs. But for 22H2 "clients" (real clients, like home, pro, workstation stuff), it takes any old date (no idea which one exactly, maybe the wim creation,- first time I see this, first time either I keep the file names like this.. so) I'm very happy about the scripts, the work in general. Always working flawless, huge respect, so I try to avoid to ask every single time, something is weird, - while high probability that the mistake is on my site.
Yea, I know, in network-view and microsofts-view its official a client. But I personal would it put a third group, like you have server, clients, and the one between, the admins/chiefs desks. They neither do slave work nor function as server, they control important stuff, access the clients while they cannot reverse etc. Small companies probably not buying a lot of enterprise licenses for everyone there, but instead pro-workstation and similar, depends. There are also 3 different group in isos, business, consumer and yea.. enterprise [LTS]. (or let say it was, seems they changed something with 24H2 idk)
Once, there were Home, Pro and Enterprise. It was good schema. Enough for everything. There was sense in. As server there was server (for the dumbs who pay to get an insecure af server system, but hey it has native "active directory" so great....) Now they do endless sht versions, Pro is basically Enhanced Home, Workstation is 1:1 same with unlocked hardware support., and so on. Enterprise also is just 1:1 with some services more running, so they can squeeze companies more, "hey its for companies, u know, its some special" Round 10/11 already (its incredible how fast it is without defender... I mean its still slow af, its in vm, but still like 3x faster than with defender)
TH = Threshold, RS = Redstone (taken from Minecraft), and then, the elements like vb = Vibranium, ge = Germanium etc. Using such things as work names is "hip" these days. FRE = free build, aka "Unchecked". Unchecked means no debug code left that could slow down operation. The only other famous build type is CHK - checked, full of Debug code to solve problems, but slower.
seems fine whats the setting you have been using in W10UI_10.45r and did you just replaced them with 2 cmd files in the updates folder in W10MUI_24_2 ?
No exist General Eval. When is EVAL then in iso file is part EVAL. and as @Enthousiast said above for GE is Germanium branch Here more explain info how is branch releases Microsoft uses the chemical elements of the periodic table and that is their internal publishing code name. Code: Cobalt co 21H2 Windows 11 co-release Nickel Ni 22H2 Windows 11 2022 Update ni-release Nickel Ni 23H2 Windows 11 2023 Update ni-release Germanium Ge 24H2 Windows 11 2024 Update ge-release