just need to do full unstaging to make update work and using pro edition Code: dism /image:P:\ /Apply-Unattend:ins.xml /LogPath:d:\servicing.log Deployment Image Servicing and Management tool Version: 10.0.26040.1000 Image Version: 10.0.25398.1 Applying package servicing unattend [==========================100.0%==========================] The operation completed successfully. 13:51:01.87 - Started 13:52:34.88 - Finished dism /image:P:\ /add-package /packagepath:"D:\Windows Server, version 23H2 (25398.1) amd64 Client LangPack.esd" /scratchdir:D:\ /LogPath:d:\add.log Deployment Image Servicing and Management tool Version: 10.0.26040.1000 Image Version: 10.0.25398.1 Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.25398.1 [==========================100.0%==========================] The operation completed successfully. Add Package "D:\Windows Server, version 23H2 (25398.1) amd64 Client LangPack.esd" -==============- 13:52:37.99 - Started 13:52:54.93 - Finished dism /image:P:\ /add-package /packagepath:d:\1.msu /scratchdir:D:\ /LogPath:d:\add.log Deployment Image Servicing and Management tool Version: 10.0.26040.1000 Image Version: 10.0.25398.1 Processing 1 of 1 - [==========================100.0%==========================] [==========================100.0%==========================] The operation completed successfully. Add Package d:\1.msu -==============- 13:53:17.39 - Started 13:54:18.25 - Finished dism /image:P:\ /is-serviceable Deployment Image Servicing and Management tool Version: 10.0.26040.1000 Image Version: 10.0.25398.887 The operation completed successfully.
Methode used winsxs script from mdl GOOD 340; Microsoft-Windows-Branding-EnterpriseS-Package 460; Microsoft-Windows-Editions-EnterpriseS-Package 462; Microsoft-Windows-EditionSpecific-EnterpriseS-removable-Package 463; Microsoft-Windows-EditionSpecific-EnterpriseS-WOW64-Package 464; Microsoft-Windows-EditionSpecific-EnterpriseS-WOW64-removable-Package 486; Microsoft-Windows-EnterpriseS-SPP-Components-Package 577; Microsoft-Windows-Licenses-EnterpriseS-Package 578; Microsoft-Windows-Licenses-IoTEnterpriseS-Package 579; Microsoft-Windows-Licenses-IoTEnterpriseSK-Package 730; Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Default-Package 731; Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-License-Package 732; Microsoft-Windows-Security-SPP-Component-SKU-EnterpriseS-Package 733; Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseS-License-Package 734; Microsoft-Windows-Security-SPP-Component-SKU-IoTEnterpriseSK-License-Package BAD ... 461; Microsoft-Windows-EditionSpecific-EnterpriseS-Package
Microsoft-Windows-EditionSpecific-EnterpriseS-amd64-and-wow64 .7z sha1: C768DF202F53EDB1E789CA786D8F84B18937217B Code: deleted
To remove Client language package? No. Anything shown with this command are already visible (except SSU which is permanent): Code: dism /english /online /get-packages
xinso Thanks for help with creating EnterpriseS EditionSpecific ESDs. Quick question: With recreated Microsoft-Windows-EditionSpecific-EnterpriseS-Package.esd and Microsoft-Windows-EditionSpecific-EnterpriseS-WOW64-Package.esd what do I need to add to convert-UUP from uupdump, to be able create EnterpriseS edition from a script? I notices that EditionSpecific ESDs from UUPdump has some schema inside WIM naming index: <NAME>Edition Package</NAME> <DESCRIPTION>Edition Package</DESCRIPTION> </IMAGE> Is that of any use? You left it as <NAME>Microsoft-Windows-EditionSpecific-EnterpriseS-Package</NAME> Thanks!
25398.887 Core series, having tzsync,exe stuck issue. Q: It is fine when EditionPack-Core was replaced with EditionPack-Professional. Why?