You can do in-place upgrade with the customized image but make sure you have integrated the necessary updates.
You can safely integrate the DaRT and DirectX9.0c without any issues. The updates should be integrated after the component removal since the component removal has been coded based upon the original image and so the updates component files/registry aren't removed if the updates are integrated before. I think Only the IE is causing the default App setting bug.
I probably removed too much things when I was creating my own ISO using this tool. I just realized that my system is missing MS Paint and PhotoViewer.dll, and also I cannot install Directx 9. Is there any option to restore these things? Without re-installing the OS of course, because I already installed many programs and copied files.
integrate the updates after the component removal causes a system error when installing windows (Pro 1809, Home 1809, LTSC 1809). so I install the updates first, then delete the components. it works
I tried Start.cmd, but i get same error. In Windows 10 Pro 1809 only removes the App TV. The other Apps tool does not remove..!!
MSMG MDL Developer All coders making the same mistake, they keep adding futures, making harder for them selves. Development time gets longer, more bugs, bloated menus. Can users update windows by them selves? Yes they can, than don’t waste you time on this future. Can users install language packs and some other packs, crappy games, crappy software, tweeks-shmeks, yes they can, then let them do it. What is MSMG ToolKit? It’s a tool to remove components right? Something users can’t do. Then do that, focus on that, make a best removing tool, stop making a swiss knife. Microsoft trying to be everything and what happened? You created removing tool, basically to undo they work. Soon we're gonna need MSMG ToolKit for MSMG ToolKit.
I always do it both ways. I prefer to pre-integrate but also build a post integrate image just in case the pre-integrate image has issues.
Fully agree with Padre_Pedro. If you first remove the components of the image, and then install the updates, then when you install the 1809 LTSC, you get an error. If you do as Padre_Pedro, then the installation is correct.
Same here. I have made several ISO from LTSC 17763.1 and 17763.112 Refresh, removing most of Windows components except telemetry. I let Windows install low drivers for my mobo. Installed on hard disks, running fine without errors even after upgrading to .168 using WU or Dism cab files. (Did not add any drivers, programs or .Net features). Prefer to do that later. Just waiting for MSMG Toolkit 9.1 and will do same job + removing telemetry.
As I wrote, I strictly followed your instructions. Deleted components strictly in the order of the alphabet in which the items went to the menu. First I deleted System Apps, and then the individual components from Advanced Windows Components in the order in which they appear in the menu. The problem with version 1809 arises, namely, during the initial removal of image components and the subsequent integration of updates. If you simply remove the updates from the image without integrating the updates, then there are no problems with installing the resulting image. Padre_Pedro suggested first integrating everything into the image, and then deleting it. At the same time, he deleted the same components as before, when he followed your instructions. It worked. I have an assumption that the updates contain components for those elements that we remove earlier and because of this, errors occur.
msmg: is it possible to manually re-add sync settings to installed windows that had their sync settings removed in the install image?
I finally succeded at getting Toolkit 9 to work with LTSC, but I had to first use NTLite to get rid of the N version. Then with Toolkit I added Edge, DX9, and removed all the apps and packages, except for System Restore. I then used W10UI 5.6 to update the resulting image, but did not integrate NetFX 3.5, eenabled full rebasing, then rebased and recompressed index thingy. The resulting image ended up larger in size than initial one. I think some packages like Hyper-V and Adobe Flash were not on the list of packages to remove and both Edge + DX9 took extra space. Why does MS still support Adobe Flash? It's ancient security vector This time I also went into registry and removed all InboxApps, except for Edge, Edge Dev Tools, CloudExpHost, Immersive CP, and ShellExpHost.
After the release of the update for Win 1809 KB4471332 (Build 17763.194) I checked the work of MSMG 9.0 using the Padre_Pedro method according to my algorithm. MS DART has been integrated too. =================================================================================================================== Source-> Select Source from Source <DVD> Folder Integrate all necessary Windows features (with the exception of Microsoft .NET Framework 3.5) Integrate all necessary updates for Windows. When integrating updates, use Integrate to Windows Setup Install & Recovery Image. Attention!!! Updates must have original names. Renaming updates will make it impossible to integrate them into an image. Apply-> Cleanup Source Images Remove all necessary Windows components You can delete all System Apps. In the Advanced Windows Components menu, it’s not advisable to remove InternetExplorer and WindowsMediaPlayer. Apply-> Cleanup Source Images Customize the image using the Customize menu Apply-> Apply & Save Changes to Source Images Apply-> Re-Build Source Images Target-> Make a DVD ISO Image =================================================================================================================== Everything worked perfectly. This method can be considered 100% working.
Without the ability to remove stuff from windows, I don't think I can remain in windows anymore. It's a real blessing to have the toolkit. Question now is if new methods of removal are stable / reliable enough with respect to future windows updates. This is what concerns me the most since the method isn't native. To a certain degree, I'm around the threshold of switching to linux desktop. I can't understand why MS is trying to make their OS worse and worse. Would be funny if Windows actually dies one day because of this.