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.
I'm glad it works for some people but I see no reason not to follow the developers recommendation To each his own I guess
The next build will be locked down to images without updates, may be that will stop people from following their own order and later complaining when it breaks the update or any OS functionality.
Just to clarify, since people interpreted my previous comment wrongly. I did my test using those steps I mentioned before MSMG suggested the correct steps. I've been using the correct steps ever since. If it means that the world would fall down on me, then so be it.
.Even though its not supported I played around with some other things. I removed all windows and system apps and everything seem fine on the surface except one thing---sfc repaired syncsettings.dll. I don't know if me testing likes this would help you at all but I thought I would give it a shot.