About Local Experience Packs

If you use a Language Pack, you should not need to use a matching Local Experience Pack, but I'm no expert on this so you should check with Microsoft, although their documentation on this is extremely lacking
Local Experience Packs

ContentPack Structure

Directories within OSLocalExperiencePacks follow this logical pattern
OSLocalExperiencePacks\$ReleaseId $Architecture\$LanguageId

Source Content

Source Content is copied from the Language Pack ISO which can be downloaded from MSDN or VLSC. The LocalExperiencePacks are in a directory called LocalExperiencePack. The entire subdirectory must be copied as it contains a License.xml

My Recommendation

If you are working with MultiLang (Multiple Languages), follow this recommendation


Create a new ContentPack for each of the languages you are working with. In this example, I will create the following ContentPacks in PowerShell for my additional languages
PS C:\> New-OSDBuilderContentPack -Name "MultiLang de" -ContentType MultiLang
PS C:\> New-OSDBuilderContentPack -Name "MultiLang es" -ContentType MultiLang
PS C:\> New-OSDBuilderContentPack -Name "MultiLang en" -ContentType MultiLang
PS C:\> New-OSDBuilderContentPack -Name "MultiLang fr" -ContentType MultiLang

Copy Local Experience Packs

Copy the Local Experience Packs to the proper destination directory. If a destination directory doesn't exist, create one using the same naming format as the existing directories. Ensure that you do not have