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

I rename the esd to a normal name and this time the process went fine. This is the result:



edit: just installed, works great :)

Well crap! Anyone know what the problem is here?

Attachment 22787

simrick said:

Well crap! Anyone know what the problem is here?

Yes. ESD is damaged, faulty. Got that with my first ESD, had to redownload the ESD. When I then compared the first faulty ESD and the latter working one, there were exactly one KB too much on the faulty one. The faulty GB-EN x64 ESD was 2,766,070 KB, the working one 2,766,069.

In my case this was because I monitored the C: drive to get the ESD as soon as WU has unpacked it, then went to get coffee and came back a bit too late, Windows was already at 50% of "preparing the update"; if you want to grab the ESD before Windows starts the upgrade process you have to constantly monitor the C: drive and as soon as WU has unpacked the upgrade files, get the ESD and drag it to desktop. Starting the copy process too late ruins the ESD.

See this post: ESD to ISO - Create Bootable ISO from Windows 10 ESD File - Page 18 - Windows 10 Forums

Kari said:

Yes. ESD is damaged, faulty. Got that with my first ESD, had to redownload the ESD. When I then compared the first faulty ESD and the latter working one, there were exactly one KB too much on the faulty one. The faulty GB-EN x64 ESD was 2,766,070 KB, the working one 2,766,069.

In my case this was because I monitored the C: drive to get the ESD as soon as WU has unpacked it, then went to get coffee and came back a bit too late, Windows was already at 50% of "preparing the update"; if you want to grab the ESD before Windows starts the upgrade process you have to constantly monitor the C: drive and as soon as WU has unpacked the upgrade files, get the ESD and drag it to desktop.

I did that - I grabbed it as soon as it was there. Then the upgrade failed with 0x8024201c. Then it started again, and I grabbed it again - same size exactly...... 2,149,487

EDIT: GREMLINS it must be GREMLINS - the 2nd ESD file, which is EXACTLY the same size, is working now.........we'll see if it finishes!

David, to get the ESD undamaged if grabbed before the update process starts is a form of art :). Patience!

jimbo45 said:

Hi there
@ Kari

The ESD file I can find doesn't seem to be the right one -- mine has a date of 02/05 which appears counter intuitive (it seems rather like the date when I installed build 10130).

I've simply on a VM just done an UPDATE to build 10158 so I'll try on another machine to create an ISO.

I assume you need to grab the esd BEFORE choosing install but AFTER the download has completed.

Cheers
jimbo

Yes. Monitor the C: drive when the download reaches 100%. WU will show next "Preparing to install updates 0%", at which point the hidden system folder C:\$Windows.~BT\Sources ​will be created and Windows starts unpacking the files. Refresh, refresh, refresh, until the install.wim appears and grab it quickly, drag to desktop.

Copying the ESD to desktop must be done BEFORE system again removes it from C:\$Windows.~BT\Sources​, somewhere after the 60% mark in "Preparing to install updates".

Maybe I just got lucky, or because I have Updates set to Notify for Restart, I grab the install.esd at the restart prompt. Even this morning, day after upgrade and several reboots, install.esd is still in $windows~~~BT.