Due to the ToolKitHelper.exe being coded using the original Windows 10 image without the updates as a reference for removal and the .NetFX35 being integrated it was breaking further updates being installed. At present the ToolKitHelper.exe is not been updated for RS4 and so removing other components which uses the DISM will not break the updates being installed at later stage.
Thanks Got it One more question I downloaded this from Microsoft Catalog How to Integrate it In Packs\WHD or Updates 2018-04 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4093112)
But previously after removing it with this tool it didn't appear in the start menu and optional features. Also, what is this default0 folder in the Users folder? It appears even if I don't use this tool. EDIT: I just noticed that even if I don't remove it this app won't appear in the Start Menu, just in the Optional Features list.
? ToolKit-v8.3 OS Win 17133.1 (vmware) source 17133.1 mount ... remove Defender and SmartScreen ... unmount and... not removed packages in wim = ToolKitHelper not working? in wim only cleaned (example \Windows\WinSxS\Backup)
It was me. I requested it. It is much easy way to use MSMG. Thank you don't forget what I asked you. Thank you again.
It is on all windows builds for years now. Actually since 14393: https://forums.mydigitallife.net/th...-refresh-pc-mobile.70297/page-50#post-1252228
If ToolKitHelper does not work on RS4, why is Defender and SmartScreen in the menu for build 17133? Or why it is not solved by deleting files and editing in the registry (example components) and uninstall packages. This is easy when cmd is running as trusted installer.
^^ You can use this command by cmd @ Admin: cmd = Net User / delete DefaultUser0 and then open the file explorer and in the users folder right click on the folder DefaultUser0 press shift and delete ok