Sorry. I don't know that kind of script in high level code. So I tested msu only. It's my dream in decades. It's very handy. You just need: 1. msu in MSU_to_esd_and_Modded_CU_202311242121 2. these source files in MSU_to_esd_and_Modded_CU_202311242121\files\Package_EnterpriseS. e.g. Code: Microsoft-Windows-EditionSpecific-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.22000.1.cat Microsoft-Windows-EditionSpecific-EnterpriseS-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum Microsoft-Windows-EnterpriseS-SPP-Components-Package~31bf3856ad364e35~amd64~~10.0.22000.1.cat Microsoft-Windows-EnterpriseS-SPP-Components-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.22000.1.cat Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.22000.1.mum 3. Run MSU_to_esd_and_Modded_CU.cmd as Administrator. Then it will generate customized ssu and cu in update folder. PS: The only thing I modified is: Code: Windows11.0-KB50*.msu ( ---> Code: Windows1*.0-KB50*.msu ( Or Code: Windows1*.0-KB*.msu (
#13529 MSU_to_esd_and_Modded_CU_202311242121.rar Just give an architecture or example, you need to customize improvements according to your needs. Need some command line basics, e.g. how to uncomment and comment e.g. #13563 How to use MSU_to_esd_and_Modded_CU_202311242121.rar.txt in 1.3 how to delete temporary folder e.g. MSU_to_esd_and_Modded_CU.cmd only Modded SSU's update.mum , e.g. replace serverdatacentercoredition by EnterpriseSEdition you can add pause command before compress Modded SSU_*.cab , add relevant files: wrapper-*~31bf3856ad364e35~amd64~~*.cat wrapper-*~amd64~~*.mum ... or simple replace, add code: for %%k in (%TU%\!SSU_Name!\wrapper-*~31bf3856ad364e35~amd64~~*.mum) do ( powershell -Command "(gc %%k) -replace 'serverdatacentercoredition', '%Modded_Parent_Edition%' | sc %%k" %_Null2% ) that maybe: Add Servicing Stack update to IoTEnterpriseS image: requires the current servicing session to be reloaded.
WindowsSecurity_Microsoft.UI is located in Windows-Server-AppCompat-FoD-Package-amd64.cab via uup dump. to add in source.esd
This is the new things of 25398.469 different to 25398.1 Professional which are necessary to be used for making custom 25398.469 EnterpriseS: Code: Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~en-US~10.0.25398.345.cat Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~en-US~10.0.25398.345.mum Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~~10.0.25398.469.cat Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~~10.0.25398.469.mum microsoft-windows-professionaledition-Wrapper~31bf3856ad364e35~amd64~~10.0.25398.469.cat microsoft-windows-professionaledition-Wrapper~31bf3856ad364e35~amd64~~10.0.25398.469.mum Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.25398.469.cat Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.25398.469.mum Package_for_RollupFix~31bf3856ad364e35~amd64~~25398.469.1.10.cat Package_for_RollupFix~31bf3856ad364e35~amd64~~25398.469.1.10.mum Package_for_ServicingStack_342~31bf3856ad364e35~amd64~~25398.342.1.0.cat Package_for_ServicingStack_342~31bf3856ad364e35~amd64~~25398.342.1.0.mum
If compatible, it's OK to Reconstruct with other build as source image. e.g. From 25393.1 to 25398.1.
How to know which files to put in MSU_to_esd_and_Modded_CU\files\Package_EnterpriseS ? If i add all EnterpriseS 25398.1 .cat & .mum to MSU_to_esd_and_Modded_CU\files\Package_EnterpriseS, Windows11.0-KB5032202-x64.esd will fail to update image. If i add .cat & .mum from the list you posted, Windows11.0-KB5032202-x64.esd will update image.
For 22621 I put: Updates OK. for 25398 if I put : Update fail on en-us, but OK on pt-br and es-es. Xinso in https://forums.mydigitallife.net/th...struction-project.80939/page-677#post-1816107 already inform of this.
Hi dear friend @Ace2 I have the same question but with the latest shared edit MSU_to_esd_and_Modded_CU_202311242121: It has two diferent folders: 1 - MSU_to_esd_and_Modded_CU_202311242121\files\Package_EnterpriseS 2 - MSU_to_esd_and_Modded_CU_202311242121\files\Package_EnterpriseS_25398.531 So should I put the files like this?: Code: V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS\Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~~10.0.25398.1.cat V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS\Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~~10.0.25398.1.mum V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS\Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~pt-BR~10.0.25398.1.cat V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS\Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~pt-BR~10.0.25398.1.mum V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.25398.1.cat V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.25398.1.mum V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS_25398.531 V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS_25398.531\Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~~10.0.25398.531.cat V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS_25398.531\Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~~10.0.25398.531.mum V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS_25398.531\Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~pt-BR~10.0.25398.1.cat V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS_25398.531\Microsoft-Windows-EditionSpecific-Professional-Package~31bf3856ad364e35~amd64~pt-BR~10.0.25398.1.mum V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS_25398.531\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.25398.531.cat V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS_25398.531\Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.25398.531.mum V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS_25398.531\microsoft-windows-professionaledition-Wrapper~31bf3856ad364e35~amd64~~10.0.25398.531.cat V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS_25398.531\microsoft-windows-professionaledition-Wrapper~31bf3856ad364e35~amd64~~10.0.25398.531.mum V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS_25398.531\Package_for_RollupFix~31bf3856ad364e35~amd64~~25398.531.1.11.cat V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS_25398.531\Package_for_RollupFix~31bf3856ad364e35~amd64~~25398.531.1.11.mum V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS_25398.531\Package_for_ServicingStack_521~31bf3856ad364e35~amd64~~25398.521.1.1.cat V:\Z\25398.1_ServerDatacenterCor_to_Client_amd64-Changed\MSU_to_esd_and_Modded_CU_202311242121\Files\Package_EnterpriseS_25398.531\Package_for_ServicingStack_521~31bf3856ad364e35~amd64~~25398.521.1.1.mum Also, following the "How to use MSU_to_esd_and_Modded_CU_202311242121.rar.txt" that @Wuyouzi067 share early #13563, I modified the MSU_to_esd_and_Modded_CU.cmd in the line 236: exit ---> exit /b and the Create.cmd in line 74 ---> add: call MSU_to_esd_and_Modded_CU.cmd, reding the indications of our Teacher @xinso on post #13583 I changed the Modded MSU_to_esd_and_Modded_CU.cmd in the line 4 from "Windows11.0-KB50*.msu (" ---> "Windows1*.0-KB*.msu (" so it could to be used with Windows 10+11+12 ? I don't run the script yet, because I want to know if the files are on the right place, if anyone can confirm it I will. Thanks in advanced for any help. Best Regards and Good Computing for all. @JeepWillys58
Finally update to 25398.531 (en-us) IoT successfully achieved. Spoiler Microsoft Windows [Versión 10.0.19045.3693] (c) Microsoft Corporation. Todos los derechos reservados. j:\25398.1_ServerDatacenterCor_to_Client_amd64>dism /english /logpath:logs\mount.log /mount-wim /wimfile:install.wim /index:1 /mountdir:mount Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Mounting image [==========================100.0%==========================] The operation completed successfully. j:\25398.1_ServerDatacenterCor_to_Client_amd64>dism /english /logpath:logs\ssu.log /scratchdir:temp /image:mount /add-package /packagepath:j:\25398.1_ServerDatacenterCor_to_Client_amd64\try\ssu Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.25398.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_521~31bf3856ad364e35~amd64~~25398.521.1.1 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_521 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. j:\25398.1_ServerDatacenterCor_to_Client_amd64>dism /english /logpath:logs\ssu.log /scratchdir:temp /image:mount /add-package /packagepath:j:\25398.1_ServerDatacenterCor_to_Client_amd64\try\ssu Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.25398.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_521~31bf3856ad364e35~amd64~~25398.521.1.1 [==========================100.0%==========================] The operation completed successfully. j:\25398.1_ServerDatacenterCor_to_Client_amd64>dism /english /logpath:logs\ssu.log /scratchdir:temp /image:mount /add-package /packagepath:j:\25398.1_ServerDatacenterCor_to_Client_amd64\try\lcu Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.25398.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~25398.531.1.10 [==========================100.0%==========================] The operation completed successfully. j:\25398.1_ServerDatacenterCor_to_Client_amd64>dism /english /logpath:logs\6-currentedition.log /scratchdir:temp /image:mount /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.25398.531 Current edition is: Error: 5023 The group or resource is not in the correct state to perform the requested operation. The DISM log file can be found at logs\6-currentedition.log j:\25398.1_ServerDatacenterCor_to_Client_amd64>dism /english /image:mount /cleanup-image /startcomponentcleanup /resetbase Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.25398.531 [===== 10.0% ] [==========================100.0%==========================] The operation completed successfully. j:\25398.1_ServerDatacenterCor_to_Client_amd64>dism /english /logpath:logs\6-currentedition.log /scratchdir:temp /image:mount /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.25398.531 Current edition is: Current Edition : IoTEnterpriseS The operation completed successfully. j:\25398.1_ServerDatacenterCor_to_Client_amd64>dism /english /logpath:logs\unmount.log /unmount-wim /mountdir:mount /commit Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image File : j:\25398.1_ServerDatacenterCor_to_Client_amd64\install.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. j:\25398.1_ServerDatacenterCor_to_Client_amd64>files\wimlib-imagex.exe optimize install.wim "install.wim" original size: 3823151 KiB Using LZX compression with 12 threads Archiving file data: 7315 MiB of 7315 MiB (100%) done "install.wim" optimized size: 3357377 KiB Space saved: 465773 KiB j:\25398.1_ServerDatacenterCor_to_Client_amd64> Spoiler Many thanks to Wuyouzi067.