Since the release of windows 8.x iso's, the ondemand cab for dotnetfx3 resides in th "iso:\sources\sxs" folder, MSMG toolkit looks in the sxs folder for the ondemand cab, and when existing, the toolkit will use it for pre-enabling dotnetfx3. manually: Code: DISM /Image:x:\ToolKit-v9.0\Mount\Install\Y\ /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:X:\ToolKit-v9.0\DVD\sources\sxs\
Hi, Pardon if this has already been mentioned, but are there plans to support Windows 10 19H1 Insider Preview builds (the 18XXX ones)? I mounted the build 18282 images with MSMG Toolkit v9.0 (while running build 18282), and when I press 4 for Remove and then 1 for Remove Windows Components, I get these errors: for each image, and then a message saying component removal finished successfully (when in fact I didn't select any components to remove). Thanks anyway! Edit: I'm going to try again, with the Toolkit folder in the root folder C:\ and antivirus disabled, and running cleanup before trying removal. Also, my ISO is en-US.
Where can I download latest StorePurchaseApp appx file? The MEGA download in there not the latest one.
Hi MSMG Could you tell me how the ToolKitHelper removes system components, I wanted to delete the CloudExpirience, but the ToolKitHelper does not support it For example, conditionally for the defender, the install_wim_tweak.exe changes the permissions, remove owners, add visibility=1 in SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Windows-Defender and dism /image:c:\ofline /Remove-Package /PackageName:"Windows-Defender" And what does the ToolKitHelper do?
Since now I have disabled WinSxS Cleanup, the registry entries for language resources also gets minimal. You need to watch out mainly for COMPONENTS registry hive for the language resources entries. A MDL member has helped with preapring the MUI image, soon I will start adding the support for all languages after processing the data.
The ToolKitHelper has been coded for Image Version: 10.0.17763.1, you need to use this image to remove components and then update the image with the latest update. Can you specify for which components you are getting that error?
The component removal has been tested in an order and removing the component random order can sometimes can break the setup due to some components sharing the files/registry entries, Do specify in which order you did removed the components using v9.0. As far my tests the StartMenu Search won't work on first boot, it takes a second re-boot to start working.
Sorry I don't have any plans to support Insider Preview Builds due to time it takes for me to add the support. By the time I do add the support there will be one or two new builds available.
ToolKitHelper is the component remover used by ToolKit to remove a component, the ToolKitHelper manually removes the files/folders/registry entries to remove a component.
I have a question about 1809 and future builds VS. 1803 and previous builds. Since 1809 made changes that requires you to at least temporarily disable WinSxS cleanup will future toolkit builds support 2 cleanup methods, one for 1803 and earlier builds and one for 1809 and later builds?
Yes when I do add back the support for pre-RS5 builds, I will also make sure the WinSxS Cleanup is performed for those builds.
MSMG MDL Developer > Please Tell Me> I Do Not Want to Remove> Windows Defender > How Do I Remove the Other Components Without Removing Windows Defender? The Question is for MSMG MDL Developer
I wouldn't had added the option Remove All Components to Advanced Windows Components since it was meant to remove the important components manually one by one But some people may wish to remove all advanced windows components too and that's why it was added. Leave Defender and remove the rest of components one by one or use the ToolKitHelper.exe to remove the selected components directly as discuses in previous posts. Will look into the possibility of implementing Package list to remove these components of user choice at once.