I have made changes to Toolkit's menu in next release, below are the changes 1) Removed Convert menu from main menu as it was missing the proper order of Toolkit functioning. Now the Main Menu looks like this Code: =============================================================================== MSMG ToolKit - Main Menu =============================================================================== [1] Source [2] Integrate [3] Remove [4] Customize [5] Apply [6] Target [7] Tools [X] Quit =============================================================================== Enter Your Choice : 2) Moved the items Convert Store ESD, MCT and Custom ESD into Source Menu as below Code: =============================================================================== MSMG ToolKit - Source Menu =============================================================================== [1] Select Source from <DVD> Folder [2] Copy Source from DVD Drive [3] Extract Source from DVD ISO Image [4] Extract Source from OEM IMG Image [5] Extract Source from Store ESD Image [6] Extract Source from Media Creation Tool Image [7] Extract Source from Custom Windows ESD Image [X] Go Back =============================================================================== Enter Your Choice : 3) Moved the Convert WIM to ESD into Tools->WIM Manager menu as below Code: =============================================================================== MSMG ToolKit - WIM Manager =============================================================================== [A] Display [B] Rename [C] Delete [D] Export [E] Convert [F] Split [G] Merge [H] Upgrade [I] Capture [J] Apply [K] Cleanup [X] Go Back =============================================================================== Enter Your Choice : People who do follow the custom menu orders do make the necessary changes in your info.
1. Sure, I can wait for the next release. The which-WIndows-build-and-Toolkit-version-can-use-together-or-not is a bit maddening for me right now but I'm trying to understand it. 2. I don't remove the firewall. It's one of the few things I leave. I remove Defender antivirus/malware/etc 3. I'm getting errors while removing those items. Path is short, C:\TK ... and I have NO antivirus at all since Windows 98. 4. I suppose those errors may be related to using both DISM and Helper methods to remove the most I can. There are things that DISM doesn't remove and some other that Helper can't either, that's why I mix them. Could you recommend the best 'mix' for removing the full list of items between both methods? Thanks!!!
I also see the clean source only lists 2004 versions, is there not a clean source for 2009 available?
The problem is with the recent CU's which generates Ghost SFC errors when Cleanup-Image is run and ESD available from MS is pre-cleaned images with more SFC errors. I haven't checked MCT, will test when I do get time.
FYI : Checked two stock MSDN [RU] images (distributed as adguard ISOs) 19041.508 and 19041.572 - both are INCONSISTENT (SFC failed), just after installation. ru_windows_10_business_editions_version_20h2_x64_dvd_979d1230.iso ru_windows_10_business_editions_version_2004_updated_oct_2020_x64_dvd_639c5230.iso
2004 (19041.1) - What the number of build exactly to find 3-rd party ISO shares over Internet? I can't use dl.delivery.mp.microsoft.com / UUP due to a massive security restrictions / firewall rules / DNS blocks over various places inside my main OS. The only exception - I can download single files (e.g. ISO/ESD) from dl.delivery.mp.microsoft.com over TOR, but can't use direct links spreaded over UUP scenarios or in standard way (main browser / ISO tools / etc.). Only by single file over TOR, I have no other way to download from M$ delivery servers. If you know any hash number for the proper Business/Enterprise [RU] ISO, please post it also. I need only 2 the proper numbers: build (w/o SFC errors) and hash. Thanks.
OK. Understood. Thanks for the clarification. Let's consider it this way now, please: Which method is preferable/cleaner/thorough? So if I have a package to remove and should only use one method, which is the order from best to least-best method to try? DISM <> Helper <> AppList
@Bokeron I'm always use only these 3 lists to remove / disable (according to templates) and always Toolkit method: DisableFeaturesList.txt RemoveAppsList.txt RemovePkgsList.txt Note: No DISM list (method) for me!
May I ask why don't you use DISM? I remove almost everything from every list. Would that change the order you follow?
Because this is recommended by @MSMG : to be sticked to the rule to use ONLY ONE method from two. And Toolkit method was always recommended. Simple. I didn't tried both at once. As @MSMG said, you may try, but only on your own risk. (Before his message I thought using both methods at once is "highly restricted", "wrong" or likely a "user fault") --------- Note: Removing of many apps / packages are not proposed by MSMG to stay within safe borders. But I always wish the capabilities of MSMG bundle become expanded with removing system apps without limits, as an "extra" options for advanced users that don't care about SFC checks, but want more debloated OS (in spite of CU are not avalable anymore). To be clear: SFC checks are important: - for original source disrtos (to check M$ quality itself, because they fail with their own images) due to poor QC (Quality Control) - for MSMG bundle with present capabilities SFC checks don't matter (they will obviously fail): - for hardened custom images or purely debloated live OS with system apps removed and w/o functional CU
@ingviowarr I've been deleting almost everything with MSMG Toolkit 10.4 and Windows 19041.264. Used all the lists, and errors were managed more gracefully than current version (and there were few than now). I cleaned with resetbase and didn't even cared to try sfc. Everything I wanted to keep was working without a single problem. Now I can't even remove Edge and get errors on different phases and elements depending on Toolkit/Windows versions combination. I'm about to give up and go back to previous versions. I'll wait for next update to see if it solves these problems and can remove everything it was able to remove before.