MSMG ToolKit

I'm looking for it too, if you find it please let me know, because there is some information that can be confusing for me

 

Well not confusing per se, we can google all components, however, 50 % of posts in this thread are dependency problems, so I would like to know behind the scenes what am I actually deleting, before completely rulling out that X feature is not necessary on my Windows installation.

 

does it restore any components that you remove or jeopardize the OS when running the command to fix ghost error message??

 

@boo123 no and no.

 

Hi MSMG ;
I updated my 2021_LTSC base iso to the Version: 10.0.19044.3086
After integrating all updates , i used MSMG Toolkit 13.4 to crop the iso
I used 2021_LTSC remove text file to crop all the list items except Notepad,Calculator and Windows Photo
After installing Windows 10 LTSC , i saw that "Taskbar and Startup menu" is not working anymore and i can not open any icon on taskbar such as Realtek Audio , Network etc. I tried to crop the ISO two times and result is the same
I will be glad if there is a solution or i will go back to Toolkit 13.3
Thank you

Here is the error image file



It is in Turkish and it says
Critical error
Your start menu is not working. We will try to fix it with your next login

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Read about the new components available for removal. Just dont remove them.

 

I'm saying people will face constant frustration if they try to create an MSMG build with the hope of trying to later add significant Windows upgrades and security fixes without breaking things. It's better to create the best Windows image you can and keep a backup copy. You ever see a house, where people constantly remodel it in the hope of making things better but, instead, it looks a mess and nothing works like it should. That's what I'm talking about.

 

@MSMG inTerActionVRI
You could not put the general driver folder, that is, instead of c: \ users \ dfa \ desktop \ toolkit_v13.4 \ drivers \ instal: w7, w10, w11y w81 a single one that covers all the four editions of Windows because if You have to put the drivers in each edition are a lot of GB.
Thank you

 

Yes brother you are right
I checked the removal list and i saw that there is new item on the list which is "StartMenuExperienceHost"
I think i should not remove it , i will try again
Thank you so much

 

i just want to make a clean AF msmg build of the new windows enterprise LTSC 2021 iso. I usually skip updates or only install security fixes or security updates.

 

hi,
@MSMG thank you for answering my question sir,
I am very greatful.
for others.
make your custom images.
when a new version of windows 10/11 getts released,
customize that iso.
when new components are added.
perform a inplace upgrade using the customized iso.
should be okay.
Majid

 

@MSMG, I sent a PM.

 

@MSMG,

So from what I understand, our discussion could be beneficial for your work, which is good news!

Do you think you can do something about WMR and RDC Resetbase issues?
I have finished what I wanted for my script and it looks stable enough, but I have not been looking into further testing on possible Resetbase fixes that would work for everyone (normal update deployment and my preferred way).
I should be able to proceed with it these days.

The below part is not so important, please feel free to ignore it.

Spoiler

As I cannot see inside your black box, it is difficult to understand what you are exactly doing even with your descriptive wording.

The Readme.txt specifies twice about the requirement of source image with specific CU integrated is needed for component removal.

This is what I found in readme.txt: Windows 10 v1809/v1909/v2004/v20H2/v21H1/v21H2/v22H2, Windows 11 v21H2/v22H2 - Component Removal requires a source image with supported cumulative update integrated.

Taking the changelog into account as well, where you specify for each month the CU support, which is built up on the previous releases (hence cumulative) literally tells me that everything that you tested for earlier updates has to work for the latest release of yours as well:

The ToolkitHelper contains only the list of files and registry keys to removed or modified and the functions to execute that list

This is exactly what I was talking about it in one of my latest post with the XML stuff:
- You already tested the CUs from the past as per the changelog, this implies that no restesting is needed
- These Registry keys and files are pretty much a fixed list (minor additions to be expected when they get updated, but as I wrote, the changes would be pretty much all the time within the files themselves or under the keys that you are already touching, so the impact should be negligible)

Again, let me show one of the many ways this could be handled, I will try to use an example as much explicit as possible, but the values referenced are pure fictional and should not be used for any purpose by anyone:


<BulildNumberMin>19044</BulildNumberMin>
<BulildNumberMax>19045</BulildNumberMax>
<MinimumPatchVersion>1</MinimumPatchVersion>
<MaximumPatchVersion>3086</MaximumPatchVersion>
<Component>WindowsMixedReality</Component>
<ToolkitActionList>

<1>reg delete HKLM:\TK_COMPONENTS\CanonicalData\Deployments\dual_percep..nsixdof.inf_31bf3856ad364e35_10.0.19041.1*</1>
<2>reg delete HKLM:\TK_COMPONENTS\DerivedData\Components\amd64_dual_perceptionsimulationsixdof.inf_31bf3856ad364e35_10.0.19041.*</2>
<3>rmdir /s /q c:\TK\mount\1\windows\amd64_dual_perceptionsimulationsixdof.inf_31bf3856ad364e35_10.0.19041.*</3>​

</ToolkitActionList>

You test it for each month's CU, and when it passes, you add store the MaximumPatchVersion to support that CU, while it also reflects the past.
If something is added only recently by you for removal, you do a conditional check as part of the step added to ToolkitActionList, which makes it backward compatible, where the data did not exist.

When I perform the cleanup (removal of the newly added or re-added components), I refer to fixed paths - versioning, which can be dynamic in the name does not matter when using pattern matching, it works for any version. When a component gets a new Registry path as part of the enhancements, I simply add it to the processing list, but there is very little hardcoded reference, or most likely just a new parent path if they follow their own naming convention patterns, so mostly I work with parent paths and manage the relevant child keys/files dynamically based on some naming convention.
I cannot imagine how you could do it differently - and you may say my imagination is very limited.

Additionally, I personally would not work .1 version images, i.e. anything which is not officially released.
One of the reasons would be that I assume that the Insider images would contain data/feature that was removed prior public release.
On the other hand, official support from your end should start from the first public release, anything, that comes later (CU, updated public release, which is essentially a CU updated image as you know) is pretty much handled based on the above example.
People can only access the public releases anyway (I don't understand the fuzz about ESD, and it looks like I do not need it currently).
No need to keep millions of images to test at all.

Here is what I would do when a new component removal support is added (like InputApp System App for instance), focusing on Windows 10 21H2
1. Test it on the CU when it was introduced (KB5026361, v10.0.19044.2965)
2. Test it on the first public release image (v10.0.19044.1288)

If it works on both, it works on everything inbetween.
And it is not like people will be using KB5019959 (v10.0.19044.2251) to integrate these days.

I will not be pushing on this topic furthermore as Windows 10 21H2 with official release version 19044.1288 seems to be working as I need it to.
But perhaps you got some ideas for compatibility support, which may also ease your work again.
I don't care how much it does not work with Windows 11, from the looks of it, it will be short-lived anyway (if Windows 12 is really coming next year), if others want to / need to struggle with it, that's just... sad.
To be fair, improvements require gambling on new ideas, given how good every 2nd major release worked out historically, I am sure things will be better for the next major release.

 

@MSMG The Thin PC apps have been deleted?

 

Thanks