via running the StartComponentCleanup Schedule task manually after every PT? disabled otherwise? That's the safest option for live (installed) OS? where these [5] & [6] options are located? UUP convertconfig.ini? I use this configuration for the latest 2xxx branch ISO, hope that's correct & would not cause any OS update related issue
My uptodate ISO creation logs are from W10UI, not UUP>ISO but in UUP>ISO it's what you show, [5] = Cleanup and [6] = resetbase. Code: ======================= W10UI v10.16 ========================== [1] Target (x64): "F:\W11UI\22000_Work_x64_US" [2] Updates: "F:\W11UI\22000_Updates_x64" [3] DISM: "Windows NT 10.0 ADK" [4] Enable .NET 3.5: YES [5] Cleanup System Image: YES [6] Reset Image Base: YES [7] Update WinRE.wim: YES [8] install.wim selected indexes: 2 / [K] Keep indexes: Selected [M] Mount Directory: "c:\W10UImount_4956" [E] Extraction Directory: "c:\W10UItemp_29580" ============================================================ Change a menu option, press 0 to start the process, or 9 to exit:
Okay got it, @Enthousiast what's the main difference between cleanup [5] & reset base [6] & why you did run both for all the versions of ISO except 1809? If I create ISO via UUP script in every month PT, what'd be the suggested way to run the configuration? Running both, the Cleanup [5] & resetbase [6], or only run the cleanup [5]?
[5] compresses superseded components and [6] removes them entirely [6] can't run without [5]. Check the scripts and the info at the option. Don't use UUP for every updated ISO, just create a .1 base ISO (no updates integrated) once and next use a copy of that with W10UI to update it monthly or whenever you want. As i said many times before, personally i run [5] & [6] on all sessions except for 1809.
Thanks for clarifying the matter of no 5 & 6, I actually do the same, i.e.replace all the new can packages in UUP folder & run the convertconfig.ini script, I hope it does the same job as W10UI do, I presume by base ISO, you mean (& use) the 19041.1 or something else you're using & would like to recommend here as 20H1 is now officially discontinued. On another note, can anyone share the link of Windows Feature Experience Pack 120.2212.4170.0? I've not seen anything regarding this new FxP here in MDL
well, so now like SSU, FxP is also embedded with LCU, where did MSFT mention this? Any official or unofficial source of this info I mean? & I've updated to the latest v1503 in the 21H2 system but the FxP version hasn't changed. What could be the reason for this? Server-side (batched) rollout?
May i know the W10UI setting "SkipBootFiles =1" if i not use ISO is it need to change to "0" ? i just use USB to install on UEFI only
so just leave it "1" right, is it wont update efisys.bin, bootmgr.efi , bootmgr , if change the setting on "0" has any problem about it ?
skipbootfiles=1 will not update the bootfiles skipbootfiles=0 will update the bootfiles and then installs from USB most likely fail to boot on UEFI systems.
Any news about how to enable this new version of Windows FEP 120.2212.4170.0? Here, it still remains in the same version 120.2212.3920.0 after install lastest LCU.
I don't know what you're looking for. I haven't specifically searched, downloaded or promised anything anywhere. And here it is. Spoiler
Here FEP still installed in old version: Code: Edição Windows 10 Pro for Workstations Versão 21H2 Instalado em 10/06/2021 Compilação do SO 19044.1503 Experiência Windows Feature Experience Pack 120.2212.3920.0 <- ??? I don't know if it's necessary to apply a regfix or install another pack individually to enable this new version. Regards,
On both installs the store is present and untouched: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-675#post-1720648
Did not install it manually. So it really is a screw-up with KB5004393 specifically, tho the blame seems shared between Microsoft and the user that rushed to integrate the update meant for insiders