The same thing happens to me. Trying to remove Components of Windows 10 Enterprise 2016 LTSB x64 . When I click on [4] Remove and on [1] Remove Windows Components, nothing appears to be removed ...
1) I have already specified that I won't be providing support for using other tools along with Toolkit, I do recommend you to stick with one tool for the component removal. First Logon Animation is a component which can be either removed or just disabled using a tweak, the Toolkit just removes the component but NTLite provides both the options to either remove or to disable. Since many components doesn't have a proper packages and so based on the previous packages info, the component removal is worked out and still many component removals do need further tuneup for complete removal. 2) Do integrate the updates after component removals and when you integrate updates do integrate the SSU first and then the CU. For RS5 the component removal requires the WinSxS files/registry to be intact and so it is still under testing to adapt to the WU. I will test the Windows Update CU install with an image with a CU already been integrated and report back. 3) Yes you can install the Apps on live system using the appropriate appx + license files. The ToolKit doesn't support Live system servicing. 4) Again my answer is the same as 1), both tools work differently.
My plan was to release the update with support for all languages but the work is not complete yet and was sick past few days. For another one week there won't be any info of update but if I do fix the IE bug then will release a small update in between.
What's there to get confused? Code: Windows 10 RS5/Server 2019 Usage Order: ======================================= [A] - Select the Source Images using [Source->Select Source from Source <DVD> Folder] menu. - <Optional> If also required to Service Source Boot/Recovery Images then Choose Yes when asked to mount. Note: The Toolkit requires a Windows Installation Image to be in a .wim format for servicing. [B] - <Optional> Integrate the Windows Language Packs (Language Packs + Language Features Packs + Winpe Language Packs) using [Integrate->Windows Language Packs] menu. Note: You need to download the Windows Language Packs for MSMG ToolKit which contains the required files (win-lp+lfp+winpe-lp). Copy the Windows Language Pack files to <Packs\LangPacks\w10\<Architecture>\<LanguageCode>> E.g: <Packs\LangPacks\w10\x64\en-GB>. Windows Language Packs for MSMG ToolKit is uploaded only on request basis due to low upload speed here. [C] - <Optional> Integrate the Windows Drivers using [Integrate->Windows Drivers] menu. Note: Copy the Driver files/folder to <Drivers\w10\<Architecture>> folder. [D] - Integrate all required Windows Features (Except Microsoft .NET Framework 3.5) using [Integrate->Windows Features] menu. Note: Some Packs for MSMG ToolKit are not included within the ToolKit Archive due to it's size and instead they are provided separately. You need to download the required packs and extract them to the Packs folder as specified below. Dart_W10.7z (Extract the folder DaRT inside the Archive to Packs folder, so that it should be like <Packs\DaRT\w10). Games.7z (Extract the folder Games inside the Archive to Packs folder, so that it should be like <Packs\Games). MediaFeaturePack_W10.7z (Extract the folder MediaFeaturePack inside the Archive to Packs folder, so that it should be like <Packs\MediaFeaturePack). [E] - Cleanup the Source Image using [Apply->Cleanup Source Images] menu. [F] - Remove all required Windows Components using [Remove->Remove Windows Components] menu. [G] - Integrate Windows Updates/WHD Update Pack using [Integrate->Windows Updates->Windows Updates/WHD Update Packs] menu. The ToolKit supports updates either in .msu/.cab format. For Windows Updates Integration you need to copy the updates to <Updates\w10\<Architecture>> folder (E.g. <Packs\Updates\w10\x64>). For WHD Update Pack Integration you need to copy the WHD Updates Packs files for Windows 10 <Packs\WHD\w10\<Architecture> folder according to the category. Copy Windows Cumulative Update file to <Packs\WHD\w10\<Architecture>\Cumulative> folder (E.g. <Packs\WHD\w10\x64\Cumulative>). Copy Windows Dynamic Update files to <Packs\WHD\w10\<Architecture>\Dynamic> folder (E.g. <Packs\WHD\w10\x64\Dynamic>). Copy Windows FlashPlayer Update file to <Packs\WHD\w10\<Architecture>\FlashPlayer> folder (E.g. <Packs\WHD\w10\x64\FlashPlayer>). Copy Windows ServicingStack Update file to <Packs\WHD\w10\<Architecture>\ServicingStack> folder (E.g. <Packs\WHD\w10\x64\ServicingStack>). Copy Windows SetupMedia Update files to <Packs\WHD\w10\<Architecture>\SetupMedia> folder (E.g. <Packs\WHD\w10\x64\SetupMedia>). Copy Windows WinPE Update files to <Packs\WHD\w10\<Architecture>\WinPE> folder (E.g. <Packs\WHD\w10\x64\WinPE>). [H] - Integrate Windows Setup Media Updates using [Integrate->Windows Updates->Windows Setup Media Updates] menu. [I] - Cleanup the Source Image using [Apply->Cleanup Source Images] menu. [J] - Integrate Microsoft .NET Framework 3.5 Feature using [Integrate->Windows Features->Microsoft .NET Framework 3.5) menu. Note: You may have to re-integrate Windows 10 Cumulative Update again to update Microsoft .NET Framework 3.5 Components or You can skip this and the Windows Update will offer a 50 MB update to update Microsoft .NET Framework 3.5 Components. [K] - <Optional> Integrate all required Windows Custom Features using [Integrate->Windows Custom Features] menu. [L] - <Optional> Customize the Image using [Customize] menu. [M] - Apply & Save Changes to Source Images using [Apply->Apply & Save Changes to Source Images] menu. [N] - Re-Build Source Images using [Apply->Re-Build Source Images] menu. [O] - Install the OS. [P] - Perform DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase once. And now with new .NET cumulative update the step [J] needs to use .NET cumulative update integration instead of normal CU.
Starting with v8.9 the component removal for Post Windows 10 RS5 has been temporarily removed, so use v8.8
Yeb, do take care of yourself, I'm really saying. I, @ffs_ and @nosirrahx are most happy to hear such updates from you.