@SunLion, thanks for the answer. Can I copy the file that is the current version and just replace it with yours in the archive, without any corrections needed?! As far as I understand from what you wrote - I only replace the existing file with the current version and nothing more. @SunLion, regarding my question from last week - when using LTSC ISO - the possibility for the script to generate LTSC in the name of the file being created - did you give up on that suggestion? :}
As @bendeyar said, copy and replace only ''W10UI.cmd''. Regarding the ISO name, I've already adjusted the _CreateISO.cmd script and the main script to capture the information beforehand. Test and see.
am wanting to try win10. but before i do that is there a full dark theme like in windows 11 for win10 besides this one Windows 10 Dark Theme Fix + Massive Tweak Pack | My Digital Life Forums i do not know how to apply this. and am using stock image of win10 to test full dark theme but am not sure what am doing wrong every time i turnb off the pc the next time it doesnt boot i need to go into usb iso and use the rpair option then select use a usb then gives an error that it was done using rufus in order to boot i need to select legacy. but its on uefi ive always have use uefi not sure what i did wrong. then after the error mentioning rufus it says to press any key then restarts and boots to windows.
there are some things i dont understand. =========================================================== SD10_Custom_1.61 Configured Options at Tue 06/23/2026, 16:45:35.60 =========================================================== Running in NORMAL mode Selected Other ISO, not related Don't Integrate Drivers Into Install.wim this integrates drivers into install.wim why should i pick install.wim over boot.wim.??? Don't Integrate Drivers Into Boot.wim index 2 same as above.? ENABLE battery in Laptops/Notebooks Don't DISABLE Windows Store REMOVE ClickToDo - GetStarted - WindowsBackup DISABLE Windows Search Don't REMOVE Windows Defender Don't REMOVE Edge NetFx3 is Enabled Enable Modern Calculator Don't Remove WinRE.wim Don't Enable Media Player Don't Enable Subsystem-Linux Don't Customize Boot.wim what is this.? Don't Pin shortcuts to the Taskbar Show ThisPC + Bin Icons on Desktop WPI - Windows Post Install will start at the end of the Windows installation =========================================================== if its called slim10 is it normal for ouput image to be 10gb in size.??
=========================================================== SD10_Custom_1.61 Configured Options at Tue 06/23/2026, 16:45:35.60 =========================================================== The separation occurs because boot.wim and install.wim are used in different phases of the installation process. Boot.wim loads the temporary installation environment (WinPE), while install.wim contains the complete operating system that will actually be installed on your computer. Below are the details of each file and which drivers should be integrated into them: boot.wim (Installation Environment/WinPE) This file is loaded into RAM as soon as the computer begins the installation process. It requires only the essential drivers needed for the Windows setup program to function correctly and recognize basic hardware. What to integrate here: • Storage controller drivers (such as Intel RST/VMD) so the installer can detect the SSD or HDD. • USB 3.0 (or higher) drivers, which are essential if the keyboard/mouse fail to work during installation or the USB drive is not recognized. • Network drivers, if you are installing Windows from a network server (WDS/MDT). install.wim (Operating System) This file is the Windows image itself. This is where all the components that will run on your computer on a daily basis are located. What to integrate here: • Motherboard drivers (chipset, audio, network, Wi-Fi, Bluetooth). • Video drivers (dedicated video card). • Any other device drivers you use. It is not necessary to place the install.wim drivers inside boot.wim. If you do this, the installation environment will be cumbersome and the drivers will not be transferred to the final Windows installation anyway. This applies some customizations to the boot screen—specifically, it adds a pleasant image to replace that purple screen. It has no impact on the installation or the image size. No, absolutely not. In this case, it would be necessary to examine the log file to see what might have happened. For example, in my last test, the install.wim image ended up with an average size of 3.9 GB, and the boot.wim with 407 MB. See the attached image.