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

OK, that might explain it. Is there someone that could direct me to a untampered Core EN-US x64 14361 ESD or directly ISO ?

Kari said:

As always, here at Ten Forums we only deal with official releases of Windows 10, and valid / legal installers, software and Windows builds. Your issue is quite clear:



This tutorial is valid and factual, the method and and the tool in it both work without an issue when you download the Windows Upgrade (ESD file) through Windows Update on a computer which is properly activated and entitled to be upgraded.

When you decide to get your Windows 10 Insider Upgrade from a not valid / not official source, there's nothing I can do or want to do to help you.

Kari

I totally understand.
Please just understand my situation : I've a Surface 3 with a French Windows 10 (legally). I'm an Insider from day-1. The last build is NOT released to French (as there is a bug in the translation - I don't care about it) ==> I can't get the latest ESD from WU. That's why I'm asking if someone could direct me to this ESD. I don't ask illegal thing as everything on my Surface is legit :) I'm just blocked out of the last Insider release as I'm using a French OS. Directing me to this ESD/ISO could just save me a large amount of time instead of installing a VM from the last slow-ring release EN-US Core build from the official ISO, then upgrading it to 14361, then getting from my VM the legit ESD and THEN, creating my own ISO :)

I hope you'll understand my situation but I'll understand if you don't want to help

Thanks !

Kari said:

To be honest, I do not understand you. The below post might go too deep in to reasons, I apologize if you feel it's off topic.

Microsoft does not make these decisions lightly; when they decided to release build 14361 in all other languages except French, they had a reason for that as was clearly told.

It means that every build 14361 French ESD or ISO file is invalid, not official. To be totally honest with you, I don't even dream to start searching solutions for issues with unofficial, cracked releases.

Some of it comes from this (quoting one of my tweets):

Tweet

— Twitter API (@user) View on Twitter

I have set that tweet as a favorite, it will be shown to everyone who happens to find my Twitter page. I am proud that I don't have nor do I use any unlicensed or pirated software. I am proud that all my operating systems on my machines (real and virtual) are valid, either licensed or trial versions.

I am really sorry, wanting to explain this to you: Even if I knew how to help you, I would not do it because your ESD is not valid, official release from Microsoft.

Please feel free to join the ever growing number of members adding me to their ignore lists, feel free to call me an old fart with no connection with reality, whatever. This is me and how I work.

Kari

Don't be sorry, I totally understand
What you didn't is that I don't want a fr-FR ESD or ISO, but the en-US that was legally released yesterday by MS ^^
I know there's no fr-FR ESD/ISO, but, as an Insider, and using actively the buggy 14352 build, I'd appreciate to use the last ENGLISH one (instead of French) without the hassle to create a VM, install the slow-ring ISO on it, then upgrading it, then getting the ESD, then making the ISO to install it on my Surface 3 :)

I really don't think it's piracy as there's nothing hacked/pirated :)

Again, sorry I confused you taking about my french version : all I'm searching is a valid and legal ESD and/or ISO, untampered, CORE x64 en-US version of the 14361 build :) If even that is not possible, that's OK

tracit99 said:

The reason lpaso is having a problem is that he is trying to using Kari's tool to create an ISO from an ESD that is encrypted. The reason Kari's tools works on the Install.esd file found in "Sources" folder is because it is not encrypted. When you download a new build from Microsoft's Windows Update the encrypted ESD is stored in Windows Software Distribution folder and it is not called Install.esd at this point. At some point this encrypted file is decrypted using the Crypto key from Microsoft and the resulting file Install.esd is placed in the Sources folder. The original file in the Software Distribution Folder is deleted. (All this has nothing to do with Kari's tool). Kari's tool when used on an Install.esd file literally becomes an ESD to ISO convertor tool because the Install.esd file has already been decrypted by Windows. If one is able to capture the encrypted file from the Software Distribution folder or from a Microsoft server then the tool has the capacity to decrypt the file provided the Crypto key for that specific ESD file is known. This is why the tool contains various Crypto keys. Once decrypted the tool moves on to the ESD to ISO conversion. Lapso's problem is that he has an encrypted 14361 ESD file for which no one has the Crypto key. Apparently MS has changed some things and the old way of getting the Crypto key is not working. Of course none of this prevents Kari's tool from working on the Install.esd file.

Thanks for resuming the situation

Hi, I've just tried to follow these instructions, when I run ESD to ISO I get a message that this is not an original Microsoft ESD file - it certainly is, I've downloaded it from Microsoft this afternoon :)

Any thoughts?