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

When I consider adding a new feature, I always ask myself three simple questions:

Does it make Windows more stable?
Does it make the Integrator more useful?
Does it solve a real problem?

If the answer is "no" to all three, it probably doesn't belong in the project.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You shouldn't post this in this thread; it's not allowed here. If you have something to say, it's better to send a private message.

 

You need to login to view this posts content.

 

Would you mind sharing a full example of the command syntax? For instance,

DismAPI_Tool.exe /p C:\mount /compcreate

and

DismAPI_Tool.exe /p C:\mount /removecomponents

and

DismAPI_Tool.exe /p C:\mount /l with where to place Package.txt

 

You need to login to view this posts content.

 

So, how are things going for you in this area? We're looking forward to seeing an updated version of this tool from you...

 

İ completed but need test again. I removed some packages that were blocking Windows Update. Now it updates without any problems; I'm saying this based on my last test.But I noticed something strange. I added the cumulative update without any problems. When I tested it with a virtual machine, even though the build version was correct, it downloaded and installed the same update again. This problem was probably caused by the modified image I was using.

 

I believe this behavior is related to the order of offline servicing rather than the cumulative update itself.

In my testing, the following sequence has consistently produced the correct result:

Perform the offline integration of all cumulative updates into install.wim.
Enable and integrate .NET Framework 3.5 into the offline image.
Finally, reintegrate the same cumulative update(s) into install.wim.

After deploying an image prepared this way, Windows Update no longer offers the same cumulative update again on a live system.

This has been consistent throughout my testing, so it may be worth trying the same offline servicing sequence to see if it resolves the issue on your side.

 

I also forgot to mention to mention one important step - Perform Component Cleanup

1. Perform offline integration of all cumulative updates into install.wim.
2. Perform Component Cleanup:
DISM /Cleanup-Image /StartComponentCleanup
DISM /Cleanup-Image /StartComponentCleanup /ResetBase
3. Enable and integrate .NET Framework 3.5 into the offline image.

4. Finally, reintegrate the same cumulative updates into install.wim.

The Component Cleanup step is important because it must be performed before integrating .NET Framework 3.5.
Otherwise, after integrating .NET Framework 3.5, Component Cleanup will not be possible.

 

İ know all, thanks
Судя по вашему профилю, вы проживаете в Украине. Моя жена также является гражданкой Украины.

 

I've now been in the Netherlands for 4.5 years. When the war began, I was forced to leave Ukraine with my two minor children, as I am the sole guardian of my children.
Sorry, friends, this is off topic.

 

Something like this, I guess? Before executing the "Commit" command.

Code:

echo == Perform Component Cleanup ==
del /q "%MNT%\Windows\WinSxS\Backup\." >NUL 2>&1
del /q "%MNT%\Windows\WinSxS\ManifestCache\." >NUL 2>&1
"%DISM%" /English /Image:"%MNT%" /Cleanup-Image /StartComponentCleanup
"%DISM%" /English /Image:"%MNT%" /Cleanup-Image /StartComponentCleanup /Resetbase

 

These two codes
del /q "%MNT%\Windows\WinSxS\Backup\" >NUL 2>&1
del /q "%MNT%\Windows\WinSxS\ManifestCache\" >NUL 2>&1
are not a mandatory requirement for the correct sequence.

 

I understand this, I added them to clean the WinSxS folder before starting the general cleaning of the image components.

 

You need to login to view this posts content.

 

Are you the creator of the DismAPI_Tool? If so, would it be possible to add a regedit feature to change Baseline 1 to Baseline 0?"

 

Yes