It will restore the resources for removed components and the CU will be re-offered to updated the restored resources and in turn the removed components will get restored back. Do wait may be today will be releasing a test version.
You need to use the CU which the ToolKitHelper supports and non English images needs an update to fix the SFC error. Do wait for the next update.
1) Copying the required CU file to the WHD folder and integrating it is fine. 2) You can set the Windows Updates tweaks if you want but remember using WU or manual installation of CU after the OS installation will restore most of the components removed.
Why can't we support the version that was originally released? 19041.208 was the official release and image. I use it for processing.
So, in this case, we need to integrate the CU using WHD and then disable all windows updates using tweaks? And doing this will ensure that the CU is installed but the removed components aren't restored?
@AkarshM Don't mix things - CU inside the ISO vs CU as a future Windows Updates. - Disabling updates mean " for the future updates" on live system. Tweaks are good, but not enough. - Today no one is sure how to avoid "restoring" of removed components within the future CU on LIVE OS (not ISO). This due to ugly WU design. - You are OK applying different options built-in MSMG (except non-English Editions, that will be fixed soon)
hmm sometimes some strange things happen to us that we are stuck up to the neck in the world of informatics i can only laugh see the newest thing that happened a little while ago i was using the W10 LTSC in pt-BR my native language but when discovering that the powershell did not I was updating the help files correctly because of the language I decided to do a test: I returned the system to the native language en-US, restarted the machine and for some reason I opened the task manager and went to check the boot time err I was amazed only 4, 9 seconds ... then I decided to do another test I went back to pt-BR restarted and did the same process haha the system took 6.2 seconds lol needless to say which language I am using ...
@Tiger-1 Also I have read somewhere that you can't simply switch the languages without further negative consequences. To have some built-in apps working properly you also need to reinstall a certain part of apps. Defender is a good example. Or you will get artifacts in the UI / Start menu or smth. even more disgusting. (Probably depends on how different switched languages are)
@Tiger-1 I'm too, my friend. Interesting language contest. I couldn't imagine that languages have affect on boot speed.
I can confirm that people, which using 2-3 languages, expecting a big troubles with ugly mixed interface / names and have some artifacts. When they use at least 2 languages for UI + switch to another one, plus have different Regional standards and 3 or more languages in Language bar to write, then Windows becomes a mixed nightmare. I'm also using 3 languages in the Language bar, using one russian UI and have other Location & Regional standards. BUT I never switch to other UI language globally after installation, that's why I never expect mixed / broken / artifact interface or smth. like this. In our multi-national digital world any respectable OS should do this job just flawlessly, on the fly, I think.
hmm going forward I will only use the English version en-US so I will avoid unknown problems so far regardless of whether I made use of the MSMG Toolkit or not...