Clean install via UUPDUMP iso

The uup dump linux machinery has serious problems. All of my attempts to get a build 22000.51 iso have resulted in build 22000.1 isos when running on linux.

I started fresh from here this morning, asking for both home and professional. After running uup_download_linux.sh and letting the entire process complete, the resulting iso contained core (not home!) and professional, and once again it was the 22000.1 build.

I moved the entire directory from the linux machine to windows 10, and without changing anything I ran uup_download_windows.cmd. The uup files were thankfully not re-downloaded. The result was an iso with build 22000.51, both home and professional. Success!

Fellow linux sufferers, you have been warned! :)

Later today I'll try to figure out how to report the problem.

@grumpus,

How are you determining which version of Windows 11 is in your ISO file? The only reliable way to tell is to run dism /get-wiminfo on a particular index in the install.wim or install.esd file:


Notice ServicePack Build in the result above.

NavyLCDR said:

@grumpus,

How are you determining which version of Windows 11 is in your ISO file? The only reliable way to tell is to run dism /get-wiminfo on a particular index in the install.wim or install.esd file:

Code:

F:\>cd sources

F:\sources>dir ins*.*
 Volume in drive F is CCSA_X64FRE_EN-US_DV5
 Volume Serial Number is E8F8-D312

 Directory of F:\sources

06/19/2021  11:23 PM     3,003,478,612 install.esd
               1 File(s)  3,003,478,612 bytes
               0 Dir(s)               0 bytes free

F:\sources>dism /get-wiminfo /wimfile:install.esd /index:1

Deployment Image Servicing and Management tool
Version: 10.0.22000.1

Details for image : install.esd

Index : 1
Name : Windows 11 Home
Description : Windows 11 Home
Size : 17,120,712,236 bytes
WIM Bootable : No
Architecture : x64
Hal : <undefined>
Version : 10.0.22000
ServicePack Build : 51
ServicePack Level : 0
Edition : Core
Installation : Client
ProductType : WinNT
ProductSuite : Terminal Server
System Root : WINDOWS
Directories : 26637
Files : 125040
Created : 7/2/2021 - 10:13:03 AM
Modified : 7/2/2021 - 10:21:20 AM
Languages :
        en-US (Default)

The operation completed successfully.

Notice ServicePack Build in the result above.

Click to expand...

Well, I did run dism /get-wiminfo, but not until after installing to a VM and finding that I got the old build. It offered core and professional at install time, and sure enough that's what dism said was on the iso. Running the windows script rather than the linux script produces an iso with home and pro and the correct build, so all's well.

I suggest using the github project Ventoy instead: it builds a 32 MB EFI partition that has enough smarts to boot and then to mount any ISO, WIM, IMG, or other similar portmanteau file for runtime use and installation. The Ventoy partition is exFAT so it can handle files larger than 4GB with ease. I use it all the time. ventoy/Ventoy
HTH,
--Ed--

One of the uup dump developers informed me that it's to be expected that I was getting the 22000.1 build because the linux scripts can't integrate patches. One of the scripts prints a message to that effect at the start of the conversion process, but it's extremely easy to miss. Anyway, I've learned a very important lesson during my first uup dump adventure: Never, ever use the linux (or macos) scripts.

Ed Tittel said:

I suggest using the github project Ventoy instead: it builds a 32 MB EFI partition that has enough smarts to boot and then to mount any ISO, WIM, IMG, or other similar portmanteau file for runtime use and installation. The Ventoy partition is exFAT so it can handle files larger than 4GB with ease. I use it all the time. ventoy/Ventoy
HTH,
--Ed--

Click to expand...

Hi there
Seems not to work with this one -- get missing boot file !!!!

The RUFUS version though works (use the correct iso of course - the official one not the "leaked one). Rufus 3.14. Also for clean installs if you have a decent external SSD that you can connect via SATA-USB3 connector you can make a Windowsto GO system directly - then simply boot it and install whatever you need just like internal Disk based Windows.

Cheers
jimbo

grumpus said:

One of the uup dump developers informed me that it's to be expected that I was getting the 22000.1 build because the linux scripts can't integrate patches. One of the scripts prints a message to that effect at the start of the conversion process, but it's extremely easy to miss. Anyway, I've learned a very important lesson during my first uup dump adventure: Never, ever use the linux (or macos) scripts.

Click to expand...

Ahhh, that makes sense. Thanks for that info.

Ed Tittel said:

I suggest using the github project Ventoy instead: it builds a 32 MB EFI partition that has enough smarts to boot and then to mount any ISO, WIM, IMG, or other similar portmanteau file for runtime use and installation. The Ventoy partition is exFAT so it can handle files larger than 4GB with ease. I use it all the time. ventoy/Ventoy
HTH,
--Ed--

Click to expand...

jimbo45 said:

Hi there
Seems not to work with this one -- get missing boot file !!!!

The RUFUS version though works (use the correct iso of course - the official one not the "leaked one). Rufus 3.14. Also for clean installs if you have a decent external SSD that you can connect via SATA-USB3 connector you can make a Windowsto GO system directly - then simply boot it and install whatever you need just like internal Disk based Windows.

Cheers
jimbo

Click to expand...

I've used VenToy, Rufus, and even Easy2Boot. Never really had a problem with previous bootable .ISOs in any of them, although E2B was finicky sometimes with Microsoft ISOs until it started including the PTM method of having a small boot partition on the USB device (I think that is how they did it, it's been a while now since I used E2B).

Typically, though, I run to Rufus because I stopped having a need to keep multiple ISOs on USB (particularly when, even with USB 3 USB devices, they were not nearly as fast for file transfers than my NVMe and internal SSDs on the new rig).

I do still use external USB devices for other machines, but the work laptop is not getting 11, and the 2 older ones are staying on CloudReady ChromeOS, so I keep most oft used utilities for the desktop rig on them like CloneZilla, the Macrium boot, and other utilities.

I am glad you managed to do it. I myself gave up after a couple of tries. Instead? I downloaded the latest dev channel ISO (apparently, Microsoft allows that), installed it on an empty drive and then it updated itself to Windows 11. I did install a couple of drivers after that and that's it.