[DISCUSSION] UUP dump - download Windows 10/11 UUPs with ease

Discussion in 'MDL Projects and Applications' started by whatever127, Sep 2, 2017.

  1. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,679
    103,527
    450
  2. cuteee

    cuteee MDL Guru

    Oct 13, 2012
    5,760
    997
    180
    Trying different time will allow to download sucessfully win11 files with uupdump.
     
  3. qta3426

    qta3426 MDL Senior Member

    Oct 11, 2014
    298
    310
    10
  4. ultimate_live

    ultimate_live MDL Expert

    Mar 15, 2011
    1,022
    671
    60
    #3848 ultimate_live, Jul 1, 2021
    Last edited: Jul 1, 2021
    Trying since yesterday, and not working. Just Errors.

    Worked like a charm. :clap::clap::clap:
     
  5. TheCollDude489

    TheCollDude489 MDL Member

    Apr 16, 2018
    147
    32
    10
    #3849 TheCollDude489, Jul 3, 2021
    Last edited: Jul 3, 2021
    When attempting to build a Windows 11 22000.51 arm64 image, this error pops up when it lists the detected updates. Afterwards none of the images appear to be updated (all of them are at 22000.1). Both the kb5004564 CAB and PSF file also matches the SHA1 checksum present in the aria download script created by the UUP downloader.
    Code:
    ============================================================
    Updating install.wim / 2 image(s) . . .
    ============================================================
    
    1/5: ssu-22000.51-arm64.cab [SSU]
    2/5: windows10.0-kb5004564-arm64.cab [LCU]
    Error: failed to extract PSF update
    3/5: windows10.0-kb5004567-arm64.cab
    4/5: windows10.0-kb5004568-arm64.cab [WinPE]
    5/5: windows10.0-kb5004569-arm64.cab [Setup DU]
     
  6. TheCollDude489

    TheCollDude489 MDL Member

    Apr 16, 2018
    147
    32
    10
    #3850 TheCollDude489, Jul 3, 2021
    Last edited: Jul 3, 2021
    OK Windows 11 22000.51 amd64 also has strange issues and does not build properly. Additionally the script breaks after pressing any key to exit.
    Code:
    ============================================================
    Running UUP -> ISO v64
    ============================================================
    
    
    ============================================================
    Configured Options . . .
    ============================================================
    
    AddUpdates 1
    StartVirtual
    
    ============================================================
    Preparing Reference ESDs . . .
    ============================================================
    
    CAB->ESD: microsoft-onecore-applicationmodel-sync-desktop-fod-package-amd64
    CAB->ESD: microsoft-onecore-directx-database-fod-package-amd64
    CAB->ESD: microsoft-windows-ethernet-client-intel-e1i68x64-fod-package-amd64
    CAB->ESD: microsoft-windows-ethernet-client-intel-e2f68-fod-package-amd64
    CAB->ESD: microsoft-windows-ethernet-client-realtek-rtcx21x64-fod-package-amd64
    CAB->ESD: microsoft-windows-hello-face-package-amd64
    CAB->ESD: microsoft-windows-internetexplorer-optional-package-amd64
    CAB->ESD: microsoft-windows-kernel-la57-fod-package-amd64
    CAB->ESD: microsoft-windows-languagefeatures-basic-en-us-package-amd64
    CAB->ESD: microsoft-windows-languagefeatures-handwriting-en-us-package-amd64
    CAB->ESD: microsoft-windows-languagefeatures-ocr-en-us-package-amd64
    CAB->ESD: microsoft-windows-languagefeatures-speech-en-us-package-amd64
    CAB->ESD: microsoft-windows-languagefeatures-texttospeech-en-us-package-amd64
    CAB->ESD: microsoft-windows-mediaplayer-package-amd64
    CAB->ESD: microsoft-windows-notepad-system-fod-package-amd64
    CAB->ESD: microsoft-windows-powershell-ise-fod-package-amd64
    CAB->ESD: microsoft-windows-printing-pmcppc-fod-package-amd64
    CAB->ESD: microsoft-windows-printing-wfs-fod-package-amd64
    CAB->ESD: microsoft-windows-quickassist-package-amd64
    CAB->ESD: microsoft-windows-stepsrecorder-package-amd64
    CAB->ESD: microsoft-windows-tabletpcmath-package-amd64
    CAB->ESD: microsoft-windows-userexperience-desktop-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-broadcom-bcmpciedhd63-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-broadcom-bcmwl63a-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-broadcom-bcmwl63al-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-intel-netwbw02-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-intel-netwew00-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-intel-netwew01-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-intel-netwlv64-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-intel-netwns64-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-intel-netwsw00-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-intel-netwtw02-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-intel-netwtw04-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-intel-netwtw06-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-intel-netwtw08-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-marvel-mrvlpcie8897-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-qualcomm-athw8x-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-qualcomm-athwnx-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-qualcomm-qcamain10x64-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-ralink-netr28x-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-realtek-rtl8187se-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-realtek-rtl8192se-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-realtek-rtl819xp-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-realtek-rtl85n64-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-realtek-rtwlane-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-realtek-rtwlane01-fod-package-amd64
    CAB->ESD: microsoft-windows-wifi-client-realtek-rtwlane13-fod-package-amd64
    CAB->ESD: microsoft-windows-wordpad-fod-package-amd64
    CAB->ESD: openssh-client-package-amd64
    
    ============================================================
    Creating Setup Media Layout . . .
    ============================================================
    
    
    ============================================================
    Creating install.wim . . .
    ============================================================
    
    Using LZX compression with 16 threads
    Archiving file data: 7339 MiB of 7339 MiB (100%) done
    Using LZX compression with 16 threads
    Archiving file data: 202 MiB of 202 MiB (100%) done
    Using LZX compression with 16 threads
    Archiving file data: 242 MiB of 242 MiB (100%) done
    Using LZX compression with 16 threads
    Archiving file data: 192 MiB of 192 MiB (100%) done
    Using LZX compression with 16 threads
    Archiving file data: 1645 MiB of 1645 MiB (100%) done
    
    ============================================================
    Updating install.wim / 5 image(s) . . .
    ============================================================
    
    1/5: ssu-22000.51-x64.cab [SSU]
    2/5: windows10.0-kb5004564-x64.cab [LCU]
    3/5: windows10.0-kb5004567-x64.cab
    4/5: windows10.0-kb5004568-x64.cab [WinPE]
    5/5: windows10.0-kb5004569-x64.cab [Setup DU]
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Image Version: 10.0.22000.1
    
    Processing 1 of 1 - Adding package Package_for_ServicingStack~31bf3856ad364e35~amd64~~22000.51.1.0
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Image Version: 10.0.22000.1
    
    Processing 1 of 1 - Adding package Package_for_KB5004567~31bf3856ad364e35~amd64~~10.0.1.0
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Image Version: 10.0.22000.1
    
    Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22000.51.1.0
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Image File : F:\WinAIO\Work\uup_converters\22000.51_amd64_en-us_multi_e012464d_convert_virtual\ISOFOLDER\sources\install.wim
    Image Index : 1
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Image Version: 10.0.22000.1
    
    Processing 1 of 1 - Adding package Package_for_ServicingStack~31bf3856ad364e35~amd64~~22000.51.1.0
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Image Version: 10.0.22000.1
    
    Processing 1 of 1 - Adding package Package_for_KB5004567~31bf3856ad364e35~amd64~~10.0.1.0
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Image Version: 10.0.22000.1
    
    Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22000.51.1.0
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Image File : F:\WinAIO\Work\uup_converters\22000.51_amd64_en-us_multi_e012464d_convert_virtual\ISOFOLDER\sources\install.wim
    Image Index : 2
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Image Version: 10.0.22000.1
    
    Processing 1 of 1 - Adding package Package_for_ServicingStack~31bf3856ad364e35~amd64~~22000.51.1.0
    [==========================100.0%==========================]
    
    Error: 0x800f081e
    
    The specified package is not applicable to this image.
    
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\DismSSU.log
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.1
    
    Image File : F:\WinAIO\Work\uup_converters\22000.51_amd64_en-us_multi_e012464d_convert_virtual\ISOFOLDER\sources\install.wim
    Image Index : 3
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Creating winre.wim . . .
    ============================================================
    
    Using LZX compression with 16 threads
    Archiving file data: 1056 MiB of 1056 MiB (100%) done
    
    ============================================================
    Adding winre.wim to install.wim . . .
    ============================================================
    
    
    ============================================================
    Creating boot.wim . . .
    ============================================================
    
    
    ============================================================
    Done. You chose to start create_virtual_editions.cmd directly.
    ============================================================
    
    Press any key to exit.
    
    ============================================================
    Checking Distribution Info . . .
    ============================================================
    
    ============================================================
    Configured Virtual Options . . .
    ============================================================
    
    AutoStart
    AutoEditions: CoreSingleLanguage,ProfessionalWorkstation,ProfessionalEducation,Education,Enterprise,ServerRdsh,IoTEnterprise,ProfessionalWorkstationN,ProfessionalEducationN,EducationN,EnterpriseN
    
    ============================================================
    Copying install.wim . . .
    ============================================================
    
    ============================================================
    Creating Edition: Home Single Language
    ============================================================
    
    
    Setting the WINDOWS/EDITIONID property of image 4 to "CoreSingleLanguage".
    Setting the FLAGS property of image 4 to "CoreSingleLanguage".
    Setting the DISPLAYNAME property of image 4 to "Windows 11 Home Single Language".
    Setting the DISPLAYDESCRIPTION property of image 4 to "Windows 11 Home Single Language".
    
    ============================================================
    Rebuilding install.wim . . .
    ============================================================
    
    "ISOFOLDER\sources\install.wim" original size: 5380790 KiB
    Using LZX compression with 16 threads
    Archiving file data: 11 GiB of 11 GiB (100%) done
    "ISOFOLDER\sources\install.wim" optimized size: 5151321 KiB
    Space saved: 229468 KiB
    
    ============================================================
    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 (500 files in 42 directories)
    Scanning source tree complete (933 files in 85 directories)
    
    Computing directory information complete
    
    Image file is 5982355456 bytes (before optimization)
    
    Writing 933 files in 85 directories to 22000.1.210604-1628.CO_RELEASE_CLIENTMULTI_X64FRE_EN-US.ISO
    
    100% complete
    
    Storage optimization saved 24 files, 14217216 bytes (1% of image)
    
    After optimization, image file is 5970268160 bytes
    Space saved because of embedding, sparseness or optimization = 14217216
    
    Done.
    
    Press 0 to exit.
    
    
    Code:
    ============================================================
    Done. You chose to start create_virtual_editions.cmd directly.
    ============================================================
    
    Press any key to exit.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.746
    
    
    Error: 50
    
    The request is not supported.
    
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.746
    
    
    Error: 50
    
    The request is not supported.
    
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    
    'wimlib-imagex.exe' is not recognized as an internal or external command,
    operable program or batch file.
    'wimlib-imagex.exe' is not recognized as an internal or external command,
    operable program or batch file.
    'wimlib-imagex.exe' is not recognized as an internal or external command,
    operable program or batch file.
    'wimlib-imagex.exe' is not recognized as an internal or external command,
    operable program or batch file.
    'wimlib-imagex.exe' is not recognized as an internal or external command,
    operable program or batch file.
    
    ============================================================
    Adding setup dynamic update(s) . . .
    ============================================================
    
    windows10.0-kb5004569-x64.cab
    The system cannot find the path specified.
    The system cannot find the path specified.
    The system cannot find the path specified.
    
    ============================================================
    Creating boot.wim . . .
    ============================================================
    
    The system cannot find the path specified.
    The system cannot find the path specified.
    The system cannot find the path specified.
    The system cannot find the path specified.
    The system cannot find the path specified.
    The system cannot find the path specified.
    The system cannot find the path specified.
    The system cannot find the path specified.
    The system cannot find the path specified.
    The system cannot find the path specified.
    The system cannot find the file bin\bootwim.txt.
    The system cannot find the file bin\bootmui.txt.
    'wimlib-imagex.exe' is not recognized as an internal or external command,
    operable program or batch file.
    The system cannot find the path specified.
    
    ============================================================
    Done. You chose to start create_virtual_editions.cmd directly.
    ============================================================
    
    Press any key to exit.
    
    Are the UUP files causing these issues with the conversion script?

    EDIT: Never mind my query, found out it was because the version of the UUP converter didn't like the UUP files or had a bug. Redownloading a fresh package from the UUPdump site while using the same UUPs I downloaded fixed the strange issues and resulted in a successful build for both amd64 and arm64 images (with and without updates integrated).
     
  7. Nicatorium

    Nicatorium MDL Novice

    Jul 3, 2021
    11
    0
    0
    Hello friends. I want to download the latest build of Windows 10 21H1 release. Now the most current version is build 19043.1082. When I look at the UUP Dump site, this version appears as a Cumultative update. But the site says it's better to download the Feature Update version. I read the difference between these two in the comments (up to the first pages), but I didn't quite understand.

    Now if I download Cumulative update 19043.1082 directly, will I be able to get new updates and others (example: optional, driver) without any problems in the future?
     
  8. yes
     
  9. Nicatorium

    Nicatorium MDL Novice

    Jul 3, 2021
    11
    0
    0
    Then why is it recommended to create ISO through Feature Update specifically?
     
  10. It contains a Setup DU, it is not super important IMO. If you want, you can download the 19043.1081 setup DU and drop it in the UUPs folder.
     
  11. Nicatorium

    Nicatorium MDL Novice

    Jul 3, 2021
    11
    0
    0
    Sorry but what is DU, SU, FU ? I read this words, but i dont know what is this terms and meaning.
     
  12. Nicatorium

    Nicatorium MDL Novice

    Jul 3, 2021
    11
    0
    0
    I read this section on Readme file. So that is true? I choosed Cleanup option. So future cumulative updates will fail?
     
  13. Nicatorium

    Nicatorium MDL Novice

    Jul 3, 2021
    11
    0
    0
    Resetbase and Cleanup are completely safe? So If I choose both of them, my system will not fail next Cumulative update or Feature update?
     
  14. it won’t
     
  15. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,209
    90,791
    340
    General rule, only perform Ceanup with patch tuesday security release (e.g. 19043.1052 or 19043.1055)
    issues happens mostly (only) when running cleanup with non-security release (e.g. 19043.1081 or 19043.1082)
     
  16. Nicatorium

    Nicatorium MDL Novice

    Jul 3, 2021
    11
    0
    0
    Thanks for clarity. So, is it okay if I use Windows Disk Cleanup after formatting? Does it work with the same logic as Resetbase? Honestly I did the Windows Disk Cleanup feature after every update, no problems at all. But after reading the forum and the readme file, I'm a bit confused.