These are grabbed from VLSC or MSDN / Visual Studio Subscription in an ISO. However more recently the naming convention is something like Microsoft-Windows-Client-Language-Pack_圆4_fr-fr.cab. These apparently used to come as lp.cab files in the “good ol’ days”. For simplicity I’m just going to use acronyms from here on out. Language Pack (LP), Language Experience Pack (LXP), Language Interface Pack (LIP) and Features on Demand (FoD). Throughout examples I’ll assume your OS media is something like en-us, the target language is fr-fr and we’re deploying Windows 10 1909. I’ve spent many hours reading docs, blogs, messing around in my lab and putting this post together. That last question was my main driver for needing to learn this topic. What on earth do I need to do to deploy Windows 10 as another language (completely localized for a user in their most comfortable language), without a million different ISOs on my Distribution Points and in my task sequence, and not screw with the InstallLanguage / default system language? (if you’re not familiar with the “InstallLanguage” issue, you will be after you’ve read this).What are language specific Features on Demand and do I need them?.Why don’t Language Experience Packs localise everything?.If a Language Pack does the job, why do Language Experience Packs exist?.

So what’s the difference between a Language Experience Pack and Language Interface Pack? To change a system’s language I need a Language Pack.How and when do I install Language Experience Packs? What are they?.It also discusses what the InstallLanguage issue was. If you haven’t read this post yet, it’s still recommended to read it as it breaks down what Language Packs, Language Experience Packs, Language Interface Packs, and Features on Demands are. The new improvements negate the InstallLanguage issue. I’ve written a new post Multilingual Windows 10 20H2 OSD with ConfigMgr which walks you through the detail on how to do this with Windand onwards. I’ll also touch on how to deploy languages via the Software Center and discuss what’s improved in Windows 10 version 2004. My aim here is to demystify the topic and show you a solid way to do Windows 10 multi language OSD with ConfigMgr along with sound reasoning. You’re faced with information that’s old, lacking real detail or generally misunderstood. Whenever I have approached the subject I have always felt overwhelmed. For a while I have been curious on how to do Windows OSD with multiple languages “the proper way” using Configuration Manager.

Windows 10 2004 download