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.
went back to MSMG 11.8 everything is perfect, 0 issues i may miss some new features that V13.4 offers but its not a pleasant experience for me yet my windows is clean and perfect, boot and load in 19s, latency is really low and stable, very responsive overall am happy with any MSMG , am looking forward to use the new MSMG when its out of issues like i experienced.
@MSMG, this: Code: if /i "!MenuChoice!" equ "" goto :ApplyTweaksMenu shoud be this: Code: if "%Tweak%" equ "" goto :ApplyTweaksMenu Because if MenuChoice is filled with any value other than the available options, it will still pass. But as Tweak is reset to empty each time you return to the menu, it will only pass when Tweak is set to a valid value.
Hi dear friend @ezgera , I also experienced a similar problem that showed me an output similar to the one you posted, but the problem was not in the Toolkit but in the iso that I had downloaded from uupdump, I discovered that the error, in my case, was because I modified the "CustomAppsList.txt" file to exclude, when creating the ISO, the apps that I consider to be bloatware and that I didn't want to be installed even in a normal installation without going through the Toolkit and the error occurred because when using the toolkit's removal menu , the same apps had already been previously made by me from the base ISO that I was using, so the toolkit could not find them to uninstall, consequently returning the error referred to these components that were pre-removed in the creation of the image used. See if you are not selecting something in the Toolkit that you previously removed when creating the image, as I did, maybe this is the reason for the error in customizing the image in the Toolkit. PS_1: I didn't even report this error, because in reality it was caused by me, after all I removed a component in ISO creation and tried to remove it again in Toolkit... PS_2: I always remove almost all the apps already in the creation of the iso, using the custom "CustomAppsList.txt" and the "ConvertConfig.ini" and assigning them the system, hidden and read-only attributes, as well as the downloadable executable and UUPDUMP iso creation can't overwrite them by adding what I don't want to the iso. I will let the files that I use here too, if you want to use it. To change the attributes, I use "Attribute Changer", just delete the .txt extension from ConvertConfig.ini to be able to use it after unpacking the uupdump file to a folder. CustomAppsList.txt ConvertConfig.ini.txt Regards. @JeepWillys58
if I'm not wrong CustomAppsList option is meant for builds 22563 and later, not for Windows 10 OS which he is using.
Hi my dear friend @MSMG First, so that all is well with you and all yours too... Sorry to ask, but the new version is avaliable to test
Keep an eye on the download.ru, mediafire and gdrive repositories. If you put pressure on the developer, it takes longer for the release to come out.
Did you read the README? Is recommended use short paths for the toolkit and I got same issue and I get a ISO working
What do you mean here? I assume that you have downloaded an ISO from UUPdump with the AddUpdated option disabled by setting the value 0 in the "ConvertConfig.ini" file. This would generate an ISO 22621.1 that is compatible with the Toolkit. If that's not what you did. Please, do it. This ensures compatibility with removing components after integrating updates through the Toolkit.