How to Create Bootable ISO from Windows 10 install.esd File
InformationThanks to our member topgundcp for the idea. This tutorial will use the decrypt script mentioned in his post, according to new information I have found the original authors are users abbodi1406, qad and synchronicityI from the MDL site, complete credits in the Read Me file included in the tool downloadable packet. I have simply edited the script a bit and finally made these step by step instructions.
The command script file tool used to create the ISO from the ESD file is a native Windows tool DISM, no third party tools or programs are involved. If you are concerned you can open the ESDtoISO.cmd file with Notepad and check it, it is totally safe only using native Windows commands.
NoteWhen Windows 10 is upgraded to a new build using the Windows Update, Microsoft uses the ESD file format to deliver install files needed. ESD stands for Electronic Software Delivery.
The Windows install.esd file contains the usual Windows install.wim file (WIM = Windows Imaging), encrypted and compressed. Install.wim file in its turn contains everything needed for a complete Windows installation.
This tutorial will show you how to create a bootable ISO file from the install.esd file you have downloaded which can then be burned to a DVD disk or USB to be used for clean install instead of upgrade.
If you have upgraded from Windows 8.1 or if you have performed a repair install on your Windows 10 see this post before starting.
InformationAdditional information about where to find the ESD file and when it will be created in this post. I recommend you read it before proceeding with upgrade,
Step OneDownload and set up ESDtoISO tool
1.) Check Windows Update for possible new build. Tutorial: Windows Update - Check for and Install in Windows 10 - Windows 10 Forums
2.) When a new build is available, let Windows Update download it. When Windows Update has prepared the upgrade, you will be told a restart has been scheduled. At this point you can find the install.esd file which contains everything needed to make an ISO image in a hidden folder C:\$Windows.~BT\Sources.
3.) The ESDtoISO tool is based on ESD Decrypter v.6.7, I have edited the original script to remove everything not necessarily needed. Download the tool (ESDtoISO.zip) from OneDrive: bit.ly/TenForums
4.) Open the downloaded ZIP archive with File Explorer, click Extract all, select where you want the files to be extracted, click Extract. Here I selected to extract the files on drive E:, folder ESD:
Step TwoRun ESDtoISO tool
1.) Copy the ESD file to same folder where you extracted the ESDtoISO tool files. Right click the ESDtoISO.CMD file and select Run as administrator. This runs the tool, automatically finding your ESD file.
2.) Select the ISO you want to create, a traditional ISO which contains the install.wim file to install Windows, or an ESD based ISO which instead of install.wim file contains the compressed install.esd to install Windows. Both types can be used the same way to install Windows, both can be used as such, mounted to a virtual drive or burned to Flash or DVD drive.NoteThis tip from a fellow Ten Forums member @f14tomcat:
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.
3.) The tool starts working, showing an error for missing key. This error can be ignored:
4.) The process can take some time, up to half an hour depending on your hardware. When finished you have an ISO image to be used as such in installing the new build on a virtual machine or to be burned to DVD or USB to be used on a clean install on a physical computer.
That's it, now you can perform a clean install with your new Windows build.
Thanks Kari (and topgundcp).