Hi, I'm trying to remove components (mainly Defender) in LTSC 17763.104 (earliest ISO I can find) however MSMG is telling me that the only build it supports is 17763.1. Does this mean, like the 1903 build, if I remove components from LTSC 17763.1 they will return when Windows updates are installed?
The pack folder has been temporarily moved due to re-structuring of the pack files and once the process is completed it will be restored back. Will try to release a small update to support the new pack folder structure.
No it's only for v1903 the removed components gets restored and so far for 17763.1 no one has reported anything about any component getting restored.
Using Toolkit with images with updates for integration/customization should not be problem, If you are integrating the CU to the boot.wim then you need to also use the Integrate Windows Setup Media Updates which will copy the updated setup files from boot.wim index 2 to source DVD folder. The process goes like this: Integrating Windows WHD General Updates to Boot Image will integrate the files present in from ServicingStack, Cumulative and any updates present inside WinPE and SetupMedia folders. Though the Standalone update file copied to SetupMedia folder does contain the updated setup files for the sources folder but it may not always or won't have a updated setup.exe matching the one integrated to the boot.wim index 2 and due to this the Load driver error dialog appears during the setup. To fix this you need to use the Integrate Windows Setup Media Updates which will copy the updated setup files from boot.wim index 2 to source DVD folder. Will checkout the image with latest update before releasing the next version to see if it needs any fix.
Thank you again, @MSMG - I won't pretend to fully understand what you have said, but integrating setup media updates does indeed seem to resolve my problem.
I did address that issue after enthousiast pointed out what was going on, you probably didn't see that. The toolkit works and worked as designed and creates a working iso IF you use integrate windows setup media updates and you had mounted the boot.wim. Cheers.
THANK YOU for these useful information this is really important to know, and maybe should be included in readme text file of the toolkit
I've never had any problems in the past from not doing this, so when it suddenly started doing it with the two latest 18362.x builds I thought it might perhaps be an issue with the Toolkit. At least I now know to integrate setup updates to avoid potential problems in the future.
Hi MSMG, well another day working with Toolkit V 8.8 using W10 PFW x64 as host I know that this O.S. NO have none UWP applications and modifing or triyng Windows Embedded 8.1 Industry Enterprise x64; when I try use 6(1)Cleanup sources images inside in install.wim item appear one message that cannot can cleanup because have pending.xml on it?? hmm I kow that this O.S. NO have none applications UWP because when I try remove ALL APP´s the Toolkit show that NO exists none UWP...then if you can help me I stay very happy with you, still I'm here again after almost 1 year I have a lot of issues here in Brazil including my wife unortunately but I hope best times someday
I used menu D in Tweaks section but it still left Office apps. Looks like a bug which can be fixed in next build. I have turned the tiles off after the install. I must thank you for this great piece of software and i can't wait for the GUI version to come out. Thanks for the suggestion. Will do that.
Ok, since Office Apps aren't 3rd part Apps it's not removing, you can use the Import Custom StartMenu Layout menu to import a clean StartMenu Layout.