That was a false alarm
Still not working. It launches OK:
... but any install.esd file I have tried with it just gives this, whatever option I choose :
Makes me angry; I am telling people this does not work and now it looks like it works, it just does not work for me
OK, I really need to apologize!
I would like to state that I have taken this tutorial, the ESD to ISO method very seriously. I have constantly checked that the tool and method work after release of every new build, posting a note about it in this thread. When tool has needed to be updated, I've done it and posted warnings for not to forget to replace the tool with new updated one.
However, now it seems that due something strange at my end here, I warned users that the method does no longer work. I alone am responsible for giving wrong information, based on the fact that in my usual tests before posting about if tool works or not, it was not working for me using one W10 PRO x64 EN-GB ESD file from a physical machine and several ESD files from various Hyper-V virtual machines (PRO x64 EN-US, SWE, FIN, EDUCATION x64 EN-GB and EN-US). I tested with six ESD files, failed six times.
After fellow geek @cereberus posting about his success and another fellow geek @blackroseMD1 posting the same positive results in another thread I reverted all virtual machines to a checkpoint before the upgrade was downloaded, let them re-download the upgrade, removed the tool from my host computer, re-downloaded it from link in tutorial, and to my extreme amazement all ESD files worked, I was now this morning able to create ISO images without an issue.
I have no explanation for why all first attempts failed, anyway this fact that they failed was the reason I posted my warnings. I downloaded several other decrypters and failed with each of them, too, with every ESD file.
Anyway, that is not an excuse, just an explanation. I am guilty for giving wrong information.
Now it's time to post the note I should have posted in the first place:
The tool in this tutorial and the ESD to ISO method both work with build 15002 ESD file released on Monday.
For those users receiving UUP upgrades instead of ESD, see this tutorial: UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files
I just can't get it: six ESD files, four decrypters including ours, all attempts failed. Now suddenly, getting five new ESD files, everything works.
During the discussion about ESD to ISO in the past few days, I have read some misconceptions about ESDs, crypto keys and decryption tool.
First is the Install.esd referenced in this tutorial. This ESD is not encrypted and never has been as far as I know. That is not to say that there cannot be an ESD named Install.esd that is encrypted but the one specified in this tutorial is not.
Second is the crypto key. The crypto key is usually found in the product.xml, but with Insiders builds it can be found in windlp.state.xml.
Third is the decryption tool. The decryption tool may or may not need to decrypt an ESDs. If so then the crypto key is needed, if not then it proceeds to the next step whatever that may be. In reality the decryption tool becomes an ESD to ISO convertor tool as is the case in this tutorial.
The only modification in tool was new key, rest of the batch file content remaining intact. With that edit, changing the key, the tool immediately stopped working with older builds (pre build 11002) and started to work with new ESD files.
Last edited by Kari; 1 Week Ago at 10:41.