MSMG ToolKit

So, what I'm getting from your comment is:
1. Remove all other not desired components (except Edge) using the regular toolkit method
2. Put only the Edge components in the package list file, then "remove Windows components using package list"

The normal toolkit removal method seems to work fine for everything else, but it seems to not remove Edge completely. Can I mix the 2 removal methods here?

 

You can remove only EdgeChromium using toolkit method by keeping only EdgeChromium in RemovePkgsList
After saving the image you can do whatever you want with it.

 

But does the order matter? I mean, does it matter if I use the toolkit helper/package list last rather than first? I just want to make sure that the order of removal by either method doesn't make a difference. My idea is to remove all other components via the toolkit's GUI, then use the toolkit helper for Edge only. And then clean up and save the image as the last step. I never integrate updates or features (via the Packs folder), I use the toolkit for removal only. I'd rather not bloat 10 any more than it is by adding to it. I add stuff as I need it, only after the OS is installed.

 

After removal using one of the methods you should save the image and then apply another method.

 

Why do you think so? Please explain the need to save the image before using the second method.

Of course, everyone can do as he thinks necessary, or as he likes. But I, for example, never do that. I don't see any need for this. Or I do it very rarely, in cases when I need to save a certain state of the image as a backup, before applying the second method (for example, DISM).

 

Let's wait for MSMG, maybe I was wrong...

 

Removing a component from the Toolkit component removal menu, and deleting using a custom list is not a mix of removal methods in the full sense. Since in both cases the Toolkit uses the ToolkitHelper method (ToolkitHelper.exe ).

As an experiment, of course, you can try to remove edgechrome using a custom list, after you have already done it using the Toolkit components removal menu in order to check whether there will be a difference, that is, whether the unnecessary EdgeChromium shortcut will be saved or deleted. Nothing terrible will happen.
Probably, the component will simply not be found, since it has already been deleted.

Methods mixing can be called the joint use of DISM and Toolkit Helper methods to attempt to remove the SAME components. And it really shouldn't be done in order to avoid errors. There is a warning about this in the method selection window in the Toolkit.

 

If components are deleted using the Toolkit component removal menu, a second attempt to delete the same components using a custom list (RemovePkgsList.txt using the ToolkitHelper method), or in the reverse order, actually does not make any sense, since in both cases the same method of deletion is used - this is the ToolkitHelper method (ToolkitHelper.exe ). Usually the user uses the method that is more convenient for him: the selection of components in the menu or a pre-prepared list.

As for the need to use the DISM and ToolkitHelper methods together to remove DIFFERENT components, @MSMG recommends using the methods in the following order:
1. DISM method
2. ToolkitHelper method
___________________

As for me, in the process of working with Toolkit, based on my experience and observations, I have an alternative opinion about this, I have outlined it here. That is, I always use methods in the following order::
1 ToolkitHelper method
2. DISM method

(The results of my tests are in some of my other posts).

 

Try to find it here:
%appData%\Microsoft\Windows\Start Menu\Programs

 

I advise you to use the component removal sequence by lists "RemovePkgsList.txt", I do it like this:
1- First use ToolkitHelper.exe method
2- Then I use the DISM method

Doing it this way I never had any problems with my images. always worked just fine

 

You don't need to do that, you can use the ToolkitHelper method, then the DISM method without saving, I recommend always saving the image before applying some new feature, such as for example: .Net 3.5

 

I will build a new ISO later today and try it in a VM.

Does removing via package list (Toolkit method or dism method) remove additional components that aren't covered in the GUI? I mainly use 10 as an OS for running non-UWP desktop programs. Ever since MS introduced UWP apps with Windows 8, I always thought it was the stupidest thing. They should have just left Windows 7 alone and continued to improve on it as a baseline. Everything from 8 going forward represented a stark departure from how old school users like me think Windows should be. In reality they were just trying to become more like mobile OSes (Android and iOS) by introducing "apps".

 

This may be resolved by applying tweak in the customize menu.
Import Start Menu Layout

Manualy:
You can add:
.\Toolkit\Bin\XMLs\DefaultLayouts.xml
.\Toolkit\Bin\XMLs\LayoutModification.xml
directly to:
%AppData%\Local\Microsoft\Windows\Shell
Replacing what is there when necessary.

Respect This Rule:

As @graver.x said.
Respecting, at least, this rule is of fundamental importance.
Putting your experience is also important along with the list of components removed in both lists.
But let each tester take his own tests, made it clear that the rule is this. And that can be done different, on your own and risk.
At first, everything looks ok and with time of use, installing other software, you eventually identify issues. The gamers who play several generations from 1990 onwards are that they identify more problems.

EDIT: But above that, what MSMG always said, "Opt for one method, in the same image being serviced on."

 

You need to login to view this posts content.

 

From my own post, friend:

"I'm running the latest TK, and have removed all Edge components. My source is 10 Enterprise LTSC, I believe it was released around November/December 2021 (not sure on that, but its' checksum matches what I've seen elsewhere)."

I did *IN FACT* specify 2021.