Cannot configure a language pack for Windows Server 2019 Desktop Experience
This article provides solutions to an issue where you cannot configure a language pack for Windows Server 2019 Desktop Experience.
Applies to: Windows Server 2019
Original KB number: 4466511
When you use the Desktop Experience in Windows Server 2019, you cannot install language packs by using the Language page in the Settings app.
Method 1: Install KB4476976
To resolve this issue, install the January 22, 2019-KB4476976 (OS Build 17763.292) update.
Then, follow the steps in Configure the display language.
Method 2: Use LPKSetup
Alternatively, you can add a new Windows display language without installing update 4476976. To do this, you must get the desired language pack CAB file, install the CAB file by using LPKSetup.exe, and then use the Language page to set your preferred language.
To use LPKSetup.exe, follow these steps:
- Download an ISO image that contains the language packs here.
- Either mount the ISO image or burn the image to a DVD.
- Press the Windows logo key+R to open the Run dialog box. Type lpksetup.exe, and then select OK.
- Step through the wizard to install the language pack. Or, you can also use the Lpksetup Command-Line Options to install the language pack by using an elevated command prompt.
Then, follow the steps in the next section.
Configure the display language
To configure a new Windows display language, follow these steps:
- Start the Settings application, select Time & Language, and then select Language.
- On the Language page, under the Preferred languages heading, select Add a language.
- In the Choose a language to install dialog box, select an entry that matches the language pack language, and then select Next.
- In the Install language features dialog box, select Install. The Windows display language box should now include the newly added language.
- To switch to the new language, select it from the Windows display language box, sign out of the current Windows session, and then sign back in.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.