MSMG ToolKit

You can try the MSDN ISO's but still the problem is due to the CU which causes SFC error when cleanup-image is performed.

Will do more test which images are safe (UUP, MSDN, MCT ISO) but I'm sure the ESD is broken as it is a system prepared image with image cleanup done and has more file or folder duplication permission issues.

 

At first the DISM method was used since removing the package through it's mum file would also remove any updated files added by the LCU.

But starting with Redstone 5 the MS started combining many packages deep into other packages which made it impossible to use DISM to remove the components and also for some packages lost there packages mum files.

So the manual method was created and the manual removes in depth than the DISM and also can support shared components compatibility.

The only reason I kept the option to remove the components using the DISM was for people who use Windows 7 - Windows 10 RS4.

I would say the ToolkitHelper method is cleaner and yes if you are going to use DISM method then don't use the ToolkitHelper as the ToolkitHelper uses file or folder checking to known the component existence and if it doesn't find it then it may report the component has been removed already or may skip certain checks done for shared components compatibility.

But if you really want to use both the methods then first use DISM and then the ToolkitHelper method.

 

AppList uses the DISM.

 

The DISM and the ToolkitHelper uses different method to detect the package and so running the ToolKitHelper may not work properly.

 

At first I wanted to stick with Windows Apps and System Apps removal as it was sufficient for average users but then expanded the list to include privacy components and now it has Internet, Multimedia, Remote and System components (a total of around 103 components).

Right now, I'm not in a position to add more components as it requires more time, effort and troubleshooting to work on it which I can't do due to my poor heath and other issues personally I'm going through.

In future will add more components when my health and other things become better.

 

If it is a ESD source then you need to wait for the next update.

 

Updated the Toolkit to v10.8

Spoiler: Changelog

v10.8
+ Updated ToolKit's Bin folder with Windows 10 20H1 Insider Preview WADK (v10.0.20246.1) Tools.
+ Fixed a Bug in the Feature "Convert Windows Store ESD to WIM Image", where the ToolKit failed to process ESD to WIM Conversion.
+ Fixed a Bug in the Feature "Convert Windows ESD to WIM Image", where the ToolKit failed to process ESD to WIM Conversion.
- Removed the Convert Menu from Main Menu as it was missing the proper order of Toolkit functioning.
> Moved the menu items Convert Store ESD, MCT and Custom ESD to Source Menu as below

[5] Extract Source from Store ESD Image
[6] Extract Source from Media Creation Tool Image
[7] Extract Source from Custom Windows ESD Image

> Moved the menu item Convert ESD to WIM to Tools->WIM Manager menu as Convert.
+ Optimized the ToolKit code for "Integrate WHD Updates" Feature (Thanks to MDL Member : RaiyvaN).
+ Updated the Feature "Remove Windows Component" to support removing Edge Chromium and Windows Apps for Windows 10 Store ESD Source OS Images.
+ Updated the Feature "Remove Windows Component" to support Windows 10 Client v2004/v2009 (v10.0.19041.572/610/v10.0.19042.572/610) Source OS.
+ Fixed Typo Errors (Thanks to MDL Members : RaiyvaN).

Note: Even though the Edge Chromium gets removed from WinSxS for Store ESD source images but still the Edge will be present when the OS is installed and this is due to Store ESD image which is a System prepared image.