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

@Kari,

A suggestion at step 3.7, page #1:

3.7) Browse to UUPtoISO\UUPs folder, select all files you pasted there in step 2.5 and delete them, leaving the folder empty and ready for the next build upgrade

Instead of deleting the 229 (?) files, zip them to one and store for safe keeping, at least temporarily. Never can be sure of the finished product (ISO) until it's been used/tested. Any number of reasons for it to be unusable. Not suggesting this process is faulty, I've used it and it works perfectly. Even upgraded a VM with the ISO. And......there may be some who might be in need of the files. Corrupt copy, forgot to copy, etc. Handy to have the zip file available to "share". Funny how the zipped file size is suspiciously similar to the size of an install.esd. I used 7-Zip, but any would do.

Just a suggestion. TC

Stats:

slicendice said:

Did ISO from UUPs on VM. No problems nor error messages. Went smooth as a babys bum.

It might be I'm the only one getting those error messages and that I posted a completely unnecessary warning.

Trying to find the reason for those messages I noticed that I get the same warning on same VM every time I run Command Prompt:

This strongly indicates the culprit is my system, not the UUPtoISO tool. VM is still running 15019 but 15042 upgrade is already downloaded and prepared. I think that I skip the upgrade and clean install 15042 :)

f14tomcat said:

Just a suggestion.

... but a good suggestion. Thanks for the idea. Will edit the tut when I have some more time in hand.

Kari

Streamlining UUPtoISO for insiders:

This may be irrelevant if UUP methodology becomes truly Delta, and does not continue to download a full quota of ESDs & CABs capable of recreating a working Windows 10 setup ISO, but currently we know (please correct me if I am wrong):

where the downloaded folder will be located (Windows\SoftwareDistribution\download\ )

approximately how large the folder will be (between 1.8 GB and 2.8GB)

what key files are universally present in all versions and any language variation

approximately how many files and folders will be present

and therefore we can deduce what that folder's name is.

We also can find out that $Windows.~BT must be of a suitably large size to be far enough along in the download/install process to ensure that all the cohort of files in the downloaded folder is complete for the purposes of UUPtoISO to successfully build an ISO, all other circumstances being normal.

At his point the files in the folder may be copied to UUPtoISO\UUPs and when complete, the copied files may be used to create an ISO without user intervention.

So, do you think it would be possible to automate UUPtoISO, Kari?

Fafhrd said:

So, do you think it would be possible to automate UUPtoISO, Kari?

I've been thinking this a lot.

Some PowerShell:

We know that the folder under C:\Windows\SoftwareDistribution\Download containing the 10+ ESD files is the correct folder, the one which has to be copied to UUPtoISO\UUPs. Let's create a variable $FileType to find ESD files:

Code:

$FileType = *.esd"

... and do a search:

Code:

Get-ChildItem C:\Windows\SoftwareDistribution\Download\$FileType -recurse | Select Directory

The search found the correct folder as we can see in listing which shows the folder for each ESD file found. In our case it's good news to see that all ESD files really are in same folder, we know now for sure this is the correct folder.

That's it, we are halfway there :)

Kari

Kari said:

It might be I'm the only one getting those error messages and that I posted a completely unnecessary warning.

Trying to find the reason for those messages I noticed that I get the same warning on same VM every time I run Command Prompt:

This strongly indicates the culprit is my system, not the UUPtoISO tool. VM is still running 15019 but 15042 upgrade is already downloaded and prepared. I think that I skip the upgrade and clean install 15042 :)




... but a good suggestion. Thanks for the idea. Will edit the tut when I have some more time in hand.

Kari

Just a outside thought and probably not the answer in your case but I once got a similar message and it turned out culprit was because I had previously mounted a Macrium Reflect Image as a drive but forgot to properly unmount it but later deleted the image so each time I booted it could not find the "virtual drive".

May not be Macrium but any previously mounted virtual drive perhaps?

cereberus said:

May not be Macrium but any previously mounted virtual drive perhaps?

A good idea but no, I have nothing mounted and Command Prompt is set to start in %userprofile%, elevated one in C:\Windows\System32. It should not even look for any drives.

Kari said:

A good idea but no, I have nothing mounted and Command Prompt is set to start in %userprofile%, elevated one in C:\Windows\System32. It should not even look for any drives.

Ah well, nonetheless I am a fan of far out thinking when troubleshooting as it often triggers other thoughts

JGToy said:

First hello to all, I am new here!

I tried to create an ISO from UUP files but I am receiving an error.

Your screenshots clearly show that you have not a standard UUP upgrade files. This tutorial only applies to and the tool in it only works with standard Windows 10 build upgrade files downloaded using Windows Update in a valid Windows 10 Insider installation.

Kari