18362.267 is the current retail release ring 19H1 build for people who actively seek updates, 18362.239 is normal retail ring. the build you show is insider preview 19H2 build.
@abbodi1406 - I have tested the creation of ISOs from UUP (18362.10012 and 10013) and it generally works, however, the ISO names are wrong. The ISOs are always named after the base UUP set, 18362.1. Is it possible to use the correct string from the updates? Edit: Couldn't test installations, yet, dealing with a defect 6TB hard drive (ouch).
This is intended, since the install.wim itself is not updated, and the updates can be manually changed not to mention that to get the new name string, i have to extract some files from the CU and i could not rely on DU setuphost.exe, since it's not always updated or reflect the CU version alright, i think i'll go with extraction option
Maybe it would be best to just determine the string and write it into a batch file so everyone can rename the ISO by executing that file if desired (kinda like the old rename script on the UUPDUMP website). Alternatively, an option in the script "Use base name" vs. "Use CU name". Just tossing some ideas.
@abbodi1406 Tested UUP creation for both 18362.10014 and 10015 (v32), and the ISOs still end up with the base image name only. For reference, here's my INI: Code: [convert-UUP] AutoStart =0 AddUpdates =2 ResetBase =0 NetFx3 =1 StartVirtual =1 wim2esd =0 SkipISO =0 SkipWinRE =0 ForceDism =0 RefESD =0 [create_virtual_editions] vAutoStart =0 vDeleteSource=0 vPreserve =0 vwim2esd =0 vSkipISO =0 vAutoEditions=
I didn't update create_virtual_editions.cmd to produce the new name scheme so it only work with StartVirtual = 0
Could you dump the ISO name into a .txt file so I can at least rename it manually? Right now, I only change the version part, but the timestamp eludes me. And when create_virtual_editions.cmd is started by the UUP converter script, is it possible to simply pass the ISO name to it?
The second part is doable for now, you can set SkipISO=1 in [convert-UUP], the result directory will have the updated name (copy it) then you can run the virtual script
An announcement I have forgot to write Since s1ave77 left MDL due his reasons, the UUP dump downloader project will not be continued by anyone. Consider it dead. No support for this project will be provided. UUPDL also is not supported. I recommend switching to UUP dump website.
Code: 1. Feature Update = Base build + updates + dynamic update 2. Cumulative Update = Base build + updates I am noob. Which one is public released ?
Is it possible to create a "18362.325.190817-2329.19H1_RELEASE_SVC_PROD3_CLIENTMULTI_X86FRE_EN-US.ISO" on a Windows 64bit operating system? I always get error messages : mraut.dll : blob not found Thank you
Should not have to do with the host architecture, i create x86 or x64 iso's on my x64 OS. Did you try it today? @abbodi1406 fixed some issues, and it should also already be implemented on uupdump.ml too. This is on my x64 OS: It already passed the wim creation: Code: ============================================================ Checking UUP Info . . . ============================================================ ============================================================ Configured Options . . . ============================================================ AutoStart 1 AddUpdates 1 ResetBase ============================================================ Preparing Reference ESDs . . . ============================================================ CAB->ESD: microsoft-onecore-applicationmodel-sync-desktop-fod-package-x86 CAB->ESD: microsoft-windows-hello-face-migration-package-x86 CAB->ESD: microsoft-windows-hello-face-package-x86 CAB->ESD: microsoft-windows-internetexplorer-optional-package-x86 CAB->ESD: microsoft-windows-languagefeatures-basic-en-us-package-x86 CAB->ESD: microsoft-windows-languagefeatures-handwriting-en-us-package-x86 CAB->ESD: microsoft-windows-languagefeatures-ocr-en-us-package-x86 CAB->ESD: microsoft-windows-languagefeatures-speech-en-us-package-x86 CAB->ESD: microsoft-windows-languagefeatures-texttospeech-en-us-package-x86 CAB->ESD: microsoft-windows-mediaplayer-package-x86 CAB->ESD: microsoft-windows-quickassist-package-x86 CAB->ESD: microsoft-windows-tabletpcmath-package-x86 CAB->ESD: openssh-client-package-x86 ============================================================ Creating Setup Media Layout . . . ============================================================ ============================================================ Creating install.wim . . . ============================================================ Using LZX compression with 8 threads Archiving file data: 4826 MiB of 4826 MiB (100%) done ============================================================ Updating install.wim / 1 image(s) . . . ============================================================ 1/2: windows10.0-kb4512941-x86.cab 2/2: windows10.0-kb4515530-x86.cab Deployment Image Servicing and Management tool Version: 10.0.18362.1 Mounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18362.1 Processing 1 of 1 - Adding package Package_for_KB4515530~31bf3856ad364e35~x86~~18362.323.1.0 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18362.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~x86~~18362.325.1.6 [===========================69.0%======== ]
I got a download package "18362.325_x86_en-us_professional_e92ed2ac_convert_virtual.zip" containing "convert.sh" and "convert_ve_plugin" beside others. I don't know what file you mean and where to find the latest version, and how to check the version? Thank you for helping EDIT I've downloaded the whole package again and now it seams to convert without problems Thank you
@whatever127 always uses the most current UUP>ISO converter from @abbodi1406 , the updates were done yesterday, so now you have re-downloaded and got the most current version too.