Jump to content


How can I install Windows 10 language packs offline with an MDT Integrated Task Sequence in System Center Configuration Manager (Current Branch)

Recommended Posts

This was massively helpful thankyou! I will try to implement your full solution shortly, however, I want to be able to install ja-jp language pack as an isolated task sequence (deploying the LP to a desktop that is already imaged). I have created a new task sequence, used the Install Language Packs Offline option and added/distributed the contents (.cab file containing the language pack) - there is only 1 step in the task sequence (to install the LP) - and it seems to fail shortly after downloading the content. error code 0x00000032. I doubt the 'full' solution will work if the standalone install of the LP using sccm's wizard-task sequence will work. 


Any ideas why this task sequence fails? Or how we can retrospectively add a language pack to a pre-built machine (whilst the user is logged in/off)?

Share this post

Link to post
Share on other sites

that error usually means unsupported subsystem (like using an x86 package in an x64 os or vice versa), but without the full smsts.log it's hard to be sure

Share this post

Link to post
Share on other sites

It seems the .cab file has to be installed under PE mode, not during a logged in session. Never mind.

I have another question - I have tried to tailor your example to substitute RegionValue for OSDComputName variable (which is declared in PE environment before the OS is deployed) . So, if OSDComputerName like TOK , then Japanese language settings are applied etc. I have read that SCCM can't handle 'like' or 'contains' queries (and for reference, I used a Custom Variable, same as you do) to declare OSDComputerName. I'm now finding that the components aren't installing, but no idea where to check on client logs where this went wrong, and why.

We want to build PC's by the region, and SCCM to detect the OSDComputerName, then apply the relevant language packs and UI languages depending on this variable. 

Do you know which logs to check, or anything to watch out for when doing things this way? I think the reason my deployment failed has something to do with OSDComputerName not being a custom variable, but I'm not sure how i should declare this in the:

IF OSDComputerName like TOK THEN

SET OSDLanguage to ja-jp



attached example



Share this post

Link to post
Share on other sites

Hello Nail, I created task sequence according the post. I am deploying on baremetal. I dont have any HTA. Is there any way i can provide region value and language value. I am deploying only in polish and english. SO i have added only polish.

any suggestions?



Share this post

Link to post
Share on other sites

Thanks for the reply, How can I hardcode them in unattendxml? just replace osduilanguage to pl-PL

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-International-Core" processorArchitecture="wow64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <cpi:offlineImage cpi:source="wim:c:/install.wim#Windows 10 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />


Share this post

Link to post
Share on other sites

If you don't need flexibility with your unattend.xml file (for changing out different language and regional settings) you can just add the code to it.

For example Inputlocale is for keyboard layout. I happen to leave the variable, and in my task sequence set it to "en-us;cs-cz" to set it to US layout as default but with the option to switch to the Czech keyboard layout.




So you can just replace your "%OSDInputLocale%" with "pl-PL" or "pl-PL;en-us" or something like that.

Share this post

Link to post
Share on other sites

You still need the unattend.xml to tell the OS what settings to use. So no matter how you get the settings into the unattend.xml (static or declaring a variable) its still required. As long as the variables are declared before the "Setup Windows and ConfigMgr" step it should work out.

Technically the "Apply Operating System Image" and other pre-OS steps are creating/modifying an unattend.xml file for you.

Share this post

Link to post
Share on other sites

@anyweb we are on CM 2006 with W10 1803 machines (planning to move to 1909) but the regional settings have to be changed to this:


I tried by deploying a TS with an XML to the actual machines but this only works for the welcome screen and new user accounts, not for the actual already known users. This is an XML I deployed

 <gs:GlobalizationServices xmlns:gs="urn:longhornGlobalizationUnattend">
    <!--User List-->
        <gs:User UserID="Current" CopySettingsToSystemAcct="true" CopySettingsToDefaultUserAcct="true" />

    <!--Display Language-->
        <gs:MUILanguage Value="en-US" />
        <!--<gs:MUIFallback Value="en-UK" /> -->

    <!-- system locale -->
    <gs:SystemLocale Name="en-US"/>
    <!--User Locale-->
        <gs:Locale Name="fr-BE" SetAsCurrent="true" ResetAllSettings="true"/>

    <!--input preferences-->

        <gs:InputLanguageID Action="add" ID="0409:00000813" Default="true"/>
        <gs:InputLanguageID Action="remove" ID="0409:00000409"/>

        <gs:InputLanguageID Action="remove" ID="0809:00000809"/>


        <gs:GeoID Value="21"/>


Any ideas how to fix that for the known users on the machines?

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...