I'm trying to add fr-FR (created using MSMG's advice) language pack to 1607 LTSB (x64). The script just stops on Code: Copying localized Windows Setup resources to the source DVD cmd.exe, conhost.exe and xcopy.exe all show 0% cpu and zero I/O rates. In general I'm finding I cannot create an updated 1607 ISO that boots correctly. I always get installation errors, varying from component missing, licence terms cannot be installed to setup cannot continue. If I use 8.8 I don't get this problem. Is 1607 LTSB really supported with 9.3.1?
I remember someone commenting on the thread a while ago about continuing support 1607 RS1 in MSMG Toolkit as EOL was 2026. I think @MSMG replied in the affirmative. Is that still the case for the latest versions of MSMG Toolkit? I would be willing to test this.
ya i wouln't hold breath. you don't rush perfection. our school district already discussed it. 1903 was way to late to the game. were sticking with 1809 17763.503 for the next upcoming school year
Installing a major update will remove all the customization done, the best you can do is to create a new image an do the in-place upgrade. Yes you can do install the normal updates through the Windows Updates.
When the Integrate Windows Updates is selected the integration order is left to the DISM and the DISM won't follow the order properly particulary with the Windows 10, it's best to use the Integrate WHD Update Pack menu.
Though the MS released the Windows 10 v19H1 (10.0.18362.30) as the Official image for public but still the ISO released is just the v10.0.18362.1 image with updates integrated, only the installation media with boot and recovery images are updated to version v10.0.18362.30. Rest of the ISO images i.e the Language Packs, Feature-On-Demand Packs, Media Feature Packs, WADK, WinPE, SDK are all of v10.0.18362.1 and installing or integrating any of these packs will still need the cumulative update to be integrated or installed. Windows 10 v19H1 (10.0.18362.30) is not like the Windows 10.0.16299.15 which was a true re-release with all the packs updated to v10.0.16299.15 Since the 10.0.18362.1 is only available through UUP and most people are not familiar with it and depend on the official ISO images released from MS, I have considered to update the component removal to support Windows 10 v19H1 (10.0.18362.30) too. Note: Only 10.0.18362.1 and 10.0.18362.30 will be supported for v19H1 component removal and no future released refreshed images will be supported.
Sorry No ETA, since I'm still updating the v1809 database, once it's finished then will proceed to v1903
Please do specify did you used Remove Windows Components or Remove Windows Components using Package List. Only if the Package name is incorrect or the Package has been removed previously then this error will occur.