UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files  

Kari said:

Read the reply I got in Twitter:

Thanks for sharing, Kari. That guy explains a lot!

I've been scrubbing the net to understand exactly how this method works. Not much there.

Does "This has to do with migration of setup actions to online" mean the "Initializing" phase at first? If so, is this where the process is searching for the needed files for upgrading?

I did find this thread rather interesting. Your UUP to ISO tutorial is referenced there. :)

UUP - what an incredibly awfully written process!

I created a freshly formatted 50 GB partition on a hard drive, then clean installed 16215 from a DVD in 18 minutes.* I left Windows with nothing else installed and then started the update to 16226.* Just getting through until it was ready to do the first restart took 1 hour 50 min.* I could write a better update program in my sleep!*
*Obviously UUP is going back to the HDD to see what needs to be updated next at each step when it could keep a table in memory with the status of EVERY Windows file in about 600 MEG (that's 0.6 GB you know).* There are well under 150,000 total files in Windows 10 Pro, so that's 4 bytes per file in 0.6 GB.* This 1st stage of the update runs in 2.5 GB when most of us have 8 GB in 64 bit systems.* That means 5.5 GB of RAM are unused while UUP is beating the poor hard drive to death.

UUP - what an incredibly awfully written process - Microsoft Community

LOL! "While UUP is beating my poor hard drive to death".

CountMike said:

UUP is not doing any more than any other kind of update would, maybe a bit more at the beginning while it checks what to update but this time it finished in 3 minutes flat.
I followed system parameters while UUP to ISO was working and it's using resources wisely. It's nicely multi-threaded using all cores and threads equally, memory in moderation and disk is sufficiently used to speed up process but leave all resources free enough to do other work.

Thanks for that, Count. I meant to, but was tired and forgot to watch during yesterdays update. Even forgot to grab the ESD file for the ISO. Oh well. There's another build eventually. :)

f14tomcat said:

Couldn't get that to do anything, but alt+49 = 1. Right numeric keypad only. Complete list here:


Special Characters Alt Keyboard Sequences

Worked here, but process Errors and likely the Build 16199 problem. Tried to download fix exe, but Chrome blocks. Will try other possibilities.

@tracit99 I brought this over to this thread so to be more on topic.

Firstly, thank you for your gracious, tactful way of correcting me if I’m wrong. An attitude not shown by a few members here recently, sorry to say.

tracit99 said:

@HippsieGypsie
You are aware that now there is no single ESD from WU that can be used to create an ISO. That was the old way. Now it is all about UUP files and there are many (some of which are .esd files). I just wanted to clarify this especially for new users.

I’m quoting from Kari’s tutorial here. Step 2.2 to be exact.

2.2) In File Explorer, search for ext:esd to find all ESD files. Only one of the subfolders of C:\Windows\SoftwareDistribution\Download contains ESD files (extension .esd). So called express UUP upgrade has only one ESD file, canonical UUP upgrades can have 10+ ESD files. Regardless of how many ESD files your search finds, they are all stored in same subfolder, the one containing necessary files to make an ISO image

Usually upgrades are differential (express) only containing one ESD file as in this example. Search for ESD files finds one file in folder staring with 5721f7. Right click it and select Open file location to open folder we need:

I am familiar with the older ESD to ISO method/process. I realize there are many files involved with the UUP download method of which downloads only those files needed to update, then creates a needed .esd files of all the files needed.

I somewhat understand UUP to ISO process, save how the executable program works other than gathering up the needed files for the ISO. Correct me if I’m wrong, but according to Kari’s tutorial here in 2.2 step we are to search for one .esd file namely the one beginning with digits 5721f7, which if I understand correctly is a compressed .esd file containing all the files needed for the ISO.

Some have reported (of which Kari cautioned) that they were able to grab the .esd file before installation was complete. I thought maybe by chance that would work for the new member. At that point I overlooked that he had 2 other machines already upgraded to grab the files, of which I wouldn’t know how to anyway since I’ve never performed that .old folder nab for UUP to ISO. If you could, I’d appreciate if you would point me in the right direction to learn that method.

MS has not totally abandoned the old ESD method (the ESD type that can be converted into an ISO). Most notably this type of ESD is currently used by the Media Creation Tool.

Again, yes I know, but only for those ISOs released, which for Insiders is a build for Bug Bash. Made many of them.

Hi,

Had a reply ready for you but IE crashed once again.
Basically, and with respect, you're misinformed on a number of points.
The important one is to use the files in the folder containing the .esd right before Windows invites you to restart to finish the update.
If not the these files can be found under Windows.old. Either copy or copy shortcuts to the UUP subfolder of UuptoIso and proceed creating the ISO.

The .esd created by MCT is of a different type and won't work with UuptoIso at all.

Cheers,