Slimdown10 – turn Windows 10 22H2 or LTSC 2021 into classic/legacy Windows

Thanks for replying.

I tried several ways, but it didn't work. This was with an initial image, that is, 26100.2_Pro, obtained from uupdump.

I downloaded version 26100.1742 business and it works without problems.

 

You need to login to view this posts content.

 

Using the MS media creation tool all are install.esd in our en-us editions.

 

@Mavericks Choice ; ach! i thought i missed one of your jokes..

 

You need to login to view this posts content.

 

Hmm, that didn't help. The image is unpacked into the DVD folder and the command line is closed. The .iso image itself and all .cmd files from the 24H2_Integrator folder are deleted. In general, the same eggs, only in profile ...

p.s. With Sergey's script, the whole process goes smoothly and without errors with any .iso image.

 

This is because you use Windows 11 as the host and its script is almost all with dism11.

I am finishing tests and will publish another version, for PRO and LTSC.

This problem is due to the use of dism, since some commands are not executed with dism11 but with dism 19041.

I will publish the new version later today.

 

Got it, we're waiting, good luck with your tests!

 

Removed

New version published

 

You need to login to view this posts content.

 

Nothing has changed at all. The image is unpacked into the DVD folder and the command prompt is closed. The .iso image itself and all .cmd files from the 24H2_Integrator folder are deleted. It's not clear what the reason is. Okay, the script doesn’t work for me, but why does the script delete the .iso image itself and all .cmd files from the 24H2_Integrator folder. In this case, the script does not produce any errors.

 

Removed
New version published

 

Hello
SunLion!
The password for the archive W11_Multi_Integrator5.3.7z is incorrect, can you review it, thank you

 

Is mdl2024

But this modification did not work here.

The problem is the DISM definition.

Removed
New version published

 

Sorry, I mixed up the archives, everything is ok, thank you

 

Hello, I finally managed to test your script. I tried it several times in the original and each time I failed. Therefore, I deleted the problematic file W11_Multi_Integrator5.2_Start.cmd, renamed the file W11_Multi_Integrator5.2.cmd to start.cmd, ran it as Administrator and everything went like clockwork. That is, the image was processed completely and without any errors - thank you!

 

Thanks for reporting.

So the problem is in the start file.

Let's abandon it then. Since it only serves to create the log file at the end. But we can also copy/paste the final result, as an alternative to the log.

Anyway, yesterday I prepared a partition and I'm going to install Windows 11 to do the tests.

Thanks for your help!

 

Hello Sainfo! I don't know how to reproduce this for you in English, I want to ask you, how can I remove these lines from the script? How can make them normal.

Spoiler

[ 1.0% ]

[= 2.0% ]

[= 3.0% ]

[== 4.0% ]

[== 5.0% ]

[=== 6.0% ]

 

I am very grateful to you and Sergey for your contribution to improving the image processing tool. Advice: try not to unnecessarily complicate your tool codes (scenario) and we, your users, will be happy.

 

No, I don't do anything to make things more difficult. On the contrary, I do it to make things easier for the less experienced user.

By the way, I installed Windows 11 just to do the tests and I believe I found the best way to make the script work well on Windows 11.

I'm attaching the script and I ask you to test it and report back the results.

There are two options:

The first is to run the Start.cmd file, which uses nsudo to start the main script with elevated rights (in this option, no log file is created).

The second is to run the 24H2_Integrator5.3_Start.cmd file, which will start the main script with elevated rights and will create the log file at the end.

In my tests, everything went well, without errors. See the attached log file.

edit: new version released