Is there a way to view what the CustomToolkit configs actually remove in an easy way? I pretty much just want to create an LTSC version for gaming and work with WSL/MS Store support. This sadly used to be quite easy a few W10 versions ago but since then we've had more packages to deal with.
Select the preset you want to see. Select Start Removing Components. See the list displayed on the screen, and press 'R' to return and make your changes.
I'm seeking experienced advice to create install ISOs which include only the necessary/current updates. I've tried NTLite, KUC, WHDownloader, DISM commands, PortableUpdate WSUS Offline Update Community Edition, UUP Dump, and MSMG Toolkit. When updating Windows, some updates must be installed in a specific non-numerically-sequential order. KUC, for example, specifically skps/removes unneeded updates and installs what is needed in the "proper" order. WHDownloader also does this and also specifically reports some updates must NOT be integrated/slipstreamed. Two questions; 1) What methods work to gather only the necessary updates as well as the proper installation sequence? 2) When integrating/slipstreaming into install.wim, does MSMG Toolkit "know" that information? If not, how can it be instructed to integrate in the proper order?
does this by default (10/11) Doesn't integrate updates, it only offers downloads of the updates and only the necessary ones (for 10/11) All comes down to what updates are provided by the user, for simple and correct updating W10UI is advised to be used. In general for 10/11: SSU first pre-enabling .net35 (when desired) LCU last
Yes, I realize WHDownloader is only for gathering updates. Prehaps I could have worded the post better. Was trying to address which updates, which order, which app. Thanks for the advice.
Please forgive me if this is mentioned somewhere, but I have searched to no avail. For Windows 11, what components absolutely need to be left installed in order for the store to work properly? I have tried several times to make an image that leaves from what I can tell are the core store components intact. However, whenever I open the store, it immediately closes after I open it.
Dependencies list for WindowsStoreClient and WindowsStoreApp If you want to have UWP Appx running, you must keep WindowsStore and its dependencies. For you to know more about these dependency they are described next to the components in the Remove menu. "Needed for" or "Depends On". Needed for: Windows Store DesktopAppInstaller - is interesting to keep for working winget commands. WindowsStoreClient - Microsoft Store Client, required to Microsoft Store work WindowsStoreApp - Microsoft Store App StorePurchaseApp - Microsoft Store Purchase App, not sure if removed you're able to buy games, apps in the Microsoft Store without issues. ServicesStoreEngagement AdvertisingXaml AccountsControl - Required to sign in to apps. AADBrokerPlugin XboxIdentityProvider Xbox Identity Provider - Require for sign in to Xbox Console Companion XboxClient - required to xbox app work XboxApp "w10" equal GamingApp "w11" - Xbox Console Companion XboxSpeechToTextOverlay
Insider preview should not be supported by the toolkit. Only releases. But this is just my opinion. Cheers.
https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-793#post-1606110 Sent an 2022-04-30 New CustomToolkit updated file attached in the link above and in my signature. VirtualCreate_ImageIndexEditions.zip 2022-04-28 (updated with 2022-04-16 @abbodi1406 "uup-converter-wimlib-79f") Download: in my signature. Note: To work with Virtual Create, it is not necessary to extract the file. Just save it to the Toolkit folder. Spoiler: CHANGELOG 2022-04-30 Updated scripts available in the Customtoolkit package. Optimized of the removal of components based on component presence information, extracted with the help command of Toolkithelper itself. Added a way to maintain the work of Custom Toolkit within Toolkit, instead of sending to the root "%Systemdrive%\ TK" root Just accept the initial terms by typing "1" instead of "a". Change from: Code: [X] Go Back and Select: [S] to "Start to: Code: [X] Go Back and Select: 'S' to "Start Just to avoid confusion with the options displayed on screen. Suggestion of the member @bala1. Changed the order of the following options for utility order. from: Code: echo. [3] Dependencies correction Filter echo. echo. [4] Select Windows Components to: Code: echo. [3] Select Windows Components echo. echo. [4] Dependencies correction Filter Corrections in the removal menu: As mentioned by MSMG, referring to the removal of the "Speechrecognition" component that can cause the narrator to break, some conditions have been corrected to avoid this break. Note: Problem only related to Custom Toolkit. Fixed the problem, in which the Media Player component was not set to be removed if selected. Added Tweak - Legacy Vertical Mixer Volume Control for W10. Optimized "Cleaning Up temporary and log files or folders" in Save Sources and Fixed Boot Path to remove Backup temporary files in this process. this: Code: del /f /q "%BootMount%\Windows\WinSxS\Backup\*.*" >nul 2>&1 should be: Code: del /f /q "%BootMount%\%%i\Windows\WinSxS\Backup\*" >nul 2>&1 Corrected the duplication of displayed image information, which occurs in some cases when optimizing the index or conversion to ESD. Fixed an error in Save Source related to the closing of source without winre. Problem pointed by member @haris_mdlf69 Modified the USB Stick list code inserted for using the "USB Copy" and "USB Sync" options. Previously, although it was possible to use the function because we already know the letter of the flash drive. However, the list of drives available on screen for Latin languages was not displayed. It is now displayed for English, some Latin languages and, for Chinese I think it works, due to the help of the member @正义羊. And added Auto Detect and Set USB Drive Letter, If Only One USB Stick Has Been Found. Tests and bug identification: grateful to @haris_mdlf69 and @Bullet. Spoiler: CHANGELOG 2022-04-22_2 1. Removed Toolkit.cmd from the Custom Toolkit package. Leaving this file can cause the replacement of a newer version of the toolkit, this is the case today. 2. Some aesthetic display changes were made and small display message fixes that not occurs in some situations. 3. I put support for "Multiple Image Index Deletion" to ESD Images on "Wim Delete" that was renamed for "WIM/ESD Multi Image Index Deletion" and was moved from WIMManagerMenu to root of ToolsMenu. Spoiler: CHANGELOG 2022-04-22_1 1. Added Image Format option to SaveSource as WIM or ESD in the CustomToolkit ApplyMenu. You can choose to save as WIM or ESD before selecting Savesource. 2. Fixed the naming process of the new ISO and viewing the image information, before rearranging the indexes (this problem did not affect the building of ISO). 3. Added Auto Generate ISO at end Optimizing Process that not occurs when VirtualCreateEditions are Disabled. 4. Merged "Extract Source from MCT" with "Extract Source from Custom" ESD Image as it is the same code. Code: [5] Extract Source from: Microsoft's Media Creation Tool or Custom ESD Image 5. Merged Custom Toolkit with new MSMG Toolkit 12.2 [2022-04-20]. Spoiler: CHANGELOG 2022-04-15 Added the option that asks if you want or not do the Cleanup Sources process before you start enabling features, since there are 80 components that generate the pending issue. Fixed my previous changes on Enabling Features for Custom Toolkit, by changing Enabling NetFX3 from the last for the first position, since it is a prerequisite for other features and is the only one that needs to integrate a CAB package to be activated . Fix about StartMenu path for Templates Folder and changes about Saving Source with rearranging Single Language to first position in the Editions list. New VirtualCreate_ImageIndexEditions.zip with new multi_arch_iso.cmd. Changed Script shortcut to literally a script because the script shortcut does not accept many characters. Now the script also removes the Edge shortcut from the desktop and QuickLaunch. Spoiler: CHANGELOG 2022-04-08 1. The Customize Menu has been changed. Reordered again. Disable and Enable Features have been repositioned before the Registry Tweaks options, because some Tweaks could be related to some enabled features, like WSL for example. 2. Fixed "Integrate Language Menu" and "Integrate Driver Menu", where the first option did not work when WinRE.wim and/or BOOT.wim were not mounted. 3. Added function to Export Host Drivers, so you can integrate directly to the image. Export of all drivers will be performed and copied to the folder referring to the Host OS, not referring to the image being prepared. A prompt will be offered so that you can choose to use Drivers extracted from Windows 10 for integration into Windows 11. I suggest that at the first opportunity to get the drivers directly from Windows 11, you do so. Then replace the ones in the ".\Drivers\Install\W11" folder. 4. Added function to Mount WinRE.wim and BOOT.wim if you need to, after you have mounted install.wim. There is no need to unmount (that is a waste of time) to do the whole process again. Just go to [7] Tools Menu and mount what you need. 5. Redesigned the code session for Customizing the Start Menu Layout in Windows 11. The templates will be placed in ".\Bin\StartMenuLayoutBIN\Templates" There is a Readme.txt on what to do. If you don't want to change anything, just apply the Start Menu Layout in the Customize Menu, a Default Template will be applied and only "File Explore" and "Settings" will be placed in the Start Menu. Hints on this subject provided by member @MIMMO61 Spoiler: Start Menu Layout BIN - ReadMe.txt content Code: "DefaultStartMenuLayout.bin" Has only pinned shortcuts for non-removables. File Explorer and Settings. That is why I selected it as Default. 1. Choose any file within Templates folder; 2. Copy it to Main ".\Bin\StartMenuLayoutBIN" folder; 3. Rename it to "CustomStartMenuLayout.bin". Note: If the file "CustomStartMenuLayout.bin" is present, the file "DefaultStartMenuLayout.bin" will be ignored. You can simply create your template (adding, removing and arranging the order of the pinned shortcuts) directly in your Start Menu. When your customization is ready, copy the "start.bin" file that was instantly overwritten, into the folder "%LocalAppdata%%\PackagesMicrosoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\LocalState". And put the newly generated "start.bin" renamed as "CustomStartMenuLayout.bin" into the ".\Bin\StartMenuLayoutBIN" folder. 6. During the "Remove Windows Components" procedure. a "Shortcut Script" will be added to the "Start Menu - StartUp" to remove the Edge shortcut from the desktop. With this technique, there is no way this shortcut will remain, but after the automatic update of Edge I don't know if it will return, most likely it will. Spoiler: CHANGELOG 2022-03-29 Warning, suggested by MSMG about: "Cleanup Source Images" moved to :CleanupSource session. For the session :WIMUpgrade "Function to Upgrade WIM Index Edition": 1. Inserted the corrections to support the possible target editions, made available by @MSMG. 2. Applied the fixes based on the idea of the problem submitted by member @shyamsundarsoni. The main reason for sending today's patch: The new version of uup-converter-wimlib-79 besides coming with several options, came with the option "AutoExit" that was already inserted in the adapted version (VirtualCreate_ImageIndexEditions) to work with CustomToolkit, however this function was not named as "AutoExit", and that way, this had to be changed. So download both packages, "CustomToolkit" and "VirtualCreate_ImageIndexEditions". Spoiler: CHANGELOG 2022-03-25 Added a warning, suggested by MSMG about: "Cleanup Source Images". Removed a small redundancy and fixed a problem with getting the previous session's "ImageEdition" values data from variable storage file that was added in yesterday's version. This allows you to resume editing an already mounted image for testing. Not many people use this. But it is fixed, and does not affect the use of the Custom Toolkit features. Spoiler: CHANGELOG 2022-03-23 *Merged with 2022-03-14 12.1 Toolkit.cmd. *Remember to change all line comments from ";" to "#" in all your custom lists. 1. Added this Tweak to Windows 11 Bypass Hardware Requirements for install.wim, not boot.wim: *Disable New Watermark Message: "System requirements not met. Go to Settings to learn more." 2. Implemented an identification of all Editions of the Image at the start of the script so that it is not necessary to call dism to check which Edition it is, in every loop of every deployment that requires this identification. This has provided a small process reduction in the integration of Windows Updates, a nice optimization in the code. 2.1 Fixed the Editions ID for removing components and for disabling and enabling features. 3. Added "Warning" in the "Remove Windows Components Menu" for very recent Image Builds and Image Service Pack Builds, not supported by the latest version of the Toolkit. 4. For the ones who always enables NetFX35... If you want to enable NetFX35 through the "Enable Features" customization option, it doesn't work because it is only a list of Features and it is mandatory to specify the .cab package. In this case, to avoid the "pending problem" in using the cleanup source, I think it would be interesting to put IntNetFX35 to be called when this is found in the Enable Features list as "NetFX3". So... If NetFX3 is present in your list to enable features, the NetFX35 Integrate session will be called, which will integrate the packages already present in the ISO being worked on. Therefore, the order of the Customize menu options has been changed, leaving Disable and Enable Features as the final customization options. I also made a Full_FeaturesList.txt. Then, the script, with the conditions, will control the features for each build. This idea came up when I was testing the final merge and forgot to put the correct list for Windows 11. And also, so that we can do the Source Cleanup before the NetFX35 integration that causes the pending that prevents the Cleanup. Note: In fully automatic mode (without questioning), the Cleanup Sources will be bypassed and not applied. 5. Added fixes suggested by member @shyamsundarsoni. Thnks for the bug hunting. 6. Fixed bug in Custom Toolkit's WIMExport option. It was saving the image to another wim file with the name ".wim", without the filename defined by user. 7. Fixed a bug that after savesource, it was not performing the final optimization of the image (rebuild). This was creating very large images due to the presence of the "[DELETED]" folder within the install.wim image. 8. Fixed typo suggested by member @正义羊. 9. Discovered the Windows 10 Tweak that caused problems in the Windows 11 Taskbar, problem fixed. Script to Fix for those running Windows 11 with this problem in the "Wifi, Volume Control, Battery Status and Calendar" icons, added in CustomToolkit package. The Windows 10 Tweak that causes this issue is: reg.exe add ... "DisableNotificationCenter" /t REG_DWORD /d "1" /f. Note about the DiskTemp variable: Since the custom Toolkit has its working folder in "C:\TK" or "%SystemDRIVE%\TK" its Temp folder is present there as "%SystemDRIVE%\TK\TMP". So there was no need to change the code in the sessions suggested by friend @正义羊. However in order to avoid conflict with environment variables I changed all from %Temp% to %TMP% and Temp= to TMP=. So, if is needed, we can use env system %Temp% var. Spoiler: CHANGELOG 2022-03-04 1 Two scripts (EdgeChromium w7 and WMF w81) for downloading the "msu files" to extract there "cab files" have been fixed. When extracting the Custom Toolkit package, allow the replacement of all files. 2. Huge Code Refactoring - Implemented automated menu generator system. Spoiler: automated menu generator Before that, I always wanted to reduce the amount of menus for only one menu, in order to optimize the code. But when some component was added the work to put in numerical or alphabetical order was very arduous. We had to change order, put number by number and letter by letter until we can make available to you. It was necessary to put all the conditions both for the menu view and the algorithm and its correspondence. Now, just add the components and display conditions to the menu and the algorithm does not need to have repetitions. Thus, the menu is generated numerically, but displaying according to your description, in alphabetical order. So, according to our choices, it seeks the respective algorithms for its correct execution. Alphabetical order, in the case of Custom Toolkit, will only be avoided in order to group some apps associated with each other. Ex: Xbox App e Gaming App. They are the same app, and this has its name changed in Windows 11, so kept next to the other Xbox Apps options. With this system implemented, all the menus I had made available in parts, I returned to make them whole. The intention of divided menus was to maintain continuous numeration without jumps. Ex: for x86 The "Mixed Reality Portal App" was not displayed and a number was missing. Shortened code block of "Integrate Features Menu" and "Integrate Custom Features Menu"... from: 3756 (CustomToolkit 2021-12-29 with Multi Selection Menus) to: 1827 code lines The Full Code Optimization... Fully implemented Auto Generate Menu for all Menus. from: 35622 lines to: 35055 lines Changed Menus: Integrate Features Menu Language Packs Menu Drivers Menu Dart Menu Windows Legacy Games Menu InboxApps Menu Integrate WHD Updates Menu Integrate Custom Features Menu Remove Menu Remove Internet Components Menu Remove Multimedia Components Menu Remove Privacy Components Menu Remove Remoting Components Menu Remove System Components Menu Remove System Apps Components Menu Remove Windows Apps Components Menu Customize Menu [8] Select Official Tweaks (Apply Tweaks Menu) [9] Select Custom Tweaks Menu Bypass Windows 11 Hardware Requirements option has been moved to each of these 8 and 9 Menus. If you have already had the job of selecting something from the "Official Tweaks" menu and resolve going to the "Custom Tweaks" menu, a filter has been added so that the corresponding options are displayed and automatically selected for you. You can add options from both menus, but never in both menus your correspondents. This is interesting so you can select options not present from the official list, but keep the implementation of the official options. NOTE: If you come back in any of the menus, you will remain the selection of common matches from the last menu accessed. Before you apply the selected tweaks, simply enter the desired menu (official or custom) to correct. 3. Optimized the add environment path code in "Function to Integrate Sysinternals Suite". 4. Fixed several Typo for displaying info. 5. Some "spoiler" mentioned fixes below, that has implemented in this Custom Toolkit version, has to be done in Official Toolkit. Thnks to some Friend members! Spoiler: all fixes to be done That was my fault! There are 3 occurrences of this error. @MSMG, as this was a suggestion of mine, this should be corrected in the Toolkit official as well. all from Code: Proessional to Code: Professional Thnks to @ghostwalkergamma Made the changes below to fix problems that I discovered, in using the command options for "eol" and "skip", in obtaining data in text files. All "Reg Query" were already in that standard (commands out of double quotation marks). In this way I decided to standardize for all "For" commands found. The "dir" command works correctly because they do not use options such as "For". But this change is crucial for "Type" and "Ver" commands. Now eol works and comments can be placed into the files. all from Code: ('"dir /s /b /ad " to Code: ('dir /s /b /ad " all from Code: "" 2^>nul') to Code: " 2^>nul') Note: These above are interdependent all from (add space after "/b" for mass replacements) Code: ('"dir /b to Code: ('dir /b " all from Code: ('dir /b "" to [code] ('dir /b " all from (add space after "type" for mass replacements) Code: ('"type to Code: ('type " all from: Code: if "%ImageInstallationType%" equ "Server" to Code: if "%ImageInstallationType:~,6%" equ "Server" and, all from: Code: if "%ImageInstallationType%" neq "Server" to Code: if "%ImageInstallationType:~,6%" neq "Server" thnks to @rulman info Added Windows 8.1 KB3014442 Added the conditions for: CapturePicker Needed for: Snip & Sketch (Screen Sketch) ScreenSketch Depends on: Capture Picker Thnks to @shhnedo issue info Spoiler: CHANGELOG 2021-12-29 Fixed a problem with Remove System Apps Menu "The component removal seems to have a problem regarding the "Windows Mixed Reality" component. It keeps getting reactivated no matter what.", thnks to @Teo265. Spoiler: CHANGELOG 2021-12-28 Fixed a problem by using the option to save your custom selection in a file list, thnks to @Teo265. Custom Toolkit Beta has made available to test. I just deployed the multiple choice schema for the Integrate Windows Updates menu. I will make available as beta (for testing). Now you can set everything from "Language Packs" up to "Custom Features" and run the "Start Integration" only once so that what is selected, be integrated. Download at Custom Toolkit's main post link. Note: Extract within the toolkit folder, the "GenericStart_LauncherMenu.cmd" will recognize the file "CustomToolkit_Beta.cmd". In "GenericStart_LauncherMenu.cmd" use option 4 for tests. This time I was able to do the implementation only with menu modifications, and in the Start Integration function, so I avoid modifications in the structure of the code that integrates the updates. This will facilitate the merge with the future changes made by @MSMG. Spoiler: CHANGELOG 2021-12-26 New Custom Toolkit bug found, thnks to @Intmd for the issue repport. I gave a visual check in the code and I found the bug that explains what he was telling me. For now just replaces from: Code: if "%IsBootImageSelected%" equ "Yes" set "Feature=%%i" to Code: if "%IsBootImageSelected%" equ "Yes" set "Features=!Features!;%%i" Note: Yes, it is from "Feature" to "Features". Bug: Only occurred when the "Integrate Setup Media Update" was selected. This blocked the integration of everything that had already been selected in the other menus. This is corrected by replacing this line. This way you can integrate 1 Language Packs, 2 Drivers and 3 features (If you want to activate the bypass for pauses and questions just press "0" before proceeding with "Start Integration". After the procedure you can press "0" inside the Integration Menu to disable.), in one step. Then do the manual steps on 4 Windows Update; And as the last step, do the 4 Setup Media Updates and 5 Custom Features after this, if necessary and proceeding with "Start Integration". Happy Holidays! Thnks!
About: "RunAs-TrustedInstaller_AutoDownload.cmd" "RunAs TrustedInstaller for Context Menu with nSudo and PowerRun" script. I put it inside the "Custom Toolkit" package that I launched yesterday, a version of the "RunAs TrustedInstaller" based on the version provided by the @freddie-o member that works for the Toolkit structure. In this case it will keep the folder structure in the Toolkit standard ".\Bin\x86" and ".\Bin\x64". Powerrun automatically downloads at any occasion to use the script, always keeping the updated. But I added the one with one with this a little differentiated approach, as it will only download the nsudo if the script is in a different folder from Toolkit, inside Toolkit it will not be replaced and the already present will be installed. Use if you find it interesting or necessary... Note: It will be installed in "%SystemROOT%\System32" and "%SystemROOT%\SysWOW64" Both have install and uninstall in the menu. Both can be installed at the same time. Will be displayed in the context menu as: "TrustedInstaller by nSudo" "TrustedInstaller by PowerRun"
have already seen this, from freddie-o, think that's the best alternative. nice script. Thanks for your feedback
@inTerActionVRI a question for you have you ever read the start.bin from the new insider, with me it always comes start2.bin I just got home from network patching, I had a quick read this morning, but it always gives me a start2.bin I'm tired, I'll test it out tomorrow and see what start2.bin is all about. edit : I found the error, but I'd rather not say what it was, otherwise I'll feel ashamed.