Page 1 of 73 1231151 ... LastLast
    ESD to ISO - Create Bootable ISO from Windows 10 ESD File

    ESD to ISO - Create Bootable ISO from Windows 10 ESD File

    How to Create Bootable ISO from Windows 10 install.esd File
    Published by Kari
    22 Oct 2014

    Published by


    Kari's Avatar
    Finnish but not finished


    Location: A Finnish ex-pat in Germany
    Posts: 9,047

    Show Printable Version 


    How to Create Bootable ISO from Windows 10 install.esd File


    information   Information
    Thanks 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.

    Note   Note
    When 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.


    information   Information
    Additional 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,







    ESD to ISO - Create Bootable ISO from Windows 10 ESD File Step One ESD to ISO - Create Bootable ISO from Windows 10 ESD File
    Download 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.

    Click image for larger version. 

Name:	2015_11_06_01_11_591.png 
Views:	1972 
Size:	217.8 KB 
ID:	46494

    Click image for larger version. 

Name:	2015_11_06_01_15_292.png 
Views:	2805 
Size:	356.7 KB 
ID:	46495

    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

    Name:  2015-03-30_18h43_06.png
Views: 251128
Size:  38.3 KB

    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:

    Click image for larger version. 

Name:	2014-10-22_17h31_07.png 
Views:	6477 
Size:	94.9 KB 
ID:	7312




    ESD to ISO - Create Bootable ISO from Windows 10 ESD File Step Two ESD to ISO - Create Bootable ISO from Windows 10 ESD File
    Run 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.

    Click image for larger version. 

Name:	2015-03-30_15h12_27.png 
Views:	2614 
Size:	10.7 KB 
ID:	15715
    Note   Note
    This tip from a fellow Ten Forums member @f14tomcat:
    f14tomcat said: View Post
    If you have any intention of doing any DISM work It will fail with "source files not found" if using the ESD based ISO format, option #2.

    (example: DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:G:\sources\Install.wim:1 /LimitAccess)

    Some facts to help you to decide, the numbers about Build 10041 ISO image created with this tool:

    1. WIM based ISO, Windows 10 Build 10041 32 bit, size 2.45 GB, ISO created from the ESD in 6:57 (Min:Sec)
    2. ESD based ISO Windows 10 Build 10041 32 bit, size 2.09 GB, ISO created from the ESD in 3:32
    3. WIM based ISO, Windows 10 Build 10041 64 bit, size 3.30 GB, ISO created from the ESD in 9:40
    4. 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:

    Click image for larger version. 

Name:	2015-03-30_15h20_05.png 
Views:	2339 
Size:	27.9 KB 
ID:	15716

    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.

    Kari



  1. Join Date : Aug 2014
    Australia, Adelaide
    Posts : 1,340
    W7 Ultimate SP1 (64 bit), LM 18 MATE (64 bit), W10IP VM, W10 Home
       22 Oct 2014 #1

    Excellent.
    Thanks Kari (and topgundcp).
      My System SpecsSystem Spec


  2. Join Date : Oct 2013
    Canada
    Posts : 909
    Windows 10 Home/10 Pro x 3/Windows 10 Insider Preview ?
       22 Oct 2014 #2

    lehnerus2000 said: View Post
    Excellent.
    Thanks Kari (and topgundcp).
    Well said lehnerus2000 this is a good example of the co-operation that exists on these forums to produce something new and unique.
      My System SpecsSystem Spec


  3. Join Date : Apr 2014
    Space coast of Florida
    Posts : 4,035
    Windows 10 Pro X64 14393.105
       22 Oct 2014 #3

    There is no install.esd file in C:\RecoveryImage. All I see is the following:

    C:\Users\rrkurtz\Desktop\ESDtoISO>dir c:\RecoveryImage
    Volume in drive C has no label.
    Volume Serial Number is 74BE-73AC

    Directory of c:\RecoveryImage

    10/21/2014 07:40 PM <DIR> .
    10/21/2014 07:40 PM <DIR> ..
    10/21/2014 07:40 PM 328 DONOTREPLACE.txt
    10/04/2014 02:22 AM <DIR> Drivers
    10/03/2014 10:08 PM 3,618,526,248 Install.wim
    10/03/2014 11:01 PM <DIR> OEMInformation
    2 File(s) 3,618,526,576 bytes
    4 Dir(s) 188,399,144,960 bytes free

    Is Install.wim the same thing? Can I rename it to .esd?
      My System SpecsSystem Spec


  4. Join Date : Apr 2014
    Space coast of Florida
    Posts : 4,035
    Windows 10 Pro X64 14393.105
       22 Oct 2014 #4

    Ran it anyway and it likes install.wim.

    Is the tutorial wrong? Should it state install.wim instead of install.esd?

    Edit: install.esd was for initial Win 10 TP. install.wim is in the new build 9860.
      My System SpecsSystem Spec


  5. Join Date : Apr 2014
    Space coast of Florida
    Posts : 4,035
    Windows 10 Pro X64 14393.105
       22 Oct 2014 #5

    Ran it anyway and it likes install.wim.

    Is the tutorial wrong? Should it state install.wim instead of install.esd?

    After I enter I the first message I get is:

    Backing up original esd file...

    Running Decryption program...

    ERROR: The ESD file is not a valid encrypted image.

    ===============================================================================
    Creating ISO Structure Layout...
    ===============================================================================

    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17029
      My System SpecsSystem Spec


  6. Join Date : Aug 2014
    Australia, Adelaide
    Posts : 1,340
    W7 Ultimate SP1 (64 bit), LM 18 MATE (64 bit), W10IP VM, W10 Home
       22 Oct 2014 #6

    I had an install.esd file (i.e. C:\RecoveryImage\install.esd).

    After I ran the tutorial tool, it had changed to install.esd.bak
      My System SpecsSystem Spec

  7.    22 Oct 2014 #7

    Thanx Kari, togundcp... just wanna mention credit also goes to the original scripter abbodi1406 at MDL.

    BTW, Has someone tried the install.esd swap with install.wim of the 9841 iso to produce similar results?
      My System SpecsSystem Spec


  8. Join Date : Apr 2014
    Space coast of Florida
    Posts : 4,035
    Windows 10 Pro X64 14393.105
       22 Oct 2014 #8

    Apparently I'm in the process of doing that. See my previous posts.

    Currently running ESDtoISO, install.wim is still there but install.wim.bak is also there.

    At 4% after 10 minutes. I'm going to have to kill this and try again tomorrow as I need to go to bed.
      My System SpecsSystem Spec

  9.    22 Oct 2014 #9

    Ztruker said: View Post
    Apparently I'm in the process of doing that. See my previous posts.

    Currently running ESDtoISO, install.wim is still there but install.wim.bak is also there.

    At 4% after 10 minutes. I'm going to have to kill this and try again tomorrow as I need to go to bed.
    I see you have an install.wim in recovery folder (?), but I was referring to using something like UltraISO to replace the install.wim in the 9841 iso with this install.esd and saving the new iso as 9860.
      My System SpecsSystem Spec


 
Page 1 of 73 1231151 ... LastLast


Similar Threads
Tutorial Category
Bootable File Manager?
Hello, is there any bootable file manager out there because I want to do the following things before installing Windows. 1. Format my C:\ drive with Windows 7.1 2. Move contents from my F:\ drive to C:\ 3. Install Windows 10 of F:\ This is...
General Support
System Information File - Create in Windows 10
How to Create a System Information File in Windows 10 MSINFO contains in depth pertinent information about your system and is often used by Seven Forums members when helping users solve issues, especially during debugging BSOD crash...
Tutorials
Solved An Alternative to Create Bootable ISO from Windows 10 install.esd File
Here's an alternative in addition to Kari's Tutorial: ESD to ISO - Create Bootable ISO from Windows 10 ESD File - Windows 10 Forums https://www.youtube.com/watch?v=lJ8SCzhbycA NOTE: It is better to create an ISO contaning install.wim so if you...
Installation and Setup
Solved USB Download Tool won't create bootable USB using 9926 .ISO
I just wondered if anyone had had any issues creating a bootable USB using the Download Tool with the 9926 .iso? I've tried multiple times now but it just gets stuck at 94% and I end up having to close the program down via Task Manager. Someone I...
Installation and Setup
New - Rufus v2.0.639 - Create bootable USB drives
Rufus - Create bootable USB drives the easy way
Software and Apps
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 01:45.
Find Us
Twitter Facebook Google+



Windows 10 Forums