If DISM is able to totally remove all the M$ bloatware all of us here wouldn't be using this tool... Win10 is not Win7 there is changes to DISM, its M$ making the changes and this tools is here to help in going around bypassing all the barrier that M$ setup. MSMG did a great job in creating this tools. If it is too sophisticated for you to use then perhaps you are not technical enough and better off staying with win7 or move over to macOS, coming here to rant and making nonconstructive remarks doesn't help just show how lazy and unresourceful you are as a person. Every words you said is non factual as the tool works for all of us and show how ignorant you are in person.
Did you also get around to test integrating CU's post-installation, with Telemetry removed? As discussed earlier, I am unable to integrate any CU post-installation.
I have never managed to remove Defender with the versions 8.4 , 8.5 and 8.6 even though i have applied all directions. Is there a new version on the way ?
Do you say integrate or be offered by Windows Update? From RS3 (I do not remember if in RS2 either) the telemetry must be configured to Basic at least to receive updates via WU.
AFAIK MSMG Toolkit removes Telemetry components entirely (advanced component removal). CU's are still being offered though via WU, but installation fails in final stage (after reboot): [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
@MSMG Welcome back! I'm glad to hear from you and very exited about upcoming updates! I found a bug, (using Win10_1803_English_x64) I deleted all WIM indexes except Windows 10 Pro Workstation N, followed the readme (KB4284848 17134.137), and did not remove defender or telemetry. At the end of the process I attempted to convert the WIM to an ESD as usual, but whenever I typed 2 for convert I would get menu 3 for integrate. I'm not mistaken, it really does do this. I don't understand why since I never had this issue before. I would also like to suggest the removal templates be updated and split (EG: RS1/RS2/RS3/RS4) so time isn't wasted on skipping non-present components.
Yes but when removing telemetry some tools configure the option to send data (telemetry) in the Settings app as Security and that prevented the WU from offering the CU in RS3 in the last tests I did a while ago. In older versions MSMG Toolkit did this, I do not know currently.
Yes the order was correct But I found out that I was using the older SS - KB4338853 instead of KB4343669, will try with the new one.
I haven't added telemetry removal for RS3 yet, only with the next version it's available and even for RS3 the WU - drivers not offering bug is still there.