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

I am studying the UUPtoESD.cmd script.

Why are we doing this at line 177?:

Code:

"%wimlib%" update ISOFOLDER\sources\install.wim 1 --command="add 'ISOFOLDER\sources\boot.wim' '\windows\system32\recovery\winre.wim'" 1>nul 2>nul

when we already have a fresh copy of WinRe in the .esd file as sub-image 2? Can't we just use index 2 instead of copying files from the active system?

Code:

<WIM>
  <TOTALBYTES>467237366</TOTALBYTES>
  <IMAGE INDEX="1">
    <DIRCOUNT>98</DIRCOUNT>
    <FILECOUNT>1705</FILECOUNT>
    <TOTALBYTES>262771049</TOTALBYTES>
    <HARDLINKBYTES>0</HARDLINKBYTES>
    <CREATIONTIME>
      <HIGHPART>0x01D28FEA</HIGHPART>
      <LOWPART>0x948DB57E</LOWPART>
    </CREATIONTIME>
    <LASTMODIFICATIONTIME>
      <HIGHPART>0x01D28FEA</HIGHPART>
      <LOWPART>0x948DB57E</LOWPART>
    </LASTMODIFICATIONTIME>
    <WIMBOOT>0</WIMBOOT>
    <NAME>Windows Setup Media</NAME>
    <DESCRIPTION>Windows Setup Media</DESCRIPTION>
  </IMAGE>
  <IMAGE INDEX="2">
    <DIRCOUNT>3477</DIRCOUNT>
    <FILECOUNT>16624</FILECOUNT>
    <TOTALBYTES>1972713018</TOTALBYTES>
    <HARDLINKBYTES>865925786</HARDLINKBYTES>
    <CREATIONTIME>
      <HIGHPART>0x01D28FB8</HIGHPART>
      <LOWPART>0x165FC507</LOWPART>
    </CREATIONTIME>
    <LASTMODIFICATIONTIME>
      <HIGHPART>0x01D28FEB</HIGHPART>
      <LOWPART>0x02744090</LOWPART>
    </LASTMODIFICATIONTIME>
    <WIMBOOT>0</WIMBOOT>
    <WINDOWS>
      <ARCH>9</ARCH>
      <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
      <EDITIONID>WindowsPE</EDITIONID>
      <INSTALLATIONTYPE>WindowsPE</INSTALLATIONTYPE>
      <PRODUCTTYPE>WinNT</PRODUCTTYPE>
      <PRODUCTSUITE></PRODUCTSUITE>
      <LANGUAGES>
        <LANGUAGE>en-US</LANGUAGE>
        <DEFAULT>en-US</DEFAULT>
      </LANGUAGES>
      <VERSION>
        <MAJOR>10</MAJOR>
        <MINOR>0</MINOR>
        <BUILD>15046</BUILD>
        <SPBUILD>0</SPBUILD>
        <SPLEVEL>0</SPLEVEL>
      </VERSION>
      <SYSTEMROOT>WINDOWS</SYSTEMROOT>
    </WINDOWS>
    <NAME>Microsoft Windows Recovery Environment (x64)</NAME>
    <DESCRIPTION>Microsoft Windows Recovery Environment (x64)</DESCRIPTION>
  </IMAGE>
  <IMAGE INDEX="3">
    <DIRCOUNT>19635</DIRCOUNT>
    <FILECOUNT>101821</FILECOUNT>
    <TOTALBYTES>15405344842</TOTALBYTES>
    <HARDLINKBYTES>7162163115</HARDLINKBYTES>
    <CREATIONTIME>
      <HIGHPART>0x01D28FE8</HIGHPART>
      <LOWPART>0x4298CB2A</LOWPART>
    </CREATIONTIME>
    <LASTMODIFICATIONTIME>
      <HIGHPART>0x01D28FEB</HIGHPART>
      <LOWPART>0x562305A8</LOWPART>
    </LASTMODIFICATIONTIME>
    <WIMBOOT>0</WIMBOOT>
    <WINDOWS>
      <ARCH>9</ARCH>
      <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
      <EDITIONID>Professional</EDITIONID>
      <INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
      <SERVICINGDATA>
        <GDRDUREVISION>0</GDRDUREVISION>
        <PKEYCONFIGVERSION>10.0.15046.0;2016-01-01T00:00:00Z</PKEYCONFIGVERSION>
      </SERVICINGDATA>
      <PRODUCTTYPE>WinNT</PRODUCTTYPE>
      <PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
      <LANGUAGES>
        <LANGUAGE>en-US</LANGUAGE>
        <DEFAULT>en-US</DEFAULT>
      </LANGUAGES>
      <VERSION>
        <MAJOR>10</MAJOR>
        <MINOR>0</MINOR>
        <BUILD>15046</BUILD>
        <SPBUILD>0</SPBUILD>
        <SPLEVEL>0</SPLEVEL>
      </VERSION>
      <SYSTEMROOT>WINDOWS</SYSTEMROOT>
    </WINDOWS>
    <NAME>Windows 10 Pro Insider Preview</NAME>
    <DESCRIPTION>Windows 10 Pro Insider Preview</DESCRIPTION>
    <FLAGS>Professional</FLAGS>
    <DISPLAYNAME>Windows 10 Pro Insider Preview</DISPLAYNAME>
    <DISPLAYDESCRIPTION>Windows 10 Pro Insider Preview</DISPLAYDESCRIPTION>
  </IMAGE>
</WIM>

Just a thought ... :)


EDIT: Now I see I misinterpreted the command. Therefore this post is irrelevant.

slicendice said:

EDIT: Now I see I misinterpreted the command. Therefore this post is irrelevant.

I was trying to figure out what you meant. Thanks for above quoted edit, without it I would still be thinking what am I missing :)

DragonFireDon22 said:

So the DISM error is something that is normal, due to Insider Preview known issues?

Yes.

BTW geeks, posted this in another tutorial thread just now:

Kari said:

The tutorial has been mostly rewritten today to be more up to date with latest changes in Windows 10. Some additional steps required earlier have been removed and instructions somewhat simplified.

An example: Making ISO as told in Part One no longer requires Windows being reset which makes the whole process a lot faster and easier.

To remind you about various options, here's a quote from beginning of tutorial:

   Information

The ISO image made as per instructions in this tutorial will be based on an existing Windows 10 installation. Tutorial shows you three alternative methods to create an ISO image, depending on your needs:

• Part One: Standard Windows 10 ISO install media
  
  • An "Out of the box" ISO, as any standard Windows 10 ISO image you can download from Microsoft. Alternative for ESD to ISO and UUP to ISO methods
  • This ISO will be generalized meaning it is hardware independent and can be used to install Windows on any computer capable of running Windows 10, regardless if the machine is a legacy BIOS machine with MBR partitioning, or a UEFI machine with GPT partitioning
  
  
• Part Two: Custom ISO with pre-installed software & pre-set user accounts
  
  • This option creates a Windows 10 ISO which already contains your preferred user accounts with all their settings, customisations and personalisations, preferred pre-installed software and so on
  • Using this ISO to install Windows is much faster than installing with standard ISO, at the same time making installing your standard software unnecessary as it's already pre-installed
  • Clean install will skip OOBE (Windows Setup) because user accounts and settings already exist
  • As the ISO is not generalized and it contains all existing user accounts and data it should only be used to install Windows on your home computers
  
  
• Part Three: Custom ISO with pre-installed software, no user accounts
  
  • As in Part Two but a generalized ISO image without any pre-set user accounts, with pre-installed software, desktop, File Explorer and Start customisations
  • All customisations and personalisations will automatically be applied to all new user accounts
  • Clean install will perform a normal OOBE, asking for regional settings, initial user and so on
  • This ISO will be generalized meaning it is hardware independent and can be used to install Windows on any computer capable of running Windows 10, regardless if the machine is a legacy BIOS machine with MBR partitioning, or a UEFI machine with GPT partitioning

Select Part One, Two or Three to prepare Windows for image capture according to your needs, continue from Part Four to capture Windows install image and create the ISO image.

ISO images will be bootable on both BIOS / MBR and UEFI / GPT systems.

Tutorial in question shows alternative methods to make an ISO: Windows 10 ISO image - Create from Existing Installation

Kari

Kari said:

Tutorial in question shows alternative methods to make an ISO: Windows 10 ISO image - Create from Existing Installation

Kari

Thanks for reminding about this tutorial. It's really useful.

   Note

Notice please:

This method does not work with build 15055, you can't make ISO from Build 15055 UUP files.

DonCuthbert said:

I see that one of the original authors of the script, abbodi1406, has made some changes to handle UUP conversions for when the UUP process runs as it did with build 15046 and only downloads a single smaller ESD file with multiple expanded folders being created. This is from MDL Forums, so would not include any of the edits that Kari has contributed for TenForums.
Windows 10 ESDs Repository - Page 130

The above revised utility from abbodi1406 also works with build 15055 UUP files. Tested today with converting both Windows 10 Home and Pro. So if anyone is desperate to create a 15055 ISO from UUP files, there is a way that works.

---

To use the current TenForums utility from this thread's Tutorial, you have to first create ESD files from all of the subfolders found in the SoftwareDistribution UUP folder (excluding the Metadata folder). Then you can copy all of the ESD, CAB and XML files for conversion with the utility.

The below DISM command line (only if run from within a .CMD file) will convert the UUP folders to ESD files, but only if the folder names begin with "amd...". It has to be run from an Administrator Command Prompt in the UUP subfolder.

Code:

FOR /D %%a IN (amd*) DO DISM /Capture-Image /Compress:max /ImageFile:%%a.ESD /CaptureDir:%%a /Name:%%a /Description:%%a

To convert the folders to ESD files right from a Command Prompt, you have to leave out one % for each %%a:

Code:

FOR /D %a IN (amd*) DO DISM /Capture-Image /Compress:max /ImageFile:%a.ESD /CaptureDir:%a /Name:%a /Description:%a

The revised utility (from abbodi1406) does all of this automatically if you simply paste the path to the UUP files when asked.

For those who have UUP files, but can not convert to ISO. Either do what @DonCuthbert described above or follow THIS POST.

Both methods does the same, exept the tool I provide is not architecture dependent because it parses the ActionList.xml in order to ESD the correct folders.

Sanity check, please. Following post #228 UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files and links to pertinent processes, results are:

(pardon cryptic tone....it's intentional)

Code:

============================================================
Preparing Reference ESDs . . .
============================================================

CAB->ESD: amd64fre_Client_en-us_lp
DIR->ESD: Microsoft-Windows-RegulatedPackages-WOW64-Package
DIR->ESD: Microsoft-Windows-RegulatedPackages-Package
DIR->ESD: Microsoft-Windows-QuickAssist-Package
DIR->ESD: Microsoft-Windows-NetFx3-OnDemand-Package
DIR->ESD: Microsoft-Windows-MediaPlayer-Package
DIR->ESD: Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package
DIR->ESD: Microsoft-Windows-LanguageFeatures-Speech-en-us-Package
DIR->ESD: Microsoft-Windows-LanguageFeatures-OCR-en-us-Package
DIR->ESD: Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package
DIR->ESD: Microsoft-Windows-LanguageFeatures-Basic-en-us-Package
DIR->ESD: Microsoft-Windows-InternetExplorer-Optional-Package
DIR->ESD: Microsoft-Windows-Holographic-Desktop-Merged-WOW64-Package
DIR->ESD: Microsoft-Windows-Holographic-Desktop-Merged-Package
DIR->ESD: Microsoft-Windows-Holographic-Desktop-Analog-Package
DIR->ESD: Microsoft-Windows-Foundation-Package
DIR->ESD: Microsoft-Windows-EditionSpecific-Professional-Package
DIR->ESD: Microsoft-Windows-EditionPack-Professional-WOW64-Package
DIR->ESD: Microsoft-Windows-EditionPack-Professional-Package
DIR->ESD: Microsoft-Windows-ContactSupport-Package
DIR->ESD: Microsoft-Windows-Client-Features-Package
DIR->ESD: Microsoft.ModernApps.Client.professional
DIR->ESD: Microsoft.ModernApps.Client.All

============================================================
Creating Setup Media Layout . . .
============================================================


============================================================
Creating boot.wim . . .
============================================================

Using LZX compression with 8 threads
Archiving file data: 869 MiB of 869 MiB (100%) done

============================================================
Creating install.wim . . .
============================================================

Using LZX compression with 8 threads
Archiving file data: 7092 MiB of 7092 MiB (100%) done

============================================================
Adding winre.wim to install.wim . . .
============================================================


============================================================
Creating ISO . . .
============================================================

OSCDIMG 2.56 CD-ROM and DVD-ROM Premastering Utility
Copyright (C) Microsoft, 1993-2012. All rights reserved.
Licensed only for producing Microsoft authorized content.


Scanning source tree (1500 files in 54 directories)
Scanning source tree complete (1710 files in 99 directories)

Computing directory information complete

Image file is 4072243200 bytes (before optimization)

Writing 1710 files in 99 directories to 15055.0.170307-1445.RS2_RELEASE_CLIENTPRO_OEMRET_FRE_EN-US.ISO

100% complete

Storage optimization saved 18 files, 133120 bytes (0% of image)

After optimization, image file is 4075831296 bytes
Space saved because of embedding, sparseness or optimization = 133120

Done.

Press any key to exit.

Does all this look correct? Data is from the 7.42GB in Software Distribution/Download. I'm going to use it to update a VM as a test.

Thanks, TC