This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We want to install the Language Experience Pack during the MEMCM task sequence right after the step "Apply Operating System Image" (WinPE).
But the .appx file will not be installed, only the .cab works.
I do some research and found a section in the "ZTIPatches.wsf" for LXP so it should work?
I know for the .cab file there has to be a folder named the language like "de-de".
So I tried with and without the folder but not working.
Any ideas?
We are using the MEMCM 2006, MDT toolkit 8456 and ADK 1903.
Hi,
Thanks for posting in Microsoft MECM Q&A forum.
1.Please help examine the smsts.log on the target system to see if there are any further information about this issue.
SCCM: How to copy SMSTS.log when a Task Sequence fails
2.Here are some great step-by-step guides to install LXP during OSD:
Windows 10 Multilanguage Deployment with MEMCM
Language Packs, Language Experience Packs, Language Interface Packs… what?!
Note: This is non-Microsoft link, just for your reference.
Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hello Simon!
Thanks for your reply.
I have attached the log files
36763-ztipatches-dism.txt
36727-ztipatches.txt
It is not possible to attach the smsts.log because it's bigger than 3.1 MB.
But you see the same in the ztipatches.txt (renamed because .log is not allowed to upload).
There are futher informations we are using an unattended.xml
Thank you for the links, I will test as workaround but I hope the MDT step will get fixed.
Hi,
Thanks for your reply.
Thanks for your great idea and hard work.
As far as I know, the only official way to automatically register the LXP language as a selectable language is to execute a script. It's hard to achieve this via MDT step. You can submit a new user voice in Microsoft Endpoint Configuration Manager Feedback or open a support case with Microsoft to get better support.
I will also keep an eye on this question, if there is any update, I will let you know. Thanks for your understanding.
Best regards,
Simon
Hello!
I understand what you mean, but I am a little bit confused, because in MDT there is already a LXP section, but will not used.
Do you know why or what the mechanism is behind?
In the meantime I was able to get this working with the manual you sent before: 1347144
Thank you!
Regs
Hi,
Thanks for your reply. I'm glad to know the workaround is working in your environment. We have limited information about the behind mechanism. As a support Engineer, we are also responsible for collection customer feedback of product itself and try the best to deliver it to the product team, in order to improve customer experience. At such situation, I will summarize this and try to deliver it to product team, but not guaranteed. Once there is any feedback, we will get back to you at the first time. Thank you for your kind understanding.
Best regards,
Simon
Hello!
Do you have new informations about the issue, may?
We cannot use the workaround in our environment anymore.
Because if we patch the WIM file in MEMCM with the newest CU (2021-01) the workaround with the manual does not work anymore.
The GUI is a mess, something german, something english.
So we will use again four images :(
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 22%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
Just as an 'alternative' answer guys, a much simpler (but unsupported) way of deploying Language Packs available on Windows Update is as follows -
Install the Language Pack from Windows Update, download all the extra content, set up everything as you want it including defaults for new users etc.
In a Powershell Administrative Window (Run As Admin) -
get-appxpackage -allusers | select name, packagefullname
Look for your Language Pack on the list (this is not alphabetical), and then mouse-over COPY just the packagefullname (on the right).
remove-appxpackage -allusers -package "<PASTE the packagefullname>"
This overcomes all the sysprep/deployment issues, and the Language Pack will just add itself back on happily for each new user. Like I say, not supported, but works well for us.