Windows 10: ESD to ISO - Create Bootable ISO from Windows 10 ESD File
Finnish but not finished
The new RSA keys are not the only change I made to the script when editing it. But OK, let's do it as you seem to suggest: next time the new keys are needed I just post here telling about it and ask the newbies to find the correct keys and fix the script by themselves.
Let me just check that I get you correctly: for some reason you are not satisfied that every newbie can convert the ESD to ISO following instructions in this tutorial? Too easy? Should be more complicated?
This discussion has been quite helpful to me, as I now understand (I think) what I was doing wrong.
It seems I was grabbing the ESD too early, while it was still encrypted? Therefore the encryption keys in the script weren't working as they weren't the latest ones?
If I'd got the ESD later in the process, or if it was still being saved in that RecoveryImage folder, then the original encrypted ESD would have been replaced by a decrypted version, which can be read with DISM etc., and the older keys wouldn't have mattered.
Is that what was happening?
Finnish but not finished
David, that's about correct. The included RSA encryption keys could not decrypt the ESD file if it was in encrypted state.
That's also the reason I decided to include a new script, instead of replacing the old one. I want to keep this so simple every newbie who can read can make his / her own ISO image.
Both scripts can decrypt both encrypted and unencrypted ESD files.
Okay I need more coffee......LOL
I am a newbie, and I grabbed and converted the 10158 ESD to ISO without any difficulty by following your instructions exactly. Thanks buddy, don't change anything!
Finnish but not finished
Let's try to clarify this. If you are simply looking instructions to see how to make an ISO, do not read further, simply jump to the first page, download the tool and follow the simple instructions.
For those reading further, here's how it works when told quite simplified.
Microsoft uses the so called RSA encryption for it's Electronic Software Distribution (ESD) files. In case of Windows 10 build upgrades, Windows Update downloads the package, unpacks it and finally decrypts the files in it. Not the other way around even if it would seem more logical, the install.esd just unpacked is still encrypted. The ESD file is basically an archive containing the boot.wim, install.wim and other files needed for Windows upgrade and installation., all other files in the package needed for the unpacking and decryption.
Windows 10 build upgrade files are always encrypted when downloaded to your computer through Windows Update.
When you see the download in Settings > Update & Security > Windows Update reaching the full 100%, the next step is to unpack the archive. When this starts you will see the text Preparing to install updates. If you now monitor the C: drive you will see system creating the working folder C:\$Windows.~BT\ and starting to unpack the files from the archive. The file we are interested in, the install.esd file will be unpacked to the subfolder Sources (C:\$Windows.~BT\Sources).
Follow the progress in Settings > Update & Security > Windows Update; when Preparing to install updates reaches about 50%, the unpacking has been done and Windows starts the final phase before the upgrade itself starts and decrypts the files.
Those who just want to upgrade need to do nothing. Just relax and let the system download, unpack and decrypt the files and Windows will upgrade itself. Those like me who do not want to wait an extra hour or so for the upgrade to finish but want the ISO instead as soon as possible have a little bit stress now: the ESD needs to be grabbed and taken to a safe place as soon as it has been unpacked but still encrypted because if we wait until the decryption is done before we start the copy process, the upgrade process will start before the copy process has finished and the file we are currently copying disappears.
I repeat that the above is a "verbally illustrated" and simplified description of the real process but I hope you got it .
Okay so, I am back on my lappy with 10159 installed now, and the install.esd is still in the Sources folder, and it's still the same size as when I grabbed it, and (as someone mentioned somewhere else that the 10159 is slightly smaller than 10158), mine is larger than 10158 - could be because mine is 32 bit? Anyways, if I look in C:\RecoveryImage, I find the install.esd from April sitting there!
Finnish but not finished
This note from an earlier post in this thread:
The Recoveryimage folder is used to revert the upgrade, go back to the build from which you upgraded. That's why it contains the old ESD file.
MS encrypted esd downloading version 10159
MS encrypted esd = you must rename from .default_ext to .esd and then run through the decryption process of this program
note: this is an encrypted file and the programs crypto keys will decrypt this file
pictured below, the decrypted install.esd is usable at about 25% - as you can see I'm already creating the ISO at 29%
when the file fist appears it will show the size - but if you snag it to fast - the file may not have been fully written and the program will fail with > "ERROR: Specified file is not found or damaged."
better off waiting until (the preparing to install updates - progress slows to a crawl)
(this install.esd is NOT encrypted, nor does it require decryption - it is just running through the index export process within this program)
Note: usually the setup media contains a single index install.esd - so far with windows 10 preview it has been the full 4 index install.esd (which is actually used to create the setup media)
once the 4 indexes are exported into a folder - the ISO creation process starts within the program
Or you can just wait and copy the install.esd to another folder just before to requested reboot
Last edited by Kyhi; 2015-07-01 at 15:44.
Thanks for posting the revised tool. I can now decrypt the 10159 ESDs I grabbed yesterday (and I guess 10158 too, although I'm not sure I'll bother), and it seems to work.
And the x64 en-gb ESD has downloaded tonight too - 24 hours ago, 2 separate machines were both refusing to admit the 64 bit version existed.
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:\
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...
Here's an alternative in addition to Kari's Tutorial: ESD to ISO - Create Bootable ISO from Windows 10 ESD File - Windows 10 Forums
NOTE: It is better to create an ISO contaning install.wim so if you...
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...
Rufus - Create bootable USB drives the easy way