Hi, I want to apply update and clean up Win11 22H2/23H2. Looking at the lists, toolkit method can remove more, but it's compatible with specified builds only. a) to get it working with any build I need to change IsCustomRemovalBuild to Yes in Toolkit.cmd, right? b) dism method needs fixed drive to work, toolkit method too? Thanks in advance.
No. This only informs you (displays the warning, but does not interfere with the operation) that the build you are trying to work with is not supported by the part related to component removal, by the "ToolkitHelper" methods. To make it work with any build: 1. Create your base ISOs (for use in the Toolkit or IMCK) without updates, through the UUP dump. You will obtain "buildnumber.1" ISOs. 2. Download the updates separately (these are in the same place where you create the zip package to create the ISOs in uupdump), and integrate them with WHD method (put the files into WHD folder), through the Toolkit (it integrates up to 23H2 without problems, but displays some information on the screen such as 22H2, in the "Enablement Update" integration and for 24H2 the integration is partial. I am transferring and implementing this code from IMCK.cmd to Toolkit.cmd) or in IMCK it is working. Note: People who already have experience with the Toolkit will see a big difference in IMCK... Because in IMCK the menus (Integrate, Remove and Customize) work by selecting everything you want to be done, returning to the beginning of the respective menu (without returning to the main menu, this would reset your choices) and using the option to apply what was selected. Can you explain your question a little better, in more detail?
I want to make whole operation on flash drive/pendrive, but I'm getting an error when mounting image, saying it must be a fixed drive.
I don't think it would be possible, because you would have to extract the Toolkit onto the USB stick and it would have to be a huge USB stick, since in the Toolkit or in the IMCk (which is a derivative), we have the extracted ISO and generally (at the user's option) all the indexes are mounted. The space to save the finished ISO will be guaranteed after the commit unmount of the indexes. But the free space requirement can reach 60GB or more. I've done it with SSDs via USB 3.0 and had no problems. But I've never tried it with a USB stick. You can configure your device as non-removable, but you'll have to research whether this is possible on your system (the last time I saw this was on w10).
There are no build.1 ISOs in massgrave. They are the ISOs provided by MS. In UUPdump, downloads are made from MS servers, but the ISOs are assembled from scratch, with @abbodi1406's scripts. MSMG maintains support for build.1 ISOs, so create these ISOs via UUPdump to use as bases for your custom ISOs. read build.1 as: 19041.1 22000.1 22621.1 26100.1 About updates: You can get them from several places: But in UUPdump the list is contains the essential update files and always correct. When you pick it up yourself, you can also follow without errors through the lists maintained by @Enthousiast who always keeps them complete, correct and updated.
UUPdump seems to be very nice option but unfortunately I can't download anything via package generete there, because of certificate chain/whatever error. I'm thinking to manully download files via Firefox, but again UUPdump says my version of Win10 is too old to create ISO. So I'm stuck with: a) ISO and update (.msu) b) ISO from massgrave, which is at least updated.
So, I advise you to get an iso of w10. Do an inplace upgrade. This will fix a lot of things for you. Then you make the custom ISO and test it in VM before performing a clean install.
Today I have tried UUP on friends computer, it works. So the correct steps are: a) create ISO of 22631.1 via UUP (without Windows Apps or with them?); b) separately download update for 22631.4169 from UUP, c) pass both ISO and update through MSMG. because trying to use ISO of 22631.4169 built via UUP, in MSMG will fail. Also from MSMG README.txt: "[H] - Remove Windows Components using Remove menu. ... Note: Only for Client (x86 & x64) editions source images with integrated cumulative update specified in the changelog.txt." and Changelog.txt: "+ Updated the Feature "Remove Windows Component" to support Windows 11 Client v22H2 (v10.0.22621.1) & v23H2 (v10.0.22631.3447 [KB5036893]) Source OS." so the Remove Windows Component feature works with 22621.1 and 22631.3447 only? Sorry for questions, but I have no experience with MSMG at all, and I want to understand how it works. Probably I'll break something, but at least I will use correct ISO
For apps you could use the customappslist option and only include these apps: Code: Microsoft.WindowsStore_8wekyb3d8bbwe Microsoft.StorePurchaseApp_8wekyb3d8bbwe Microsoft.SecHealthUI_8wekyb3d8bbwe Microsoft.DesktopAppInstaller_8wekyb3d8bbwe Microsoft.Windows.Photos_8wekyb3d8bbwe Microsoft.WindowsCamera_8wekyb3d8bbwe Microsoft.WindowsNotepad_8wekyb3d8bbwe Microsoft.Paint_8wekyb3d8bbwe Microsoft.WindowsTerminal_8wekyb3d8bbwe Microsoft.WindowsCalculator_8wekyb3d8bbwe Microsoft.ScreenSketch_8wekyb3d8bbwe Microsoft.XboxSpeechToTextOverlay_8wekyb3d8bbwe Microsoft.XboxGameOverlay_8wekyb3d8bbwe Microsoft.XboxIdentityProvider_8wekyb3d8bbwe Microsoft.WindowsSoundRecorder_8wekyb3d8bbwe Microsoft.GamingApp_8wekyb3d8bbwe Microsoft.XboxGamingOverlay_8wekyb3d8bbwe Microsoft.Xbox.TCUI_8wekyb3d8bbwe Keep in mind, everything from Photos down is completely optional, the top 4 are needed to avoid various errors as far as I know. ScreenSketch is needed for various screenshot taking capabilities. Xbox stuff and GamingApp are needed by some games(mostly ones published by MSFT) to run. The feature will either: A) Work as described for the supported builds(in this case .1 and .3447) B) Work partially when using the toolkit against unsupported builds - incompletely remove stuff, hang for a time during removal process, etc. C) Not work at all, because, well, UNSUPPORTED build. The "support list" exists to reduce various functionality questions to a minimum, when the cause for said questions is obvious. Using the toolkit against an unsupported build is completely up to you and your experience will vary to others. Just don't expect too much.[/code]
Ok, I found this: https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-1363#post-1852927 "Any time you don't include updates for 22635 22631 22624 22623 22622, you will get the base build for any of those which is 22621.1." So the base build for 23H2 is 22621.1, not 22631.1. That would explain my confusion.
MSMG / anyone who knows: How do you download those Bin\AppLicense\*.xml files? (yes i know i can use the xml's in your dir, but i'd like to know how to actually download them) I need those files for a little project of my own.
When you dont have the xml, on DISM command, just use the argument /SkipLicense I had read that the XMLs are in AggregatedMetadata.cab (Only from w11 22621 onwards). Here, .
@Paul Mercer. The DesktopTargetCompDB_App_Neutral.xml file is installed with what MSMG dialog? I haven't used MSMG in a while but I don't recall a screen mentioning adding or integrating a license. Also does this restore or affect Microsoft Apps that have been removed? Thanks in advance for the help.
The XMLs that were mentioned in the previous messages refer to the integration of Appx (This can be related to Toolkit). Paul only added to the quote I made from one of his posts. Nothing else that was mentioned about XML previously, in the last messages, has any exclusive relation to the Toolkit.