Thank you, kind man, for your patience! Yes, I want to make a Windows 11 IoT Enterprise LTSC x64 RU build for myself from this server build 25398.584. What to do with these 25398_OtherEditions-UUP-Patch files ? Unpack them and put them completely in the Package_EnterpriseS folder with the four files you described ? It's not quite clear what to do with them, 25398_OtherEditions-UUP-Patch files. ================================================================ И еще, 3A011AB217896371930801C7C1C3FD404FA768B58A3D4D34169C65085CE2E0EC~31bf3856ad364e35~amd64~~10.0.25398.521.mum исправил. In the code: dism /Mount-Wim /WimFile:C:\install.wim /index:1 /MountDir:C:\Mount Dism /Image:C:\mount /Add-Package /PackagePath:C:\SSU-25398.521-x64\update.mum Dism /Image:C:C:\mount /Add-Package /PackagePath:C:Windows11.0-KB5033383-x64.esd Dism /Image:C:C:\mount /Cleanup-Image /RestoreHealth Dism /Image:C:\mount /Cleanup-Image /StartComponentCleanup /ResetBase Dism /Unmount-Image /MountDir:C:\mount /Commit As I understand Dism /Image:C:\mount /Add-Package /PackagePath:C:\SSU-25398.521-x64\update. mum should be 3A011AB217896371930801C7C1C3FD404FA768B58A3D4D34169C65085CE2E0EC~31bf3856ad364e35~amd64~~~10.0.25398.521.mum renamed to update.mum ? When executing this line it writes that there is an error opening this file.
Unpack them and put them completely in the Package_EnterpriseS folder = No 25398_OtherEditions-UUP-Patch.7z files are to build install.wim 25398.1 You can use these four files Code: Microsoft-Windows-EditionSpecific-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.25398.1.cat Microsoft-Windows-EditionSpecific-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.25398.1.mum Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.25398.1.cat Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.25398.1.mum from 25398_OtherEditions-UUP-Patch.7z to build update 25398.584 as well. P.S don't forget to correct mistake in Code: Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.25398.1.mum if using files from 25398_OtherEditions-UUP-Patch.7z
No just edit 3A011AB217896371930801C7C1C3FD404FA768B58A3D4D34169C65085CE2E0EC~31bf3856ad364e35~amd64~~~10.0.25398.521 then leave it alone. use Dism /Image:C:\mount /Add-Package /PackagePath:C:\SSU-25398.521-x64\update.mum for update.mum
Currently, what are exactly missing to continue to remove system components towards even smaller images/custom editions ?
It's getting more and more difficult for the latest Windows 11. But Starter is still the smallest it could be: Barebone + .NET48.
Indeed, that's why I have created this thread - https://forums.mydigitallife.net/th...hout-obscurity-and-lost-of-granularity.87860/
I can try to make and share some summaries to reflect the current state of the art, pending subjects, work in progress and future projects.
Web Server is base edition for Windows Server. Editions section can be Windows Server 2008+. Also there is Windows Embedded family, but I don't know what is base edition for that.
Next 11. Runlevel Win4. 25398 Runlevel-Win4-Package Removed. OK. 26010 Microsoft-Win4-Feature ---> Runlevel-Win4-Package Removed, KO. Long in short: Don't touch it.
Lightest image means basically nothing. You have to specifiy what you mean. Say the server datatcenter images are surely bigger than many client ones (because all the optional components), but the server install is by far lighter (less ram used, less services running and so on) than any Starter/Home/Pro client (again because optional components do nothing other than taking a bit of storage, until you enable them). And speaking of the storage, all unused (not enabled) components can be removed using a one liner command Code: for /f %%a in ('dism /online /get-features /format:table ^|find "| Disabled"') do (dism /online /disable-feature:%%a /remove)
To take a concrete example, Let's try to rebuild Nano Server 2016 installation option image (found on /Nanoserver/NanoServer.wim on Windows Server 2016 iso)