- #WINDOWS 10 1809 ISO FILE LATEST FIXED AS OF TODAY HOW TO#
- #WINDOWS 10 1809 ISO FILE LATEST FIXED AS OF TODAY INSTALL#
This caused a problem when admins tried to later IPU or deploy feature updates to their Windows 10 devices in the language that was of the install media they used in their task sequences (in this scenario, English en-us). So what? That’s not new! Correct, but what is new, is that previously, doing the above would have changed the system’s default language and the InstallLanguage key to French. Windows 10 20H2 task sequence, click to enlarge This saves from needing multiple Apply Windows Settings steps. You’ll notice below I’m depending on the OSDWindowsSettings* task sequence variables, which are picked up by collection variables.
This means in our task sequence, after the Apply Operating System Image step, we can now install our language content (LP, LXP and FoD) and set the locale options to match that of the newly installed LP in the Apply Windows Settings step. We can see from the above output, this is the new distinction of user and system default languages on a system. Type: partially localized language, MUI type. System user interface default language: en-US Here’s the translation of the above output:ĭeployment Image Maintenance and Management Tool Here is the dism.exe /online /get-intl output after we have built a fr-fr system using en-us base install media with this “new” process in Windor 20H2: dism.exe /online /get-intl output in French Microsoft created a difference between system default language and user default language. 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). In summary of said improvements, instead of completely changing the system default language, we now have a distinction between a user default language and system default language – this negates the whole InstallLanguage issue ( read my previous post if you don’t know what the InstallLanguage issue is). In this post I’ll discuss what those improvements are and what the process of localising a Windows 10 system in your ConfigMgr task sequence is now moving forward. I took a couple of cheap shots at Microsoft by complaining how annoying the process is, but ended on a high note because they came through with huge improvements to the process in Windonwards. I covered what Language Packs, Language Experience Packs, Language Interface Packs and Features on Demand are.
#WINDOWS 10 1809 ISO FILE LATEST FIXED AS OF TODAY HOW TO#
In that post I broke down the necessary bits in order to understand how to localise a Windows system. This is a follow up from my previous post Language Packs, Language Experience Packs, Language Interface Packs… what?! In this post I’m going to share with you a task sequence for ConfigMgr / SCCM / MEMCM / MECM / MCM (this is just getting silly now) that localises Windows 10 to a language other than the default language of the OS install media.