I always use an 17763.1 image and I start the script with the help of a program called ExecTI. I stopped having that window message problems I had. Maybe it's an overkill if it works I keep on using it.
Absolutely... Started with an image downloaded via heidoc tool. updated with the whddownloader tool and built with msmg 9.2. The only errors were the Systemreflection windows ones. The image built and installed correctly, all features added/removed were effectively added/removed, but won't activeta using any method possible (including the knwon pirate ones). To verify my key wasn't blacklisted i installed the vanilla iso downloaded, and installed and activated ok. Since my weekend is ending, i'm just going to stick to 1809 v1 and update from it. last time worked ok, so should work now.
I have realised something while testing the Toolkit for sfc errors. The message box error that I reported previously in this thread (link to post) does not appear when working with 17763.1 images. Also these are the same images that do not give sfc errors. Perhaps this is linked, perhaps not. But why would 17763.1 not give errors and refreshed images, such as 17763.253, give errors?
This issue has been covered before by others but isn't fully confirmed. It's because Toolkit is not compatible after v17763.107, and thing above this version will not work right. So just download 17763.107, use Toolkit v9.2 then update through Windows Updates afterwards. Work like a charm!
He has his own topic: https://forums.mydigitallife.net/threads/abbodi1406s-batch-scripts-repo.74197/ You'll find it at the bottom of the first post. There are two, the first one is for WinX. Cheers.
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 .
