Okay. I just tried without enabling 3.5 and something else left behind pending.xml and thus making component cleanup impossible. I think it's best to take the image to virtual machine and do the component cleanup there. Thanks for the support MSMG, you rock.
Hi ceo54, well only suggestion when I work with MSMG Toolkit I never include.NET 3.5 because I know that in most of times ends causing error ( Are many operations at the same time and very easy to make mistakes) so I prefer enable after system installed using Dism with installation media pendrive, DVD is simple fast and secure and for last to earn time I have other option: go to first page of MSMG Toolkit thread click download and there search for packs then download ONLY .NET 3.5 for future use (same thing system already installed) so when you want install this file you need first install Winaero Tweaker for enable a lot of "things" after restart go to where you have file .NET 3.5 right click on file and simply install NO more errors ok
In the menu itself it says "Windows Cortana & StartMenu Search App". Glad to know that the customised OS is working for you.
Yes it works if you properly follow the instructions provided inside the readme.txt The Toolkit will remove the component that exist and gives a message if it doesn't exist. Do use the latest updates if integrating the updates.
For Windows 8.1, integrating some updates does triggers the pending.xml. For Windows 10, when using the ToolKit, it's only the .NET35 which triggers the pending.xml unless ortherwise if you had enabled/disabled any features manually outside the ToolKit. If you want to integrate .NET35 then do it after the component cleanup.
Well as the Windows 10 RS5 RTM ESD images have been released for download, the current version of Toolkit won't fully work with RS5. The Toolkit support for the RS5 will take some time and so I do request people to wait for the Toolkit update.
happy to hear this! can you just say your time map for relise it? just ~about its ok, im just have not many time to check all projects everyday and if you say me around how many months it be ready it will be very helpfull. thank you!
MSMG MDL Developer Please Tell Me: When Does the Version Compatible With Windows 10.0.17763 Come Out?
Hi people, a noob here If we divide system MS apps and components into Crapware and Spyware, what is the best approach to remove Crapware and reduce Spyware while retaining "fully" operational Windows 10? Today I made a custom Windows 10 Pro 1803 version (17134.112) using the MSMG ToolKit v8.8 I removed majority of Crapware, except MS Store, all MS components and some of the advanced ones like Telemetry, Cortana, Defender etc. The end result is a pleasantly clean and "light" version of Win10. Unfortunately Search is gone and some of newest updates are impossible to install (I've tried regular ways and fixes without re-integration of updates). I've read posts from the last couple of months. But I cannot summarise things well enough to help myself out. From what I understand, at the moment, best way to achieve what I want is to remove Crapware, leave Spyware and later on in Windows use some other tools to improve privacy behaviour (disable Telemetry etc.). Cortana remains? I'm returning back to Win7 for the moment but I have to admit that Win10 looks and feels much more modern and pleasant for work. Unfortunately, at this point they're both Malware (allowing 3rd party apps to be installed in updates) and Spyware. Thank you for your help Bye, M Edit: Ofc thank you MSMG for creating this tool
Thanks for the suggestion I'm just somewhat afraid that it has a similar load as Win10 Win7 are dull but we "know" what is going on. I use my laptop primarily for development and media. It has a 3rd gen i5, 16GB RAM and a Samsung 850 Pro SSD and it will idle with CPU at 30-50% servicing background crapware/spyware in Win10. On my Surface Pro 3 that means fan kicking in, device heats up, battery gets drained quicker A custom debloated version of Win10 is much more better but it might be crippled in ways that I've not yet perceived. Shame, shame on you Microsoft