MSMG ToolKit

README FILE

its a step by step guide for every major build

before you ask, use the un-refreshed ISOs. use the forum search feature if you get lost or have questions

 

You need to login to view this posts content.

 

I was more or less talking about the specific things that should be integrated and which customisations should be made.

 

Sorry. Edit

 

If you could at least remove OneDrive via ToolKit
Thank you.

 

If I have Win10 1903 ISO (.30) and I want to use the toolkit (only remove default metro apps), but I ultimately want an ISO that when installed will be at 18362.175, what's the best way? ...use the toolkit to integrate the CU so I end up at .175, or would SVF work? If SVF, then would I apply the patch after the toolkit processing is done?

Thanks.

 

SFV would likely not work. Because to make a delta patch you must have a static source. The toolkit does not create a static source, to much variables.
Just integrate the CU and necessary SSU to get the image up to date.
Likewise, this will change monthly when a new CU is released by MS.

Cheers.

 

I am anxiously waiting for the next release that will allow me to delete system applications like Onedrive, Connect and Content Delivery Manager, for Edge I will find a way to hide it from the taskbar.
I thank MDL Developer very much for the time and passion you dedicate to this work.

 

I used for first time yesterday reasonably happy quick question how do you remove the xbox app and office app I selected to remove the office app but didn't seem to remove and no option to remove xbox apps I am using 1903

 

You need to login to view this posts content.

 

Windows 10 version 18362.30 is the most up to date version that's currently supported; however, windows components cannot be removed yet and MSMG is in the process of getting that function working. In saying that, default apps and programs can be removed and the ISO can be customised using the Customisation menu.

 

Thanks. So the latest version which I can strip to (almost) bare bones is...
17763.1? Refreshed .107, 253, 379?

 

Or maybe even 17134.1 or refreshed 112?

 

Thanks! After I posted, I thought integration made more sense, and that SVF is geared more towards converting between editions/SKUs, or bringing an image up-to-date.

 

SVF can be used for more purposes but it's only a file, made from a target file and a source file, mainly used for iso distribution.

For it to be used for updating an iso, you still need to create an updated iso and use it as target iso for svf creation combined with a source iso.

 

You can prevent Onedrive installation, by mounting the image registry and navigate to HKEY_LOCAL_MACHINE\TK_SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce and delete the onedrive install entry, this way it don't get installed - after windows install you can delete the onedrive startmenu entry from c:\Users\USERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\

/LR

 

Hopefully before 1909 or whatevr the next version is.

 

A couple of corrections to the ReadMe for 9.3.2:

copy the updates to <Updates\w10\<Architecture>> folder (E.g. <Packs\Updates\w10\x64>) ...should remove "Packs\"
[L] - Integrate Microsoft .NET Framework 3.5 ...this should be optional, right?

 

Thanks. So the latest version which I can strip to (almost) bare bones is...
17763.1? Refreshed .107, 253, 379?

Or maybe even 17134.1 or refreshed 112?

 

Why always when i try to integrate the .net framework 3.5 into Windows 8.1 image, apperars this error?
PS: I already put the folder NetFX35-w81-x64- into the folder "Packs".