Hi, wellcome Of course this large community can help you, let me introduce for you one great tool, usually called W10MUI which was created by abbodi1406. This tool can make your hopes come true after you have the en-US version later.
@Javac75 Could you explain to me where you got the SXS files to create the EnterpriseS edition of Windows 11 21H2 (22000.1)? As I recall, some Windows 10 files were used in the previous thread, but I see that your SXS files (bedi) seem to be different.
I think only 22621.1 LTSC was the only official leaked ISO. as it has not been confirmed yet with 22000.1
zwl29107 confirmed in this post if it is trustable for you. https://forums.mydigitallife.net/th...ns-reconstructions.88605/page-40#post-1861360
What's the preferred choice concerning inbox apps for the LTSC -keep or remove?. I tried removing :: for clean to allow removal and the full_build.cmd got access denied trying to remove Microsoft.DesktopAppInstaller_2019.125.2243.0_neutral_~_8wekyb3d8bbwe. I will give that a :: and see what happens. Edit: Letting Microsoft.DesktopAppInstaller stay in the wim, will allow for a clean EOJ. Spoiler Code: Available Images: ----------------- Index: 1 Name: Windows 10 Enterprise LTSC 2021 Description: Windows 10 Enterprise LTSC 2021 Display Name: Windows 10 Enterprise LTSC Display Description: Windows 10 Enterprise LTSC Directory Count: 17108 File Count: 74911 Total Bytes: 12887332338 Hard Link Bytes: 5746717727 Creation Time: Sat Dec 07 11:20:48 2019 UTC Last Modification Time: Fri Jan 10 16:34:27 2025 UTC Architecture: x86_64 Product Name: Microsoft« Windows« Operating System Edition ID: EnterpriseS Installation Type: Client Product Type: WinNT Product Suite: Terminal Server Languages: en-US Default Language: en-US System Root: WINDOWS Major Version: 10 Minor Version: 0 Build: 19041 Service Pack Build: 1 Service Pack Level: 0 Flags: EnterpriseS WIMBoot compatible: no Will see if this as a base fixes my component store problem here. Edit : It doesn't.
2025-01-11 01:15:31, Info CBS Exec: Failed to commit stager to resolve execution chain. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
How to install .1308 onto Server AzureStackHCI 25398.1189? SSU-25398.1241-x64.esd installs fine as usual but Windows11.0-KB5048653-x64.esd errors out.
I am still getting component store is repairable after reconstruction using the EnterpriseS-19041.1-x64_rev.7z posted by abbodi1406 here. 1.Created reconstructed wim and simply applied it. 2.Dism scanhealth shows problem with component store I have a feeling the Windows Pro wim that I use as input for reconstucting is the cause of this problem. It's been a while now and I don't exactly recall how I ended up getting this wim. Can someone please give me a link or tell me how to get the correct iso for the wim I need for a valid 19041.1 LTSC reconstuction? Edit: This (spoiler: Consumer Install.wim) is what wim I used for reconstruction.
[About Edge on 19044 21H2 LTSC] Some say registry trick would do, some say it'll come back sooner or later. Just now I saw maur0 shows some tool is working fine.
Mini-Test Construct Windows 11 IoT Enterprise LTSC with Store 22000.1 es-ES Code: Select Desired edition (with Store): [1] Windows 11 Enterprise LTSC [2] Windows 11 IoT Enterprise LTSC Please enter the number of the desired edition: 2 Converting 22000.1 Windows 11 Professional to IoT Enterprise LTSC (with Store) amd64 es-ES Mounting image Deployment Image Servicing and Management tool Version: 10.0.19041.746 Mounting image [==========================100.0%==========================] The operation completed successfully. Removing Notepad-FOD-Package (Professional) Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 Processing 1 of 1 - Removing package Microsoft-Windows-Notepad-System-FoD-Package~31bf3856ad364e35~amd64~~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Creating EnterpriseS Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 Removing package Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.22000.1 Removing package Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.22000.1 Removing package Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Integrating Language Pack es-ES Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~es-ES~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 Starting to install product key... Finished installing product key. The operation completed successfully. Current Edition : IoTEnterpriseS (OEM) Setting up and copying license files Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 The operation completed successfully. Removing Apps Integrating Notepad-FOD-Package (IoTEnterpriseS) Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 Processing 1 of 1 - Adding package Microsoft-Windows-Notepad-FoD-Package~31bf3856ad364e35~amd64~~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 Processing 1 of 1 - Adding package Microsoft-Windows-Notepad-FoD-Package~31bf3856ad364e35~wow64~~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 Processing 1 of 2 - Adding package Microsoft-Windows-Notepad-FoD-Package~31bf3856ad364e35~amd64~es-ES~10.0.22000.1 [==========================100.0%==========================] Processing 2 of 2 - Adding package Microsoft-Windows-Notepad-FoD-Package~31bf3856ad364e35~wow64~es-ES~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Adding PhotoViewer Updates Not Found Reset Base Image. Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image Version: 10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Unmounting image Deployment Image Servicing and Management tool Version: 10.0.19041.746 Image File : C:\22000.1_EnterpriseS_x64_with_modLCU\install.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. "install.wim" original size: 3538521 KiB Using LZX compression with 2 threads Archiving file data: 7018 MiB of 7018 MiB (100%) done "install.wim" optimized size: 3169414 KiB Space saved: 369106 KiB Setting the NAME property of image 1 to "". Setting the DESCRIPTION property of image 1 to "". Setting the FLAGS property of image 1 to "". Setting the DISPLAYNAME property of image 1 to "". Setting the DISPLAYDESCRIPTION property of image 1 to "". Setting the NAME property of image 1 to "Windows 11 IoT Enterprise LTSC 2021 (with Store)". Setting the DESCRIPTION property of image 1 to "Windows 11 IoT Enterprise LTSC 2021 (with Store)". Setting the FLAGS property of image 1 to "IoTEnterpriseS". Setting the DISPLAYNAME property of image 1 to "Windows 11 IoT Enterprise LTSC 2021 (with Store)". Setting the DISPLAYDESCRIPTION property of image 1 to "Windows 11 IoT Enterprise LTSC 2021 (with Store)". 22000.1 Windows 11 IoT Enterprise LTSC (with Store) amd64 es-ES has been successfully created Presione una tecla para continuar . . . Results: The iso works only now I will add other FOD packages to finish the script. the script is able to detect updates if they are placed in the "updates" folder otherwise it will do an install.wim 22000.1 a script is needed to create the LCU modification. I will publish other progress in another post in a while. New test in the following post with more new information about the script: https://forums.mydigitallife.net/th...ns-reconstructions.88605/page-63#post-1867137