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

tracit99 · 08 Jul 2017

@HippsieGypsie

I like most users of Windows TenForums am here to learn and when possible to pass along some tidbit I have learned. I see now that you do understand the UUP update process and were not saying what I thought when I first read your posts.

I thought you were saying that there is one single ESD file that UUP would use the make an ISO and I think we both agree that is not how UUP to ISO works. I see now you were using the ESD reference as a way to find the UUP files. My bad. Sometime I read too much between the lines.

Tony K · 08 Jul 2017

tracit99 said:

@HippsieGypsie

I like most users of Windows TenForums am here to learn and when possible to pass along some tidbit I have learned. I see now that you do understand the UUP update process and were not saying what I thought when I first read your posts.

I thought you were saying that there is one single ESD file that UUP would use the make an ISO and I think we both agree that is not how UUP to ISO works. I see now you were using the ESD reference as a way to find the UUP files. My bad. Sometime I read too much between the lines.

That's quite alright, tracit99. No biggie. No one is perfect and we all overlook or misunderstand posts, especially with tech. Heck, I overlooked the new member's post title to know he had 2 systems upgraded already to nab the needed files. Anywho, he seems to be on his way and that's all that matters. :)

If you or anyone could direct me as to which file or files to copy out of the .old folder to use the UUP to ISO method I'd appreciate it, for in Kari's tutorial it calls for finding the esd file with the with digits 5721f7 of which I can never find in the .old folder.

This is what I have or am I using the wrong input (.esd) for the query? I tried *.esd to no avail. What is encompassed in red is my 16237 partition. The query is of my .old folder.

Attachment 143094

tracit99 · 08 Jul 2017

Thanks, and sorry to say I do not have an Windows.old folder at the moment.

Tony K · 08 Jul 2017

tracit99 said:

Thanks, and sorry to say I do not have an Windows.old folder at the moment.

Ok, thanks anyway. :)

Kari · 08 Jul 2017

HippsieGypsie said:

If you or anyone could direct me as to which file or files to copy out of the .old folder to use the UUP to ISO method I'd appreciate it, for in Kari's tutorial it calls for finding the esd file with the with digits 5721f7 of which I can never find in the .old folder.

My mistake, I might have explained that badly in tutorial. Folder with name starting 5721f7 was an example I used to explain screenshot in step 2.2, as was a526e in same step for next screenshot. They were the UUP upgrade folders with build upgrades when those screenshots were made.

Short: the folder name is different in each build, and for 32 and 64 bit versions. Build 16237 upgrade files in 64 bit Windows 10 are found before the upgrade itself is started in following folder:

C:\Windows\SoftwareDistribution\Download\4121528c6aaf458d2f8e172253135233

... and after the upgrade in following folder:

C:\Windows.old\Windows\SoftwareDistribution\Download\4121528c6aaf458d2f8e172253135233

For 32 bit Windows 10 build 16237 upgrade the UUP folder before the upgrade itself is started:

C:\Windows\SoftwareDistribution\Download\5c14da9f5237df057a2c849090b80b8d

... and after the upgrade the following folder:

C:\Windows.old\Windows\SoftwareDistribution\Download\5c14da9f5237df057a2c849090b80b8d

When next build will be released, we will again have new UUP upgrade folder both in 64 and 32 bit Windows. That's why you need to search / find the correct folder in every build upgrade.

Logically thinking, if the folder name would be the same in each build there would be no need to search the folder containing one (differential upgrades) or more (canonical upgrades) ESD files to be used in ISO making process.

Kari

Tony K · 08 Jul 2017

Kari said:

My mistake, I might have explained that badly in tutorial. Folder with name starting 5721f7 was an example I used to explain screenshot in step 2.2, as was a526e in same step for next screenshot. They were the UUP upgrade folders with build upgrades when those screenshots were made.

Ok, I see. One whipping for you with a wet noodle.

When next build will be released, we will again have new UUP upgrade folder both in 64 and 32 bit Windows. That's why you need to search / find the correct folder in every build upgrade.

Logically thinking, if the folder name would be the same in each build there would be no need to search the folder containing one (differential upgrades) or more (canonical upgrades) ESD files to be used in ISO making process.

Kari

Will these folders then be in this usual place you just described? I'm understanding with a different number of course.

Here's mine. So just copy this address into the UUP to ISO program.

Attachment 143109

Kari · 08 Jul 2017

HippsieGypsie said:

Will these folders then be in this usual place you just described? I'm understanding with a different number of course.

Yes. The correct folder to be used is always a subfolder in following location:

C:\Windows\SoftwareDistribution\Download\

... or after you have performed upgrade but not removed Windows.old:

C:\Windows.old\Windows\SoftwareDistribution\Download\

The UUP folder name is always a 32 bit hexadecimal string.

HippsieGypsie said:

Here's mine. So just copy this address into the UUP to ISO program.

Yes.

Kari

Tony K · 08 Jul 2017

Thank you, @Kari. Much obliged. :)

Kari · 08 Jul 2017

You are most welcome :)

Fafhrd · 09 Jul 2017

Just for Information Kari, Chrome is still showing UUPtoISOsetup.exe downloads as being a dangerous file and blocks it.
I know that some time ago you applied to have the file whitelisted.
I just downloaded UUPtoISO using Chrome Canary, and the warning is present there also:

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

The file can still be downloaded by opening downloads:

and selecting keep dangerous file: