If you want to keep the native way of associating txt files, you should keep one of the two. It depends on the Build you are using. For W10 and W11, just keep the one in the "[6] Remove System Components Menu" options. In Windows 11 there are both versions. Just remove the one in the "[8] Remove Windows Apps Menu" option. Or you can perhaps remove the "[6] Remove System Components Menu" option and keep the "[8] Remove Windows Apps Menu" option. You will have to test it. Once you have tested it, let us know.
Hey guys. Below I have highlighted the code, in Toolkit.cmd v12.1 I already have an item: if "!MenuChoice!" equ "04" ( if "%C_Calculator%" equ "+" ( set "C_Calculator=-" ) else ( set "C_Calculator=+" ) ) do I need to change it to? if "!MenuChoice!" equ "04" ( if "%C_CalculatorApp%" equ "+" ( set "C_CalculatorApp=-" ) else ( set "C_CalculatorApp=+" ) ) line above we changed from C_Calculator% to C_CalculatorApp% hope you understand me. Thanks. I want to make a build but I see a lot of typos and changes, maybe there is already a corrected toolkit.cmd with all the fixes?
You have to do this change too. from Code: echo. [04] %C_Calculator% Calculator App to Code: echo. [04] %C_CalculatorApp% Calculator App This Changes only for "[8] Remove Windows Apps Menu". Not for Calculator in "[6] Remove System Components Menu". EDIT: I reversed that, at the time of posting here. MSMG understood that there was a need to check this part anyway. It is exactly as you said. You have to do that part too! from Code: if "!MenuChoice!" equ "04" ( if "%C_Calculator%" equ "+" ( set "C_Calculator=-" ) else ( set "C_Calculator=+" ) ) to Code: if "!MenuChoice!" equ "04" ( if "%C_CalculatorApp%" equ "+" ( set "C_CalculatorApp=-" ) else ( set "C_CalculatorApp=+" ) )
@MIMMO61 I think these days they just redownload themselves(or the store does) and there's not really a convenient way around it(?) Or at least I don't know of one as of now.
Thanks for the attention. I processed the updated ISO (build 593) with ToolKit and re-applied RemovePkgsList, in theory it shouldn't detect any app, instead there were some apps. Code: ============================================================================== MSMG ToolKit - Remove Windows Components Using Package List =============================================================================== ------------------------------------------------------------------------------- ####Starting Removing Windows Components Using Package List#################### ------------------------------------------------------------------------------- Image : Install.wim Image Index : 1 Image Architecture : x64 Image Version : 10.0.22000.593.0 ------------------------------------------------------------------------------- ####Removing Windows Components Using Package List############################# ------------------------------------------------------------------------------- ===========================[Install.wim, Index : 1]============================ MSMG ToolKit Commandline Helper Version: 1.0.5508.0 Image Version: 10.0.22000.593 Component : ContentDeliveryManager Removing Package files... Modifying Package files... Loading Image Registry... Modifying Package Registry... Unloading Image Registry... The operation completed successfully. Component : MapControl Removing Package files... Modifying Package files... Loading Image Registry... Modifying Package Registry... Unloading Image Registry... The operation completed successfully. Component : PeopleExperienceHost Removing Package files... Loading Image Registry... Modifying Package Registry... Unloading Image Registry... The operation completed successfully. Component : RetailDemoContent Removing Package files... Modifying Package files... Loading Image Registry... Modifying Package Registry... Unloading Image Registry... The operation completed successfully. Component : SkypeORTC Removing Package files... Loading Image Registry... Modifying Package Registry... Unloading Image Registry... The operation completed successfully. Component : WindowsMixedReality Removing Package files... Modifying Package Registry... Loading Image Registry... Modifying Package Registry... Unloading Image Registry... The operation completed successfully. Component : WindowsStoreClient Removing Package files... Modifying Package files... Loading Image Registry... Modifying Package Registry... Unloading Image Registry... The operation completed successfully. Component : XboxGameCallableUI Removing Package files... Loading Image Registry... Modifying Package Registry... Unloading Image Registry... The operation completed successfully. ------------------------------------------------------------------------------- ####Finished Removing Windows Components Using Package List#################### ------------------------------------------------------------------------------- ===============================================================================
Yes, it can be that way too. The only reason I don't make this suggestion, with the removal of the ContentDeliveryManager, is that I don't know what the situation will be for those who don't use the autounatended.xml file for installation. I never tested it again, since I was using the 1909 in 2021-10. So currently I don't know if this causes problems or not. Needed for: Out of Box Experience (OOBE) & Microsoft Account. It's up to each one of us to do our own testing.
No, removing ContentDeliveryManager does not violate the installation process itself at the OOBE stage, in the case when the installation is performed without using autounattend.xml . The removal of ContentDeliveryManager obviously violates only Microsoft's plans to impose some of its undesirable content on us. In addition to removing this component. like many other users, I also disable all cloud functions of the consumer (CloudContent) in my practice: Disable_CloudContent.reg: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CloudContent] "DisableWindowsSpotlightFeatures"=dword:00000001 "DisableWindowsConsumerFeatures"=dword:00000001 "DisableSoftLanding"=dword:00000001 "DisableCloudOptimizedContent"=dword:00000001 To the question of dependencies: And also I remove AADBrokerPlugin, WindowsFirewall, OOBENetworkCaptivePortal and OOBENetworkConnectionFlow (removing them does not require the mandatory use of autounattend.xml) and recently I have also tested the removal of the OOBE component itself (this is now easy to do in NTLite free), and after that I use autounattend.xml for installation. With all this, I constantly use a Microsoft account, use the Office software package, connected to OneDrive, and use the Store without any problems (the StorePurchaseApp component has also been removed) to install some FREE applications, add-ons and their further updates (the WindowsFirewall service must be enabled). I also delete Wallet and Payments packages using a custom list using the DISM method. Thus, all the functionality necessary for me works well. This is thoroughly tested by me for Win10 v1809 -v2004-v20H2-v21H1-v21H2 and Win11 v21H2. I agree with you, friend, each of us, using the recommendations of even the most experienced fellow testers, should pay maximum attention to our own testing results, because in the end, it is very important for each of us that the operating system, as a very complex tool with a wide variety of settings, is used on a huge variety of hardware configurations, fully met the individual requirements of each of us in her work. Therefore, once again I will note - I am very glad that we have the opportunity to share our experience and observations here!
So, removing the ContentDeliveryManager only breaks the OOBE for 1909 18362 and 19363. I abandoned testing for 1909 when I decided to migrate to v21H2 19044. In case anyone does the test, it will be interesting. I used, very rarely, some inboxapps (like PPI Projection - App to project the screen to a Wireless Display (ConnectApp)), present in it that were not present in the 17763. I think it is a big loss that they discontinued this app. I don't even know if there is another native app that does its function. If there is, let me know. I know there are non-native alternatives. I was so disappointed in v2004-v20H2-v21H1 that I stayed for years on the 1909 18363, until all these details, in v21H2 19044, were running smoothly. I think this is due to some peculiarity of a friend's Gamer Hardware that I was testing. They used to give a lot of glitch in games, and in the build 18363 they didn't, very stable. Now, at build 19044, on the same hardware (AM3+ with AMD FX-9590), there are no more such problems. However, at this level of maturity of 19044 I believe that all the previous ones also do not have the problems I experienced.
So then how can I remove packages like this ones? MicrosoftWindows.Client.CBS MicrosoftWindows.UndockedDevKit Microsoft.Windows.CloudExperienceHost Is it even possible with DISM or just other manual ways.
hi there do you plan to add the ability to completely cut / disable from the image - need for OS to have SecureBoot and TPM 2.0? I just see that custom OS builds begun to appear with this cut
I am removing all packages and applying all tweaks When i am using Version 12.0 and previous versions , my computer boots in 7 seconds after installing LTSC 2021 but with using 12.1 my computer boots in 3 minutes and 28 seconds after installing LTSC 2021 and it is really so boring So what is wrong with version 12.1 ?