The Toolkit component remover is neither backward nor forward compatible it works only with the version to which it is updated to. If you use v572 then don't remove Internet Explorer and Kernel Debugging. If you use v610 then don't remove Kernel Debugging. Rest of the components can be removed, From next version will stick to released CU's only.
The cleanup-image is not done, when you perform the cleanup image the GHOST SFC error occurs for recent CU's.
If you perform Image cleanup and run SFC you get that error even if System Restore, File History or Windows Backup are not removed. This issue is present with recent CU's.
The delay in removing the components is due to a new version of code protector I have used to pack the exe. It takes time to unpack and then executes the command.
We can see many "cleanups" or cleaning leftovers during we use MSMG. Please, clarify to everyone here which exactly option you mean. I.e. the cleanups can be performed when Apply [6] or you mean do not use option in the [5] -> [8] Tweaks section? Which exactly option is restricted to be used with rescent CUs?
I meant [6] Apply -> [1] Perform Image Cleanup Please do check my earlier post here Performing DISM /Image-Cleanup /StartComponentCleanup is breaking SFC with recent CU's even if components are not removed. Will perform a fresh component removal test with 19042.572.201009-1947.20h2_release_svc_refresh_CLIENTBUSINESS_VOL_x64FRE_ru-ru.esd and report back.
Aaah... I thought you ran this command "as command" (outside MSMG) - I understood that message literally. Now your clarification make things much more clear. Thanks.
The Edge Chromium package used in 19042.572 is older than the current enablement package and that's why the Edge Chromium was getting skipped while removing. Will fix the issue.
@MSMG right now I'm doing the conversion from ESD to WIM but using Toolkit V10.6 in the W10 2004 image without any problem (I used the modified media creation tool) ...
I mean in v10.7, as random multi-index mode was added earlier the Store ESD-WIM conversion required a fix which I just added.
Hi ingviowarr I agree of course just think a little bit these components are essential within the operating system at least for me I NEVER removed them for this reason I never had any problems...
To summarize, we can consider the last ESDs (572) as broken by M$? What are recommendations then? Is it OK to use 20H2 Build 19042.508 (ISO) + Update integration up to 572 / 608 using the next MSMG build? (I suggest 572 / 608 choice will depend on Toolkit component remover support capabilities)
For time being - Get 19041.1 UUP Generated ISO (Set not to integrate .NET FX35 or any other updates) - Copy the below updates to WHD Update Pack folder Copy Windows Cumulative Update (KB4579311) file to <WHD\w10\<Architecture>\Cumulative> folder (E.g. <WHD\w10\x64\Cumulative>). Copy Windows Defender Update (defender-update-kit-x64.zip) file to <WHD\w10\<Architecture>\Cumulative> folder (E.g. <WHD\w10\x64\Defender >). Copy Windows Dynamic Update (KB4558130) files to <WHD\w10\<Architecture>\Dynamic> folder (E.g. <WHD\w10\x64\Dynamic>). Copy Windows Enablement Update (KB4562830) files to <WHD\w10\<Architecture>\Enablement> folder (E.g. <WHD\w10\x64\Enablement>). Copy Windows Flash Player Update (KB4580325) file to <WHD\w10\<Architecture>\FlashPlayer> folder (E.g. <WHD\w10\x64\FlashPlayer>). Copy Windows .Net Cumulative Update (KB4580419) file to <WHD\w10\<Architecture>\NetCumulative> folder (E.g. <WHD\w10\x64\NetCumulative>). Copy Windows Servicing Stack Update (KB4577266) file to <WHD\w10\<Architecture>\ServicingStack> folder (E.g. <WHD\w10\x64\ServicingStack>). Copy Windows Setup Media Update (KB4588844) files to <WHD\w10\<Architecture>\SetupMedia> folder (E.g. <WHD\w10\x64\SetupMedia>). Copy Windows WinPE Update (KB4579305) files to <WHD\w10\<Architecture>\WinPE> folder (E.g. <WHD\w10\x64\WinPE>). Use this windows10.0-kb4562830-x64_816fd030691161bfc9f892f0e9e1259e23a56c82.msu Enablement Update file. - Use Toolkit's WHD Update Pack Integrate menu to integrate the updates - Use Toolkit's Remove Windows Component using Pack List method to remove component (Don't include Internet Explorer and Kernel Debugging) - Don't run the cleanup-image since it breaks the SFC. - Apply and Save the Image. - Rebuild the Image. By the time next version will be released, there will be a new public CU released will update the Toolkit to same version.
well although i'm just a humble apprentice in the art of working with the code for now i came to the conclusion that Toolkit V10.6 is more consistent than the new one (V10.7) I may be wrong of course and I still hope that our master forgive but that's what i think at the moment