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

"blob" used to stand for binary large objects in Database files such as Microsoft's Access MDBs - for instance, within a database container file, images, video or audio clips were not stored as individual files but as blobs, with standard methods for accessing or displaying them.

"blobs" were also the descriptive term for the humans aboard the Axiom in WALL-E (Pixar, 2008) whose prolonged weightless or Low-G state had affected bone development so that people had to be supported on mobile recliners, and had rounded body forms.

Take your pick!

I have had the missing Blob error in UUPtoISO on one machine repeatedly with x86 builds (and not another PC that handled the UUPtoISO conversion OK) going back several weeks. UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files



Whereas the original post failed both to upgrade to 15019 and to create an ISO with UUPtoISO (I eventually downloaded and upgraded from 15025 ISO), the 15042 upgrade succeeded, but the UUPtoISO again failed to complete.

The batch script is looking for the files in wrong location, all the files exist but they are not under \Windows\WinSxS\...

instead they are located here(applies for Windows Pro) and many other places:
\amd64_Microsoft-Windows-EditionPack-Professional-Package~~AMD64~~10.0.15046.0\


There seems to be some steps missing in the script, that was included in the UUP upgrade files in most upgrades and was thus automated. Can we fix this?

slicendice said:

There seems to be some steps missing in the script, that was included in the UUP upgrade files in most upgrades and was thus automated. Can we fix this?

I'm working on it but I don't feel confident.

Anyway, I believe this being a bug which will once again be fixed in the future builds. I mean, it can't be true that a build upgrade downloads over 10 GB as now with 15046 UUP upgrade, at least in my case it downloaded 2.5 GB in BT folder and 7.3 GB in SoftwareDistribution (EN-GB PRO x64).

The difference between previous UUP download and the current is that this time we downloaded .rng-files that were extracted into their respective package folders. Earlier UUP downloaded a bunch of .esd-files, which had the proper folder structure when extracted into the temp folder.

This should be an easy fix, but I am terrible at batch-programming. ;-)

Build 15025 UUP upgrade was the same. At the moment we have got 8 UUP upgrades, two of them not allowing ISO to be created for same reason for same reason.

Windows insider said:

you can after the upgrade by going through the windows.old folder and going to software distribution and download and searching it. so if you forget you can still do it

Sometimes you can, sometimes NOT. Very often these files gets deleted too after upgrade, but this is not what we are talking about right now. The problem is the structure of the files downloaded, and our batch file is not compatible (missing checks and is not as intelligent as it could be).

AAHAH, now I see the problem...I think!?

In 15042 we had a file called Microsoft-Windows-EditionPack-Professional-Package.ESD, but now we instead have a folder called Microsoft-Windows-EditionPack-Professional-Package. Both the ESD and the folder contain the same sets of files, except now we of course have 15046 specific files there.

I think we need to convert these package folders to ESD files and add them to uups_esd.txt file, so that the rest of our script can process those ESDs as usually.

I really think the best way to approach this whole thing is to rewrite the whole thing and document every step. I don't see the point in creating a ton of ESD files when we could copy the stuff straight to it's correct location and then start building the .wim

What if we process the ActionList.xml? Starting from <Media>-tag we have all the packages. What if for each Package we take the [PackagePath] and .ESD (capture) that folder contens into the [Id].esd? This way we have all the ESD-files we are used to have.

We must do it before the uups_esd.txt-file is created as all ESDs get added there and the list is processed later.

After this all should work again? Right?

slicendice said:

What if we process the ActionList.xml? Starting from <Media>-tag we have all the packages. What if for each Package we take the [PackagePath] and .ESD (capture) that folder contens into the [Id].esd? This way we have all the ESD-files we are used to have.

We must do it before the uups_esd.txt-file is created as all ESDs get added there and the list is processed later.

After this all should work again? Right?

I am not going there anymore. I have tried and tried, cancelling an important meeting and delayed other tasks today only to find a way to do this.

You may of course test various scenarios and ways to make ISO from UUP but I'm done with UUP to ISO for this build, honestly believing this is a cock up from Microsoft's side and we are back to normal in future builds.

Based on above, I refer to my earlier post:

Kari said:

   Note

Tweet

— Twitter API (@user) View on Twitter

PLEASE NOTICE:

Apparently I was wrong saying after last build upgrade (15042) that ESD to ISO method seems to be dead. It is working again, build 15046 upgrade includes a normal install.esd file if UUP has been disabled in registry settings. This time it's UUP to ISO method that does not work; build 15046 upgrade using UUP method is OK and works as it should but UUP to ISO produces an error when writing ISO image.

In case you want an ISO and upgrade is not yet downloaded on your PC, edit the registry to disable UUP as told in this post.

If the upgrade has been downloaded but you have not started the upgrade process yet (not clicked Restart now), you can remove the UUP upgrade files from your PC using Disk Clean-Up, edit registry to disable UUP, restart and let your PC download ESD upgrade instead. Instructions in this post.

In case you have upgraded already and want an ISO image, the only option is to restore previous build, edit registry, remove UUP files as told above and start from scratch letting your previous build to download ESD upgrade.

Kari