@MSMG ToolKit 8.7 Host OS: W10 Insider Preview build 17713 x64 en-us. Double Click on Start.cmd: But Run as Administrator work is fine.
I remove or comment out the line but it does not work. Script is broken. In version 8.6, everything worked without errors. https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-340#post-1436579 How to do it right?
hi @MSMG, thanks for your work. But past few Windows Insider Preview builds will give an error about explorer.exe stack overrun error after slimed down using MSMG Toolkit I believe it's related to some of the component removal process. I know your toolkit haven't support RS5 prerelease builds yet but just a reminder who wish to use it for insider build. DON'T USE TOOLKIT ON INSIDER BUILD YET.
So, should I use ToolkitHelper.exe to remove things or Start.exe? Are there things that can only be removed by ToolkitHelper.exe and not Start.exe?
Hello, dear forum users!!! Сan you advise me?To date, there is a newer instruction for properly using the MSMG ToolKit? If there is, then tell meplease see where it can be found
I have a question about something I have noticed since I started using this tool. When you use the media creation tool you get a sources folder with ~71 sub folders and ~880 files. After the toolkit does its work on the WIM file virtually all of this is blown away. Since the beginning I have always just copied what what the toolkit creates over my original sources folder letting letting all duplicates be replaced. What I want to know is, do I actually need to keep all of those untouched original files or can I simply use the sources folder created by the toolkit exactly as it is after I modify the image?
Another question, I just noticed that there is one removal mentioned specifically after cleanup: [L] - Cleanup the Source Image using [Apply->Cleanup Source Images] menu. [M] - Remove Microsoft Hyper-V Windows Component using [Remove->Remove Windows Components->Remove Advanced Windows Components->Microsoft Hyper-V] menu. I did not notice this change until I had built the image I am about to install. Is this a critical ordering? I did all of my removals first before cleanup, should I dump the image and start over or install it as is?
That instruction is for Windows 10 TH1. Were you really using this version as source? Make sure you didn't misread the instructions.
Double clicking Start.cmd calls the Nsudo which in turn runs the script using TrustedInstaller. So right-clicking and then choosing run as adminstrator may not be required, but some people earlier reported to have issues doing so. On RS5 Insider Preview OS's, there seems to be some issues calling NSudo inside a cmd, so choose run as Administrator for RS5 Preview OS's. Sometimes editing the script using notepad may give errors especially when the script is running, use rem instead of :: to comment the line Toolkit.cmd uses the TooolKitHelper.exe to remove the component manually., if you are familiar with using the ToolKitHelper.exe then you can use it.
Will check with the MCT Image and see what's wrong with it. Did you choose MCT Image to WIM Image in the ToolKit to convert the image to regular WIM Image? If you had choosen Remove Windows Manual Setup Feature in the Advanced Windows Components then it would keep only the required files to do a clean install.
Ok, but there are things that can be removed by Start.exe and Toolkit.cmd (I think) so in that case should I remove them with which one of the two, i. e., which of them removes more things?
The ToolKit.cmd uses ToolKitHelper.exe for only these components : Microsoft Telemetry (CEIP, KernelDebugging, Asimov, WER) Windows Defender PeopleExperienceHost SmartScreen ToolKitHelper removes more components than ToolKit.cmd but also lacks few components present in the ToolKit.cmd like IE, Hyper-V, WMP, PhotoViewer, Search, System Restore etc. ToolKitHelper allows more components and is for experimental purpose, once it's working properly then the ToolKit.cmd will be made to use it to remove all components.