When using ESDtoISO to make a an installable ISO image from the install.esd file, one has the option of making a 'full' or 'compressed' ISO file. Is there any reason not to make the compressed iso? (The compressed iso fits on my nominally 4 GB USB stick, while the full iso does not.)
TIA...
Extract from the tutorial:
That's the difference, it's up to you to decide which version to use.Some facts to help you to decide, the numbers about Build 10041 ISO image created with this tool:
- WIM based ISO, Windows 10 Build 10041 32 bit, size 2.45 GB, ISO created from the ESD in 6:57 (Min:Sec)
- ESD based ISO Windows 10 Build 10041 32 bit, size 2.09 GB, ISO created from the ESD in 3:32
- WIM based ISO, Windows 10 Build 10041 64 bit, size 3.30 GB, ISO created from the ESD in 9:40
- ESD based ISO, Windows 10 Build 10041 64 bit, size 2.68 GB, ISO created from the ESD in 4:35
Above times to create the ISO using this tool using an HP ProBook 4530S i5 laptop.
Because the ISO based on ESD intead of WIM is more compressed and encrypted to save space, Windows needs to do more decompressing and decrypting when using it. The difference is not significant but to give you an example, installing Windows 10 to a Hyper-V virtual machine took using the 32 bit Build 10041 ESD based ISO (#2 in above list) 15 minutes (from boot to first Settings dialog after the installation), and using the same Windows version but a WIM based ISO file (#1 in above list) 12:35. Both virtual machines had exactly the same settings, the virtual hard disks were created on the same drive on host, and the host was not used for anything else during the installation.
Kari
Quote