Windows 10 22h2 Language Packs
Derrick Drescher
We have exactly the same problem, the installation of the language packs is not a problem, but as soon as the language is changed, the firewall no longer works. (And a Firewall reset is also not possible)
@Malex17 I have the same issue and discovered this yesterday when upgrading machines from Win10 20H2 and 21H2 to 22H2. Tried everything to get Windows Defender Firewall running again but nothing worked. This morning I upgraded two test machines from 21H2 to 22H2 while closely monitoring the SMSTS.LOG and running a ping. After the OS upgrade everything was still fine, but after the language packs installed (nl-NL, fr-FR, en-US) and the machines rebooted with nl-NL as default system language, they could no longer be reached over the network. After the TS completed I checked the machines and they both failed to start the Windows Defender Firewall. If I change the default system language to en-GB, set it as default language for new user accounts and the welcome screen and reboot, ONLY THEN does the Windows Defender Firewall start.
From what I read in the other threads, people are able to solve it by using an older build of 22H2 and patching it in the TS prior to installing the language packs, but that is quite the hassle and not a good solution imo.
I downloaded Windows 10 22H2 from October, created an Operating System Upgrade Package in SCCM and used this image for the upgrade. I then applied all my language packs in the TS (EN, NL, FR), rebooted the machine and then applied the LCU (Latest Cumulative Update) which in this case was KB5021233. After applying the patch and rebooting the pc, the Windows Defender Firewall is working fine again when the pc boots with NL set as system language.
I have a lot of customers who want to give their end users a localised experience with AVD and W365. This means that they install language packs onto the Session Hosts and configure it either with GPO or scripts so end users will have their session in their own language.
I know from experience that working with language packs is not that easy. We are talking about Language (interface) pack and also about the Features on Demand like spell check, fonts, handwriting, text-to-speech etc. You need to download the correct versions, need multiple files and also some scripting knowledge to get it working.
Today I came acros a post from Scott Breen where he gave an update about a new way of installing languages on Windows 10 20H2+ and Windows 11 without the need to download and script all of this. In this post I will show you how you can easily make new languages available and even configure it is as the default language.
According to Microsoft this new PowerShell Module allows users to easily add languages and related language features and manage settings like System Preferred UI Language, System Locale, Input method (Keyboard), Locale, Speech Recognizer, User Preferred Language List using the new cmdlets.
You can use this cmdlet during the build of Master Image for AVD or Windows 365 for example. You can also use this during for example an Autopilot deployment or deploy it as an application via Intune. For this blog I will focus on AVD and how you can use these cmdlets in an Scripted Action with my favorite tool Nerdio Manager for Enterprise.
Open up PowerShell as an administrator. Use the following command to install a language pack. For a list of available languages you can check out this overview from Microsoft over here. For this command to run you need the Language/region tag also known as the bcp47 tag. When you use this cmdlet you need to provide the language tag and optional you have a few parameters.
If you specify this parameter the cmdlet will set the System and Default Device Settings (Windows Display Language, regional and locale formats) to the installed language. If you use this command you have to restart the device or login again for the changes to take effect.
There are multiple ways you can set a default language as the System preferred UI Language. You can use the previous command with the -CopyToSettings parameters. But you can also use the following command to configure the default language. For both the options you will need to restart the device or login again for the changes to take effect.
You see, no more preparing the correct content for all the languages and features. No more downloading different files for different version of Windows. An extreme easy way to install new language, uninstall languages
Like I said in the beginning of this post, there are multiple ways you can use this cmdlets. I have created a super simple script to install multiple languages and to configure the default language. The only things you need to provide within the script are the languages you need to install and which language needs to be configured. I have created this script so I can use it with Nerdio.
Scripted Actions are extremely powerfull to performs all kinds of actions on your Azure Virtual Desktop or Windows 365 session hosts. See it like a library of PowerShell scripts which you can run during the VM Provisioning process or for example manually on all the hosts within a certain hostpool. Or use it during the creation of Images with Nerdio.
Navigate to Scripted Actions, select Windows scripts and scroll to the bottom of the page. There you will see a buttom Add scripted action. You will see the following screen where you can create your own Scripted Action.
If you have a script which should be run on his own you can choose for Individual. For this example I will use Individual with restart. Why? I think these kind of customizations we need to at least ensure the machine has been restarted. I would recommend to use this script before installing the applications and other customizations.
Just copy and paste your PowerShell code in the Script pane and you are ready to go. Hit Save & close and you are ready to use it! The script is available on my GitHub because I want to integrate it within Nerdio. In the next chapter you will find the script, for the latest version go to GitHub
The script will place a transcript in C:\Windows\Temp\NMWLogs\ScriptedActions\languages, you can use this for troubleshooting or to validate the script worked. If the script worked you should see the configured languages being available on your Session Hosts and the default Language must be configured.
I'm a consultant with a passion for the perfect cup of coffee. Each morning, I take the time to craft a delicious espresso, savoring the rich aroma and flavor. When I'm not busy at work, you can find me in my garden, tending to my plants and enjoying the beauty of nature. My love for coffee and gardening brings balance to my life, providing moments of peace and tranquility amidst the hustle and bustle of the day.
In modern versions of Windows 11 22H2 and Windows 10 21H2+, you can use PowerShell to install and manage language packs and language interface language packs (LIPs). In previous builds of Windows, the only way to add or remove language packs was to use the classic Control Panel or Settings user interface (quick URI access command: ms-settings:regionlanguage). (adsbygoogle = window.adsbygoogle []).push();
In recent versions of Windows, a built-in PowerShell module LanguagePackManagement has been added. You can use the cmdlets from this module to install an optional Windows language pack and set your preferred language for the Windows user interface.
If your computer is disconnected from the Internet, you can install additional language packs and components offline using DISM ( -us/azure/virtual-desktop/windows-11-language-packs), mount the ISO image in Windows, and install a language pack and its components using the commands below:
So there are still some bugs to work out, but at least conceptually it seems to be heading in the right direction. End users can still add languages through Settings (with the same end effect), and IT admins can do it with a single PowerShell command.
We are testing to deploy Language Packs for windows 11 and we have similar problems like you describe.
For example we could install spanish Language over Powershell successfully but only the display Language kept in english-US (Like the OS is) and only when we change it manually as User it works. do you have already found a solution how we can install Spanish Language completely also as default Display Language without manually interaction? or other tipps how we can deploy it
We are working with Windows machines that are delivered with an English-installed operating system, no matter if the machine is handed over to a user in The Netherlands, Spain or whatever country. But we want to provide our users with an easy way to completely change the machine in another language of their own choice. This means we want to provide an automated manner of changing the language of the machine. Because we want to make changing the language as easy as possible, but also because installing a language pack requires administrative permissions.
Last week I wrote an article to change the language of a device by installing a language pack during Autopilot enrollment. But another option is to allow the user to choose the language of their device after enrollment To provide the end user the option to change the language of the device themselves in an easy way.
For Windows 10 Oliver Kieselbach created an awesome PowerShell script to get the job done, which he describes in this blog post. This script installs the needed language pack to the device and sets the language as the default language, including the logon screen for example. The script uses a temporary scheduled task, to also set the language for the sign-in user.
The script can be wrapped as a win32 app and made available with Microsoft Intune to be installed by the end user via the Company Portal app.