I've never encountered that problem. However, sometimes strange things happen when you have the Mount directory open in Windows Explorer while simultaneously copying files between that folder and another which can lead to Windows being unable to cleanly unmount a Windows image once the operation is over. Good luck.
no idea what you mean by that i tried 4 different ISO builds from different download sources and its the same problem the Setup.exe gets deleted while executing "start removing windows components" can i copy Setup.exe from the mounted ISO to MSMG DVD folder and create the custom ISO ? does it work that way ?
Don't redo the work. Just do what I said: keep the generated wim(s) and copy everything else from a stock iso. Then build the ISO, *do only this* don't restart the whole process
so i keep wims from source file ? and copy everything else ? that means the setup.exe gets the installation packages from wims library, means we using MSMG to only modify the wims to call/not call packages from wims !! good to know
What's so complicate ? MSMG modifies only the installation image (and maybe the boot and recovery image). Everything else is (normally) left unchanged. You have (for unknown reasons) something of such "everything else" deleted. So just get everything from the original ISO, but keep all the *.wim you have already modded. wims aren't "libraries" are filesystem images. ISOs in 2023 are practically useless. Setup.exe is useless for fresh installations. ISOs are still built in 2023 because people is used to them since Win95. For in place upgrades you still need setup.exe (but you need just the installation folder, isn't needed that they reside in a ISO file) For fresh installations all you need is dism /apply-image command and the install.wim file
when you say get the wim, i dont know where is it/they are located , is it from DVD\source folder ? i dont know the location of the image that MSMG works on, as far as i understood its in DVD folder ( that i copied from the mounted ISO)
Save the ".\DVD\sources\boot.wim", ".\DVD\sources\install.wim" files in a place other than the DVD folder. Extract the ISO you used as a source into the DVD folder. Remove the boot.wim and install.wim or install.esd files. Put the .wim files you saved elsewhere back in the DVD\sources folder. Avoid removing the "ManualSetup" component the next time you do a new customization.
Perhaps reading a bit of the readme and looking at what you're doing helps. Also windows has a search button since 1995, don't know where a file is located? Search for it!!
yes what i meant with important settings should not be messed with, they shouldnt be listed for a standard user of MSMG ( or at least get a warning ) , am an example i spend over 30 hours playing around it without knowing because i dont even understand what those options are i usually remove the most components from windows to keep it as light as possible, this time i messed up "Manual Setup" i wonder why such a decisive option is even listed in there, anyone may fall for it MSMG is GREAT, not complaining but such important functional components shouldnt even be listed to be messed with
it easily could be , and probably should be am working on it like "Manual Setup" which deletes Setup.exe from the image so my USB didnt boot it is a must have component so your image can boot, why is it even listen to be removed, who does remove it , how would he boot if inTerActionVRI didnt mention it i would be running in circles because as an engineer you shouldnt put any MUST have component accessible or without warning so the usual user doesnt encounter problem MSMG provides amazing flexibility, by default it shouldnt touch any MUST have functional components, it should work around optional components that doesnt harm the basic functionality of windows installation or windows use. like "Manual Setup" creator knows best, but this is my own opinion for simplicity
here we go again now i am going to find previous MSMG with the most tools , without the dangerous components that inTerActionVRI mentioned ( components added in V13.4 ) 13.4 is kinda pretty bad , 2 days trying to make a custom ISO and errors / bugs on every try
i have been using MSMG for over 2 years my friend, am just having multiple issues with 13.4 it has a more component cleaning process but a field of mines
Your error at end of installation is something new... I assumed it could be something to do with the new components. Using the previous version won't help you much. You simply must remove the same components that you have always removed. And it should have the same result as version 13.4. That last error you had is related both to not using start.cmd and to the toolkit folder in the long path. Use short path c:\TK. You have to read the readme to see if anything else you're doing wrong. However long you have to use the Toolkit, you may be during that time, remaining in some error. This error, because of the long path, does not occur in all components, it may be that you are removing a component that has this problem. The real problem is not that there are more components to remove. But yes, remove everything that is available without knowing about the consequences. And this was discussed here on the forum. The MSMG, spoke about it, we just repeat what he warned. With that in mind I think now that your problem is in the OOBE. If you are removing components that OOBE is dependent on. You need to create the Autounattend file. And remember to provide supported ISO Builds. You'll have to look for the latest ToolkitHelper Updates post to find out which builds are supported in each version. Or always use a 19041.1 or 22621.1 and integrate updates through the Toolkit so component removal is supported.