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

adamf said:

Kari said:

No, I have tested both MS account and local account, there's no difference.

There has to be a reason why some users get the WIM file instead of ESD... Intriguing!

Upgrade rather than clean install? I upgraded from 8.1 and got a wim.

That's a theory worth checking.

lehnerus2000 said:

I just noticed that this test install does not have a RecoveryImage folder (C:\RecoveryImage).

Lehnerus, it shouldn't have: it was a clean install from ISO, not an upgrade from PC Settings > Update and Recovery.

Kari said:

lehnerus2000 said:

I just noticed that this test install does not have a RecoveryImage folder (C:\RecoveryImage).

Lehnerus, it shouldn't have: it was a clean install from ISO, not an upgrade from PC Settings > Update and Recovery.

I suspected that it might only exist due to the upgrade process, but I wasn't sure if that was the case.

Worked great for me. I have a VMWare Player VM that was originally clean installed with TP 9841 then upgraded to 9860. It had the esd file. I ran the script and it successfully created an ISO which I used to setup a VirtualBox VM running 9860.

I couldn't be certain since I didn't time it, but I believe the process of creating the ISO and then doing a clean install to a VM took less time than it took to download and install the upgrade. That makes sense since I don't have the fastest internet connection (4Mbs max). Doing a clean install vs upgrading via Windows Update is definitely faster.

Hats off to everyone involved in making this available.

strollin said:

Hats off to everyone involved in making this available.

Just for the records, this is how tutorials are often made .

As is quite common with tutorials, the method told in this one is absolutely not invented nor found out by me. I got the original script from a friend in May when trying to find a way to create 8.1 install ISO from the ESD file and was getting frustrated when I did not find the right arguments and parameters to use with DISM to do it. Got the script as email attachment, the original script has none whatsoever information about the author. I only found out the original author after reading this post today. Thanks for that info!

I forgot the whole script until I stumbled upon this thread of fellow geek topgundcp ​yesterday. I thought that I have that script, edited and shortened for just creating the ISO, tested it with Build 9860 and it worked. Made the tutorial crediting topgundcp, not crediting the author of the original script because I did not know who had made it but making it clear that the tool is based on another script from another author. This from the beginning of the tutorial:

   Information

Thanks to our member topgundcp for the idea. This tutorial will use the decrypt script mentioned in his post, I have just edited the script to remove unnecessary code and corrected some errors and finally made these step by step instructions.

Somehow I feel now I need to make this absolutely clear: I did not try to take credits for the idea nor the original esd-decrypter-v3 script. Credits where they belong.

Kari

Just realized the install.wim is dated 10/3 which is when I upgraded 8.1.1 to 10 TP. Has nothing to do with build 9860.

I think the only way to make this work so a build 9860 ISO can be created is to remove the C:\RecoveryImage directory before doing the upgrade to 9860.

The RecoveryImage direcotry appears to be there so you can go back to whatever was installed before upgrading to Windows 10 TP or if 10 TP was a clean install then to be able to get back to it when build 9860 is installed. I'm guessing it will stay there no matter how many updates are applied on top of 10 TP.

If you have the drive space you could probably have one for each version you update. For instance:

ren C:\RecoveryImage RecoveryImage-10TP
Install 9860 and it should create a new C:\RecoveryImage
ren C:\RecoveryImage RecoveryImage-9860

Not sure what to do next but just an idea.

Kari, you deserve a lot of credit for getting everyone's ideas together and placing them in an order we can follow. Your tutorials on 7,8 and 10 are just informative and excellent. I have followed this twice on 2 virtual machines to extract the ISO to mail to a member who has metered high speed internet and costs would be prohibitive for him to download these. M$ will I am sure provide ISO files when 10 ships but with this method we can convert and save.

Kari said:

strollin said:

Hats off to everyone involved in making this available.

Just for the records, this is how tutorials are often made .

As is quite common with tutorials, the method told in this one is absolutely not invented nor found out by me. I got the original script from a friend in May when trying to find a way to create 8.1 install ISO from the ESD file and was getting frustrated when I did not find the right arguments and parameters to use with DISM to do it. Got the script as email attachment, the original script has none whatsoever information about the author. I only found out the original author after reading this post today. Thanks for that info!

I forgot the whole script until I stumbled upon this thread of fellow geek topgundcp ​yesterday. I thought that I have that script, edited and shortened for just creating the ISO, tested it with Build 9860 and it worked. Made the tutorial crediting topgundcp, not crediting the author of the original script because I did not know who had made it but making it clear that the tool is based on another script from another author. This from the beginning of the tutorial:

   Information

Thanks to our member topgundcp for the idea. This tutorial will use the decrypt script mentioned in his post, I have just edited the script to remove unnecessary code and corrected some errors and finally made these step by step instructions.

Somehow I feel now I need to make this absolutely clear: I did not try to take credits for the idea nor the original esd-decrypter-v3 script. Credits where they belong.

Kari

That's why I didn't thank anyone in particular since it was a team effort and I didn't want to start thanking individuals and risk missing someone.

OK geeks, the results of all day extensive but still only preliminary testing. Your results, comments and opinions are highly valuated :).

• Windows 8.1 in-place upgraded to Windows 10 TP Build 9841:
  
  • C:\RecoveryImage folder has the build 9841 install.wim file after upgrade to Windows 10 TP
  • When this setup is further upgraded to Build 9860, the C:\RecoveryImage folder has the build 9860 install.wim file after upgrade
  
  
• Clean install of Windows 10 TP Build 9841
  
  • C:\RecoveryImage folder has the build 9841 install.esd file
  • When this setup is further upgraded to Build 9860, the C:\RecoveryImage folder has the build 9860 install.esd file after the upgrade

Interesting is that if the WMC is added to a cleanly installed Windows 10 TP Build 9841, the only way to get the Build 9860 upgrade to work is first to perform a repair install with build 9841 install media (in-place upgrade with same version). At this point the install status is changed from clean install to upgrade install and although the system was never upgraded from Windows 8.1, it now acts as if it was and creates the WIM file in C:\RecoveryImage instead of the ESD file as after the clean install.

Summary:

• An upgrade from 8.1 to build 9841 and later builds creates the install.wim file for current build in C:\RecoveryImage folder, the method in this tutorial to create an ISO image cannot be used.
• Installing Windows 10 TP clean uses ESD file format for upgrades, the method in this tutorial to create an ISO image can be used.

Next test install running as we speak, more later :).

Kari

This Tut works perfectly Kari I successfully created the ISO and it installed flawlessly in VMware, Then I created a Win 10 installation USB and installed it to a real drive.

   Note

Although the below results and conclusions are by far not absolute facts but simply results of my testing, I am convinced they are valid and true conclusions. I have tested each and every installation scenario listed below at least twice on a physical machine and twice on a virtual machine and can reproduce each test result on physical and / or virtual machines.

The below is simply my opinion, facts as I believe them to be at the moment. You are welcome to show any errors in them and post your findings.

The reason why some users do not get the install.esd file it being replaced by install.wim is now quite clear: if Windows 8.1 has been in-place upgraded to Windows 10 Technical Preview Build 9841, or if a cleanly installed Build 9841 has been repair installed (an in-place upgrade to same version and edition), Windows uses the old WIM file format to deliver upgrade to Build 9860.

Notice that adding the Windows Media Center to Windows 10 Technical Preview build 9841 causes the internal version information to be changed to Windows 8.1 Pro with Media Center. Due this, before upgrading to build 9860 the build 9841 must be repair installed, thus causing the build upgrade being in WIM format instead of ESD even if the original build 9841 was installed clean.

By default only a cleanly installed Build 9841 which has never been repair installed uses the new ESD file format for upgrade. We need to "distract" Windows to make it think it's all new and fresh, never been upgraded .

To do this and get the upgrade in ESD format and about 30% smaller download on a Windows 8.1 to Windows 10 TP upgraded system, or on a Windows 10 TP system which has had at least one repair install, do the following before starting the upgrade build download from PC Settings > Update and recovery > Preview builds:

1.) Close all open applications, open Explorer, delete the following folders:

• C:\RecoveryImage
• C:\$Windows.~BT (system folder, UAC asks your permission, click OK to accept deletion)
  
  • This is a hidden folder, be sure to enable showing Hidden Items, otherwise you won't see it and might forget to delete it

2.) Delete the file C:\$UPG$PBR.MARKER (system file, UAC asks your permission, click OK to accept deletion), close the Explorer.

3.) Open the Registry Editor (WIN + R, type regedit, hit Enter), browse to key HKEY_LOCAL_MACHINE\SYSTEM\Setup

4.) Delete both the DWORD Upgrade (right pane) and KEY Upgrade (left pane), see screenshot. The system warns you that skies can fall down if you delete these items, just laugh loud and accept the deletion:

5.) Still in Registry Editor, browse to key HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus, if either DWORD CleanupState or DWORD GeneralizationState has any other value than 7, change it to 7 by double clicking the DWORD in question and entering the new value:

6.) Close the Registry Editor

7.) Go to PC Settings > Update and recovery > Preview builds and start downloading the new build. When downloaded click Install. Be patient, it takes some time and worst part is there's no indicator to show how it's proceeding. In my tests now for instance after first reboot while installing the new build, I had 20 to 26 minutes (depending on if vm or real machine) a totally black screen with nothing on it, no pointer or indicator before next reboot.

That's it. The above process (steps 1 to 6) takes no longer than a minute or two, when I timed it I did the whole process in well under one minute. You can then upgrade to new build and create a bootable ISO as told in this tutorial for further installations.

   Note

To be prepared for the next build upgrade you might want to delete the file DONOTREPLACE.txt in C:\RecoveryImage. If the file is present when upgraded to next build the install.esd file will not be replaced with the new one. Windows will be upgraded but the esd file in Recoveryimage folder will remain build 9860.

Kari