Slimdown11 – turn Windows 11 or LTSC 2024 into classic/legacy Windows

To be honest, I prefer to support and provide guidance to the script's original designer. I actually have a separate project of my own going on right now. I'm currently working on developing version 13.7 of the MSMG Toolkit. I'd be happy to share it with you if you're interested, so you can test it out as well.

 

Agree, I do like to retain win media player too, its fit for my purposes.

 

I understand, but personally, I don't like to make additional adjustments to an OS that's already installed. That's why I prefer to work with the install.wim image so I can configure everything I need from the OS right there. And regarding the tool you provided: I'd advise you to remove everything from it that isn't specifically related to your version of the code. Remove everything that just clutters up the script with commands nobody needs. For example: in your version, I would remove the “DEBUG” section and add this command to that section:

Spoiler

Code:

:: ===========================================================
:: Set Default Values
:: ===========================================================
set “Update=1”
set “DisableStore=1”
set “RemoveClient=0”
set “DisableWindowsSearch=0”
set “DisableDefender=1”
set “RemoveEdge=1”
set “EnableClassicCalculator=0”
set “RemoveWinRE=1”
set “RemoveMediaPlayer=0”
set “WindowsPhotos=0”
set “PinShortcuts=1”
set “InstallOpenshell=0”
set “CustomizeBoot=0”
set “DesktopIcons=2”
set “MASCode=1”
set “VisualCppRedist=1”
set “DotNet35=0”
set “KeepCodecs=0”
set “WPI=0”

And many other settings that have no real bearing on the task at hand ...

 

Thank you for the detailed feedback and the default values snippet. I completely agree with keeping the script as clean and efficient as possible. Beyond replacing the 'DEBUG' section with these variables, could you point out specifically which other commands or sections in the current script you consider 'clutter' or unnecessary? A few examples of what exactly to remove would be incredibly helpful for my optimization

 

Hello, mustafa gotr. Could I send you my script so you can review it? I'd be very grateful.

 

O course

 

I need 20 minutes to send it to you.

 

That’s exactly what I’m working on right now—creating a script without any unnecessary components. This will take me some time. Once I finish the testing, I’ll send it to you for review.

P.S. Actually, I always work with the install.wim image because I don’t find working with an .iso image necessary (I use my own pre-made DVD). But since many people here prefer to work with the .iso image, I’ll create two scripts: one for myself, using the install.wim image, and another for those who want to work with the .iso image. Of course, they could be combined into a single script, but I won't do that—I don't want to complicate the script's code, which is already complex enough.

 

@sainfo I too prefer that, though when I use SD or your script I always extract the install.wim, like you I have my own dvd structure in place.

 

You need to login to view this posts content.

 

Well, yeah, because all this fiddling with the .iso image is a pointless exercise that just “clutters up” the script. Plus, for some reason, people “tinker” with the boot.wim file—why the standard boot.wim doesn’t suit them is a mystery. For example, I personally edited the boot.wim file once for my own use: I removed index 1, which I didn’t need, left only boot index 2, and deleted everything else in it that I didn’t need. In the end, mine came out to be 230 MB. As far as I’m concerned, it’s much more convenient and proper to create a DVD file for yourself just once and simply place the resulting install.wim image into it. If necessary, you can always use a very simple piece of code to extract the coveted .iso image from the DVD created this way. Of course, if an ISO image processing script could do the same with a boot.wim file, i.e., leave only index 2 in it and reduce its size by half, then I would be all for such a script!
IMHO

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

I wasn't referring to that error; I was talking about this one:

I found the cause of the script failure: I changed this error from “—” to “-,” and the script ran without a hitch—everything's OK!

 

You surprised me, I never made such mistakes in a script.

 

Hmm, well, if that error isn't in the original, then maybe it showed up on my end when I extracted the downloaded 7z archive.

 

That's interesting. In my original script the message uses a normal dash, so I'm not sure how that character appeared. Could it be an encoding issue or a copy/paste problem?
The source file should contain a normal dash, not "—.

 

I see. Well, I just put a dash there. After that, the error went away.

 

@sergey130270 I ran the script with pers selections, works well only small gripe resulting wim was 5.8gb without using NTlite
ran in a VM no issues all appears to work very well. Thank you!

 

Thank you so much for testing the script and for your kind feedback! I'm so glad everything worked well in your virtual machine. I sincerely appreciate you taking the time to test it and sharing your results.