I dont know... On linux sonds like Trusted Installer, full permission enable. On windows the admin default is different of trusted installer. So I would like to know if Sudo for Windows 11 is like Trusted Installer.
With each new script, I made some changes to make it the way I wanted. With the script "2xH2_Creator_14.0" I only changed "DirectX9c" and "Calculator", I didn't install them. There was nothing else to change. The script became the tip of the iceberg. It's great. After using "NTLite", the resulting "install" file was 3.9gb in size. Thanks to "SunLion".
In the folder 2xH2_Creator_14.0, OEM there is still an old Massgravel 3.5, can I replace it with the newer 3.7?
It works with the file “de-de_windows_11_enterprise_ltsc_2024_x64_dvd_4f136f69.iso”, ( 2xH2_Creator_14.0 ) However, I occasionally receive a message from the Security Center stating that it is disabled. Change Windows Edition IoT LTSC with Mas 3.7 Works to LTSC 2025. Activate with Tsforge StaticCID works.
I'm now going to build four images and add them to one image. IoT LTSC 2025 LTSC 2025 Pro VL Enterprise VL and add the activation to each wim. The script is really good for removing components. I'll adjust the registry entries for myself, but otherwise, great work to everyone who contributed. Have a nice evening PS: I'll let you know tomorrow if it worked, But before that, I'll test the business
Thanks for your contribution! I believe it's possible to do this through a script. I'll try to write the code for this, including two options: 1 - Add setupcomplete.cmd directly to the mounted install.wim; or 2 - Add setupcomplete.cmd to the $OEM$ folder, as we're currently doing. Therefore, I believe two setupcomplete options would be necessary, one for HWID and one for TsForge. Give me some time and we'll see... Cheers!
I downloaded it, there is a “Readme” file from sainfo with content: Code: User instructions: 1. Download the “24H2_GamerOS” archive and unzip it to any partition 2. Move your Windows 11 IoT Enterprise LTSC [26100.1742] install.wim file to the “Wim” folder in the localization you need 3. Place the necessary .reg and .cmd scripts in the “Data\PersonalTweaks” folder. 4. Place the necessary cumulative updates in the “Data\UUP” folder. 5. Run the “Runme.cmd” file as an administrator. 6. The install.wim file is processed by the script and then moved to the “DVD\sources” folder 7. The $OEM$ folder will contain everything you need to install and activate your OS Note: after processing the install.wim image with the script, process it with the NTLite program (the .xml file is located in the Data\Presets_NTLite folder). The final, clean configuration of the image is performed in the DISM++ program. After the final configuration of the image in the same program, convert the install.wim image to the install.esd format. Next, in the DVD\sources folder, replace the install.wim image with the resulting install.esd. Use the DVD at your discretion. The answer file (in my case) is located in the boot.wim file. The logfiles.txt file is located in the Data\logfiles.txt folder. Good luck! Hmm, what is a 24H2_GamerOS?
Interesting case. Once again read my text. We look for the familiar letters and see: I decided to share with you what I got on the basis of an excellent script from SunLion. And what's not clear? Everything is in your hands, what you choose in the settings you will get in the output. Good luck!
================== 2xH2_Creator_14.1 ================== Updated to 26x00.6584 - Modified the $OEM$ folder and the script copy. Now the activation scripts are copied to the install.wim and the other apps/tools are kept in the $OEM$ folder. This way, those who want to use multiple indexes to create an AIO version will already have the scripts inside the install.wim for each index (suggestion from @KleineZiege) - When it is image 25H2_LTSC, TsForge will be used and in the other options the HWID - Updated defender-dism-x64.cab (release 2025.09.16) - Added option to create 24H2 or 25H2 image - In this format, all questions will be presented for choice. - The all.txt file was updated - Several small adjustments Test with: - pt-br_windows_11_enterprise_ltsc_2024_x64_dvd_2bb6b75b_2.iso - pt-br_windows_11_business_editions_version_24h2_x64_dvd_ecc90645.iso https://forums.mydigitallife.net/threads/slimdown10-–-turn-windows-10-22h2-or-ltsc-2021-into-classic-legacy-windows.86552/page-120#post-1872013 Enjoy!
No, I am not stealing anything from anyone, and especially not attributing anyone else's merits to myself. I just offer my own, different approach to the formation of the structure of the tool. In my opinion, it is more optimal and more convenient for the end user. It is up to you to use it or not.