1) If it's about components not returning after updating with latest updates, yes it won't return for Windows 10 v1809 and below versions. Starting from v1903 the components expect the Windows Apps do return when updated. 2) If it's about the removing components for 17763.2237 and the next CU is not getting installed properly, then it's due to the current version of Toolkit can remove components only for 17763.2183.
When reporting an error do specify in detail what's not working, do specify which components are giving error and what errors.
MSMG, A blue window appears with the message "Why did my PC restart?" at the end of a Windows 10 Version 21H2 19044 installation. A list of components that I have excluded from removal: Code: InternetExplorer FirstLogonAnimation SnippingTool WindowsMediaPlayer WindowsPhotoViewer WinSAT WiFiNetworkManager Paint WindowsFirewall Wordpad OOBENetworkCaptivePortal OOBENetworkConnectionFlow Calculator
Hostbuild and others, I put through the "ver" command. I made other changes. I replaced the DISM to get HostLanguage through the registry, for performance. You can see the difference when the "for" command does a search for data through the "dism" command. It is very minimal, there is a difference. I modified how you get the displayVersion (for Builds before 19041) on the build 22000 the key to look for LocaleName is different (I wanted to avoid searching the HKCU key. I kept the search on the HKLM key.), this was added. And, it was modified as the full version of the host version through the "ver" command is displayed on the screen.
It would be interesting to take a picture of the message. I believe that a StopCode message has been displayed. If that's the case, what was the StopCode offered at the end of the message? Note: problem that is usually caused by importing .reg files. This is a very vague assumption due to the few details you provided.
Thx MSMG Toolkit v11.8 first release works for 1809 LTSC with no returns, and the new Cu is installed properly
This problem only occurs on UEFI and can only be detected on real hardware. I speak from experience. I'm using these same registry tweaks, after removing the following components for Windows 10 Enterprise LTSC - no problems detected, neither on the virtual machine nor the real one. UnifiedTelemetryClient WindowsErrorReporting SecurityCenter BioEnrollment ContentDeliveryManager EdgeDevToolsClient FileExplorer ParentalControls PeopleExperienceHost SmartScreen WindowsDefender From my experience with toolkit v11.8 LTSC 1809 has no issues 21H2 v10.0.19044.1237) Source OS is needed to remove above packagelist correctly
To remove components in Windows 10 Version 21H2 - I used the original Windows 10 LTSC with the protector disabled. Is it necessary to use the latest version to uninstall? p.s I don't understand anything, what do I need to do to remove unnecessary components correctly?
JLT2000, The readme says Windows 10 is supported, I didn't find there that LTSC is temporarily not supported. p.s There is no option to download the Enterprise edition.
Read changelog in toolkit, and you will find the only supported versions with the Updated Feature "Remove Windows Component Choose only pro, and select last option, additional editions, then enterprise is available If you want LTSC 21H2 To my knowledge LTSC 21H2 is not yet arrived, as consumer downloads And will probably not work correctly, before a new supported Toolkit
Carefully study the contents of the Changelog and README before getting started.. It helps a lot. Let me clarify a little for proper understanding (useful for beginners who at least sometimes view the topic): not the Toolkit, but the component removal module itself (ToolkitHelper.exe ) for the correct removal of components should be used only with the assembly that it supports (this is indicated in the current Changelog). For integration of components and other tasks, such precision with the CU number is not required.
Please try to formulate it better - what exactly are you doing? We all speak different languages, and translators correctly reflect the meaning of what has been said, if you try to explain in more detail and intelligible words what you understand and what you mean by asking questions. Apparently you mean LTSC as a host system? If so, then no problems should arise. If you only need to get the Enterprise edition with uupdump, you should select Pro as the source edition on uupdump.net and then, edit ConvertConfig.ini as follows: Spoiler: ConvertConfig.ini [convert-UUP] AutoStart =1 AddUpdates =1 Cleanup =0 ResetBase =0 NetFx3 =0 StartVirtual =1 wim2esd =0 SkipISO =1 SkipWinRE =0 ForceDism =0 RefESD =0 [create_virtual_editions] vAutoStart =1 vDeleteSource=1 vPreserve =0 vwim2esd =0 vSkipISO =0 vAutoEditions=Enterprise Warning: If you perform a cleanup: Cleanup =1 ResetBase =1 , you will get an SFC error after installation, but this is fixable using sfc /scannow (this is true for versions 2004-20H2-21H1-21H2, details about this problem are in the topic)
Is Windows 10 LTSC compatible with MSMG Toolkit v11.8? Will I be able to remove the components correctly from Windows 10 Enterprise Version 21H2, listed below? Code: UnifiedTelemetryClient WindowsErrorReporting SecurityCenter BioEnrollment ContentDeliveryManager EdgeDevToolsClient FileExplorer ParentalControls PeopleExperienceHost SmartScreen WindowsDefender