Hello, changing the edition from PRO to Home is unlikely to work. I don't have PRO, so I can't check it. But here are the instructions, give it a try. Maybe it will work for you... Spoiler Code: Changing the Windows image release using DISM 1. Open the command prompt as an administrator. Run DISM with the Get-ImageInfo parameter to obtain the name or index number for the image you want to change. Dism /Get-ImageInfo /ImageFile:D:\PRO\Sources\install.wim 2. Mount the Windows image. dism /Mount-Wim /WimFile:D:\PRO\Sources\install.wim /index:1 /MountDir:D:\Mount 3. Enter the following command to find the Windows edition that your image is currently configured for. Dism /Image:D:\Mount /Get-CurrentEdition 4. Use the DISM Get-TargetEditions parameter to find the Windows editions that the image can be changed to. Dism /Image:D:\Mount /Get-TargetEditions 5. Enter the following command, specifying the edition ID, to change the Windows image to a higher edition. Dism /Image:D:\Mount /Set-Edition:IoTEnterpriseS ProfessionalWorkstation 6. Check the image for errors Dism /Image:D:\Mount /Cleanup-Image /RestoreHealth 7. Enter the following command to find the Windows edition that your image is currently configured for. Dism /Image:D:\Mount /Get-CurrentEdition 8. Unmount the image, committing the changes. Dism /Unmount-Image /MountDir:D:\Mount /Commit
I ve tried to run the script with an iso created with Ms creation tool, but got error, saying it's not an original iso.. which version should I DL french iso??
In essence, those drivers that you do not need for work are removed. Actually, the script was provided as an example. So that users could see the principle of processing the install.wim image that I provided. If you have ideas on what needs to be removed from the script or what can be added to the script - offer your options. p.s. I repeat that I am interested in processing only the install.wim file and only the Slim variant and nothing else. Therefore, there is nothing "extra" in the script, that is why the script is composed in such a way.
what do you think about removing defender, webview2 (legacy) and smart screen? wouldn't it be beneficial for iso size? Very interesting sainfo, the install.wim file I obtained with your codes was 3.91 gb, I removed defender and webview with NTLITE and the size was 3.91 gb again
What I think, Defender itself is not completely removed, but some of its functions are removed, the rest of its functions are disabled. Regarding WebView2, I don't know for sure, but people write that it is needed somewhere for some reason. Smart Screen is completely removed from the image? Of course, this will benefit the reduction of the image size, but this is not as significant as we would like. Only competent cleaning of the WinSxS file can significantly reduce the size of the image. People do this without compromising overall system performance. Their WinSxS file ends up taking up to 250 MB, while the instal.esd image itself takes up about 1.2-1.6 GB! Instead of the usual 2.5-2.6 GB. Unfortunately, I don't have much experience working with the WinSxS file. I tried, but to no avail. Either the system does not install, or it installs normally but does not update at all.
Thank you very much for the work done! Next I will test the result of this script on real equipment. p.s. You haven't written anything about what I'm deleting in the script. Is there something extra that I'm deleting or, on the contrary, is there something that needs to be added to the deletion script? Also, in 24H2_GamerOS_v3_test you removed the update function completely. I guess it should look something like this? Spoiler Code: . . . . ECHO. ECHO. ECHO ============================================================= ECHO Mount install.wim ECHO ============================================================= "%DISM11%" /english /Mount-Wim /WimFile:"%~dp0Folder\install.wim" /index:1 /MountDir:"%~dp0Mount" ECHO. ECHO. ECHO ============================================================= ECHO Upgrading image LTSC to IoT LTSC ECHO ============================================================= "%DISM11%" /English /Image:"%~dp0mount" /Set-Edition:IoTEnterpriseS echo. echo. echo ########################################################### echo Running W10UI for integrate updates echo ########################################################### CALL "%~dp0W10UI.cmd" echo. echo. echo Finalized :: restore title title %title% echo. echo. echo Done... ECHO. ECHO. ECHO ==================================== ECHO Installing LCU1 Cumulative Update into install.wim ECHO ==================================== "%DISM11%" /English /Image:"%~dp0mount" /Add-Package /PackagePath:"%~dp0UUP\LCU1" ECHO. ECHO. ECHO ==================================== ECHO Installing LCU2 Cumulative Update into install.wim ECHO ==================================== "%DISM11%" /English /Image:"%~dp0mount" /Add-Package /PackagePath:"%~dp0UUP\LCU2" echo. echo. echo Done... ECHO. ECHO. ECHO =========================================================== ECHO Remove Capabilities ECHO =========================================================== . . .
There is a rumor (no any official reconfirm), Any removing has no noticeable improvements on computer performance. it impacts only on OS size or OS functions (search, defender, store, , ,).
Please be noticed that This thread is for Windows 11 than 10. please make sure you are using Windows 11 iso. If you are working on Windows 10. here is right thread. https://forums.mydigitallife.net/threads/slimdown10_v2-0-2-continued.88599/page-27 btw, I did run this 24H2_Integrator today to generate W11 24H2 Home version. no issues. its test passed on VM. last time, my test of W11 24H2 Pro version also passed.
echo Running W10UI for integrate updates echo ########################################################### CALL "%~dp0W10UI.cmd"
You should not use both forms together. Use one or the other, for example: Use script integrates LCU automatically: Or use W10UI:
Damn i tried to use 10.0.2 script...i use 10.10 now and its running you should put this one on first page, on 1st thread to avois errors...