I will wait to see what @MSMG says about it. I would feel more comfortable if he ToolKit removed it for me, but right now it is not supported - perhaps there is a reason for this?
But Teams installs only after the first startup. You have to apply Tweak to disable this automatic update in the Customize Menu. [8] Apply Tweaks [C] Disable Automatic Download and Install of Microsoft Teams App So, you can use that powershell command to remove the Teams App.
I realised this later, after a bit more testing. Now I am almost happy with the final image. I can't seem to eliminate Get Started from my images. Although I have it my list and the ToolKit shows it has deleted it, it still shows in the Start menu.
No, there are component changes related to removed components in the 22000.593 preview CU and so using with latest CU and then updating with WU further can give errors.
1) CommunicationsApps is the component name for the Mail & Calendar App. 2) The support for removing Microsoft Teams apps has been added for future Windows 11 releases when MS makes it a inbox app. Right now the current Windows 11 release installs the Teams App online so you can use the tweak to disable it's installation.
There are two Get Started Apps, one is a inbox app and other one is a sub component of MicrosoftWindows.Client.CBS_cw5n1h2txyew system app.
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.