@abbodi1406 Thank you for the explanation! Here is how/what I end up doing to solve my question: • Since I do not wanted to write anything to C:\Windows\SoftwareDownload\Download\hex…. • Than I changed the code as follow: Original line:- IF %RefESD%==1 move /y "%CD%\temp\*.ESD" "%UUP%" >nul 2>&1 Modified line:- if %RefESD%==1 move /y "%CD%\temp\*.ESD" "%~dp0UUPs" >nul 2>&1 & copy /y "%UUP%\Professional_en-us.esd" "%~dp0UUPs" >nul 2>&1 This way no matter what path you gave or ESDs are already located at UUPs folder or you copied UUP files to UUPs folder the result always will be the same “ESDs will be saved at UUPs folder” of course with RefESD=1. On my tests, there was no errors creating an ISO:-x86 Single Edition. x64 Single Edition. x86 AIO 10 Editions. x64 AIO 10 Editions. Thanks and happy weekend to everyone!
Sorry to disturb, but i just found this thread and wanted to ask what i have to do to convert the *.esd file (downloaded within the Windows 10 1703 ISO via MediaCreationTool) to a *.wim file. I always get the following error message when i start decrypt-esd.cmd. *********************** ERROR: "4" is not a valid image in "install.esd.orig"! Please specify a 1-based image index or image name. To list the images contained in the WIM archive, run wimlib-imagex.exe info "install.esd.orig" ERROR: Exiting with error code 18: Tried to select an image that does not exist in the WIM. ERROR: "4" is not a valid image in "install.esd.orig"! Please specify a 1-based image index or image name. To list the images contained in the WIM archive, run wimlib-imagex.exe info "install.esd.orig" ERROR: Exiting with error code 18: Tried to select an image that does not exist in the WIM. "9600" kann syntaktisch an dieser Stelle nicht verarbeitet werden. ******************** Thanks in advance ! TEN
@enthousiast Thank you for your help - you were absoluteley right, i used the wrong tool Now the only thing left ist that i have to edit the downloaded *.ISO file and change the containing install.esd to the created install.wim file. Or can this be achieved by another tool (like when you have downloaded a new Windows Insider build in the past and afterwards created a complete *.ISO out of this file)? Thank you again for helping ! Greetings TEN
@abbodi - Can't get to it. No internal links are working at the moment. I think it's just links that are posted as post= and thread= Reported in chat, Daz is looking to fix it.
Is option-1 using ESD > ISO supposed to create an ISO with the same hashes as listed on MSDN? The one I tried did not.
Ahhh, okay, I did not realize using the same esd twice to build an iso would create output with different hashes. I just re-ran the same conversion and the hashes do change.
While the internal files are exactly the same, but exporting ESD to WIM is like creating new WIM every time, with different GUID and timestamps which result in different WIM hash and different ISO
Small question: The ESD Decrypter has an option to create an ISO with compressed Install.ESD. The UUP Converter can only create ISO with Install.WIM. Is there a reason to that?
The ESD Decrypter has the option because it doesn't create it actually, it just export/split install image from already compressed ESD to install.esd while in UUP, the reference ESDs has different types, compressed ESD, regular CAB, uncompressed expanded folder (Express UUP) assembling the install image require creating a compressed ESD from scratch, which require a lot of CPU/RAM, and takes considerable time for Canonical UUP, most reference ESDs are already compressed ESDs, so exporting install.esd might not take that amount of resources but i didn't bother verify that
Spoiler: Quote In other words: It's possible, just not offered because it's expensive. AIO ISOs created from UUP are currently a little too large to fit on a DVD-5, ESD would have fit, I guess.
Anyone knows what is going on here: Code: Deployment Image Servicing and Management tool Version: 10.0.16179.1000 Details for image : I:\sources\Install.wim Index : 1 Name : Windows 10 Home Description : Windows 10 Home Size : 15,698,524,616 bytes Index : 2 Name : Windows 10 Home Single Language Description : Windows 10 Home Single Language Size : 15,668,278,114 bytes Index : 3 Name : Windows 10 Pro Description : Windows 10 Pro Size : 15,808,843,521 bytes Index : 4 Name : Windows 10 Education Description : Windows 10 Education Size : 15,644,186,964 bytes Index : 5 Name : Windows 10 Enterprise Description : Windows 10 Enterprise Size : 15,785,497,909 bytes Index : 6 Name : Windows 10 Pro Description : Windows 10 Pro Size : 15,781,741,622 bytes Index : 7 Name : Windows 10 Home N Description : Windows 10 Home N Size : 14,608,001,256 bytes Index : 8 Name : Windows 10 Pro N Description : Windows 10 Pro N Size : 14,732,489,902 bytes Index : 9 Name : Windows 10 Enterprise N Description : Windows 10 Enterprise N Size : 14,732,058,332 bytes Index : 10 Name : Windows 10 Pro N Description : Windows 10 Pro N Size : 14,735,164,887 byte I just created this iso with uup-wimlib-9 and this is what I see when checking it, 2 Pro and 2 Pro N... It doesn't sound right.
It was a bug with v7 and 16170 UUP files, one of the pro (n) indexes is cloud (n) instead of pro, it was solved with v8 but when i used it with 16179 UUP files the error was there again. Didn't try v9 yet.