MSMG ToolKit

Getting this while trying to select pro - Cant convert esd to wim. And my other install.wim, i cant even select pro.

 

Same I think its just an issue with Pro?

 

Is there any difference between the ISO converted from ESD and the direct ISO file ?.
I mean is the ISO converted from ESD (
19041.264.200511-0456.vb_release_svc_refresh_CLIENTBUSINESS_VOL_x64FRE_en-us.esd)
better to service with MSMG 10.0 than en_windows_10_business_editions_version_2004_updated_may_2020_x64_dvd_aa8db2cc.iso ?
Thank you.

 

i have the same issue

 

I am assuming you are working with the latest stable Windows 10 build 2004 / 19041.264?

In the ToolKit folder, check Bin\Lists where you will find the file RemovePkgsList_W10_10.0.19041_Template.txt. Use this to build up your RemovePkgsList.txt file.

You have these in the above list which you want to remove:

Code:

Advertising Xaml
Alarms & Clock App

Therefore add the below to RemovePkgsList.txt:

Code:

ToolKitHelper:AdvertisingXaml
ToolKitHelper:Alarms

You will quickly learn.

 

I believe your ISO has multiple editions, but I have extract only Enterprise from the ESD.

 

Is that possible to extract the Enterprise part alone from the ESD ?. Kindly let me know the procedure. Thanx

 

Using the ESD Decrypter I linked to earlier, yes it possible.

 

1909 19H2 18363.836

And, what about CallShellApp? Does ToolkitHelper support its removal? I ask because the codeline is not in the script.
If I add the following commands, would it work?

Code:

           call :RemoveWindowsComponent "%InstallMount%\%%i", "Call Shell App", "CallShellApp"
           call :RemoveWindowsComponent "%InstallMount%", "Call Shell App", "CallShellApp"

And, if you remove Your Phone and People from that app, I supposedly believe it will lose its function.

 

I used the ESD Decrypter from Feartamixg - Extracted the Pro install.wim and I was able to then load up the source image.

This is great, I was looking for this.

I used the above ESD Decrypter - Extracted my install.wim and was able to select the source.

 

Yes, Done.

Code:

===============================================================================
              MSMG ToolKit - Display WIM Image Information
===============================================================================

Reading Image Information...

===============================================================================
| Index | Arch | Name
===============================================================================
|   1   | x86  | Windows 10 Pro x86
|   2   | x86  | Windows 10 Home x86
|   3   | x86  | Windows 10 Education x86
|   4   | x86  | Windows 10 Enterprise x86
|   5   | x86  | Windows 10 Enterprise 2015 LTSB x86
|   6   | x64  | Windows 10 Pro x64
|   7   | x64  | Windows 10 Home x64
|   8   | x64  | Windows 10 Education x64
|   9   | x64  | Windows 10 Enterprise x64
|   10  | x64  | Windows 10 Enterprise 2015 LTSB x64
===============================================================================

Press any key to continue . . .

Enterprise & LTSB does not install. It says License Agreement is missing but it is installed with edition specific product key. So I want to predefine product keys for each edition in setup so as to prevent product key prompt during setup and also Enterprise install without entering key.

 

I think the toolkit is running too fast, too many users and too many problems for everyone, and we have to understand that only few people contribute their knowledge to msmg, we should go in order, because we leave behind something that we can integrate into a previous edition, to remove something in a newer edition, Do we think how many daily messages should msmg read and give us the answer we expect? Dear msmg, take your time so that your precious instrument continues helping us, if I am wrong I apologize to all.
Traduced with Google translate

 

I think the issue is that users do not understand some basic knowledge and ask the same questions over and over. An FAQ would go a long way for this project, but I'm not the person to make that...

Another big issue is people don't understand how complex removing something can be. In many cases simply disabling a component is not only easier but a lot more stable. Windows Defender is a good example of this. Removing it is a bad option, disabling it is better. It's not like it takes up a lot of space so there really is no point in doing that.

The importance of certain other components is not fully realized by so many people. Windows Firewall for example. If you understand how it works and why it exists you wouldn't even think about removing or disabling it. But again since people don't understand the full implications of these requests they think it's not going to be a huge problem.

I greatly respect the efforts of MSMG and do understand the desire to strip down windows to it's "Core" though. Looking at the list of components that can be removed it's honestly quite amazing what has been achieved thus far!

 

@InstantAli3n Can I disable components with the toolkit?

And if it's a bad idea to remove it, then it's probably not a good idea to include in the template. Just food for thought.

I think an FAQ would indeed help. Reading through 800 pages is just not very effective.

 

The file name should be RemovePkgsList.txt.

 

@MSMG

Hello, i have a question:
In the RemovePkgsList method, the ToolkitHelper initialization procedure, has to be done for each component seperately? Can't it just be initialized once in the beginning and remove all the components afterwards?

This would definitely improve the speed of removal, if it is possible.

Thanks

 

Do you have a headache?

 

you are sick?

 

You need to login to view this posts content.

 

You're the one not understanding how it works when it's pretty simple yet you get pretty feisty at other people

and he did state the correct answer. Put what you want in that text file and it will get removed. If it's not in the template then it probably can't be removed or not recommended.