Please pardon me, I am not a programmer, I am only a user. I want to understand the difference between W10UI and WHD-W7UI in this situation. They are both based on Updates downloaded by WHDownloader. Again, please excuse me for my incompetent question. I sent an identical reply to delMicron.
I don't say it enough, but I would like to take time to thank you for all the work over the years @abbodi1406, @Windows_Addict and our beacon @Enthousiast and many others who contribute in mdl and other support forums.
Standalone Check-Activation-Status.ps1 is updated with some enhancements https://github.com/gravesoft/CAS
Can multiple language packs generated by YAOCTRU be stacked together in the same folder so that the setup.exe from one language would not use the language specific cabs from another? for example SetupLanguagePack.x64.bg-BG.exe should not use pl-PL i641045.cab. edit: looks like it works fine
Another small fix update (the incomplete check prevented detecting Office 2010 on Windows XP) https://github.com/gravesoft/CAS
@abbodi1406 Does need to update W10UI to respond to this? https://support.microsoft.com/en-us...-manager-d4064779-0e4e-43ac-b2ce-24f434fcfa0f Copy the updated files from the "boot.wim\$index\Windows\Boot" folder end with "_EX" to Setup Media. Core part in "Make2023BootableMedia.ps1" Code: $ex_bins_path = $bootWimMount + "\Windows\Boot\EFI_EX" $ex_fonts_path = $bootWimMount + "\Windows\Boot\FONTS_EX" $ex_dvd_path = $bootWimMount + "\Windows\Boot\DVD_EX" Copy-Item -Path $ex_bins_path"\bootmgr_EX.efi" -Destination $global:Temp_Media_To_Update_Path"\bootmgr.efi" -Force -ErrorAction stop | Out-Null Copy-Item -Path $ex_bins_path"\bootmgfw_EX.efi" -Destination $global:Temp_Media_To_Update_Path"\efi\boot\bootx64.efi" -Force -ErrorAction stop | Out-Null Copy-Item -Path $ex_dvd_path"\EFI\en-US\efisys_EX.bin" -Destination $global:Temp_Media_To_Update_Path"\efi\microsoft\boot\efisys_ex.bin" -Force -ErrorAction stop | Out-Null New-Item -ItemType Directory -Path $global:Temp_Media_To_Update_Path"\efi\microsoft\boot\fonts_ex" -Force | Out-Null Copy-Item -Path $ex_fonts_path"\*" -Destination $global:Temp_Media_To_Update_Path"\efi\microsoft\boot\fonts_ex\" -Force -ErrorAction stop | Out-Null Get-ChildItem -Path $global:Temp_Media_To_Update_Path"\efi\microsoft\boot\fonts_ex" -Filter "*_EX.ttf" | Rename-Item -NewName { $_.Name -replace '_EX', '' } -Force -ErrorAction stop Copy-Item -Path $global:Temp_Media_To_Update_Path"\efi\microsoft\boot\fonts_ex\*" -Destination $global:Temp_Media_To_Update_Path"\efi\microsoft\boot\fonts" -Force -ErrorAction stop | Out-Null Remove-Item -Path $global:Temp_Media_To_Update_Path"\efi\microsoft\boot\fonts_ex" -Recurse -Force -ErrorAction stop | Out-Null
If they don't enforce it yet, neither W10UI will do but i could add it as part of "UpdtBootFiles" option
I would include this as a separate point. Otherwise it will only cause problems if someone doesn't remember it
W10UI https://files.catbox.moe/8wcgdr.zip uup-converter https://files.catbox.moe/vnxm6e.7z for testing some changes: LCUmsuExpand auto enabled for builds 26052+ UpdtBootFiles also update new UEFI CA 2023 boot files ResetBase for builds 26052+: set to 2 to run rebase cleanup after each LCU
So, the first two tests with W10UI are done. If you have an ISO built with KB5050009 (2894), then it runs without errors. However, if you build the same ISO with KB5050094 (3037), an error (source not found) occurs when integrating KB5043080 (1742) into the boot.wim. The script then continues to run. The error may also be due to the fact that I activated UPtBootFiles during the second test (CA2023). I'll have to test again later. I can provide the logs if required.
I'm a bit confused about SafeOS updates. Does W10UI apply this update to the Winre.wim in C:\Recovery\WindowsRE\? The update seems to be ignored by W10UI so I don't know where it would get applied unless it's for adding to an iso which I don't use.
After further tests I can say that the error with KB5043080 (1742) was caused by something else, it had nothing to do with the script. But one question arises: the script first executes /StartComponentCleanup and then /StartComponentCleanup /Resetbase. Can't this be done all at once? /StartComponentCleanup /Resetbase contains /StartComponentCleanup? Or not?
@Jens1976 Thanks for testing the issue with boot.wim is not new, and it depends on what current LCU is installed and if some cleanup is performed mostly, it's not very effective error since Win10 1709, the double commands are needed to work with SupersededActions registry however in Win11 24H2, cleanup behavior changed a little, but it's still best to keep both commands
No winre.wim is only updated for install.wim can't you see the drama and frequent updates / errors for applying SafeOS updates to current OS active winre.wim? it's not clean or easy, or possible all the time
I just don't know if it really makes sense with the 24H2. Spoiler Code: ============================================================== KB5043080 - 1742 (/StartComponentCleanup) The following actions will be performed: Regeneration Candidates: 0 Removal Candidates: 5716 Superseded/LDR (Delta Compression) Candidates: 962 Null-Delta Compression Candidates: Mutable file Candidates: 253 Boot-Recovery Candidates: 995 Backup regeneration candidates: 0 Deletion Candidates (Non Driver): 0 Driver Deletion Candidates: 0 WinSxS Orphaned Objects Candidates: 0 Manifests Orphaned Objects Candidates: 0 No Errors. ============================================================== KB5043080 - 1742 (/StartComponentCleanup /ResetBase) The following actions will be performed: Regeneration Candidates: 0 Removal Candidates: 0 Superseded/LDR (Delta Compression) Candidates: 0 Null-Delta Compression Candidates: Mutable file Candidates: 0 Boot-Recovery Candidates: 2 Backup regeneration candidates: 0 Deletion Candidates (Non Driver): 0 Driver Deletion Candidates: 0 WinSxS Orphaned Objects Candidates: 0 Manifests Orphaned Objects Candidates: 0 Error CBS Failed to load C:\Users\***\AppData\Local\Temp\SSS_3684e74f167adb0101000000b835a805\cmsofflineservicing.dll.: HRESULT_FROM_WIN32(127) Info CBS Warning: Failed to clean up noncommitted transactions. [HRESULT = 0x8007007f - ERROR_PROC_NOT_FOUND] No further cleaning. ============================================================== KB5050094 - 3037 (/StartComponentCleanup) The following actions will be performed: Regeneration Candidates: 0 Removal Candidates: 0 Superseded/LDR (Delta Compression) Candidates: 168 Null-Delta Compression Candidates: Mutable file Candidates: 18 Boot-Recovery Candidates: 354 Backup regeneration candidates: 0 Deletion Candidates (Non Driver): 0 Driver Deletion Candidates: 0 WinSxS Orphaned Objects Candidates: 0 Manifests Orphaned Objects Candidates: 0 No Errors. ============================================================== KB5050094 - 3037 (/StartComponentCleanup /ResetBase) No plan Error CBS Failed to load C:\Users\***\AppData\Local\Temp\SSS_46fecc07197adb01010000005434f02c\cmsofflineservicing.dll.: HRESULT_FROM_WIN32(127) Info CBS Warning: Failed to clean up noncommitted transactions. [HRESULT = 0x8007007f - ERROR_PROC_NOT_FOUND] No further cleaning; stops at 70%. (Retained earlier scavenge flags 103 and skipped Scavenge) ============================================================== Resetting OS image base... ============================================================== /StartComponentCleanup No plan - No further cleaning (Retained earlier scavenge flags 103 and skipped Scavenge.) Error CBS Failed to load C:\Users\***\AppData\Local\Temp\SSS_46fecc07197adb01010000005434f02c\cmsofflineservicing.dll.: HRESULT_FROM_WIN32(127) Info CBS Warning: Failed to clean up noncommitted transactions. [HRESULT = 0x8007007f - ERROR_PROC_NOT_FOUND] /StartComponentCleanup /ResetBase No plan - No further cleaning (Retained earlier scavenge flags 103 and skipped Scavenge.) Error CBS Failed to load C:\Users\***\AppData\Local\Temp\SSS_46fecc07197adb01010000005434f02c\cmsofflineservicing.dll.: HRESULT_FROM_WIN32(127) Info CBS Warning: Failed to clean up noncommitted transactions. [HRESULT = 0x8007007f - ERROR_PROC_NOT_FOUND] ============================================================== /StartComponentCleanup /ResetBase after /StartComponentCleanup ends only with a non-fatal error, after the scavenger skipped any further action due to the scavenge flags. Just /StartComponentCleanup does any usefull. But apart from the cleanup, W10UI works so far. Even with the CA2011 revoked, a clean installation and an inplace upgrade works fine. No errors found. Testet with W10UI 10.50.