We can see many "cleanups" or cleaning leftovers during we use MSMG. Please, clarify to everyone here which exactly option you mean. I.e. the cleanups can be performed when Apply [6] or you mean do not use option in the [5] -> [8] Tweaks section? Which exactly option is restricted to be used with rescent CUs?
I meant [6] Apply -> [1] Perform Image Cleanup Please do check my earlier post here Performing DISM /Image-Cleanup /StartComponentCleanup is breaking SFC with recent CU's even if components are not removed. Will perform a fresh component removal test with 19042.572.201009-1947.20h2_release_svc_refresh_CLIENTBUSINESS_VOL_x64FRE_ru-ru.esd and report back.
Aaah... I thought you ran this command "as command" (outside MSMG) - I understood that message literally. Now your clarification make things much more clear. Thanks.
The Edge Chromium package used in 19042.572 is older than the current enablement package and that's why the Edge Chromium was getting skipped while removing. Will fix the issue.
@MSMG right now I'm doing the conversion from ESD to WIM but using Toolkit V10.6 in the W10 2004 image without any problem (I used the modified media creation tool) ...
I mean in v10.7, as random multi-index mode was added earlier the Store ESD-WIM conversion required a fix which I just added.
Hi ingviowarr I agree of course just think a little bit these components are essential within the operating system at least for me I NEVER removed them for this reason I never had any problems...
To summarize, we can consider the last ESDs (572) as broken by M$? What are recommendations then? Is it OK to use 20H2 Build 19042.508 (ISO) + Update integration up to 572 / 608 using the next MSMG build? (I suggest 572 / 608 choice will depend on Toolkit component remover support capabilities)
For time being - Get 19041.1 UUP Generated ISO (Set not to integrate .NET FX35 or any other updates) - Copy the below updates to WHD Update Pack folder Copy Windows Cumulative Update (KB4579311) file to <WHD\w10\<Architecture>\Cumulative> folder (E.g. <WHD\w10\x64\Cumulative>). Copy Windows Defender Update (defender-update-kit-x64.zip) file to <WHD\w10\<Architecture>\Cumulative> folder (E.g. <WHD\w10\x64\Defender >). Copy Windows Dynamic Update (KB4558130) files to <WHD\w10\<Architecture>\Dynamic> folder (E.g. <WHD\w10\x64\Dynamic>). Copy Windows Enablement Update (KB4562830) files to <WHD\w10\<Architecture>\Enablement> folder (E.g. <WHD\w10\x64\Enablement>). Copy Windows Flash Player Update (KB4580325) file to <WHD\w10\<Architecture>\FlashPlayer> folder (E.g. <WHD\w10\x64\FlashPlayer>). Copy Windows .Net Cumulative Update (KB4580419) file to <WHD\w10\<Architecture>\NetCumulative> folder (E.g. <WHD\w10\x64\NetCumulative>). Copy Windows Servicing Stack Update (KB4577266) file to <WHD\w10\<Architecture>\ServicingStack> folder (E.g. <WHD\w10\x64\ServicingStack>). Copy Windows Setup Media Update (KB4588844) files to <WHD\w10\<Architecture>\SetupMedia> folder (E.g. <WHD\w10\x64\SetupMedia>). Copy Windows WinPE Update (KB4579305) files to <WHD\w10\<Architecture>\WinPE> folder (E.g. <WHD\w10\x64\WinPE>). Use this windows10.0-kb4562830-x64_816fd030691161bfc9f892f0e9e1259e23a56c82.msu Enablement Update file. - Use Toolkit's WHD Update Pack Integrate menu to integrate the updates - Use Toolkit's Remove Windows Component using Pack List method to remove component (Don't include Internet Explorer and Kernel Debugging) - Don't run the cleanup-image since it breaks the SFC. - Apply and Save the Image. - Rebuild the Image. By the time next version will be released, there will be a new public CU released will update the Toolkit to same version.
well although i'm just a humble apprentice in the art of working with the code for now i came to the conclusion that Toolkit V10.6 is more consistent than the new one (V10.7) I may be wrong of course and I still hope that our master forgive but that's what i think at the moment
right now i'm finishing my work but using the version of Windows 2004 with MSMG Toolkit V10.6 i say this after seeing this in within the own M$FT itself so i think it is common sense NOT to use the latest one because it is evident that it has many problems...
MSMG, Thanks for the clarification. From version 1903 onwards - I feel more and more that our journey into the world of win10 adventures is just beginning, friends! With regard to cleaning images with the latest CU versions and related subsequent sfc errors, everything is now clear, thanks to your efforts. But as far as I understand, this is not particularly suitable for my case, since the cleaning was not actually performed at the stage [6] Apply -> [1] Perform Image Cleanup due to pending operations (presence of Pending.xml) related to EdgeChromium, which can be seen in my screenshot. Looking forward to your test, with gratitude!
@MSMG, I sent you information, by PM, about some typos and maybe some others that I'm not sure if they are or not. Also, a suggestion! I was unable to carry out my tests and post results. So, as of Tuesday, I will be able to check the implementation of the implementation of that suggestion that I proposed, "return to the previous menu". In the Custom Toolkit, I removed that extensive questionnaire for applying the tweaks, as the code gets smaller simply by returning to the menu that we were previously using. And, returning to the Home Menu is made easier by pressing "X -> X -> X". The idea of code reduction implemented in the removals part, can now be implemented in the Windows 8 integrations part. That question with "variables" was very top. In the custom there were multiple questions, one for each option for multiple removal. 01 The original multiple removal questions; 02 one copy of each (customized) and; 03 one of each, for the creation of each customized edition. Then, I reduced from approximately 15 questions to just 1 question. Very, very toooooop! Thanks for that idea! I made a suggestion regarding the multiple removal system simultaneously. I hope to send an outline of the idea ready Tuesday or Wednesday. Big hug!
Can somebody please explain what Enable DISM Image Cleanup with Full ResetBase does and if it's good to use it? 6 > 8 > M (Enable DISM Image Cleanup with Full ResetBase)
hmm well as far as I know if applying this command is not possible uninstall updades so it's better to ask directly to MSMG is easier I think
Starting from v1909 WinSxS files needs to be retained for installing updates due to new update format. See: One and Two