Good, but it is certainly possible to integrate updates in the same process. I've seen the CBS.log and there are way to many errors, that's not normal. Can you describe your workflow? Do you use WHD updates and integrate them before removing stuff? Cheers.
The main reason MSMG does not support 1903 images is because of the (possible) changes that may go in before it is released. There would be no point in investing a lot of time to support 1903, only to find out that some stuff has changed when it goes final. Cheers.
For now I shall work only with 17763.1 as I know from testing that this doesn't give me any sfc errors.
ISO: 17763.1.180914-1434.RS5_RELEASE_CLIENTENTERPRISE_VOL_X86FRE_EN-GB.ISO SSU: windows10.0-kb4493510-x86_9e3f2ba44fbf4f486ee3d57427b735c736459873.msu CU: windows10.0-kb4493509-x86_47af6f3f17da14a289340b880c88eeb27723c7ec.msu Spoiler: Method Extract ISO (1 > 3) Select source (1 > 1) (also mount boot and recovery images) Integrate Win32 calculator (3 > 3 > B) Apply updates (3 > 4 > 2 > 1 > 3) Cleanup (6 > 1) Remove all metro apps (4 > 1 > 1 > 8) Remove Onedrive, People, Connect, Skype (4 > 1 > 2 > H/J/K/P) Remove Store, Xbox, Game bar, Xbox ID (4 > 1 > 3 > 1/5/6/7) Cleanup (6 > 1) Tweaks for Task View, App Downloads, Photo Viewer (5 > 5 > 2/4/7) Apply changes to image (6 > 2) Rebuild (6 > 1) Convert WIM to ESD (2 > 4) Make ISO (7 > 1) The step in red is where I would normally integrate updates. But I follow these steps in the same order each time.
msmg: are you able to do up a version without the removal of defender, edge and other breaking removals.. and keep simple easy-to-work removals for 1903? and then slowly add support for those? that way, we can continue building without waiting for those... as those may take a lot of time. \ sorry if its rude to ask that
I did use NTLite and MSMG toolkit to remove stuff from 1903 but it's better to wait for full support on 1903 cause in my case WU got broken with updating the latest CU
Problem is when remove Holographic packages and then no working WU updating system auto and manual install updates.
I want to create a windows to go usb. Im going to use windows 10 pro iso, do i have to integrate windows to go or is it already included in the iso ? Thanks
i used ntlite to remove stuff from 1903 and i got this error 0x800f081f When i try to install the update KB4495666 from windows update .
I have updated and tested the ToolKit to support Windows 10/Server v1903 and as expected it's working properly with all updated packs. Windows 10 v1903 component removal will be added in due time once the Windows 10 v1809 component removal is fixed, I have fixed shared component removal issues and now I'm testing the images with updates pre-integrated. Hope to release an update in this week.
I make 1 VM clone for with removed Holographic and WU is bad, but 2 VM without remove Holographic package WU work Update is accepted no error. But will make today again reinstall for sure 100% is work. Edit: Again clean install with Holographic packages and work WU. CBS log is all need know what is wrong I analyze and detect package here is problem.
At my side it failed but now only removed defender and cortana edge and connect WU worked after that I have removed all the remaining apps hehe so basickly I have got what I wanted for now