Yes for both questions, some use the term RS6 for 19H1. @MSMG has removed the links for the packages because he is going to restructure the packs, you should be able to find the package on one of the mirrors, but iirc the toolkit also looks for the sxs folder inside the dvd\sources folder too.
Thanks for clarification. One more question. I don't know if this was asked before, but i got used to making "true addons" for WinNT6.x True Integrator (from wincert forums, which are in my opinion centered on Windows 7). Although it says it has support for Windows 10, it is quite dated now (which can be an issue, authors of newer OS modification apps admit there are problems that need fixing with new ISO releases) so i'm not sure it could do the job anymore. I ask this because my addon not only adds files to wim, it also creates start menu shortcuts (via .inf files) so its all ready to be used (tested on Windows 7 machine). And it also shows up as normal windows feature that can be removed via Programs and Features. From available .tpk addons i don't see an example to do such .inf-like modifications. I did look inside Games .tpk which shows that specific folders can be targeted.
i am new to this toolkit. in the download section under PACKS do i need to download all packs.? another question in drivers if i have cab driver pack for my laptop i can use that there.? i have read that 1903 reinstalls apps. if i go the 1903 way when if they fix the reinstalling apps ill need to redo an image right.? should stay on last 1903 or try the 1809.? thanks is this the order to do so.? 1) Integrate all the functions you want to add, except .NET Framework 3.5 using the integration functions menu. 2) Integrate the language pack you want if necessary 3) Integrate updates. 4) Remove unwanted applications 5) Remove unwanted components 6) Apply changes, this will carry out the cleaning 7) Reassemble the fountain 8) Add .NET Framework 3.5 using the integration functions menu. 9) Apply changes. 10) Rebuild the image.
Only the packs you plan on using. Check what's in the cab (use 7zip) and if it contains .inf files, use them. The toolkit is not ready to remove apps from 1903 (afaik), but the reinstalling stuff, by windows, is not a bug, chopping is not accounted for by msft.
i do not know the packs so i searched. dart--- Diagnostic and Recovery Toolset 10.. not needed Media Feature Pack--- installs windows media player. i need wmp. why so many netframeworks? do i need them all.? RSAT---- not needed games---- not sure am new to win10 i know win7 solitarie mine sweeper ect. E11 its not the same as edge.? thin PC not sure what it is. wmf 51--- not sure but seems important
Is there a way to unset the flag so I can continue adding monthly updates and cleaning, then set it back before exporting to ISO? Redoing the ISO each month, leaving out .NET 3.5 or not cleaning after adding updates are all non ideal scenarios... if I had to I'd leave out .NET 3.5 and look if it's possible to have some sort of post install script run... (no experience with that yet).
1. DaRT can be more useful then most packs. 2. Just use a non N source and you don't need it. 3. Only the framework version for the used source is needed. 4. It is just the games available 5. MSIE11 = Microsoft Internet Explorer, not edge. 6. Special windows edition. So, just download what you want or can use, if it's applicable to your source anyway.
You can avoid the pending flag by not doing stuff that sets it. The cleaning only cleans the superseded files in the sxs folder, with 1903 not a good idea to do anyway.
For people who only want to integrate the updates, it's maybe better to use W10UI_6.6+ it can perform the full /resetbase but leaves the 1903 CU out of the action.
W10UI is the best option these days to integrate updates. It is always up to date and any tool focused on one function will be better than AIO tools.
All components given are safe for removal but you need to select which components you need based on your preference. You can find the list of components under packs folder in the file RemovePkgsList_Template.txt
The Toolkit add-on .tpk files are basically .wim files compressed with /recovery switch containing the add-on files in their original form with their file/folder permissions kept intact. The add-on pack registry setting are bundled separately outside the .tpk files. The Toolkit applies the .tpk files to the install.wim image and then imports the .reg files to the install.wim image. and for Start menu shortcut creation, now I do use a custom vbscipt file which will be included in the .tpk file and will be called while installing the OS using the registry run once key and the script will be deleted at the end of it's execution.
Only way you can do this is by making a custom .NET Framework 3.5 pack like the .NET Framework 4.8 pack created for Windows 7.
It's almost ready for the release, I'm doing the final testing of component removal and will release it in two-three days. Remember still the component removal for v1903 will restore the removed components when using the WU, this is due to the recent changes done to the WU.