It runs fine, but slow because of low VM specs, but try with convertconfig.ini set options and autorstart =1.
I built it just fine a few days ago, got 29641.1000.260729-1515.rs_flight_server_x64fre_ru-ru.iso It was with AutoStart=1, I'll check with AutoStart=0 edit: no issues with the AutoStart=0, I'm on 28000.2704 host OS this is with the 29641.1000_amd64_ru-ru_multi_62eb4764 UUP set
No, he doesn't want to. What is most interesting is that the script processes all the builds that were before this release, and this 29641 is in failure. Now I'll try to run it on WinPE and on a virtual machine.
Autostrat=0 also works: I accidentally removed the previous gif with the autostart=1 test but the picture shows it working
Strange things are happening. On my laptop on build 26300, the script refuses to work. It works on a desktop computer on 26300. I reinstalled it on my laptop to 28000 and everything went fine. Thank you for your time.
uup-converter v125f - Update the workaround for baseline KB5122055 (LCUmsuExpand will be disabled only for 26300.9032/26220.9022) - Recognize 26340 EKB - Change wim2esd state when selected via choice menu
Hi abbodi, some findings in W10UI and uup-converter-wimlib that could help for improvements: W10UI: - ResetBase=2 is not applied to WinPE images, i.e. when updating ADK winpe or more usually boot.wim (:cuboot vs :cuinstall sections) - DismRoot option, as specified by user, is not applied for all dism command instances. It defaults to dism.exe in path (host OS if no ADK installed) for those instances "hardcoded" as dism.exe /english command or dism.exe command instead of using %_dism2%:"!_cabdir!" command as well. uup-converter-wimlib: - in convert-UUP.cmd, StartVirtual=1 is not supported if AutoStart=3 (install.wim only) because create_virtual_editions.cmd does not support .\install.wim only. Currently to workaround this I move the created .\install.wim to a "dummy" folder structure like ".\myiso\sources" and manually start create_virtual_editions.cmd. It throws a "file not found" error during the "=== Checking distribution Info . . ." stage, but script continues through "=== Creating Virtual Editions . . ." stage without errors.
@Reducer - Cleaning after baseline LCU in WiinPE breaks installation for the 2nd LCU - Some commands doesn't require newer dism.exe, it's compatible with Win7 or later specially some check/grab commands (for loop) will not work with full or long ADK dism.exe path - StartVirtual is ignored indeed if the target is not ISO (1 or 2) i don't know what do you need exactly?
Sorry the delay in replying, abbodi. 1. ResetBase=2 for WinPE images. The following script log shows that it is possible to resetbase after each CU for a WinPE image. Is a very basic update script, of course, just straight commands. The point is: in current W10UI some processing happens between CU apply command and the resetbase command which seems to be different depending on the target image (WinPE or not). The breaking cause could be in one of the steps of this different processing. I mean: it seems to me that :rebase section cannot simply be called from :cuboot like it is done from :cuinstall because before the final resetbase command each type of image is processed differently. Spoiler: Script log: successful resetbase after each CU Code: Setting up dism... 2026-08-20 22:39:26.346 Found driver [WIMMount] 2026-08-20 22:39:26.346 Driver file path: C:\10u\d\wimmount.sys 2026-08-20 22:39:26.346 Hive file path: C:\10u\d\WIMMount.hiv 2026-08-20 22:39:26.348 Installed driver [WIMMount] 2026-08-20 22:39:26.348 Driver [WofAdk] supports maximum target build [10240], while this OS is build [26100]; skipping install Mounting image... Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Mounting image [==========================100.0%==========================] The operation completed successfully. Adding optional components... Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.1 Processing 1 of 12 - Adding package WinPE-WMI-Package~31bf3856ad364e35~amd64~~10.0.26100.1 [==========================100.0%==========================] Processing 2 of 12 - Adding package WinPE-WMI-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1 [==========================100.0%==========================] Processing 3 of 12 - Adding package WinPE-NetFx-Package~31bf3856ad364e35~amd64~~10.0.26100.1 [==========================100.0%==========================] Processing 4 of 12 - Adding package WinPE-NetFx-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1 [==========================100.0%==========================] Processing 5 of 12 - Adding package WinPE-Scripting-Package~31bf3856ad364e35~amd64~~10.0.26100.1 [==========================100.0%==========================] Processing 6 of 12 - Adding package WinPE-Scripting-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1 [==========================100.0%==========================] Processing 7 of 12 - Adding package WinPE-PowerShell-Package~31bf3856ad364e35~amd64~~10.0.26100.1 [==========================100.0%==========================] Processing 8 of 12 - Adding package WinPE-PowerShell-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1 [==========================100.0%==========================] Processing 9 of 12 - Adding package WinPE-StorageWMI-Package~31bf3856ad364e35~amd64~~10.0.26100.1 [==========================100.0%==========================] Processing 10 of 12 - Adding package WinPE-StorageWMI-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1 [==========================100.0%==========================] Processing 11 of 12 - Adding package WinPE-DismCmdlets-Package~31bf3856ad364e35~amd64~~10.0.26100.1 [==========================100.0%==========================] Processing 12 of 12 - Adding package WinPE-DismCmdlets-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.1 [==========================100.0%==========================] The operation completed successfully. Adding SSU... Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_9156~31bf3856ad364e35~amd64~~26100.9156.1.0 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_9156 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. Adding EP... Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package Package_for_KB5054156~31bf3856ad364e35~amd64~~26100.6717.1.4 [==========================100.0%==========================] The operation completed successfully. Adding BCU... Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.1 Processing 1 of 1 - [==========================100.0%==========================] [==========================100.0%==========================] The operation completed successfully. Performing BCU cleanup + resetbase... Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.1742 [===========================99.4%========================= ] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.1742 [===========================70.0%======== ] The operation completed successfully. Adding CU... Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.1742 Processing 1 of 1 - [==========================100.0%==========================] [==========================100.0%==========================] The operation completed successfully. Performing CU cleanup + resetbase... Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.9168 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.9168 [===========================70.0%======== ] The operation completed successfully. Getting packages... Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.9168 Packages listing: Package Identity : Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.9168 State : Installed Release Type : Language Pack Install Time : 20/08/2026 21:43 Package Identity : Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.26100.9168 State : Installed Release Type : Foundation Install Time : 20/08/2026 21:43 Package Identity : Package_for_KB5054156~31bf3856ad364e35~amd64~~26100.6717.1.4 State : Installed Release Type : Update Install Time : 20/08/2026 21:39 Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.9168.1.19 State : Installed Release Type : Security Update Install Time : 20/08/2026 21:43 Package Identity : Package_for_ServicingStack_9156~31bf3856ad364e35~amd64~~26100.9156.1.0 State : Installed Release Type : Security Update Install Time : 20/08/2026 21:39 Package Identity : WinPE-DismCmdlets-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.9168 State : Installed Release Type : Language Pack Install Time : 20/08/2026 21:43 Package Identity : WinPE-DismCmdlets-Package~31bf3856ad364e35~amd64~~10.0.26100.9168 State : Installed Release Type : Feature Pack Install Time : 20/08/2026 21:43 Package Identity : WinPE-NetFx-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.9168 State : Installed Release Type : Language Pack Install Time : 20/08/2026 21:43 Package Identity : WinPE-NetFx-Package~31bf3856ad364e35~amd64~~10.0.26100.9168 State : Installed Release Type : Feature Pack Install Time : 20/08/2026 21:43 Package Identity : WinPE-PowerShell-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.9168 State : Installed Release Type : Language Pack Install Time : 20/08/2026 21:43 Package Identity : WinPE-PowerShell-Package~31bf3856ad364e35~amd64~~10.0.26100.9168 State : Installed Release Type : Feature Pack Install Time : 20/08/2026 21:43 Package Identity : WinPE-Scripting-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.9168 State : Installed Release Type : Language Pack Install Time : 20/08/2026 21:43 Package Identity : WinPE-Scripting-Package~31bf3856ad364e35~amd64~~10.0.26100.9168 State : Installed Release Type : Feature Pack Install Time : 20/08/2026 21:43 Package Identity : WinPE-StorageWMI-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.9168 State : Installed Release Type : Language Pack Install Time : 20/08/2026 21:43 Package Identity : WinPE-StorageWMI-Package~31bf3856ad364e35~amd64~~10.0.26100.9168 State : Installed Release Type : Feature Pack Install Time : 20/08/2026 21:43 Package Identity : WinPE-WMI-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.9168 State : Installed Release Type : Language Pack Install Time : 20/08/2026 21:43 Package Identity : WinPE-WMI-Package~31bf3856ad364e35~amd64~~10.0.26100.9168 State : Installed Release Type : Feature Pack Install Time : 20/08/2026 21:43 The operation completed successfully. Committing changes... Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. Exporting to new wim... Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Exporting image [==========================100.0%==========================] The operation completed successfully. Spoiler: Script log: update and resetbase commands used Code: echo. echo Adding SSU... %_d% /Image:%_M% /Add-Package /PackagePath:%_UP%\SSU-26100.9156-x64.cab echo. echo Adding EP... %_d% /Image:%_M% /Add-Package /PackagePath:%_UP%\Windows11.0-KB5054156-x64_ep25h2.cab echo. echo Adding BCU... %_d% /Image:%_M% /Add-Package /PackagePath:%_UP%\bcu\Windows11.0-KB5043080-x64_bcu.msu echo. echo Performing BCU cleanup + resetbase... %_d% /Image:%_M% /Cleanup-Image /StartComponentCleanup %_d% /Image:%_M% /Cleanup-Image /StartComponentCleanup /ResetBase echo. echo Adding CU... %_d% /Image:%_M% /Add-Package /PackagePath:%_UP%\Windows11.0-KB5121003-x64_cu.msu echo. echo Performing CU cleanup + resetbase... %_d% /Image:%_M% /Cleanup-Image /StartComponentCleanup %_d% /Image:%_M% /Cleanup-Image /StartComponentCleanup /ResetBase 2. Honor DismRoot as specified by user. Your concern on exceeding max command lenght totally makes sense. However note: in current W10UI, if ADK is detected, you add its dism.exe to the script "Path" definition, which drastically cuts "_dism2" command lenght. Surprisingly, you never add "DismRoot" to "Path" for the same benefit. To confirm this I performed the following test: Spoiler: W10UI test: setup Code: 1. Default dism ADK bin path is C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe 2. "DismRoot" is set to exactly the same char lenght C:\10u\ddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd\dism.exe 3. "DismRoot is added to script "Path" definition at a suitable point 4. "_dism2" definition in :proceed does not use "DismRoot", but simply "dism.exe" 5. All instances of hardcoded dism.exe /English and dism.exe commands are replaced with %_dism2%:"!_cabdir!" 6. All script options are set using the menu to test behavior after changes. Note: Current W10UI rejects ADK winpe.wim as a valid target ("Detected wim version is not Windows NT 10.0"). I have to target the mounted image. Spoiler: W10UI test: script log Code: ============================================================ Running W10UI v10.62 ============================================================ ============================================================ Configured Options... ============================================================ LCUmsuExpand 1 Cleanup ResetBase DismRoot: "C:\10u\ddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd\dism.exe" ============================================================ Extracting dpx.dll file... ============================================================ ============================================================ Extracting .cab files from .msu files... ============================================================ 1/2: Windows11.0-KB5043080-x64_bcu.msu [Combined UUP] 2/2: Windows11.0-KB5121003-x64_cu.msu [Combined UUP] ============================================================ Extracting files from update containers (cab/wim)... *** This will require some disk space, please be patient *** ============================================================ 1/5: Windows11.0-KB5054156-x64_ep25h2.cab [Enablement] 2/5: Windows11.0-KB5043113-x64_inout.cab [SSU] 3/5: Windows11.0-KB5123304-x64_inout.cab [SSU] 4/5: Windows11.0-KB5043080-x64.wim [LCU] 5/5: Windows11.0-KB5121003-x64.wim [LCU] ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_9156~31bf3856ad364e35~amd64~~26100.9156.1.0 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_9156 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package Package_for_KB5054156~31bf3856ad364e35~amd64~~26100.6717.1.4 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.1742 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.9168.1.19 [==========================100.0%==========================] The operation completed successfully. ============================================================ Resetting WinPE image base... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.9168 [===========================86.2%================= ] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.9168 [===========================70.0%======== ] The operation completed successfully. ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Finished ============================================================ Getting packages... Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Image Version: 10.0.26100.9168 Packages listing: Package Identity : Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.9168 State : Installed Release Type : Language Pack Install Time : 22/08/2026 18:07 Package Identity : Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.26100.9168 State : Installed Release Type : Foundation Install Time : 22/08/2026 18:07 Package Identity : Package_for_KB5054156~31bf3856ad364e35~amd64~~26100.6717.1.4 State : Installed Release Type : Update Install Time : 22/08/2026 18:06 Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.9168.1.19 State : Installed Release Type : Security Update Install Time : 22/08/2026 18:07 Package Identity : Package_for_ServicingStack_9156~31bf3856ad364e35~amd64~~26100.9156.1.0 State : Installed Release Type : Security Update Install Time : 22/08/2026 18:06 Package Identity : WinPE-DismCmdlets-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.9168 State : Installed Release Type : Language Pack Install Time : 22/08/2026 18:07 Package Identity : WinPE-DismCmdlets-Package~31bf3856ad364e35~amd64~~10.0.26100.9168 State : Installed Release Type : Feature Pack Install Time : 22/08/2026 18:07 Package Identity : WinPE-NetFx-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.9168 State : Installed Release Type : Language Pack Install Time : 22/08/2026 18:07 Package Identity : WinPE-NetFx-Package~31bf3856ad364e35~amd64~~10.0.26100.9168 State : Installed Release Type : Feature Pack Install Time : 22/08/2026 18:07 Package Identity : WinPE-PowerShell-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.9168 State : Installed Release Type : Language Pack Install Time : 22/08/2026 18:07 Package Identity : WinPE-PowerShell-Package~31bf3856ad364e35~amd64~~10.0.26100.9168 State : Installed Release Type : Feature Pack Install Time : 22/08/2026 18:07 Package Identity : WinPE-Scripting-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.9168 State : Installed Release Type : Language Pack Install Time : 22/08/2026 18:07 Package Identity : WinPE-Scripting-Package~31bf3856ad364e35~amd64~~10.0.26100.9168 State : Installed Release Type : Feature Pack Install Time : 22/08/2026 18:07 Package Identity : WinPE-StorageWMI-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.9168 State : Installed Release Type : Language Pack Install Time : 22/08/2026 18:07 Package Identity : WinPE-StorageWMI-Package~31bf3856ad364e35~amd64~~10.0.26100.9168 State : Installed Release Type : Feature Pack Install Time : 22/08/2026 18:07 Package Identity : WinPE-WMI-Package~31bf3856ad364e35~amd64~en-US~10.0.26100.9168 State : Installed Release Type : Language Pack Install Time : 22/08/2026 18:07 Package Identity : WinPE-WMI-Package~31bf3856ad364e35~amd64~~10.0.26100.9168 State : Installed Release Type : Feature Pack Install Time : 22/08/2026 18:07 The operation completed successfully. Committing changes... Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. Exporting to new wim... Deployment Image Servicing and Management tool Version: 10.0.26100.8972 Exporting image [==========================100.0%==========================] The operation completed successfully. Test was successful, apparently no dism commands issues. One of the longest, currently harcoded, dism commands reported in dism.log becomes as follows when using _dism2 definition + "DismRoot" in script "Path": Spoiler Code: 2026-08-22 19:04:37, Info DISM PID=2672 TID=2824 Scratch directory set to 'X:\Windows\SystemTemp\'. - CDISMManager::put_ScratchDir 2026-08-22 19:04:37, Info DISM PID=2672 TID=2824 DismCore.dll version: 10.0.26100.8972 - CDISMManager::FinalConstruct 2026-08-22 19:04:37, Info DISM PID=2672 TID=2824 Scratch directory set to 'C:\10u\t_13053'. - CDISMManager::put_ScratchDir 2026-08-22 19:04:37, Info DISM Initialized Panther logging at X:\Windows\Logs\DISM\dism.log 2026-08-22 19:04:37, Info DISM PID=2672 TID=2824 Successfully loaded the ImageSession at "C:\10u\ddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd" - CDISMManager::LoadLocalImageSession 2026-08-22 19:04:37, Info DISM Initialized Panther logging at X:\Windows\Logs\DISM\dism.log 2026-08-22 19:04:37, Info DISM DISM Provider Store: PID=2672 TID=2824 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger 2026-08-22 19:04:37, Info DISM Initialized Panther logging at X:\Windows\Logs\DISM\dism.log 2026-08-22 19:04:37, Info DISM DISM Manager: PID=2672 TID=2824 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession 2026-08-22 19:04:37, Info DISM DISM.EXE: 2026-08-22 19:04:37, Info DISM DISM.EXE: <----- Starting Dism.exe session -----> 2026-08-22 19:04:37, Info DISM DISM.EXE: 2026-08-22 19:04:37, Info DISM DISM.EXE: Host machine information: OS Version=10.0.26100, Running architecture=amd64, Number of processors=8 2026-08-22 19:04:37, Info DISM DISM.EXE: Instance information: Parent process=X:\Windows\System32\cmd.exe, Parent process PID=1244 2026-08-22 19:04:37, Info DISM DISM.EXE: Dism.exe version: 10.0.26100.8972 2026-08-22 19:04:37, Info DISM DISM.EXE: Executing command line: dism.exe /English /NoRestart /ScratchDir:"C:\10u\t_13053" /Apply-Image /ImageFile:"C:\10u\t_13053\Windows11.0-KB5121003-x64.wim" /Index:1 /ApplyDir:"Windows11.0-KB5121003-x64" /NoAcl:all [2672.2824] [0x4144012c] 2026-08-22 19:04:37, Info DISM DISM WIM Provider: PID=2672 [CreateParallelDecodeInfo:(4036) -> Multithreaded decoding for chunked WIM is enabled!] (null) (HRESULT=0x0) - CWimManager::WimProviderMsgLogCallback 2026-08-22 19:05:05, Info DISM DISM.EXE: Image session has been closed. Reboot required=no. 2026-08-22 19:05:05, Info DISM DISM.EXE: 2026-08-22 19:05:05, Info DISM DISM.EXE: <----- Ending Dism.exe session -----> 2026-08-22 19:05:05, Info DISM DISM.EXE: I attach W10UI 10.62 (current) including suggested changes, so you can easily inspect them with your file comparison tool of choice and import them if you want. 3. uup-converter-wimlib Please correct me if I'm wrong, but there is no need to create any intermediate iso files (that includes boot.wim) if the user just want an install.wim containing let's say Enterprise 19041.1 from Pro UUP files. It would be nice if that kind of use case would be supported without creating unwanted additional files/folders. From UUP files to install.wim (only) with virtual editions, automated. EDIT: forgot to attach edited W10UI EDIT2: changed point where "DismRoot" is added to script "Path". Otherwise DismRoot is not used for dism commands before or during the menu.
@abbodi1406 A new PSF-specific processing tool, MSUpdateExtractor, has just been released. It has all the features of PSFExtractor and can also handle combined update files of msu, cab, wim, and psf. You can get the source code and download it at https://github.com/win-story/MSUpdateExtractor. I tried it out and replaced PSFExtractor in uup-converter-wimlib, and did all sorts of update integrations like usual. It worked really well, even a bit better than PSFExtractor. Hopefully, it can replace PSFExtractor used in the current tools.
PSFExtractor.exe is currently used only for 22000/22621 updates 22631 and later uses psfx.txt (powershell/.NET) to expand wim+psf files extracting cabs (SSU for example) may require dpx.dll from the target build DesktopDeplyment.cab depending on host os version 25398 introduced PA31 delta format, which require UpdateCompression.dll (can be renamed to msdelta.dll) to support recent 2026+ updates DesktopDeployment.cab include dpx.dll which now also have msdelta functions too
I know the principle. But I mean, all the features of PSFExtractor are supported in MSUpdateExtractor. When you use PSFExtractor, you need to carry its configuration file along with the exe, but with MSUpdateExtractor, you don’t need an extra configuration file.
I recently started to see printmanagement modern uwp app on startmenu is there an entry we can add to "CustomAppsList" to remove it?
BypassESU-X v2 - Add support for build 14393 (LTSB/Server 2016) Spoiler hopefully they don't use the old esu component name