1607: Code: 1. SSU = KB4132216 2. Flash = KB4457146 3. Dotnet472 = KB4054590 4. CU = KB4457131 kb4343902 = old flash
These components like Defender, SmartScreen, PeopleExerperienceHost uses the ToolkitHelper.exe for removal and the ToolkitHelper.exe has been coded using the Windows 10 vanilla image without any updates pre-integrated, and so may not fully remove the updated files added by the update. I'm still working on ToolkitHelper.exe to make it better to deal with updates pre-integrated. Till then we may have to move the integration step after the removal one.
@Enthousiast and @MSMG I have tested simply just integrating updates then removing People and I still get the error. So I am certain that the removal of People is giving me problems. Code: Integrate Win32 calculator (3 > 3 > B) Apply updates (3 > 4 > 2 > 1 > 3) Remove all metro apps and associations (4 > 1 > 5; 5 > 3) Remove connect, Onedrive, Skype (4 > 3 > A/B/C) Remove Store and People (4 > 3 > 2 > J/N) Windows Photo Viewer (5 > 5 > 6) Cleanup (6 > 1) Apply changes to image (6 > 2) Convert WIM to ESD (2 > 4) So move Integrate Win32 calculator (3 > 3 > B) and Apply updates (3 > 4 > 2 > 1 > 3) so they are done after Remove Store and People (4 > 3 > 2 > J/N)?
I can confirm that this method works. Should I use this method for my future builds, or will there be a fix to MSMG?
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 ?