Thanks for the tutorial. Quick question though. In your first W10UI.cmd (when integrating updates into an ISO) you have Cleanup and ResetBase enabled. May I ask why you chose this and if you recommend it? If I then use that ISO to install windows to a PC, can that PC still use Reset this PC? (is that note for ISO images or for in-place upgrades)
Cleanup = compressing the superseded components. Resetbase = entirely removing the superseded components. For Win 11 22h2 it's not recommended to use any cleanup when you're planning on enrolling into the IP channels or manually installing Beta channel updates. Most users use resetbase (which will only work when cleanup is enabled) to reduce the install.wim file size (i.e. trying to fit FAT32 max. file size of 4GB) and also results in a smaller ISO file size. Only on 1809 builds the resetbase option will break the "Reset PC" option under Recovery in settings, but now only Server/Enterprise 2019 LTSC are the only supported 1809 SKUs this is getting less important.
There have been a few updates. If I'm building a public release of Win 11 (I guess 22631.xxxx), would I want to enable LCUwinre or UpdtBootFiles? (Currently I'm enabling Net35, Cleanup, ResetBase, WinRE, and ISO) As always, thanks for your contributions and your support!
In a few minutes the new monthly updates will be published and i will run W10UI to test all with my preferred settings: Code: :: target distribution, wim file or offline image :: leave it blank to update current online os, or automatically detect wim file next to the script set "Target=%~dp022621_Work_x64_NL" :: updates location :: leave it blank to automatically detect the current script directory set "Repo=%~dp022631_Updates_x64" :: dism.exe tool custom path (if Host OS is Win8.1 or earlier and no Win10 ADK installed) set "DismRoot=dism.exe" :: enable .NET 3.5 feature set Net35=1 :: optional, specify custom "folder" path for microsoft-windows-netfx3-ondemand-package.cab set "Net35Source=%~dp022621_SXS_x64" :: Cleanup OS images to "compress" superseded components (might take long time to complete) set Cleanup=1 :: Rebase OS images to "remove" superseded components (warning: break "Reset this PC" feature) :: require first to set Cleanup=1 set ResetBase=1 :: update winre.wim if detected inside install.wim set WinRE=1 :: Force updating winre.wim with Cumulative Update regardless if SafeOS update detected set LCUwinre=1 :: update ISO boot files bootmgr/memtest/efisys.bin from Cumulative Update set UpdtBootFiles=1