Best to do, yes. But you can now run the cmd on the multi iso and when you use W10UI, for offline updating, you can select the Enterprise SKU, to be serviced and set it to delete all others.
The error is most likely on you, as MCT can't upgrade editions that are not offered on the media - for example LTSB/LTSC. That is, until you do a reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v EditionID /d Enterprise /f and ofc use the universal mediacreationtool.bat to unlock the Enterprise edition, or use another EditionID such as Education, Professional or Core
@KleineZiege I've updated my post a bit: https://forums.mydigitallife.net/th...c-rp-19h1_release.79259/page-151#post-1525989
Apps not opened for me now after install 18362.30. When I installed 18362.1 it fixed in .30 or .53. Now it's working.
Download Pro x86 and Pro x64 separately and set the create additional editions to create Enterprise and delete the source index. When both Enterprise only iso's are made, run the multi-arch.cmd from the UUP>ISO v27 project, it will create a dual arch. iso from both source iso's. If you want, i can create a more detailed howto, but using the UUP Dump Website.
Hi. Im on build 1809. I always used pro edition. Not sure about that registry key. Will take a look. Never had a problem upgrading windows 10 on this pc.
there is a way to check if .iso i made with upp automated script is ok ? i mean, hash should match (with other upp iso reference i mean) or can be some differences ?
No, only officlally distributed untouched ISOs from a single source (MSFT, Techbench, VLSC/MVS, or mirrors containing the official untouched iso's) can be verified, as soon as you touch the content of the iso, it gets a different hash.
okay, and if i make the same upp .iso twice ? i will have two hash cause of some minor differences (time, system etc) or i have a matching duplicate ?
I have made some progress I think - but before I continue I want to make it clear that I want both architectures in their own ISO images, not both in one single ISO image. I downloaded 18362.1_x86_en-gb_professional_fa88b32f_convert.zip and edited ConvertConfig.ini as you told me. I also found another ConvertConfig.ini in \18362.1_x86_en-gb_professional_fa88b32f_convert\files\uup-converter-wimlib.7z, so I also edited this as you told me. This has generated a 18362.1.190318-1202.19H1_RELEASE_CLIENTENTERPRISE_VOL_X86FRE_EN-GB.ISO file which seems to boot normally. Should I also do something else with the SKU? This is the part that confuses me also.
Now do the same for x64 and put both iso's in the uup>iso v27 project folder and run, multi_arch_iso.cmd.
1903 ARM64 in all languages: https://forums.mydigitallife.net/threads/windows-10-esd-repository.59082/#post-992532