He modified KB5073032 to accept installation on 26100.1 keep this "hacking" stuff in the correct thread [GUIDE] [DISCUSSION] Windows Editions Reconstructions
I see when you said "(DISM Offline Only)" i thought it's modified but that's still preprelease, and signed with dev certificate i don't think there are hidden features yet, so it only change registry display version to 26H2
You should check the uup-converter-wimlib-125 version you provided, why did you allow 26200.8973 to accept the KB5073032.cab file. https://forums.mydigitallife.net/threads/windows-10-esd-repository.59082/page-61#post-1303176
It does not "allow" it, it's dism / cbs that does similar to how 25H2 EKB can be applied to LTSC 2024 and Server 2025
Concerning UUP Converter. How do the "wim2esd = 1" and "vwim2esd = 1" options in ConvertConfig.ini fit into the script, logically? When you start it standalone, you will get an explicit choice to create install.wim or install.esd (or ISOs containing them). This choice MUST absolutely override anything set in the ini. Yet, when I select to create a WIM in the menus, it will still create an ESD nonetheless (and lists the wim2esd option at the start). So either one or both of these options from the ini seems to have a too high priority.
On August 11 next update the confusing on 26340.xxx will be the next 26h2 beta 26300.xxx will be 26h2 this new build should have no expire date or water mark keep fingers cross and no Biggy since it is just an enablement package not a major update of the OS
Which builds are actually upgrades? They can be spotted by looking at the HAL (Hardware Abstraction Layer) version via MSInfo32.exe. At the moment all official stable public non-beta releases use kernel base and HAL 26100.1. All current 26100 and 26200 public builds (and older 26220, 26300 beta releases without watermarks) share that 26100.1 base. Recent beta releases (watermarked) have switched to 26100.2, but everything became very confusing afterwards. I doubt 26100.2 is just an update. It is supposed to be an upgrade and not some enablement package. Is 26340.xxx going to be HAL 26100.2 or is that coming out later this year?
Hmm 10.0.26100.6 is new start for new update KB5122055 to 10.0.26100.1746 how checkpoint for 26300.xxxx ?
That's not the same thing. Until a few months ago, all 26100, 26200, 26220, and 26300 versions shared the same kernel base and HAL, which was 26100.1. Ever since 26220 and 26300 builds started having watermarks, their kernel base and HAL went up to 26100.2. When kernel base and HAL version goes up, it is supposed to be an upgrade, but maybe not as major as going from 22631 to 26100, but still an upgrade. I am only curious when public is going to get that kernel base and HAL 26100.2. I'd use beta versions myself, but I can't stand the watermark and a certain script that removes it half-baked, not always working.