Hello, I used psfx2esd_CLI.cmd to make Windows11.0-KB5034123-x64.esd from both Windows11.0-KB5034123-x64.psf and Windows11.0-KB5034123-x64.cab I downloaded using UUPDump website. It seams the resulting ESD file is not detected by W10UI when trying to update a Windows source. W10UI could detect them some time ago if I correctly remember. If I use the original CAB and psf file to update the Windows source it works just fine. Thank you.
W10UI can't detect this update as SafeOS https://www.catalog.update.microsoft.com/Search.aspx?q=KB5034229 please fix it Code: ============================================================ Running W10UI v10.38 ============================================================ ============================================================ Copying DVD Drive contents to work directory... ============================================================ ============================================================ Extracting dpx.dll file... ============================================================ ============================================================ Extracting .cab files from .msu files... ============================================================ 1/1: windows11.0-kb5034130-x64_LCU_643.1.4.msu [Combined UUP] ============================================================ Extracting files from update cabinets (.cab)... *** This will require some disk space, please be patient *** ============================================================ 1/5: defender-dism-x64_10.01.2024.cab 2/5: windows11.0-kb5033917-x64-ndp481_CU_9214.3.cab [NetFx] 3/5: windows11.0-kb5034223-x64_DU.Sources_643.cab [Setup DU] 4/5: windows11.0-kb5034229-x64_DU.SafeOS_640.1.2.cab 5/5: Windows10.0-KB5034285-x64_inout.cab [SSU] ============================================================
thanks, the same issue affects the uup-converter as well I'll update this post with test results Code: ============================================================ Running W10UI v10.39 ============================================================ ============================================================ Copying DVD Drive contents to work directory... ============================================================ ============================================================ Extracting dpx.dll file... ============================================================ ============================================================ Extracting .cab files from .msu files... ============================================================ 1/1: windows11.0-kb5034130-x64_LCU_643.1.4.msu [Combined UUP] ============================================================ Extracting files from update cabinets (.cab)... *** This will require some disk space, please be patient *** ============================================================ 1/5: defender-dism-x64_10.01.2024.cab 2/5: windows11.0-kb5033917-x64-ndp481_CU_9214.3.cab [NetFx] 3/5: windows11.0-kb5034223-x64_DU.Sources_643.cab [Setup DU] 4/5: windows11.0-kb5034229-x64_DU.SafeOS_640.1.2.cab [SafeOS DU] 5/5: Windows10.0-KB5034285-x64_inout.cab [SSU] ============================================================ everything is ok now, thank you
I still get errors Code: ============================================================ Running W10UI v10.39 ============================================================ ============================================================ Copying DVD Drive contents to work directory... ============================================================ ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Extracting files from update cabinets (.cab)... *** This will require some disk space, please be patient *** ============================================================ 1/9: defender-dism-x64.cab 2/9: Windows10.0-KB5011048-x64_NDP481_Base.cab [NetFx] 3/9: Windows10.0-KB5015684-x64.cab [Enablement] 4/9: windows10.0-kb5032906-x64.cab [Setup DU] 5/9: Windows10.0-KB5033909-x64-NDP48.cab [NetFx] 6/9: Windows10.0-KB5034203-x64.cab [LCU] 7/9: Windows10.0-KB5034224-x64.cab [SSU] 8/9: windows10.0-kb5034232-x64.cab [SafeOS DU] 9/9: Windows11.0-KB5034224-x64.cab [SSU] ============================================================ Mounting sources\install.wim - index 1/3 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.22621.2792 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.22621.2792 Image Version: 10.0.19045.1889 Processing 1 of 2 - Adding package Package_for_ServicingStack_3989~31bf3856ad364e35~amd64~~19041.3989.1.2 [==========================100.0%==========================] Processing 2 of 2 - Adding package Package_for_ServicingStack_3989~31bf3856ad364e35~amd64~~19041.3989.1.2 [==========================100.0%==========================] The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.22621.2792 Image Version: 10.0.19045.1889 Processing 1 of 1 - Adding package Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4690.2 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.22621.2792 Image Version: 10.0.19045.1889 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.3992.1.6 [==========================100.0%==========================] An error occurred - Package_for_RollupFix Error: 0x800710fe Error: 4350 This file is currently not available for use on this computer. The DISM log file can be found at C:\Windows\Logs\DISM\DismLCU.log ============================================================ Adding Defender update... ============================================================
YAOCTRU2013 for Office 2013 https://github.com/abbodi1406/WHD/raw/master/scripts/YAOCTRU2013.zip https://download.ru/files/NsBjLIw4
If i implement "Adding Drivers" option for W10UI (and maybe uup-converter), should i set single drivers folder location for both? or separate folders? the option would be mainly for chipset and disk controllers (boot critical), to allow easier installation (instead loading the drivers manually) with single folder, WinPE might get bloated with unnecessary drivers, if the user gathered them all with separate folders, the user has to gather (duplicate) the needed drivers in both Edit: or maybe specify separate folders depending on usage one folder for needed drivers (boot critical), which added to all wim files and one folder for extra drivers, which added only to install.wim
Draft Code: :: ### Options for wim or distribution target only ### :: add drivers to install.wim set "Drv_AddOS=0" :: add drivers to boot.wim / winre.wim set "Drv_AddPE=0" :: folder path for boot-critical drivers - all wim files (default is "DriversB" folder next to the script) set "Drv_BootC=" :: folder path for extra drivers - install.wim only (default is "DriversX" folder next to the script) set "Drv_Extra="
"Drv_BootC=" folder is for all wims, but if it's configured like this "Drv_AddPE=1" "Drv_AddOS=0" then it will be integrated into PEs only or in all wims?
so one use case is impossible: 1. Drv_AddOS is enabled, extra drivers are located in Drv_Extra folder for install.wim 2. Drv_AddPE is enabled, boot drivers are in Drv_BootC folder and user do not want to integrate these drivers into install.wim, but it will be integrated because of enabled Drv_AddOS option it's getting complicated but maybe use 3 folders: 1. all wims 2. PEs only 3. install.wim only this way user can integrate everything from one folder or differentiate PEs and install.wim
no idea, I just like to have more options for any possible use cases if you think critical drivers are also needed for install.wim then ok, current draft version is fine
It's just a bonus, it should not be too sophisticated simple as: - i want these drivers (which i already tried and know it's working) to be integrated - sure, place the driver(s) inside this folder(s) and enable the option