Does the ToolKit presently support removal of both of these, if so how? If not, will it be implemented? I really appreciate your answers to my many confused questions.
Right now only the first one the Tips App (GetStarted) can be removed using the Toolkit. For the second one which is a system app, there's a method to skip it's installation by modifying its AppManifest.xml but it will cause the SFC error due to the modification of the XML file, for this I do have an workaround which will be implemented soon in future version of ToolKitHelper program.
YES! Thanks! Dumb question but what's the command to display this list? Assuming standard C:\Toolkit installation?
Hi there, is there a way/script to bypass these annoying intial Win10 setup steps with preconfigured options?
Search, here in the forum, by: autounattend.xml This is the file of answers that the friend @shhnedo suggested.
Hi. I want to create my iso without trash, telemetry with minimal size, like many other build from internet like zosma mini, and many other. In ltsc 2021 I selected everything from menu "4. Remove" and size 4_776_103_936 changing only little to 3_916_503_040. But on the internet many builds with size 2GB, amelioretad build with removed completely updater components and so on. 1. Why I selected to remove everything, but output size is so huge. I want size 2.5GB, minimum ram usage, minimum disk space usage? 2. How I can create builds like zosma or other minimal size builds? Here is mu results (MSMG20220314): Windows 10 Enterprise x64 micro 21H2 build 19044.1586 by Zosma iso 2_242_347_008 boot.wim 253_202_301 install.esd 1_669_245_744 ram usage 0.8GB process 50 threads 622 descriptors 19427 space used 6.55GB windows_10_enterprise_ltsc_2021_x64_dvd_5044a1e7 (original iso) iso 4_776_103_936 boot.wim 656_812_110 install.wim 3_837_704_223 my msmg output iso 3_916_503_040 boot.wim 425_599_898 install.wim 3_458_098_235 ram usage 0.9GB process 80 threads 826 descriptors 25906 space used 16.3GB
I removed all packages and applied all tweaks for 2021 LTSC But after these processes Intel Management Engine stopped working and it is giving the error CODE 10. After this error , my computer started to boot in ery long time exactly in 2 minutes I wonder if this error is related with MSMG or not ? Thank you
I was also looking into this, and found your post with sample files Is there an example where there's only 1 or 2 things changed? Personally I only need AcceptEula, DarkTheme, and 'No' to everything on the telemetry screen. Is it safe to delete everything else besides those 3, or are you required to specific certain values even if they're same as default? Thanks!
You need to convert WIM to ESD after servicing image and next create ISO. It will decrease ISO final size significantly. [7] Tools [1] WIM Manager [E] Convert This is one of the reasons why final ISO size (made by MSMG Toolkit) is way larger compared to the custom "Zosma" mod. Also, don't forget to select Do you want to cleanup Image folder ? [Yes] option in MSMG Toolkit during the process of "Applying & Saving Changes to Source Images". This reduces the final size of image. You can disable some unnecessary system services in NTLite - this can decrease amount of running processes. [MSMG Toolkit unfortunately doesn't have this option.] About Space Used after installation - I don't know how exactly it can be achieved with such low space used 6.55 GB, but I guess it can be done by some heavy components chopping (DISM hidden packages removal & other tools) + manually removing some stuff from mounted image folder.
There is an "AutoUnattend - ReadMe.txt" file. In it you find info about customizing the file. It will not remove anything, it will only answer the questions from the installation.
Oh, I didn't know this option is located there, because placing it in Tools menu doesn't make any sense. This should be available during Applying & Saving changes to Source Image as final option for format output (WIM or ESD).
You can try. But I believe there are some more topics for this to work during the installation. It has been a long time since I made and left as complete as possible, made some reviews to remove unnecessary parts and to make specific autounattend.xml files for some Windows builds. It is up to you to test. Start the installation and see if you get to the selection of editions without any question. When you get it. Follow with the installation to see if the questions about User will be answered or not, and if the bypass will occur for parts of the telemetry options. The way I left, you only choose Edition and partitions. So after coffee, you'll already be on the logon screen. All related to Wim Files, for images that are not in service or after Save Source, is in this menu.
Yeah I know, but for "average Joe" that is using tool for the first time or doesn't have enough knowledge about Windows Imaging Formats, this is counter-intuitive for placing it in separate menu for use after saving changes to source image and de-mounting image. Most users hit "Apply" and next "Target > Make a DVD ISO Image" option without knowledge, that there is option to decrease final size of image in additional menu by converting it to ESD. For example, Nuhi added option in NTLite to select Image Format before finalizing entire process of saving changes to the image/creating ISO. Which makes more sense for end user. So option of selecting Windows Imaging Format (WIM or ESD) during "Apply & Save Changes to Source Images" menu or "Make a DVD ISO Image" menu is better. Image could be automatically converted to ESD after Applying & Save Changes to Source Image process + de-mount or before Making a DVD ISO Image process, if user selected ESD option. + There could be a descriptions in parentheses to indicate that ESD provides smaller size and is read only, WIM has bigger size and write & read availability.
In the old days this conversion was in another position. Yes, it is possible to put before Save Source, better option. Just one opinion of mine: I do not have this concern to decrease the size of the image, it only takes too long to close the image. I use 8GB or 16GB pendrive if I need it. But 4GB, no longer serves, nor for ESD format. Anyway...