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

It's not Windows 10 I need to convert - it's Windows Server 2019 (arm64)! Here's the link again:
Find files in Feature update to Windows Server, version 1909 (18363.449) arm64 - UUP dump

The above does not come with a conversation script - but 95% of Windows 10 versions do - just not the Server ones I am gagging to test on my various arm64 devices and hypervisors!

Who knows a way to convert CAB + ESDs to install.wim by way of manual intervention since the automatic tools I tried failed to even initialize with Windows Server 2019 on ARM UUPs...? Any release will do... just need a successful output with install.wim/ISO:
Select language for Feature update to Windows Server, version 1909 (18363.449) arm64 - UUP dump
Select language for Feature update to Windows Server, version 1909 (18363.448) arm64 - UUP dump
Select language for Feature update to Windows Server, version 1909 (18363.446) arm64 - UUP dump
Select language for Feature update to Windows Server, version 1909 (18363.418) arm64 - UUP dump
Select language for Feature update to Windows Server, version 1909 (18363.387) arm64 - UUP dump
Select language for Feature update to Windows Server, version 1909 (18363.385) arm64 - UUP dump
Select language for Feature update to Windows Server, version 1903 (18362.267) arm64 - UUP dump

You could try uup-converter-wimlib, but that same script is also used by UUP Dump, so if you have a UUP Dump ZIP file for some other build, you should be able to find the same script in that too. Just put your downloaded files in the UUP folder after unzipping the file linked below, or you can just paste the path of folder they are in when running the script.

I don't know if there are differences in the script that would be required for Windows 10 Server, but since no conversion script to make a Server ISO is provided at UUP Dump, I think that could be the case.

WHD/uup-converter-wimlib-42.7z at master . abbodi1406/WHD . GitHub

I think that you should be able to export all of those CAB and ESD files into a single install.wim file, just as the conversion script usually does for Windows 10. You can then partition your disk for UEFI, use DISM to apply the WIM file to the C: partition and then run bcdboot to create the files needed in the System partition. I am presuming that this all matches what is needed on an amd64 device, because I have never looked at an arm64 device.

You would need to first boot your device using normal arm64 Windows 10 install media and then use SHIFT-F10 to get a Command Prompt. From there you can copy your WIM file to the C:\ partition. You could just copy your Server WIM file to whatever you booted the device from, or to a network share and use networking to copy it to C:.

I could only test this on an amd64 VM, using amd64 files, to see it it works like I think it should.

I already tried that. The standard conversion script does not initialize when the Windows Server UUPs are placed inside the UUPs folder and running convert-UUP.cmd; here's the error:

==== ERROR ====
UUP Edition file is not found in specified directory

Press 0 to exit.

Does anyone know a manual CMD/PowerShell method for converting CABs/ESDs to an install.wim? What exactly is the process that the UUP tools were designed to automate? Or perhaps the existing tools/scripts need tweaking or prerequisites in place for this particular set of dumps?

BTW, you don't need an ARM64 device to use DISM and BCDEDIT with the actual installation files, etc. I prepare all my ARM64 files using my x64/AMD64 PCs.

[QUOTE=gilius;1809078]It's not Windows 10 I need to convert - it's Windows Server 2019 (arm64)! Here's the link again:
Find files in Feature update to Windows Server, version 1909 (18363.449) arm64 - UUP dump
The above does not come with a conversation script - but 95% of Windows 10 versions do - just not the Server ones I am gagging to test on my various arm64 devices and hypervisors!
Who knows a way to convert CAB + ESDs to install.wim by way of manual intervention since the automatic tools I tried failed to even initialize with Windows Server 2019 on ARM UUPs...? Any release will do... just need a successful output with install.wim/ISO:
Select language for Feature update to Windows Server, version 1909 (18363.449) arm64 - UUP dump
Sorry, I missed the fact that you were trying to build the server and not just the regular Win 10.
Did you ever get the Arm64 server ISO built before ?

No, I've not been able to get any of the ARM64 Servers to build - they only appeared last year and nobody else seems to have tested them. Microsoft doesn't even seem to be advertising them. There were 4 x Server 2016 ARM64 betas back in the day that were in ISO format already - but few people have ever got to the desktop on those; I managed to get as far as the login screen via a virtual machine before they crashed. However, with these new Server 2019 dumps I'd imagine they will be more boot-friendly - but unless there's any resident UUP experts here I fear we may never get as far as an install.wim? For convenience I've uploaded all 953 files into one ZIP file here to save you having to download each file individually:

Download 18363.449arm64.zip... (right-click > save target...)

Perhaps you guys could have a go at testing? Again, everything can be processed from a normal x86-64 Windows PC when it comes to other ARM64 dumps that come with a working script, etc.

[QUOTE=gilius;1809206]No, I've not been able to get any of the ARM64 Servers to build - they only appeared last year and nobody else seems to have tested them. Microsoft doesn't even seem to be advertising them. There were 4 x Server 2016 ARM64 betas back in the day that were in ISO format already - but few people have ever got to the desktop on those; I managed to get as far as the login screen via a virtual machine before they crashed. However, with these new Server 2019 dumps I'd imagine they will be more boot-friendly - but unless there's any resident UUP experts here I fear we may never get as far as an install.wim? For convenience I've uploaded all 953 files into one ZIP file here to save you having to download each file individually:

I noticed that this problem is not just for Arm64 server, Amd64 server has the same issue.
Maybe the problem needs to be reported to the uupdump.ml guys ?.

They do not appear to be contactable: UUP dump . GitHub

I guess we just need to know more about how UUP conversion works since we cannot rely on the standard scripts on this occasion. Maybe everything can be extracted using 7-Zip and manually pieced together somehow with DISM or PowerShell... again, I don't even know the basics about UUP to troubleshoot this; who does know?

- - - Updated - - -

I found out they can be contacted on Discord and am currently talking to them: Discord

I managed to edit my aria2_download_windows.cmd from UUP Dump (from some other build) to auto-download all 2236 files shown on the site for Windows Server, version 1909 (18363.449) amd64. That was a simple edit, which will at least automate that portion of the task at hand. Since a Server image is not language-specific, that should give you all of the source files required to build the full image. If you have already downloaded over 900 files, one at a time, that must have been very tedious. It was certainly a much longer download than what goes into a normal Windows 10 set of UUP files. I got one tiny error the first time, so I had to run it twice to get that one file again. It re-downloads the problem files and only verifies the successful ones, if you run it twice.

To do this, once you have found the page containing your chosen list of ARM64 files from Microsoft, on the UUP Dump site, you just need to substitute that ID from the url in your browser for that page, in place of the one from some previous build. You also need to delete the part of the URL that mentions language from the CMD script. In my test, the URL was Find files in Feature update to Windows Server, version 1909 (18363.449) amd64 - UUP dump so I just used the number after id= to get the files.

Here is that section from my above mentioned CMD file, after editing it to get the Server files. The edited part is in red (for some reason it turned out green):

Code:

echo Retrieving aria2 script...
"%aria2%" --no-conf --log-level=info --log="aria2_download.log" -o"%aria2Script%" --allow-overwrite=true --auto-file-renaming=false "https://uupdump.ml/get.php?id=02cfe468-8c7d-4e2c-89b6-93524e69993b&aria2=2"
if %ERRORLEVEL% GTR 0 call :DOWNLOAD_ERROR & exit /b 1
echo.

Of course, this still leaves the main task of building all of this into a usable Windows Server image.