That is a copy of every log in the folder, are there any other logs I can get for you? I haven't edited these, and even still have the UUP - ISO console window up. For the record, I have no antivirus running, and I use no kind of cleanup tools or anything that could interfere with this. I'm wondering if it is anything to do with the system I'm using running Windows 21382.1000? Code: ============================================================ Running UUP -> ISO v58 ============================================================ ============================================================ Checking UUP Info . . . ============================================================ ============================================================ Configured Options . . . ============================================================ AutoStart 1 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-hello-face-migration-package-amd64 CAB->ESD: microsoft-windows-hello-face-package-amd64 CAB->ESD: microsoft-windows-internetexplorer-optional-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-basic-en-gb-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-handwriting-en-gb-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-ocr-en-gb-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-speech-en-gb-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-texttospeech-en-gb-package-amd64 CAB->ESD: microsoft-windows-mediaplayer-package-amd64 CAB->ESD: microsoft-windows-mspaint-fod-package-amd64 CAB->ESD: microsoft-windows-notepad-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-wordpad-fod-package-amd64 CAB->ESD: openssh-client-package-amd64 ============================================================ Creating Setup Media Layout . . . ============================================================ ============================================================ Creating install.wim . . . ============================================================ Using LZX compression with 24 threads Archiving file data: 7230 MiB of 7230 MiB (100%) done ============================================================ Updating install.wim / 1 image(s) . . . ============================================================ 1/6: ssu-19041.1022-x64.cab [SSU] 2/6: windows10.0-kb5000736-x64.cab [Enablement] 3/6: windows10.0-kb5000983-x64.cab [WinPE] 4/6: windows10.0-kb5001679-x64.cab 5/6: windows10.0-kb5003214-x64.cab [LCU] 6/6: windows10.0-kb5003240-x64.cab [Setup DU] Deployment Image Servicing and Management tool Version: 10.0.21382.1 Mounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.21382.1 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_ServicingStack~31bf3856ad364e35~amd64~~19041.1022.1.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.21382.1 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_KB5000736~31bf3856ad364e35~amd64~~10.0.1.3 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.21382.1 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.1023.1.17 [===========================69.0%======== ] Error: 1726 The remote procedure call failed. An error occurred closing a servicing component in the image. Wait a few minutes and try running the command again. The DISM log file can be found at C:\Windows\Logs\DISM\DismLCU.log Deployment Image Servicing and Management tool Version: 10.0.21382.1 Image File : C:\Users\Tone\Desktop\19043.1023_amd64_en-gb_professional_0e51fec7_convert_virtual\ISOFOLDER\sources\install.wim Image Index : 1 Unmounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Creating winre.wim . . . ============================================================ Using LZX compression with 24 threads Archiving file data: 988 MiB of 988 MiB (100%) done ============================================================ Adding winre.wim to install.wim . . . ============================================================ ============================================================ Creating boot.wim . . . ============================================================ ============================================================ Checking Distribution Info . . . ============================================================ ============================================================ Configured Virtual Options . . . ============================================================ AutoStart AutoEditions: ProfessionalWorkstation,Enterprise ============================================================ Copying install.wim . . . ============================================================ ============================================================ Creating Edition: Enterprise ============================================================ Setting the WINDOWS/EDITIONID property of image 2 to "Enterprise". Setting the FLAGS property of image 2 to "Enterprise". Setting the DISPLAYNAME property of image 2 to "Windows 10 Enterprise". Setting the DISPLAYDESCRIPTION property of image 2 to "Windows 10 Enterprise". ============================================================ Creating Edition: Pro for Workstations ============================================================ Setting the WINDOWS/EDITIONID property of image 3 to "ProfessionalWorkstation". Setting the FLAGS property of image 3 to "ProfessionalWorkstation". Setting the DISPLAYNAME property of image 3 to "Windows 10 Pro for Workstations". Setting the DISPLAYDESCRIPTION property of image 3 to "Windows 10 Pro for Workstations". ============================================================ Rebuilding install.wim . . . ============================================================ "ISOFOLDER\sources\install.wim" original size: 3463559 KiB Using LZX compression with 24 threads Archiving file data: 7743 MiB of 7743 MiB (100%) done "ISOFOLDER\sources\install.wim" optimized size: 3437296 KiB Space saved: 26262 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 41 directories) Scanning source tree complete (898 files in 85 directories) Computing directory information complete Image file is 4209115136 bytes (before optimization) Writing 898 files in 85 directories to 19041.1.191206-1406.VB_RELEASE_CLIENTMULTI_X64FRE_EN-GB_r.ISO 100% complete Storage optimization saved 25 files, 14200832 bytes (1% of image) After optimization, image file is 4196974592 bytes Space saved because of embedding, sparseness or optimization = 14200832 Done. Press 0 to exit.
OK, running the process now. Will be back in a few mins... OK, it worked fine. It even spat out an image at the end! Thanks for your help, but what do you think happened?
Some question about UUPD While creating an updated ISO via aria2 script, when should I configure the ConvertConfig.ini file & place these three update files in UUP folder? Before starting/running the uup_download_windows.cmd? Or after? 2021-01 IMC KB4589212 [10.0.2.4] 2021-04 WFEP KB5003345 120.2212.3740.0 [19041.686.1.3] 2021-05 DotNET KB5003254 [10.0.4360.1] Also, is there any specific filename format required in order to work in aria2 script to work & add those updates into the ISO i.e. no space or gap in a filename or exact name as the original filename from the MS server side? & when should I configure the ConvertConfig.ini file (I believe this is the INI file that you mentioned as your configuration) & about NetFx3 =1,should I keep this as =1 been though am gonna add this 2021-05 DotNET KB5003254 [10.0.4360.1]? or set as 0?
I would do it differently download the UUPs source and use the uup-converter-wimlib-59. You can then simply put your updates in the UUPs folder. However, I would always create a new ISO with all updates. ConvertConfig.ini [convert-UUP] AutoStart =1 AddUpdates =1 Cleanup =0 ResetBase =0 NetFx3 =1 StartVirtual =0 wim2esd =0 SkipISO =0 SkipWinRE =0 ForceDism =0 RefESD =0 SkipEdge =0
When you have created your Windows 10 Pro, you can also use the create_virtual_editions.cmd to create an Enterprise version, for example, which takes a few seconds. You only have to mount the created Windows 10 Pro with UltraISO or a programme of your choice. Then run the create_virtual_editions.cmd with the following settings. ConvertConfig.ini create_virtual_editions] vAutoStart =1 vDeleteSource=1 vPreserve =0 vwim2esd =0 vSkipISO =0 vAutoEditions=Enterprise ---------------------------------------------------------------------- you can change all versions in vAutoEditions= that are available for the Pro, and it only takes a few seconds to create them. and these are the versions you can enter vAutoEditions=ProfessionalWorkstation,ProfessionalEducation,Education,Enterprise,ServerRdsh,IoTEnterprise Here you can determine whether the created windows version should be deleted. vDeleteSource=1 1 means the source is deleted and the desired version is created, vAutoEditions=Enterprise etc.... will be created. ---------------------------------------------------------------------- and remember that you only edit a source in virtual cmd that has an install.wim, with install.esd there will be complications with the created Windows version. ADK for the 19041.1 from Microsoft must be installed
This still is accurate: https://forums.mydigitallife.net/th...load-windows-10-uups-with-ease.75052/page-122
seeing Azure Stack HCI is now being flighted the same way as Windows 10 is could you add 20348 AzureStackHCI to UUPDump
Am getting this error constantly while trying to dl any file/iso via the aria2 script "Name resolution for tlu.dl.delivery.mp.microsoft.com failed:Timeout while contacting DNS servers" Tried in 3/4 different system, but the same result. I believe this is something from my ISP/DNS side, not system-specific 9I.e. corrupted registry or overclocked RAM etc), so asking, is there any way to get rid of this? Any workaround or troubleshooting? Attaching the full Log here if anyone wanna take a look & suggest anything. P.S: I didn't change any ISP/DNS configuration, running on the default settings, google DNS probably. Earlier, in this same ISP & settings, UUPD runs/downloads just fine, lately facing such issue.