can we add something in the readme file for this? this gets extremely old fast when people don't forum search sorry in relation to people saying it doesn't work or gives errors and we find out they are using refreshed images. I typed up something just as an example. Feel free to use it if you want: MSMG Toolkit is designed to only work with original, non-refreshed, images. Windows 10 1507 (Initial Release) – 10240.16405 Windows 10 1511 – 10586.3 Windows 10 1607 – 14393.10 Windows 10 1703 – 15063.138 Windows 10 1709 – 16299.19 Windows 10 1803 – 17134.48 Windows 10 1809 – 17763.1 Windows 10 1903 – 18362.1 If you need to find any of the above mentioned ISOs, please use the following link and follow the guide on how to use the UUP method. https://forums.mydigitallife.net/th...ump-download-windows-10-uups-with-ease.75052/ You can still upgrade your image to the latest Windows Cumulative Update (CU) by integrating it. Follow the readme file step by step if you have questions. Next to each build you could put which version of MSMG to use. And of course edit any of the above if I got something wrong.
Mount the wim. Code: 3 (Integrate) > 3 (windows features) > B (Microsoft .net Framework 4.8) When to integrate it is depending on what you plan to do more to the wim.
Good morning I kindly ask when will the updated version of MSGM Toolkit be released to work with the latest Windows 1903 release? Thank you very much.
Hello i am doing W7 custom image. Question is should i use toolkit v8.8 or latest ? Do you have any donation link. I really wish to somehow repay you, for all the effort you putting into this project .
@MSMG Has the issue with the 1607 ltsb ver. been fixed in v9.3 regarding the sfc scan errors when using the toolkit?
Would this be able to take an official eval enterprise ltsc v1809 and turn it into an activated genuine copy?
Not possible, except by recreating a normal iso with a svf patch and the eval source iso. Only server sku's have the option to set-edition from eval to full.
Hi, I was using this toolkit to remove "bloatware" from Win10 v1903 (UUP 18362.1 ISO). While removing mixed reality app I encountered the following error. Spoiler It says removed successfully after I clicked OK but then when I try to remove it again the behavior is same instead of "The specified component has already been removed..." I suppose. Other components seem to do that if they're removed successfully. Regards.