Xinso. I read and forgot to see your images before. Replaced and until now adding packages without any error. Seems to work.
My apologies if this has been asked before - but if you use the same ZIP (no config change) and generate a few ISOs they're all different file sizes, is this just because of dates being different?
Thanks, much appreciated Out of curiosity I dug into the WIM files and compared them with WinMerge, and noticed that data is also being captured from the local hosts C:\ProgramData directory because "Users\All Users" inside the capture path redirects to it, is this perhaps a bug?
I downloaded a Windows Home + Home Single Language 19043.1149 script from UUP dump, however the ISO is not created, only ISOFOLDER, and checking install.wim with DISM, there's a single index of Windows 10 Home, the Home Single Language SKU was not integrated. The script worked fine for creating multiple editions images of Windows 11 Insider Preview, I don't understand why an Windows 10 AIO image is not being created this time.
@ksio89 please don't crosspost but let's keep this conversation in this thread. Can you show the full conversion progress?
Sorry, I didn't know a dedicated thread existed. I found the solution, I generated Cumulative Update script, when I should have done a Feature Update instead, now the ISO was built with additional editions.
ISO should be made using any of the two options, the only difference is that the cumulative update option doesn't offer the DU for setupmedia and the feature update does.
Strange, CU script didn't create an ISO. And for some reason the script created a 19041.1 image, which was the installed build. This is the script I downloaded: Code: 19043.1149_amd64_pt-br_core_9acda6c6_convert_virtual.zip And this was the iso created: Code: 19041.1.191206-1406.VB_RELEASE_CLIENTMULTI_X64FRE_PT-BR I don't get it, in another PC I downloaded a 19043.1149 script of Windows 10 Pro and it created an ISO of the same build.
Just show us the full progress of the runs you did that didn't create an ISO, the only difference between the 2 options is one or two extra updates included.
Sorry, but what do you mean by progress, where is the log you're asking for located? edit: I guess you mean the CMD window titled "UUP -> ISO v67"? I'll copy the log next time.
The progress is the txt you saw scrolling by in the command prompt window in which the conversion progress was shown. Example: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-644#post-1675435
Yes, as Linux scripts cannot integrate any updates, including the Enablement Packs that turn 2004 into 21H1. Base build for 2004, 2009 and 21H1 is always 19041.1.