oh well with this exp date we know now 26340.xxx is in dev and the real 26H2 26300.xxx is about finished
There is a difference between making an unofficial Frankenstein build, where no consideration is given to how future updates will be affected by that edition's policies, and integrating updates according to the official procedure.
- This is not the LTSC thread - LTSC will never be 26H2 and very specially not an Insider Build - And the above reply
Some people do actually care about the edition's policies and future updates compatibility and updating according to the official procedure. And they do create versions compatible with such mentioned things. UUPDump is also a Frankenstein of sort just close to the official. It's not an official way by Microsoft for sure, it's sticking Microsoft's packages together until they all work together. Microsoft builds their ISO/.wim differently. To Microsoft UUPDump is "Frankenstein", the same way Hackjobs are "Frankenstein" to you. If UUPDump != Frankenstein then Hackjobs identical to official thing != Frankenstein either. Good Hackjobs are identical to the real thing, the same way uupdump is. Even if everything is 101% same as official, if it's not made by Microsoft, which uupdump isn't, it's automatically a frankenstein hackjob, just a really convincing/functional one.
Can we stop this, @Windows_Addict meant the LTSC part is frankenbuild from this thread, the original dev who made that possible deeply regrets creating it ever (he is no longer among us). UUP dump ISOs is officially Homebrew because the ISO is made by files from MSFT servers and the cosing skills and knowledge by @abbodi1406, only the MVS, Techbench and VLSC ISOs are official ISOs and can be verified by its sha/sha256.
Let me give you an example of why such custom LTSC builds are not compatible with future updates. LTSC 2021 has a build number 19044, and some people thought, why not make it 19045 to satisfy some programs' requirements, so they installed an older version of EKB, which allowed changing the LTSC build number. At first, it looked normal; 19045 is supported, so what could go wrong? Turned out that Windows stopped offering updates to those 19045 LTSC builds because of a build mismatch when W10 went EOL. Similar things would happen to that custom LTSC build 26340.9212, and it's pretty much guranteed. That is why it's lebelled as Frankenstein and discouraged here.