So if resetbase is specified, why are superseded files being compressed to only be deleted afterwards since I'm using 1607 and 1809?
It should only delete them when /resetbase is used in W10UI, afaik. On <1903 builds it will break the resetpc option.
I thought you said on 1903 and up, it gets broken. I don't have a problem with Reset PC being broken because I never use it. Backups are much better IMHO. The ini file states that component cleanup must be set to 1 in order to use resetbase. Why not just allow resetbase by itself, if a broken Reset PC is unimportant to the user?
No, i said for all under 1903, it will break resetpc, but for 1903 and up @abbodi1406 made it so that resetbase will skip CU components, so it won't break and there were some other psfx related reasons, iirc. /resetbase is an addition to the /cleanup-image dism command. /cleanup-image can run without /resetbase, not the other way around.
I did not mean resetbase by itself, I meant instead of running 2 separate commands only use the one that included the resetbase option. One command instead of 2.
Component Cleanup compression does not occur in builds prior to 1903. The 2 calls to dism occur because it is a workaround to allow resetbase in an offline image: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-251#post-1396708
That post was about the workaround for the disabling of resetbase, a few weeks after 15063 (1703) was released. On 1809 and up, when resetbase is enabled, and ran, it breaks resetpc, that's why the new workaround was introduced on 1903 (and because psfx updates already do some sort of rebasing), to do the resetbase for the other components (flash/dotnetfx) and exclude the CU ones.
Aside from the info, @AeonX linked at, there are still two options, because one offers only compressing of superseded components, takes longer and slightly less decreasing of wim size, and the other offers full resetbase, faster and slightly more decreasing of wim size, all depending on the amount of superseded components.
The problem with broken resetpc does not come since 1607 (or maybe even before) where is the reg trick DisableResetbase = 0 necessary to do the ResetBase? And the new workaround in 1903 was to avoid breaking future CU installations: https://forums.mydigitallife.net/threads/abbodi1406s-batch-scripts-repo.74197/page-39#post-1530461 From 1903 onwards ResetBase is no longer needed for Cumulative Updates but is needed for other updates. Although this will break future CU installation. So the workaround used by @abbodi1406 was to use the reg tweak SupersededActions = 3 to do CBS delta-compress of the superseded components. So from what I understand they are not removed but compressed. The /ResetBase done afterwards may be to mark the updates as permanent as explained in the other link I posted. More information here: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-419#post-1532957
@AeonX And still the resetbase option, when ran with 1809 will brake resetpc and cleanup won't. that's all i need to know about it all
Sorry for being dense, I'm new to this... If I get the latest localized LTSC iso and want to integrate all available updates using W10UI, do I need to download the x64 SSU, CU, flash, dotnet and LP files from this post only? Is this enough?
Thanks. Out of curiosity, is it normal that a 4 GB iso + 500 MB of updates (those 6 files mentioned in your post) results in a 10 GB iso?
Sorry, I probably forgot to delete the iso file after unpacking it. I've tried again: I installed ADK, extracted the localized LTSC iso (4.2 gb) to an empty folder, added the 6 update files for x64, then the W10UI files, and run the script as administrator. The resulting ISO is now about 6 GB... Log at pastebin.com/WjCFL8qa
You didn't use the cleanup or resetbase (latter is not advised to use on 2019 LTSC). I always use these W10UI settings on 2019 LTSC: Code: ============================================================ [1] Target (x64): "D:\W10UI\17763.1_Work_x64_NL" [2] Updates: "D:\W10UI\17763.1_Updates_x64" [3] DISM: "Host OS" [4] Enable .NET 3.5: YES [5] Cleanup System Image: YES [6] Reset Image Base: NO [7] Update WinRE.wim: YES [8] Install.wim selected indexes: 3 4 / [K] Keep indexes: Selected [M] Mount Directory: "c:\W10UImount_15918" [E] Extraction Directory: "c:\W10UItemp_26507" ============================================================ Change a menu option, press 0 to start the process, or 9 to exit:
Thanks! With all (LTSC + LTSC N) indexes enabled, the iso is now 5.2 gb. The cleanup option took an awful amount of time though... is it really needed, or is it only for reducing the file size?
The size should be around 4.2GB for n and non n, with cleanup image selected and yes it takes forever to finish. It's mainly used for size reduction, yes.