https://forums.mydigitallife.net/threads/abbodi1406s-batch-scripts-repo.74197/page-214#post-1923263 fix manually, or use v10.63 for now
Thanks. That worked for preview update KB5124010, but not when I swapped it out for the 9/14 OOB security update (KB5129195 26x00.9457).
https://pixeldrain.com/u/6uEcTyF6 - https://download.ru/files/SLmigSiE W10UI-10.64u: - fix the missing lcuwpe in line 1652 - check and force LCU msu for boot.wim only if the integrated LCU is not Baseline === https://pixeldrain.com/u/q272hrR4 - https://download.ru/files/UzbDaf8H W10UI-10.64z: - above fixes - precheck boot.wim to avoid unnecessary LCU expand, or copying LCUs msu to temp directory when the boot.wim contain integrated non-Baseline LCU: if the target is mounted boot.wim or direct boot.wim file, LCUmsuExpand value will be auto changed to 3 if the target is distribution (iso), LCU msu will be used for boot.wim, regardless LCUmsuExpand original value
I will test again with your latest uploads. After initially making your suggested fix on line 1652, it integrated KB5124010 properly, but when I ran the fixed version with KB5129195, I saw it was again missing during the boot.wim phase. I tried to reproduce the issue another time but then it started working, so I'm not sure what I did wrong. Maybe I confused two runs. If I don't post again, assume I figured it out.
abbodi1406, how can I forcefully integrate LCU into Winre.wim in 26340 using uup-converter-wimlib? When I change the LCUwinre =1 in the ConvertConfig.ini file, nothing happens, as if the designation =0 is used. Everything goes smoothly when integrating into 19045 or 22631.
You can't even if i add support for it, LCU msu is designed to skip winre it would work only if LCUmsuExpand=1 is active but for 26340, expanded LCU installation fail anyway why do you want to bloat winre.wim with LCU? SafeOS update is already mini LCU
Thank you for the clarification. I’m just seeing that the original 26340 images in Winre.wim contain LCU, and MumX is also needed there. Perhaps this will soon change the entire update in the future, for 26100 and above.
Thanks for the fixes. I noticed one issue on line 757 as I use wimlib. In the for loop command, the first and last tokens are both double-quoted, so cmd.exe will remove the first and last character, leading to a malformed command and the message "The system cannot find the file specified." is displayed. The command should be quoted again: Code: if %_wlib% equ 1 for /f %%# in ('^"!_wimlib! dir "!_w_!" 1 --path=Windows\Servicing\Packages ^| findstr /i "Package_for_RollupFix.*.mum"^"') do (
From the log, they already have a feature or a setting check that ignore the ignored LCU msu condition for winre.wim Code: WinRE OnePackage Servicing allowed; ignoring condition that blocks WinRE LCU install so i guess i should allow LCUwinre for 26100+ and let LCU msu decide unfortunately yes, MumX thing will probably reach Retail branch sooner or later
Non of the changes required for UUP i did not change LCUwinre behavior for now will do some tests on 26340
Hello @abbodi1406 In the past, I made an opinion about Windows NT 10.0 Updates Installer (W10UI) and Windows NT 10.0 Multilingual Creator (W10MUI). It is known that W10MUI includes W10UI inside. The problem is W10UI is updated more frequently than W10MUI, so if someone wants to create a multilingual and updated ISO, both scripts (W10MUI and W10UI) must be used (because the W10UI inside W10MUI is an ancient version). So, there are some approaches that could be made to improve this situation: Merge both scripts in a single one (which would be very nice). There would be a W10UI with multilingual optional features that would be updated frequently. Separate both scripts. Don't include W10UI inside W10MUI, so the user will use the latest version of scripts (separately). Thanks, dear abbodi1406 .
- Merging is impossible - i could add a simple updater or downloader script for latest W10UI (using bitsadmin or powershell Invoke-WebRequest)