In the previous version I had implemented a automated method to recognize and remove the language resource registry keys but there was drawback it also removed some of keys bit early and trigger the log to report reg key removal failure and so I had to revert back to old method of removing the language resource registry keys which has increased the code size. And the code protection I have added with compression takes time to load, will checkout for better setting so that the executable will run faster.
@MSMG ,Actually in the regular integration tasks, the Metro Skin Integration Task for Windows Photo Viewer, Windows Media Player, and Win32Calc are work normal. Also, there is no running problem obviously with the components of the integrated skin. maybe you can delete version judge to test corresponding feture.
Since MSMG Toolkit won't support CUs and SSUs for some time, it means I won't need to build my image every month like I did previously. But I am experiencing ~30 second delays currently.
Microsoft are the ones making things hard for everyone with their bloatware. In any case, being able to remove stuff than not is of highest priority i'd say. I'm just waiting for a working 1903 version... even if removal is minimal. Whatever works is better than not work.
Wow, I never thought I would decide to switch to 10, this tool changed my mind Thanks for this great software, appreciate it
Sfc comes up clean even when you remove all components and then integrate all updates. This is on 17763.1 pro x64 en us
See this post for more details: https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-513#post-1517803
There are a number of people here that have done it the way I do and the way MSMG recommends. No sfc errors on the 17763.1 pro or ltsc x64 en us. If you follow the right steps it should be fine. If you are installing to a virtual drive....well I don't trust that so I always install to a physical drive. I've tested it more than a few times and always the same result.
Not if you use 17763.1 build (not refreshed ISO, no updates) and remove components BEFORE integrating updates.
you pointed me to a method that removes components after update integration, which isn't the right way
I made both LTSC x64 and x86, integrating updates first and then removing stuff. SFC comes up clean on both images. Don't say things are not possible when several people have done it successfully. Cheers.
Did you remove all windows apps, all system apps and all advanced components? If you did then I guess we know it works both ways. I'm going to do it in the order that MSMG recommends since he is the developer of this program . In all honesty whichever way you do it if it works that's the important thing.
The SFC comes clean due to the automation added to WinSxS part to remove the sub key values be it 10.0.17763.1 or 10.0.17763.XXX. But there are other sub keys that needs to be removed and some removed sub keys needs to be retained if there are updates pre-integrated, which may cause future issues.
Integrating updates first is certainly works when I tested it. The caveat is, you should do a cleanup image only after components removal. I've tested the ISO build this way few times on VirtualBox and one time on a real machine. SFC were all came clean, updates via WU working just fine and I didn't notice any errors.