@SunLion i always disable allow contents indexed on this drive. there are some files that cant be disabled on a live windows am wondering if it benefits those files too. add a option maybe in slimdown10 if it can be done, attrib.exe +I C:\*.* /S /D I think it's probably impossible to change it from a running Windows. You'll probably have to do it from dual boot, or PE, etc.
for the IoT ltsc i was watching a video and talks acout activation. does the script takes care of this or i need to activate it separatelly.??
mmm i got error what di i do wrong.? the test you sent if i test and no errors can i use it as stable script.? once the script its done and i install iso how do i tell it applied the script.? OK UPDATE tried test script no erors but not activated iso i guess this way i can tell if script was applied
In my opinion, this is a very good decision - thank you! I'll try to test this option too. You've posted so many versions of the script that I'm already a little confused about them. Of course the script is wonderful, no doubt about it. But why does the output produce such a large install.wim file? It seems that the script runs without errors, but does not remove the “garbage” from the image. On one of the variants of your script, I got this: the initial install.wim file was 4.2 Gb in size, after being fully processed by the script (with an update), it turned out to be 3.2 Gb. And after converting to the .esd format, the file size of the install.esd file was 2.2 Gb. The image was made from 26100.1742 and received 26100.2894 from it. At the request of my comrades, I placed the resulting assembly on a file sharing site. Here, in this thread, I also shared a link to it (for your reference). The problem is that I have never used your script clean, untouched. I always removed everything that I didn’t need from it and added what I needed. But now I can’t do that anymore. After processing the install.wim file, its size becomes about 3.9 Gb and after converting to .esd about 2.9 Gb. Damn, I don’t remember what I did then to get an acceptable image size - it’s a shame!
If reducing INSTALL by directly deleting files WIM size, Unattend.xml is required to install the system.
I thought it would be a good idea to make the iso/install.wim as small as possible. but I ended up regretting it, as any idea to reduce the size resulted in installation problems in some scenarios. I prefer ISO/install.wim that can be easily installed in any way. Size is no longer important in order to install normally.
Personally, I don't think so. If you worked as a system administrator and you would need to install the OS ten times a day and on different PCs, but probably yes. And so, for the average user to get an image without losing its main functions, the smaller the size, the better. IMHO
What I have noticed is that with each new Windows 11 update, Microsoft includes more and more junk, making it difficult to remove many things. For example, on the NTLite website, nuhi (developer) stated that servicing does not allow removal as we want, that is, we do the entire removal process with NTLite and in the end nothing is actually removed. I don't know, I'm very skeptical about this system.
I’ll ask you just two questions: can you show your Presets from NTLite and is it licensed or Repak? I have Repak (I’m under pressure to buy a license) and that’s probably why the NTLite program doesn’t reduce the image size for me, literally at all.