I suggest you do use the original Windows 10 v1803 (10.0.17134.1) image since the Toolkit's ToolKitHelper.exe is been coded based on the original image. Since you have specified removing any of the Windows component is breaking the setup, I will check with a ru-RU image to see if anything is wrong and will fix it.
Hi there, I have just used MSMG Toolkit for the first time to create a de-bloated version of Windows 10 Pro 1803. The process went smoothly but I have noticed an issue with the new installation. For some reason, the search feature in the Start Menu is not working. When I try typing with the start menu open, nothing happens. I have also tried pressing Win+X and selecting 'Search' but that doesn't do anything. The search box in the Settings app is also broken. I find this odd because I did not intentionally remove the search feature when configuring the ISO in MSMG Toolkit. Did I delete it by accident? Even this scenario seems hard to believe since I was making notes at the time of each item I removed. Is there anything I can do to solve this other than creating another ISO from scratch and reinstalling Windows? I see this as an absolute last resort.
Yes the W10 image v10.0.17134.1, that's the first release and you need to check with the ISO hash to verify the image. I usually do use the MSDN images.
You have removed the Cortana, which is also the Search feature, removing it will break the search functionality in StartMenu, Settings search box. You may need to re-do the image that would be better.
Thanks for your assistance. Yes, I did remove Cortana so that must've been what happened. Maybe you could include a warning within the program to inform users the side-effect of removing Cortana? Anyway, I re-produced the ISO with Cortana included this time, and now everything seems to be working as intended. It's great being able to install Windows and not have to clean all that junk that usually comes pre-installed. I had previously used Windows 10 LTSB but since it's still based on the old 1603 release, some UWP games like Forza Motorsport 7 refuse to work with it. The new LTSB release should be coming next month, but this is a great alternative for me since I needed something now rather than later.
does it work correctly on windows 10 2016 LTSB ? i mean will it show the components that do not exists ? (like store apps .... )
hi thank you for this util can you add more remove list in it? i would like to see here something more deep than cortana and defender.. at sample, delete all AMD drivers if you never use AMD CPU. remove all printers drivers remove all speach voices and components. for new hardware (cpu/intelGPU/IDE/old network interface/ets) - delete all old hardware-support files/drivers (at sample choose year which you have and delete before it, or choose generation line 7000/5000 something like this) remove some usless servises etc etc...more deep. can you do it? best regards
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!