Yes, I've made some progress in the translation process. The biggest challenge in the translation process is not having a proper classification.
Sorry if I am posting to the wrong forum. But does anybody know if Microsoft Windows Package Manager automatically installs apps in the default "C:\Program Files" location or can you script a custom installation location, like D:\Apps? I'm not a big fan of putting apps on the same drive partition as Windows.
I think this is the MS standard. I don't know if it's possible to customize it. It needs research. I know the "Microsoft Windows Package Manager" is Winget and all installation paths are defined by the installed application if you are installing, in non-interactive mode.
@tefor, Spoiler: how to: manually create the full filled partition In this screen press SHIFT + F10 to open CMD. Commands list after SPOILER. Commands List. Code: DISKPART LIST DISK SELECT DISK 0 or the number of your disk. CLEAN CONVERT MBR CREATE PART PRIMARY FORMAT FS=NTFS QUICK EXIT EXIT Choose the Edition and go on... autounattend file for storage clean and automated creation of one MBR table full filled partition for BIOS machines, attached. Not tested you need to make your mods. If you need to remove any of comments, just remove <!-- from before and --> after de comment line or block code of xml file. WARNING for other users, this autounattend.xml file will erase the entire disk.
Yesterday, I removed the links from my signature, because version 13.6 had some bugs when removing Provisioned Appx via DISM. IMCK has a configuration file with many options. A help was implemented so that these options can be accessed and also have support for translation via the command line, the integration of Updates for 24H2 is finished, and the removal of components via ToolkitHelper or via DISM for Builds not supported via ToolkitHelper are OK, too. Now everything is well tested and complete. I will soon release the version compatible with Toolkit v13.7.
I think this week. You will know when my signature changes. Note: Signature just doesn't show on mobile. Yes, dates, versions and adding links are the changes to be made. As you can see, I had set a release for 2023-08-14, but I encountered a problem when creating LTSC ISOs, which I have already fixed. However, I really don't have much time to carry out tests and work on the script. I want to make it as complete as possible without any major problems, hehehehe. It's best to handle anything related to IMCK here in the appropriate thread.
A few posts above I explained that I would launch it last week, but many details were being taken care of regarding the issue of integrating updates for 24H2. Now that people have reached a consensus on the best integration approach. Tomorrow more tests and on Thursday night (GMT -3) I will release the IMCK.
IMCK 13.7 merged with MSMG Toolkit 13.7 [2024-05-25] Code: 1. Several aesthetic code changes have been made. Like "ImageRegistry" to "RegistryImage" and so on. 2. New options added to the IMCK.ini configuration file. If you already have this file modified by you. Create a backup and extract the new one from IMCKcfg.zip. If this is your first time using it, run IMCK and everything that needs to be extracted on the first use will be extracted ONCE. This will prevent your custom lists from being overwritten in future updates. If there are updates to the lists made available in new versions, you should note the dates between your custom file and the date of the corresponding zip file. If the zip file is more recent, take a look at the changes. 3. The IMCK.ini options can be accessed using the "help" commands in CMD. 1. Open CMD in the IMCK.cmd folder; 2. type: IMCK.cmd /? IMCK.cmd /h IMCK.cmd /help IMCK.cmd -h IMCK.cmd -help ##### "_DEBUG" ##### "ColorCode" ##### "UImode" ##### "Localization" ##### "OnlySystemDrive" ##### "WorkingFolder" ##### "InstallMediaSource" ##### "DialogAndPauseOptions" ##### "UUPdumpConnection" ##### "DISM_Wimlib-Imagex" ##### "UpdateOptions" ##### "BypassRequirements" ##### "DescriptionsView" ##### "ToolkitHelperMethod" ##### "SpecificRetaining4Testing" ##### "CleanUpOptions" ##### "AutoUnattend" ##### "ISObackup" ##### "InPlaceUpgradeISO" ##### "RemoveManualSetup" ##### "InstallersFolderLocation" ##### "ShiftF10_ToolsMenu" ##### "RenameISOfilename" 4. ShiftF10_ToolsMenu was made with help and tips from my friend [USER=186858]@JeepWillys58[/USER] and is to be used during an installation, in which errors occur. It makes it easier to use. It is a script to bypass some errors and complete the installation. Apply the bypass. Disable network, etc. The name is ShiftF10 so you remember this shortcut, hehehehe The cmd will open. Your installation media maybe is D: Enter D: by typing: D: press <ENTER> type: Shift press <Tab> will complete the script name press <ENTER> Use the script. 5. Fixed issue in menus with choice selection method with ErrorLevel actions. If any option after the first option of the Menu returned ErrorLevel 1, this could start 2 options of that menu. Obviously this ended up starting the 1st option which is the ErrorLevel 1 option of that Menu. [USER=231182]@MSMG[/USER] this should also change it in some of Toolkit’s Menus. 6. Removed the "boot.wim" presence condition for users who want to work only with install.wim present in the "\InstallMedia\sources" folder. A recommendation from [USER=226364]@zero cool root[/USER]. 7. Improved details of the AutomatedProcess Mode. This is a hidden function present in the Main menu, to use all your custom lists. Use the letter "P" in the Main Menu. 8. Changed the positions of Extract Source and Select Source in the Sources Menu. 9. Changed the IMCK Drivers folder structure to be compatible with abbodi1406's W10UI Drivers folder structure. If you start Toolkit and needs to integrate drivers through it, Please move your Drivers to apropriate Toolkit's folder structure. 10. For Integrate Remove and Customize Menus, there are zip files with initial lists for you to customize and use the "P" (Personal) option. These lists can be used as they are. Try making an ISO with the options provided as a test once. So you can give feedback. I'd appreciate it! After that, customize your lists. Just remove to enable or add to disable where there is only one #. There is no need to delete lines. Note: if there is ## or ### or more, do not change them. This is just information. 11. Imagex is being used directly from the ADK. Before, it was being used from the Bin folder and was out of date with the ADK. 12. You can use ToolkitHelperRules4UnsupportedNewUpdates via IMCK.ini if you encounter problems using Component Removal via ToolkitHelper with integration of very recent Updates that may generate some conflict when removing components in versions not supported by the current ToolkitHelper. Ex: Although it is working with 24H2, the ToolkitHelper provided in MSMG Toolkit 13.7 does not support builds 26100. In other words, problems may occur. 13. Optimized the ":PackageBuild_ServicePackBuild" function. 14. All IMCK Lists are independent of the Toolkit lists. There is no concern about this. To identify the IMCK lists, note "_List" in their name. The Toolkit lists do not have "_". The Removal List via ToolkitHelper has a different name than the Removal List via DISM. A good change that was made to the IMCK lists is that the Removal Lists via ToolkitHelper were unified, there are no longer different lists for W10 and W11, you can leave whatever you want enabled for Removal within the list. If the component is present in the Image being worked on, it will be removed as long as it obeys the rules of dependencies on the components. In case you want to remove indiscriminately. There is an option to remove without filter. 15. As previously stated, your custom lists will no longer be overwritten when extracting a new version of the IMCK package. 16. Fixed an issue with ESD extraction, thanks to [USER=1437294]@fabricio simoes[/USER]. 17. NetFX35 has been removed from Integrate Features Menu. Now, only via Customize Menu Enable Features. 18. Added the Extra Features Menu to the Integrate menu, where InboxApps and GPedit are the options. Thanks to [USER=587894]@RafhaCorreia[/USER] for testing. I felt the need to, in compliance with the standardization of keeping the menus in the order of use, have a place to add Features that must be done after integrating updates, are not customized options and must be done before removing components, as is the case with activating GPedit for Core Editions, which was moved from the Customize Menu to this "Extra Features" menu. 19. A black screen freeze was occurring after downloading Updates that was related to the pause suppression settings, but it was not suppressing the warnings although it was suppressing their display. This problem of suppressing Warnings was fixed thanks to the tests carried out by my friend [USER=587894]@RafhaCorreia[/USER] and because of calling the Updates Downloader in some tests by [USER=226364]@zero cool root[/USER], in which some of these Warnings were also being called. 20. Fixed DaRT integration 21. Fixed Select All from Integrate Windows Custom Features Menu 22. Updates Integration has been completely restructured to support the integration of new updates for 24H2, the old method for integration in previous Windows has been preserved in this restructuring. 23. Optimized the differentiation function between LTS and non-LTS to improve Update integration details and designate specific folders to place LTSC Updates. 24. Optimized the definition of paths for WHDUpdates according to Windows versions and types. 25. Added 24H2 Multi-MSU update files support. 26. Added an option in IMCK.ini (MultiMSU_Procedure) that is related to procedure to Integrate Multi MSU files - For any CheckPoint Cumulative Updates and Latest Cumulative Updates 27. Fixed :ReadIntegrateMenuList function that doesn't properly selected the Update Options from this list. 28. Issues with Updates integration menus reported by [USER=587894]@RafhaCorreia[/USER] and [USER=226364]@zero cool root[/USER]. One of the problems was related to downloading updates via UUPdump, even if the option was disabled. It was calling the Updates Downloader script even though it did not repeat downloads if they had already been done through it. If it was added by the User, the Downloader could clear the folder and download again, causing a waste of time and preventing the integration of other files that the user could have added manually. This has been fixed. Thanks for testing help guys. 29. We also fixed the removals via ToolkitHelper and DISM Provisioned Appx that were not obeying the user's removal choices. 30. Compatibility with ToolkitHelpers from previous versions has been improved (considering that sometimes ToolkitHelpers had their components renamed or split, this respects the names of the Components of each version). So, for some reason, if the user wants to use the most current version of IMCK, but uses an older ToolkitHelper, they just need to replace the executable "\Bin\ToolkitHelper.exe". 31. Fixed a naming issue with the VCLibs140 removal component. The removal only works if you rename "C_VCLibs140UWP" to "C_VCLibs140". Be careful when renaming in bulk if someone wants to fix your Toolkit.cmd, as it will rename "C_VCLibs140UWPDesktop" to "C_VCLibs140Desktop". Then you should rename it back to "C_VCLibs140UWPDesktop". I have already reported this issue to [USER=231182]@MSMG[/USER] via DM. Note: I do not recommend removing it. 32. Added the possibility to select any Removal PreSet list via ToolkitHelper in automated options, including you can create several lists with different names as long as you preserve the original name of the files in the naming, your lists will be displayed for selection. To be more clear, do this in the "\Bin\Lists" folder, not in "\Bin\Lists\PreSets". So: create copies of "\Bin\Lists\RemoveComponents_ToolkiHelper_List.txt" Enter the names keeping the prefix "RemoveComponents_ToolkiHelper_List". examples: RemoveComponents_ToolkiHelper_List_TESTING.txt RemoveComponents_ToolkiHelper_List_W11_LTSC.txt RemoveComponents_ToolkiHelper_List_W11.txt 33. Reduced the amount of duplicate options in Menu and List form, transforming list options into "P" options within their respective menus. This was done for options within the Remove and Customize Menus. Added display of list paths with names where relevant. 34. Optimized the DISM Packages and DISM Appx Component Removal Menus. Note: You can expect an empty Menu behavior. Mainly if no components are detected for removal or if you enter the menu after removing all available components. Many times after removing components via ToolkitHelper, the same component will not be available to be removed via DISM. 35. You will notice that when you use the "Disable Features Menu" after a feature is disabled, it will appear in the "Enable Features Menu" so that it can be enabled again. However, this can cause problems. So, it is recommended that if you disable or enable something by mistake, discard it and start over. Customization through lists came to make this easier. 36. Optimized the Bypass Hardware Requirements function. Also fixed the functioning of Bypass Hardware Requirements in Inplace Upgrade. Thanks to the Tweaks provided by friend [USER=104688]@Enthousiast[/USER]. 37. Optimized Disable Features Menu and Enable Features Menu 38. Fixed the "Import Custom StartMenu Layout" that was clearing the shortcuts already pinned by the user in the Start Menu, after doing an Inplace Upgrade. Now, after the Inplace Upgrade the changes made by the user remain. 39. Added the "Disarm RECALL" and "Disarm Copilot" Tweak options 40. Creating the "AutoUnattend.xml" file, even if the ISO is in a different language, now allows you to keep the keyboard layout and timezone of your host. 41. Removed "Autologon" Option and "Insert Autounattend in Boot.wim" Option. Too much issues, no benefits for those who had used this. 42. Added “Bypass Hardware Requirements” on AutoUnattend file, for those who don't mount boot.wim. 43. Optimized the function of identifying ISOs in ISO folders. You can now define a custom path to your base ISOs obtained from UUPdump for use in customizations, in "IMCK.ini". This way, you don't need to take up space on C: inside the IMCK folder, e.g.: my folder was originally "B:\IMCK_TOOLs\ISOsource" now it is "D:\UUPdump\ISOsources" while my script folder is in "B:\IMCK_TOOLs\IMCK.cmd" and the temporary ISOs continue to be saved in "B:\IMCK_TOOLs\ISO". 44. Updated the "Winget Settings File Content" that is in "Custom Files" function on "Custom Features Menu". Now, you can place your settings.json in ".\Bin\WingetSettingsJSON" folder. 45. Improved the function to "CleanUp Image Temporary and Log Files or Folders". Now, the removal of these temporary files is guaranteed. In the previous method, remnants of registry changes, among others, were remaining. 46. Added useful options in Tools Menu. Possibility to mount something else if you forgot to do it at first. 47. Fixed details of ImageEditions_VirtualManager control to avoid repeating Editions Export procedures. Some observations about repeated exports were reported by friend [USER=1437294]@fabricio simoes[/USER]. Note: With the reduced processes, the performance to complete customized ISO has also been improved. 48. Skip ISO creation if there are no "boot.wim" in place. 49. The automatic ISO naming process has also been improved. My thanks to all of you who helped with testing and bug reports. To @abbodi1406 for being patient with my questions and teaching me a lot. And especially to @bala1 who provides full support, both in testing and as a maintainer of the IMCK Localization files, main LOCALE en-US and translation to pt-BR. Download in my signature. @nguyenhuuchinh @faiska @win11me Note: The Temporary and Interim Update for Toolkit.cmd is in progress, it will take a while yet.
Writing AutoUnattend.xml option was breaking IMCK. Reported by @fabricio simoes. I improved a message in the AutoUnattend.xml writing menu. Please, download it again, lol...
I've already left this one unlocked to deal with 24H2. IMCK 13.7 hadn't been released yet when MSMG released version 13.7, because there were many bugs found in IMCK 13.6 that had to be completely fixed. Only now, the appropriate level of stability has been reached for the release of this update. It was a long job, but done with care. Just extract it over the Toolkit folder. After the first run. The IMCK configuration file, "IMCK.ini" in the root along with the IMCK.cmd script and several lists inside "\Bin\Lists" will be extracted automatically. After you configure the lists (add or remove the # prefix, where there is only one #), you can use the "P" option (it is hidden in the Main Menu) to make an ISO from scratch, almost without interacting with the script (just press "P"). My suggestion: Make a test ISO with the lists that are already pre-configured. If you find any bugs, please report them. Make suggestions and request improvements.
I forgot to mention that the update folders for LTSC and Server builds should be renamed so that there are no problems when downloading the updates. As in the case of downloads for 19045 normal and 19044 LTSC, which ended up replacing the download for 19045 or vice-versa, because the respective default folder for these two builds was 19041.1. I just decided to adopt a new parameter to avoid a problem like this in the future. And something told me that this would end up happening again... And it did happen in "26100" (since there are "Normal", "LTSC" and "Server"). The download script already places the updates in the correct folders. But manually, you must take this care. On WHD folder: 10.0.17763.1 10.0.17763.1_LTSC 10.0.19041.1 10.0.19041.1_LTSC 10.0.20348_Server 10.0.25398_Server 10.0.26100 10.0.26100_LTSC 10.0.26100_Server
IMCK [2024-10-16] version. 1.The folders for the path to place the update files for the Builds described above were added to the zip package, to prevent the user from having doubts when manually placing their updates in the appropriate folders within WHD. 2. Fixed part of "Bypass Hardware Requisites" related to "AppRaiserRes" that was running on W10. This is only for W11, but it shouldn't cause any problems. 3. Fixed ToolkiHelper functions aren't showed for LTSC versions. Bug reported by @zcelakdgl member. Thnks! 4. I have encountered and fixed others: "Adobe Flash Player" wasn't being displayed for removal for any build that it should be showed for removal. And the "Windows Apps Menu" should now be displayed to the user because MSMG placed some components of the "System Apps Menu" in the "Windows Apps Menu" and this affects Server and LTSC. EDIT: IMCK [2024-10-17] version. 5. Added a condition to prevent the automatic deletion of Indices when an LTSC is being worked on. This will only occur if the user uses the TrimEditions option. 6. Added a compatibility check condition for LTSC 2019, which is not supported by the "Image Editions Virtual Manager". I had not defined such conditions, because I am not used to using this version of LTSC. 7. Critical Correction: Safe OS DU was not being identified for integration in LTSC, the new SafeOS DU are identified by the same method used for builds from 26080 onwards. 8. Added a condition to prevent the GPedit integration function from being executed in LTSC. An attempt was being made to execute this function, although it was interrupted, I prefer to prevent the attempt from occurring. GPedit is only integrated in Core Editions. 9. Fixed an error when finalizing an ISO when the user does not have ISOs in the ISOsource folder (folder which was designed for the user to place their base ISOs (usually ".1" builds), avoiding having to extract manually) and the ISO folder. The extraction function is now easier to use, as an automatic menu lists the ISOs present in both folders. Bug reported by @zcelakdgl member. Thnks! Download in my signature.
I fixed this yesterday and today. Several details related to LTSC have been fixed. Please read more in the previous post.
inTerActionVRI Where can I download IMCK? I didn't even find a signature on your profile. Sorry. Found it.