@ Sunlion, ok though I haven't experienced this before, it would appear the predownloaded updates become redundant & while the script runs, a new set are downloaded & integrated into the wim?
Hello. It seems you used some other script. This script really reduced the size of the install.wim. I'm not at home right now, but once I get home I'll provide a picture of the size after installing Windows 11. These photos prove that the sizes have indeed been reduced. 1. install.wim created with "26H1_Creator_2.1_8". 2. Installed operating system "Win11_Pro_26H1_28000.2704"
When using the GenerateUpdateList.ps1 script, it is executed again by the main script even after the updates have been downloaded; however, no issues are expected.
There's the option after creating the images to make an ISO. I used that to install the OS. The other script you mentioned was prior to using this Slimdown11.
Your right. Never thought to keep it. I gave up and deleted all the files, deciding I liked my version instead... I'll have to download the zip file again, and run the program again. The log file, it was huge. I wasn't expecting the process to take so long to complete. It lease 1/2 hour. Now that I know how it works I'll be prepared for the time. It will be a while.
not sure why but i also posted similar question i said its called slim but the final iso size is like almost twice the size. i think some files werent deleted or removed.
The same answer applies to you: we need the log file to see how you carried out the process. For example, in the last test I ran with version 2xH2_Creator_17.4, the result was as follows:
i did give you the log . i remember you mention that windows 11 as a host for the script i did but i was for windows 10 but after several tries it did crreated a slimmer version wich am using. no need to check you already did i think you mention that runing the script on windows 11 as host could be the problem. https://forums.mydigitallife.net/threads/slimdown10_v2-0-2-continued.88599/page-74#post-1915827
Several errors were found. We recommend using version 26100.1742 as the source, since newer versions are already bloated with new components that Microsoft wants us to use... Additionally, the script is set up to remove the Microsoft-Copilot and UserExperience-Recall packages from version 26100.1742, using the specific identifiers for those packages in that version. Several "Access is denied" errors occurred. Did you disable your antivirus before running the script? Did you close all running apps and open Windows Explorer windows before starting the script? Another potential issue is that you are using Windows 11 Professional (x64) as the host system. I can't say for sure that this is the cause, but there are many reports that Windows 11 is terrible for running scripts.
Those errors are not important. It creates the iso and installed windows to an empty partition correctly. What I failed to do was select windows security when the menu came up... this was a test anyway. Now using dism++, powercfg off, the result was near the same installed size to my way of making windows11. My way is install the Windows ISO, then dism++, powercfg off, and use "Raphire/Win11Debloat". All this on a live system. This seems to take longer. One hour for the script to complete, then using the ISO to install Windows. I'm intrigued with the process though.... There is one thing you scripts build a complete slimmed ISO, mine requires manual labor.
Third time a charm... Down loaded and used "us_windows_11_consumer_editions_version_25h2_updated_aug_2026_x64_dvd_ec320f81.iso" to complete the process. Zero errors. The ISO I was using, was from May 2026. Apparently I needed the newer issue. Also it took less time to complete.