How to: Install Language Pack file ( lp.cab ) in Windows 8 RTM Standard Currently, DreamSpark Premium (formerly MSDNAA) only have access to the en-US version of Windows 8 RTM, fortunately enough if you want to change the display language now you can download the official Language Pack.
I have already given the download links for the. You can download the win8lang files from my previous article.
Now the question arises that how to install these win8lang files. There is one thing that should be clear that there is a difference between the Windows 8 language pack and Windows 8 language interface pack. The Windows 8 language pack has more translations of the dialogs and help files than Windows 8 language interface pack. Windows 8 language pack can probably be installed only on Windows 8 Ultimate and Windows 8 Enterprise editions.
This is not for sure because Microsoft has not yet released. Let’s go through the installation process of each type of language pack separately. Install Windows 8 Language Packs. First you will need to download Windows 8 language pack of your choice. Download WDP Universal Language Installer from below:. download id=”14″. Click on the “ Open.win8lang and install it” button and select the language pack you have downloaded.
This will install the language pack in your Windows 8. Install Windows 8 Language Interface Packs. Go to the Search dialog (WinKey + Q) and search for “language”. Click on the Settings and select Add language. Another window will open where you can add the languages of your choice.
You can select multiple languages and then switch to any language of your choice. If you are using Windows 7, you may be interested into install language packs in Windows 7. Update: We have added.
Managing Windows languages and language packs on Windows 10 and Server 2016 can be a bit of a daunting task. This article aims to clarify most issues. Change Log: added information on (languages for handwriting, speech, etc.).: small error correction in the of language packs (I wrote%SystemDrive% instead of%SystemRoot%). Added that changing the language for Windows Apps, Edge and Internet Explorer concerns the language displayed within the application and not the language of the application itself. Table of Contents. An introduction to language packs A language pack allows you to display Windows in a different language besides English. All windows and menus are displayed in your locale language.
This is not the same as configuring local settings such as keyboard layout, date, time and number formatting. You can configure these locale settings without changing the Windows language. DSWriteLog 'I' 'End of script' $LogFile If you want to go one step further and create an SCCM package as well, please follow the step-by-step explanation in the article. How to change the Windows display language The Windows display language is configured per user, not per machine.
There are a couple of methods how to change the display language. You can choose one of the following options:. Most methods apply to both Windows 10 and Windows Server 2016 unless stated otherwise.
Change the display language manually (Windows Server 2016) Note: in an enterprise environment, I strongly recommend installing the required language packs during the initial installation. This goes for both client and server operating systems. To manually change the Windows display language on a machine with Windows Server 2016 version 1607, go to Control Panel Language.
In the menu the entry Add a language adds the keyboard layout for a particular language. Under Options you can enable the Windows display language if it has been installed. Change the display language manually (Windows 10) In Windows 10 version 1803, changing languages is handled differently. Go to Settings Time & Language. On the left side select Region & Language. In this window you can add a language.
After adding a language, Windows checks if there is a language pack available for it. In case a language pack is found, you have the option to download and install it. Click the Options button. Select the Download button beneath the language options to start the download. After installing the language pack, Windows will automatically install it.
After installing the language pack, a new popup box is available where you can select the preferred Windows display language. As mentioned before, this is for the current user only. After changing the Windows display language you have to sign-out (and sign-in again) for the changes to apply. Change the display language using Microsoft Group Policy The Windows display language for a specific user or group can be forced by enabling the Group Policy setting Restricts the UI language Windows should use for the selected user in the Group Policy User Configuration Policies Administrative Templates Control Panel Regional and Language Options. It is important to be aware that this setting prevents a user from selecting a different display language, even if more languages are installed on the local system. In case you want to be less restrictive towards your users, use a Group Policy Preference item instead of a Group Policy item. How to use a Group Policy Preference item is explained in the.
Change the display language using a Group Policy Preference item In case you want users to be able to change their Windows display language, you cannot use a Group Policy setting. As mentioned in the previous paragraph, configuring a Group Policy setting to define the user's display language results in the user not being able to change the Windows language. The solution is to use a Group Policy Preference item instead. The preferred Windows display language is stored in the registry value PreferredUILanguages in the registry key HKEYCURRENTUSER Control Panel Desktop. The value PreferredUILanguagesPending is only used to store the language that will be active at next logon in case the user changed it manually and did not sign-out yet. Changing the language in this multi-string registry value accomplishes the same result as when changing the language manually using the GUI.
Of course, for everything to work the language pack has to on the local system. This solution applies to both Windows 10 and Windows Server 2016 (and higher). Using a Group Policy Preference registry item allows an administrator to configure the preferred Windows display language while still allowing a user to change the language manually.
Configuring the option 'run one time' ensures that the preference item is not enforced at next logon. Applying the preference item only once ensures that the display language is never overwritten should the user decide to change it. Using (ILT) you can assign preferred Windows languages to different users based on a number of criteria (see the section Configuring regional settings using Group Policy in my article for an example how to use ILT). Using a logon script As explained in the, the setting to configure the Windows display language is a registry value.
Therefore, it is possible to use a logon script to configure this setting. In case you use a PowerShell script I invite you to use my. You can configure the registry value using the function. To prevent a user from having to sign-out in order to apply the language settings, make sure to run your logon script synchronously. This means that your logon script needs to run before the user's desktop is started (so before the initial explorer.exe process is stared). Enable the Group Policy item Run logon scripts synchronously in the Group Policy Computer or User Configuration Policies Administrative Templates System Scripts.
How to change the display language for Windows Apps and Store, Edge and Internet Explorer As stated in the of this article, the Windows display language is applied to all Windows components including Windows Apps and Store, Edge and Internet Explorer. However, it is possible to use a different language for the Windows Apps and Store, Edge and Internet Explorer. Note: the language settings I am referring to here is the language used inside a Windows App, Edge or Internet Explorer, not the menu language of the actual application!
For example, when the language of Internet Explorer is set to German and you visit Microsoft.com, the content is displayed in German. This is possible by changing the order of the languages. You can choose one of the following options:. Most methods apply to both Windows 10 and Windows Server 2016 unless stated otherwise. Manually (Windows Server 2016) To manually change the Windows display language for Windows Apps and Store, Edge and Internet Explorer, on a machine with Windows Server 2016 version 1607 installed, go to Control Panel Language.
In the menu, move the preferred language to the top of the list. Manually (Windows 10) In Windows 10 version 1803, changing languages is handled differently. Go to Settings Time & Language Region and Language. Use the arrows to move the preferred language for Windows Apps and Store, Edge and Internet Explorer to the top of the list. It is also possible to change the display language for Windows Apps and Store, Edge and Internet Explorer from within Internet Explorer. Go to Internet Options and on the tab General go to Languages. In the window Language Preference, click on the button Set Language Preferences.
This will lead you to the settings page. Note: those of you who have experience with older operating systems will quickly realize that Microsoft made some significant changes concerning the language configuration in Internet Explorer. Group Policy Preference As far as I am aware, there is no Group Policy setting to configure the display language for Windows Apps and Store, Edge and Internet Explorer. But don't worry; you can use a Group Policy Preference instead. The preferred Windows display language for Windows Apps and Store, Edge and Internet Explorer is stored in the registry value Languages in the registry key HKEYCURRENTUSER Control Panel International User Profile. Changing the order of languages in this multi-string registry value accomplishes the same result as when changing the order using the GUI. This solution applies to both Windows 10 and Windows Server 2016 (and higher).
See the section in this article for more information how to configure a preference item. Using a logon script As explained in the, the setting to configure the display language for Windows Apps and Store, Edge and Internet Explorer is a registry value. Therefore, it is possible to use a logon script to configure this setting. In case you use a PowerShell script I invite you to use my. You can configure the registry value using the function.
To prevent a user from having to sign-out in order to apply the language settings, make sure to run your logon script synchronously. This means that your logon script needs to run before the user's desktop is started (so before the initial explorer.exe process is stared). To accomplish this, enable the Group Policy item Run logon scripts synchronously in the Group Policy Computer or User Configuration Policies Administrative Templates System Scripts. How to prevent users from changing language settings By configuring the Windows display language, you basically prevent a user from changing the language, at least until the next Group Policy refresh cycle (this will likely be every 30 to 90 minutes in most organizations). Dennis Span works as a Senior Citrix Architect for a large insurance company in Vienna, Austria.
He holds multiple certifications such as CCE-V, CCIA and CCEA. In 2017, Dennis became a Citrix Technology Advocate (CTA). Besides his interest in virtualization technologies and blogging, he loves spending time with his family as well as snowboarding, playing basketball and rowing. He is fluent in Dutch, English, German and Slovak and speaks some Spanish. This entry was posted in and tagged,. Bookmark the.
Super-informative article cutting through all the noise on this thorny subject. In view of your extensive experience on this subject, I was hoping you might have come up against the following problem which is widely reported but doesn't affect users in the United States (which may explain why it is not getting due attention from Microsoft). Even though I have English (GB) installed and operational on my Google Cloud-based Windows Server 2016, the user's Display Language reverts to the originally installed Language, i.e.
![Pack Pack](/uploads/1/2/5/5/125589438/900714267.jpg)
English (United States), after every user sign off/sign on (via RDP). The Keyboard Language is not affected by this problem and I can change the Display Language to English (United Kingdom) via the task bar during a logon session. However it reverts back to English (United States) on next sign-on.
I have tried all of the stated approached in your article but to no avail. Hi Roger, I am happy you enjoyed the article. You say that this problem is widely reported. Can you send me a couple of links perhaps? The user display language is a current user setting that can only be overwritten automatically in two situations: 1) The registry value HKEYLOCALMACHINE SOFTWARE Policies Microsoft MUI Settings - 'PreferredUILanguages' with the value 'en-US' is configured (as I state in my article this can be set via Group Policy as well). 2) The user profile is not persistent: the user gets a new, clean profile at each logon. Please check if any of the above situations apply.
If not, please get back to me. In an RDP session, the local client keyboard is parsed to the RDP session (that is why the keyboard settings work).
Actually Dennis, I just found the solution not long after commenting on your article. See: I am gobsmacked by Microsoft's continuing efforts to destabilise their operating system by introducing crazy off-the-cuff design decisions with every new release. To quote the relevant section: « For some reason, Windows seems to regularly check to see if I'm using the EN-US keyboard layout, and adds it if I'm not » Actually Microsoft in 2008 added to Windows an 'improvement' where a PC when booting, changes the Language and Keyboard Layout set on this PC, to the one of a nearby other PC on the network, which of course is often US, but also can be US-International, French, German, or any of the 150 others. Of course this behavior, being full unexpected and full hidden, puts the user in a long period of doubt and fruitless search for solution. Diego gave on 07 Oct 2012 a Total protection against these Keyboard Layout changes from nearby computers, which is immediately, totally, and reliably effective: In RegEdit, navigate to HKEYLOCALMACHINE SYSTEM CurrentControlSet Control Keyboard Layout, in right pane right-click and choose 'New' then 'DWORD Value', name it 'IgnoreRemoteKeyboardLayout', then double-click it and under 'Value data' type '1' (don't mind 'Hexadecimal' or 'Decimal', either will do).
Hi Roger, I am slightly confused. I thought you had an issue with the user's Windows display language changing, not the keyboard layout. I guess I misunderstood. Concerning the keyboard layout, it is correct that the registry value 'IgnoreRemoteKeyboardLayout' prevents that the keyboard of the local client device is parsed in an RDP session. This is also officially documented by Microsoft. This is also what I meant to say with my phrase 'In an RDP session, the local client keyboard is parsed to the session' in my previous comment. The fact that the keyboard reverts back to English (US) tells me that the keyboard on your local client is set to English (US) and not English (UK).
It is actually best practice to NOT create and set the registry value 'IgnoreRemoteKeyboardLayout' to '1'. Under most circumstances, it is a good thing that each user logging on to the remote machine gets his or her local keyboard redirected. But I am happy that your problem was solved!