I seen a post where a guy said that the only downside to this tool is you have to manually add new Windows builds that come out through the tool. Is that true? or can you use windows update? The persons post: "I think the downside to MSMG Toolkit is that each time a new Windows 10 build comes out (Creators, Fall Creators for instance) you have to manually download the ISO and apply your customization again and then upgrade using your custom ISO as if you update directly through Windows Update it's going to install all the bloat again."
V8.6 can’t remove windows defender on windows 10 enterprise LTSB 2016, it can’t find the cab files. V8.4 works fine. Please ignore, it seems 8.4 is not working as well now ? I did this the other day and it was fine, only difference is i'm using the latest cu update instead of the previous one.
The solution is simple, don't integrate any updates... Seems that the toolkit is having some problems with the latest CU.
I just tried again with clean rs4 iso and removed all metro apps and all windows compenents and cortana i didn't remove those in 'at last' section telemetry, defender etc so now i can see smartscreen settings there are inside windows defender itself i think you should just mention that removing defender remove also smartscreen along with it except for edge if you didn't remove edge itself or smartscreen and about the phone section in windows 10 settings it still disabled and same message given 'settings managed by your organization' i thought keeping telemetry will make it works but no, it seems that it is related to something else i don't konw what is it but i hope to find a way to make it work, it's the only problem i have now after using the toolkit
That's actually the point of discussion we have here. LTSB does not install any bloat when using Windows Update. But if you used a non-LTSB image, and don't disable feature updates, you will get all the bloat back after 6 months. If you read back you can see that there are some solutions to tackle this, by means of group policy or registry entries. You can use still use Windows Update, but if you like to upgrade to a new version (feature upgrade) then you'd better first make an image with MSMG and upgrade from that one. @Gadget-Man: Defender can be removed without problem on LTSB 1607, I did it a few days ago. No issues at all. You can also integrate the CU. It seems you are not following the correct order. Cheers.
please someone tells ms which part of the toolkit is responsible for this issue !! what i did with the toolkit is the following: Code: Integrated Windows Features: Microsoft Win32 Calculator Microsoft DirectX 9.0c Microsoft .NET Framework 3.5 ======================================= Removed all Default Metro Apps except Store ======================================= Removed Windows Components: OneDrive Desktop Client Skype ORTC Take Test App Hyper-V Internet Explorer UI Windows Media Player Microsoft Telemetry Windows Defender Windows People Experience Host ======================================= MSMG Toolkit Tweaks: Cortana Disabled Automatic Driver Updates through Windows Update Disabled Automatic Downloading and Installing 3rd Party Apps Disabled Windows Photo Viewer Enabled as default viewer i tried again from the start without removing telemetry, defender and people experience and same problem still happens View attachment 45691 View attachment 45692
like posted several pages ago, if you remove Asimov, you will not be able to get drivers for devices from windows updates!
I did it in the same order as I've always done it, i integrated the CU first, then removed defender. This is exactly the way i did it with the previous CU and it worked fine, so it must be the latest CU causing it as already mentioned.
I know but if you say remove telemetry but Asimov you're saying nothing. Hope it can be solved in another way.
posted by MSMG: quote "Tested with the ToolKit regarding the failure of Windows Update not downloading the drivers and sticky notes not working when the Microsoft Telemetry component is removed and it was found that the removal of sub-component Unified Telemetry client (asimov) was causing the bug. So either skip removing Microsoft Telemetry component or skip the sub-component Unified Telemetry client (asimov) until the issue is solved." there are a couple more telemetry packages besides Asimov btw
^yep you are correct, well when I used W10 1803 for test only for 3 days I don't have issues with WU because I always put any CU previously downloaded in my Folder 1803 Updates and remembering that I make my job using new Toolkit v8.6 and ALSO remove M$FT Telemetry for this reason is I don't see none issues; but after this 3 days I discover that severals members here complain about this behaviour so I also discover in Reditt a lot of peoples complaining about new changes by M$FT including TPM and more a lot of things for this reason I go back to EnterpriseS that I make fresh install without removing NOTHING and 100% without issues because I found some manner of only disabling "features" or same removing via Regedit or gpedit.msc really M$FT for me it is only including cosmetics and a lot of bloatware I believe that in 1903 or 1909 I'm only using Linux distro's with wine for games is my 2 cents dude