Someone shared homebrewed install.esd of all SKUs. Q: How to extract language pack from install.esd? e.g. Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~zh-CN~10.0.20348.1. en-US provided by Skylined: Microsoft-Windows-Client-LanguagePack-Package-en-US.esd (17,509 KB) zh-CN extracted: Microsoft-Windows-Client-LanguagePack-Package-zh-CN.esd (21,599 KB) Code: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Add zh-CN Client language :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.20348.1 Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~zh-CN~10.0.20348.1 [==========================100.0%==========================] An error occurred - Microsoft-Windows-Client-LanguagePack-Package Error: 0x80070490 Error: 1168 Element not found. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log Error: 87 UI language is not installed. Error: 87 Could not set UI Language. UI language is not installed. ERROR: dism.exe has encountered an error.
Q: What exactly happened to the latest 25398 CUs that won't update en-US Pro? It just got suck at that Powershell component. Microsoft-Windows-LanguagePackManagement-Powershell.Resources, version 10.0.25398.1, arch amd64, culture [l:5]'en-US' Code: <dependentAssembly dependencyType="install"> <assemblyIdentity name="Microsoft-Windows-LanguagePackManagement-Powershell.Resources" version="10.0.25398.1" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </dependentAssembly> </dependency> ---> Code: amd64_microsoft-windows-l..owershell.resources_31bf3856ad364e35_10.0.25398.1_en-us_725e8653bdc5e7ec.manifest ---> Code: <file name="Microsoft.LanguagePackManagement.Powershell.Commands.Resources.dll" destinationPath="$(runtime.system32)\WindowsPowerShell\v1.0\Modules\LanguagePackManagement\en\" sourceName="Microsoft.LanguagePackManagement.Powershell.Commands.Resources.dll" importPath="$(build.nttree)\loc\en-us\managed\LanguagePackManagement\cmdlets\" sourcePath=".\"> ---> C:\Windows\System32\WindowsPowerShell\v1.0\Modules\LanguagePackManagement\en\Microsoft.LanguagePackManagement.Powershell.Commands.Resources.dll [25398.1308] amd64_microsoft-windows-c..equired-deployment0_31bf3856ad364e35_10.0.25398.1189_en-us_60e71eca412c414d.manifest ---> Code: <dependentAssembly dependencyType="install"> <assemblyIdentity name="Microsoft-Windows-LanguagePackManagement-Powershell.Resources" version="10.0.25398.1" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </dependentAssembly> </dependency>
@xinso you should try with medthod #1011. I do with 25398.1_ProfessionalWorkstation and success update to 25398.1308 (i do not test installation)
Thank you. I'd better wait for zwl29107. Or I just use LTSC. Q: Same package for all Editions, why it (the cat) went wrong on the latest CUs started from 1128? Test 1: 25398.1128 Code: ======================================================================================================== 25398.1128 Windows 11 Enterprise LTSC (Volume_GVLK with Edge without Store without NetFx3) amd64 en-US has been successfully reconstructed on 2024/12/15 ======================================================================================================== Test 2: 25398.1308 Code: ------------------------------------------------------------ Add Cumulative update to IoTEnterpriseS image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~25398.1308.1.6 [==========================100.0%==========================] An error occurred - Package_for_RollupFix Error: 0x80092004 Error: 0x80092004 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ------------------------------------------------------------ Test 3: 25398.1308 Code: ------------------------------------------------------------ Add Cumulative update to IoTEnterpriseSK image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~25398.1308.1.6 [==========================100.0%==========================] An error occurred - Package_for_RollupFix Error: 0x80092004 Error: 0x80092004 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ------------------------------------------------------------ Test 4: 25398.1128 Code: ======================================================================================================== 25398.1128 Windows 11 IoT Enterprise LTSC Subscription (OEM_DM with Edge without Store without NetFx3) amd64 en-US has been successfully reconstructed on 2024/12/15 ======================================================================================================== I just changed Edition and SSU\CU.
yes cos the lang pack the mui file of branding getting strip off but changing the build number like u did there should avoid this problem
Method Ace2 elaborated: Code: forums.mydigitallife.net/threads/guide-discussion-windows-editions-reconstructions.88605/page-51#post-1863801 Code: Need: Microsoft-Windows-Client-Desktop-Required-Package~31bf3856ad364e35~amd64~en-US~10.0.25398.1.cat Microsoft-Windows-Client-Desktop-Required-Package~31bf3856ad364e35~amd64~en-US~10.0.25398.1251.mum * Rename Microsoft-Windows-Client-Desktop-Required-Package~31bf3856ad364e35~amd64~en-US~10.0.25398.1.cat to Microsoft-Windows-Client-Desktop-Required-Package~31bf3856ad364e35~amd64~en-US~10.0.25398.1251.cat * Edit Microsoft-Windows-Client-Desktop-Required-Package~31bf3856ad364e35~amd64~en-US~10.0.25398.1251.mum Find <update name="DE296F1E1603DC0EB735745ECA216E75EB0FA158810AFD8EFB1C45911919A0FB"> <component> <assemblyIdentity name="microsoft-windows-client-desktop-required-deployment0" version="10.0.25398.1189" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </component> </update> Edit to <update name="DE296F1E1603DC0EB735745ECA216E75EB0FA158810AFD8EFB1C45911919A0FB"> <component> <assemblyIdentity name="microsoft-windows-client-desktop-required-deployment0" version="10.0.25398.1" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </component> </update> * Replace original cat & mum with modded versions. Microsoft-Windows-Client-Desktop-Required-Package~31bf3856ad364e35~amd64~en-US~10.0.25398.1251.cat Microsoft-Windows-Client-Desktop-Required-Package~31bf3856ad364e35~amd64~en-US~10.0.25398.1251.mum I would now recommend using Code: <update name="3A85776914ECCD84253163D62474F25B20F3E924A0D2B6760BA0FFD3B44E97D8"> <component> <assemblyIdentity name="microsoft-windows-client-desktop-required-deployment0" version="10.0.25398.1" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </component> </update> as replacement code. Last edit: Added correct code for [name="microsoft-windows-client-desktop-required-deployment0" version="10.0.25398.1"] Code: 3A85776914ECCD84253163D62474F25B20F3E924A0D2B6760BA0FFD3B44E97D8 [credit] xinso
About License Package: Old: License New: Default + License About License Edition: Old: Standalone Edition New: Parent and Virtual Edition(s) About Parent License: Pro: Using Enterprise as default Others: Using its own as default
Look: This Microsoft-Windows-Client-Desktop-Required-Package00. [25398.1128] Microsoft-Windows-Client-Desktop-Required-Package~31bf3856ad364e35~amd64~en-US~10.0.25398.1128.mum Code: <update name="5970B555F6220AA16BE172A9E058669EF202CF836AEA9FA0B85072660EA64C83"> <package integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-Package00" version="10.0.25398.469" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> ---> version="10.0.25398.469" <update name="5970B555F6220AA16BE172A9E058669EF202CF836AEA9FA0B85072660EA64C83"> [25398.1308] Microsoft-Windows-Client-Desktop-Required-Package~31bf3856ad364e35~amd64~en-US~10.0.25398.1251.mum Code: <update name="950EF263B01458615786C8EB0BB9277AB1D31C338A0709A5D57646EF3DB34A4E"> <package integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-Package00" version="10.0.25398.469" processorArchitecture="amd64" language="en-US" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> ---> version="10.0.25398.469" <update name="950EF263B01458615786C8EB0BB9277AB1D31C338A0709A5D57646EF3DB34A4E">
25398.1308 has user admin problem it let run as admin without password ? (not via console / runas.exe ) just me ?
[FYI] About the reconstructed 20348.1 Hyper-V Server (ServerHyperCore) PS: Lacking Microsoft-Windows-EditionSpecific-ServerHyperCore-WOW64-Package and Microsoft-Hyper-V-ServerHyperCoreEdition-Package.
Last night, EnterpriseS, OK. Now, after adding ServerHyperCore, the EnterpriseS, IoTEnterpriseS and EnterpriseSN, not OK. Code: 2024-12-19 09:06:06, Info CSI 000004ae Couldn't find the hash of component: Microsoft-Windows-Shell32-OEMDefaultAssociations-Legacy, version 10.0.20348.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the catalog \??\X:\Windows\WinSxS\Catalogs\9d7602575a4f6eb2b12ad2d4b1b04ec9df685ae9bd81e5745963c7f5a2d180e0.cat. ---> Microsoft-Windows-Shell32-OEMDefaultAssociations-Legacy ---> ReAdded "20348.1" package and Deleted all "19041.*" components. ---> Code: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Create EnterpriseSN :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.20348.1 [==========================100.0%==========================] The operation completed successfully.
Q: A package, modified and repacked, which is more reliable? A: It depends. e.g. 19041.1 arm64 LTSC. Case 1: My 19041.1 packages are modified with 19044.1288 components. After any CU update, it is truned to be "Official". Case 2: Some repacked 19041.1 packages, the Win32Calc is not accepted by CU. i.e. The CU, which has Win32Calc update, failed.