Yes, MSMG toolkit provides an enable feature/add package option for it, afaik. Manually it's: Code: DISM /Image:x:\Mount\ /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:y:\iso\sources\sxs\
Although integrating the updates after component removal works, it also have an issue like sometime the updates may restore a empty folder or resource file of the removed component which can't be fixed since we are using the DISM to integrate the updates. Starting from next release of Toolkit, I will change the order to integrate the updates after the component removal, so that this will help to integrate the .NetFX35 before the updates integration. I'm also working on component removal with updates pre-integrated for future versions.
I didn't understand this. Please somebody help me solve this .NET 3.5 riddle. It leaves the Pending.xml which makes componentcleanup impossible, resulting ISO not only has more size but also takes more time to install. One way of doing this would be to add the updates, do the componentcleanup and then enable 3.5 but I'm hesitant to take that road. Some updates might not get integrated before 3.5 is enabled on the image. I was thinking maybe after doing all the stuff with the toolkit, take the image on VM and do the componentcleanup and resetbase in auditmode. Will it have the same effect is the real question. Can anyone please help me with this. I'm on 8.1 x64.
Should I wait for your next release before going back to my old method? Or wait for your next release and use my new method? In the meantime I can live without removing People, as this causes the error in my testing.
Hello developer, kindly include an option to disable / remove windows update completely and permanently. There is no way to do this in the current version of MSMG, isnt it ?
^^ What do you mean by "already included" guys. It gets automatically enabled when O/s is installed or we have to use the dism command to enable it ?
But it has to be enabled for it to directly work after installation, right ?. I ran MSMG in the July update and it states the dot net fx is not enabled and i enabled it. So it may be integrated, but it doesnt mean it will get enabled automatically after the O/s is installed, right ?
I removed all other windows 10 editions, left only Windows 10 Pro, debloaded it, and got an error in installation, , Windows setup cant countinue, wtf :/, i think it has to do with the fact that i removed windows editions ?
It could be helpful to mention the exact error you got? Simply deleting sku's from the install.wim should not cause errors when installing.
The next version will be delayed as I'm refining the component removal for Windows 10 RS3, RS4, so till then better use the present version. Don't integrate the updates, just remove the components and leave the updates installation to WU, this method will work.
You need to integrate the .NET FX3.5 after the cleanup, please do follow the steps specified in the Readme.txt.