The software in the Tools folder is very old. I dug out the old software and upgraded it to the latest DISM11 and also upgraded it to ADK 27798
Normal SKUs and LTSC SKUs are from two totally different branches. Neither are they virtual siblings of the same parent SKU (for easy switching using Product Key), nor is there an officially supported upgrade path whatsoever. So, according to MS, you can't. You might still be able to do it with a tool like this: https://forums.mydigitallife.net/threads/upgradematrix-xml-fix-tool-very-beta.88518/ and following ISO upgrade installation.
Here is the post below, the same message in English. On the Integrator 10.10 version everything was fine.
I had this problem too, but I don't remember what it was. You use autounattend.xml, right? Check this file.
Found two differences in the process. 1 - You are editing the ru-ru_windows_11_iotenterprise_ltsc_2024_x64_dvd_HM(CES_X64FREO_RU-RU_DV9).iso image, but the IoT Enterprise edition only exists in the en-US language. Your ISO has probably been edited before. 2 - In Remove Capabilities in your log there are more removed packages and an error: In the original script only the following are removed: This may have caused the error. Try using the ISO "ru-ru_windows_11_enterprise_ltsc_2024_x64_dvd.iso" to see if the error occurs as well.
No, that's not the issue. I used your Integrator 10.10 with this image, updated it to version 26200.5670. The system installation in this case went without errors. The problem was with Integrator 10.19.
Not much code has been added since version 10.10. Please remove the following lines from your scripts CreateSlim.cmd line 229 to 246 CreateDefault.cmd line 252 to 271 And do a test to see if that was it.
I see, thank you! In the end, I used part of your code from Integrator 10.10 for my purposes. I compiled the IoT 25H2 LTSC 26200.5670 build for myself. I installed it, and this time the installation went smoothly. In order for all the .reg files I needed to work properly, I had to combine two different scripts into one. They (.reg files) were performed by the Integrator, but in fact were not applied to the image. Now everything works fine.