1. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,651
    3,398
    60
    Not. Just use it as always.
     
  2. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,651
    3,398
    60
    Do you use any NOT Open Source software out there?
    Like Windows as an operational? And other utilities who are collecting data on you?
    You can trust the wide range of users, no problem.
    You can use some system with Windows Sandbox or other virtualization, to attest to security, until you create confidence.

    This project has only closed code software. It's Toolkithelper. The rest is made up of MS and other Open tools available and used by the community around the world in its Windows images customization projects, among other projects.

    Scripts only allow you not to do things manually.

    So I recommend learning to use the tools manually.

    This is the only way for you to trust and value this work.

    And, you don't have to use the proprietary part. Just use only Toolkit and do not use the removal menu or component removal via Toolkithelper list.
    Use only removal through the list for removal via Dism (MS tool).

    Custom Toolkit uses Toolkithelper to get the list of components in the image being worked for the automatic display of the menu options. So it wouldn't serve you.
     
  3. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,651
    3,398
    60
    #22643 inTerActionVRI, May 15, 2022
    Last edited: May 16, 2022
    Complementing the Changelog description of the alternative to Setupcomplete through StartMenu.

    Once the installation USB stick is created, extract the "Installers.7z" file into the USB stick, creating the the folder with the name of the "Installers" file.
    Run the "StartMenu_SetupComplete.cmd". It's a menu.
    This is the file that will be integrated into ISO by applying the option 'A' In "Cutomize Menu".
    If you want to edit this script, remember to add it by replacing what is inside the "Custom" folder in the Toolkit's folder.

    At the end of the installation of Windows the "StartMenu_SetupComplete.cmd" will read this folder inside the flash drive and detect the existence of scripts displaying the menu.
    NOTE 1: This script already removes the Edge icon from the desktop, if it is present there;
    NOTE 2: If you have a habit of removing the USB stick during the installation, after the last boot, this menu will simply end, keeping the script that will be performed in the next restart. There is an option on the menu to remove the script from startup. You can also run this script at any time, perform your functions and remove from startup. Everything is a matter of personal preference.

    According to the previous description left in Changelog, the scripts performed by the menu can be edited.
    For the least experienced, the delimitation that is defined in the form of notes within the script. Between Begin and End you can erase, add or update things.

    * In the script "1stLogon_SetupComplete.cmd" there are links to download what is supported by the script for silent installation.
    For the K-Lite Mega Codec Pack the configuration files for silent installation were made available.
    Others application files are listed on Chagelog.

    * In the script "1stConnection_SetupComplete.cmd", in the part that can be deleted, there is Enable WSL Feature, WSL kernel Update, and Debian and Kali Distro Linux installation. You can exclude that part.
    The other part will offer the list for multi-selection application that will be installed with the Desktop App Installer (Winget) feature directly from web. Which acts as the Linux repository system for installation of applications through CLI - Command Line Interface. That in this case, I offer in the form of a list with GUI - Graphical User Interface through PowerShell Out-Gridview.
     
  4. bala1

    bala1 MDL Member

    May 2, 2015
    178
    149
    10
    It was sensational. Congratulations

     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. graver.x

    graver.x MDL Senior Member

    Jan 18, 2020
    342
    476
    10
  6. Supern00b

    Supern00b MDL Addicted

    Dec 30, 2010
    728
    540
    30
    #22647 Supern00b, May 19, 2022
    Last edited: May 20, 2022
    Hmmm uupdump issues, that would be a very sad affair for many of us.
    Hopefully it can be fixed to work as before.

    A heads up for those who remove AADBrokerPlugin with the toolkit:
    Don't.
    It breaks modern authentication, used for example for Office 365 activation.
    When prompted to activate, you'll get as far as typing your account name, but the password screen never shows up.
    This will prevent login to the customers Office account, thus preventing activation.
    "AAD" stands for Azure Active Directory, having figured that out, the solution was not so far away.

    What I did was enabling updates and install latest CU, we know that the CU re-installs system apps so that includes AADBrokerPlugin.
    Defender also returned though, albeit not a big issue.
    After a reboot I could activate Office 365 just fine.

    Cheers.
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,273
    94,758
    450
  8. graver.x

    graver.x MDL Senior Member

    Jan 18, 2020
    342
    476
    10
  9. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,651
    3,398
    60
    #22650 inTerActionVRI, May 20, 2022
    Last edited: Jun 21, 2022
    https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-793#post-1606110

    Sent an 2022-05-20 New CustomToolkit updated file attached in the link above and in my signature.

    VirtualCreate_ImageIndexEditions.zip 2022-05-25 (updated with 2022-05-25 @abbodi1406 "uup-converter-wimlib-80f")
    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.

    1. General Review of Remove Menu

    Optimized and improved the dependency filter system.

    Corrected problem with:
    StickyNotes being set to be removed when the ServiceStoreEngagement is setted to be removed in Windows 11, this should only occur from the 19044 Build down.
    "Todos" option should not be displayed for Windows 10, and added the name of this application "To Do List and Task Management App (Todos)".
    SolitaireCollection when changed to a negative signal on Windows 11, it did not return to positive if necessary.
    Typo fixed that not displaying SearchApp option.

    Thanks to the member @bala1 for the help in some tests, in this review of Remove Menu.

    2. If the Cortana is removed, the tweaks related to this removal will be automatically set.
    For Builds 18362 and 18363 Searchbox Breaks, so HideTaskbarSearchbox will be setted too.
    If Edgechromium is removed "Block Edgechromium Delivery" tweak will be automatically setted with this removal.
    Note: This can be changed in "Customize menu".

    1. Minor aesthetic display message Fixes and Improvements to the code.
    2. Relocated the message about Cortana removal to builds below 19041 can cause Searchbox to break in some languages. In pt-br this breaks.
    3. Fixed the bug that broke the script in case of denial (pressing 'N') in some dialogs. Thnks to @haris_mdlf69.

    4.Now when asking for mount WinRe there are the option to remove WinRe.

    5. Member @bala1, in our conversations, made me think of some things, and that below idea came up.
    I read that Setupcomplete doesn't work on Sku IoT Entreprise, perhaps Server either.
    @KleineZiege, this maybe help you.

    The interesting thing is that tests fit here.
    If anyone wants to volunteer, be my guest.

    So... Added the alternative to SetupComplete to provide direct web installation after the internet connection is established and interactively, as in Winget the -silent argument for total silent mode, because make some apps enter infinite loop.

    It is something relatively simple.

    You just have to integrate a small script "StartMenu_SetupComplete.cmd" through the Customize Menu --> [A] option. Which after install will detect Internet Connection and the presence of 2 possible scripts within a folder called Installers within your installation USB stick and display a menu for the execution of these scripts.
    In the menu there is a 'R' option to remove the script from startup.
    You may want to continue installation of the applications at another time, when restarting the computer, if the USB stick is in place the menu will be displayed again. Otherwise it will only be closed due to the absence of "installation media" with the "Installers" folder and these scripts.
    The purpose of this is to install Windows quickly and be able to use your features while installing your applications in there latest released versions.

    Script 1 - "1stLogon_SetupComplete.cmd" you customize for anything offline, apps in Silent Install or others that don't run through the setupcomplete that can be placed in the Installers folder created inside the USB stick. I am also studying some details about "FirstLogon.cmd", as one of the scripts I named "1stLogon". There are still some details to be completed, maybe I have done a job that already exists, but I have never seen it.

    Script 2 - "1stConnection_SetupComplete.cmd" is specific for installing apps directly from the web.
    This script will perform a PowerShell "Winget_install [Interactionvri] .PS1" script that will display a list of apps for you to choose. These will be installed through Winget, sequentially according to the order you select the options.
    It is interesting to keep the prerequisites of MS Store and App Installer that will receive an update at the beginning of the execution of this script.

    NOTE 1: Only the menu script will be integrated. However, it is interesting to keep the 4 scripts inside the Installers folder in case it is necessary to run manually, so you can test as well, in your current installation or virtual machine already configured.

    NOTE 2: Within scripts 1 and 2 there is a delimitation for you to change, add or remove parts from the script.
    Code:
    rem Begin your Script block from here.
    .
    .
    .
    rem End of your Script block here.
    

    Follow the list of applications I keep in the "Installers" folder for direct installation that work with the example script:
    Code:
    StartMenu_SetupComplete.cmd
    1stConnection_SetupComplete.cmd
    1stLogon_SetupComplete.cmd
    winget_install[inTerActionVRI].ps1
    
    DirectX_Redist_Repack_x86_x64.exe
    dotNetFx35_WX_9_x86_x64.exe
    HashCheckSetup-v2.4.0.exe
    K-Lite_Codec_Pack_1698_Mega.exe
    klcp_mega_unattended-x64.ini
    klcp_mega_unattended-x86.ini
    ndp48-x86-x64-allos-enu.exe
    ndp48-x86-x64-allos-ptb.exe
    PowerShell-7.2.3-win-x64.msi
    PowerShell-7.2.3-win-x86.msi
    RapidCRC-Setup-0.3.37-x64.msi
    RapidCRC-Setup-0.3.37-x86.msi
    VisualCppRedist_AIO_x86_x64-60.exe
    windowsdesktop-runtime-6.0.4-win-x64.exe
    windowsdesktop-runtime-6.0.4-win-x86.exe
    
    If any of these are not in the folder, the script ignores. And, you don't have to seek to rename versions, just keep updated and remove apps with old version of the folder.


    Note3: This is not possible with preinstalled apps, as it gets obsolete and there is a need to prepare another ISO, and do the manual work of: download, rename and position everything in their proper places. While, this is not necessary.


    6. Added Wimlib-Imagex to Export for testing, only when Changed to ESD through Custom Toolkit ApplyMenu then SaveSource. And added Updated wimlib-imagex 1.13.5 to bin folder.
    The other ways to convert wim to esd remains through DISM command.

    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.

    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.
    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].

    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.

    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
    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.

    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".

    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.

    *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.

    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.
    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!

    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

    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.

    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.

    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!
     
  10. delft 1985

    delft 1985 MDL Novice

    Oct 20, 2021
    21
    12
    0
    Can we expect an update of MSMG ToolKit in the near future to use the May builds of Windows 10 and 11?
     
  11. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,651
    3,398
    60
    We only can wait!
     
  12. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    Don't rename the update files, just copy them as it is and the Toolkit will auto renames the files.
     
  13. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    With Windows 11 there is no one click option to set a default for file types, will check what can be done for this.
     
  14. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    Yes I have included wimlib-imagex with Toolkit and using it for renaming the WIM info, I do also have included Microsoft's new esdtoolcore.exe too.

    Will be making changes to Toolkit to use wimlib-imagex to convert wim->esd and rebuilding wim image.
     
  15. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    The new version of Gaming App doesn't get integrated properly only the one found in original apps ISO works properly.

    The dependency are selected based on the dependency present in the original image and there are no x86 dependencies found in the x64 images.

    Also for some Apps it requires the image to contain certain LCU version.
     
  16. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    Will fix it.
     
  17. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    Well I have said this many times in my earlier posts that the main Toolkit program is open sourced and the dependent tools used by the Toolkit may or may not be open sourced depending on its developers.

    Though the Toolkit's dependent tool (ToolKitHelper.exe) used for removing components is being developed by me still I haven't made it to be opened sourced because
    as said in my earlier posts, the ToolKitHelper program was developed for the Toolkit GUI (closed source) a professional product, since the product has been delayed
    due to personal, health and other reasons I had to make the ToolKitHelper program temporarily available for the current Toolkit and once the GUI is ready it will be merged with it.
     
  18. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210
    #22659 MSMG, May 21, 2022
    Last edited: May 21, 2022
    (OP)
    For people who can't wait for new version, have uploaded just the updated ToolKitHelper.exe (component remover) to support the latest patch Tuesday builds.

    17763.2928
    1836X.2274
    1904X.1706
    22000.675

    Code:
    Name: ToolKitHelper.exe
    Size: 11573248 bytes (11 MB)
    SHA1: 22afe72bea2d1764eba8b6afeb5448f8c0ea7b2d
    

    New Components Added

    Code:
    ## MultiMedia ##
    LockScreenBackground
    ScreenSavers
    SoundThemes
    Wallpapers
    WindowsThemes
    
    
    ## Network ##
    WindowsMail (Split from Windows Mail App - Communications App)
    
    ## SystemApps ##
    WebcamExperience
    
    
     
  19. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,487
    210