The downloaded file was a disk image and in the 'sources' folder was a file named 'install.esd'
When I attempted to use the ESD to ISO tool I got the error mentioned in my previous post.
The "disk image" is the ISO....The downloaded file was a disk image and in the 'sources' folder was a file named 'install.esd'
inside that Image is an install.esd - which is the wrong esd for this tool...
download your media from here > https://www.microsoft.com/en-us/soft...load/techbench
it contains an install.wim instead of install.esd..
Rather than waste any more time trying to fix it I'm going to have to reinstall (again).
I'm probably going to get shot down in flames here but Windows 10 is still too flaky when it's being pushed hard (3D animation etc) as it seems to fall over all too regularly on our 'work' machines but is fine on the (similar spec) 'home' machines.
What do I do if the computer restarts and updates Windows 10 on its own? The Install.esd of the new build is no longer in $WINDOWS.~BT\ folder and instead is found the Install.wim of the old build.
IF roll back Windows build in Advanced Options, when it is finished the resulting $WINDOWS.~BT\ folder equals exactly a Windows 10 install image of the latest release.
all somebody has to do is run a command when the new build is downloading to snag the official esd download links.. Then run the newest esd decrypter wimlib v18 - it now support newest build decryption...
Code:if exist "C:\$Windows.~WS\Sources\products.xml" ( findstr /c:"<FilePath>" "C:\$Windows.~WS\Sources\products.xml" >"%userprofile%\desktop\Windows 10 ESD Download Links.txt"
The tool and the method in this tutorial work without issues with the latest Insider Build 14366 ESD file, released yesterday.WarningThe tool has been updated 10 days ago, on June 5th. In case your tool is older please delete it from your PC simply by deleting the folder it was extracted to and download the updated tool. Download link in the first post (step 1.3).
Although the old version will create a functioning ISO image which will allow you to install Windows 10, there's a bug in ISO creation process that leaves out the repair console, meaning you can not boot to repair options if / when necessary. This bug has been fixed in updated tool.
More information about the bug in previous version of the tool can be read in this post.
A reminder, do this to copy the upgrade ESD file to a safe please:
1.) If Windows Update shows Install now button after downloading the build upgrade, click / tap it to extract upgrade files to $WINDOWS.~BT folder (install.esd file is not ready yet):
2.) When Windows Update shows you the upgrade is ready to be started, Restart now button is shown. Do not click / tap it yet:
3.) In File Explorer, open the C: drive. If the $WINDOWS.~BT folder is not shown, select View > Hidden items to show it:
4.) Open the $WINDOWS.~BT folder, open subfolder Sources, copy install.esd file and paste it anywhere outside the $WINDOWS.~BT and other Windows system folders:
That's it. You can now start the upgrade restarting PC, the install.esd is saved and you can use it after the upgrade to create an ISO image.
Last edited by Kari; 15 Jun 2016 at 03:55. Reason: Added reminder with screenshots
NoteThe tool has been updated today, only change being I have changed the title ESD to ISO decpryption to ESDtoISO because the word Decryption in title caused some people to complain about it (don't ask me why!).
If you have downloaded the tool after the June 5th and do not mind a word apparently not belonging to title being there, you don't need to redownload as the tool itself is the same.
On another note, something very important I want to address:
I was asked if I think I have done injustice to original developers of the ESD to ISO conversion script, taking the credits. Answer to that question is and should have been very clear all the time.
Let's start with a quote from beginning of this tutorial:
InformationThanks to our member topgundcp for the idea. This tutorial will use the decrypt script mentioned in his post, according to new information I have found the original authors are users abbodi1406, qad and synchronicityI from the MDL site, complete credits in the Read Me file included in the tool downloadable packet. I have simply edited the script a bit and finally made these step by step instructions.
That notice has been at the very beginning of this tutorial since the day it was published.
Furthermore, the ReadMe file included in this tool begins with what's shown in below screenshot, ReadMe file being unedited and not modified in any way since the tool and this tutorial were published:
I hope the above answers all possible questions about where the credits belong. If some of you geeks still feel I have taken credits from someone else's work, I can't help it; in my opinion I have done everything in my power to give credit where credit belongs.
Last edited by Kari; 15 Jun 2016 at 08:13. Reason: Some typos fixed