Language Pack chaos in W11

J

jjanssens

New Member
Messages
3
Reaction score
0
Using the latest Windows 11 22H2 iso ("en-us_windows_11_business_editions_version_22h2_updated_april_2023_x64_dvd_6d06ec14") from MSDN and the latest Language Pack DVD (""), I get a result that would be funny if I wouldn't have needed the image by this week. Goodbye deadline.
I can add the updates to the image, but if I then look at the result, it's very wrong. The text does not fit with the UI object.
View attachment 9733
In this screenshot for example, it says something like "Variable refresh rate" where it should say System. It says "Environment" where it should say Bluetooth, "Graphics configuration" where it should say Network & internet, it says "DNS settings" where you should activate Windows, and so on. This is a German example, but the same happens in French, Dutch and Danish. Interestingly, the wrong translation is exactly the same. I didn't check the other languages I use (Italian, Spanish, Polish), but I presume it's the same result.

At first sight, this happens in the modern interface and not in the classic interface. Nevertheless, I can't deploy it like this :(

Is something wrong with the language packs, with Windows or with NTLite? This worked perfectly in the past with an earlier W11 image and an earlier NTLite version.

PS. Using NTLite x64 2023.5.9228, professional license.
 
garlin said:
Are you integrating LP's before updating the image?
Immersive ControlPanel is showing completely wrong labels (Clicking "Wi-Fi" brings you to "Display settings" etc)
Click to expand...

I'm not updating the image. It's just the latest updated version from Microsoft. Your link is however exactly the same issue, so the solution might be indeed to use the original 22H2 and apply the LPs to that, and then integrate 2023-05 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5026372). Thanks. In case you know, can I do this in one go in NTLite or should I do it in two 'edits', i.e. create a new image with the LPs and then remount to add the LPs?

Meanwhile I had tried adding the LPs through dism directly, and strangely I got not error but I also didn't get the language available once booted.
 
MSDN monthly releases all have the updates pre-installed. They're not intended to be source images for customization, but available for easy deployment for VAR's and devs who don't have IT staff. While MSDN releases the same image in each of the supported languages, there is no multi-language version of that image.

1. Download 22H2 RTM (en-US) ISO. Use the 22H2 Optional Languages DVD to extract all your LP's.
2. From NTLite, integrate all the language files as updates.
3. Keep this base image as your new master ISO. Don't touch it unless you need to change LP's.

4. When you make a new ISO, copy the master ISO and add the monthly updates. Now everything is applied in the correct order.

Installing LP's after CU doesn't get you any warning or errors. But WU will realize something is wrong, and ask you to re-install the CU even though it's already there.

Language Experience Packs (LXP's) avoid this problem because they are UWP packages, separate from Windows KB's. The advantage is they can be changed at any time, but cannot localize legacy Win32 features (Control Panel).
 
garlin said:
MSDN monthly releases all have the updates pre-installed. They're not intended to be source images for customization, but available for easy deployment for VAR's and devs who don't have IT staff. While MSDN releases the same image in each of the supported languages, there is no multi-language version of that image.

1. Download 22H2 RTM (en-US) ISO. Use the 22H2 Optional Languages DVD to extract all your LP's.
2. From NTLite, integrate all the language files as updates.
3. Keep this base image as your new master ISO. Don't touch it unless you need to change LP's.

4. When you make a new ISO, copy the master ISO and add the monthly updates. Now everything is applied in the correct order.

Installing LP's after CU doesn't get you any warning or errors. But WU will realize something is wrong, and ask you to re-install the CU even though it's already there.

Language Experience Packs (LXP's) avoid this problem because they are UWP packages, separate from Windows KB's. The advantage is they can be changed at any time, but cannot localize legacy Win32 features (Control Panel).
Click to expand...

So, I got the oldest ISO MSDN offers, September 2022, which is also the date of the LP DVD. Still the same problem, just other strings. I just checked: that iso is 22621.525, while the RTM was 22621.521. I'm giving up for today.
 
If you're under a deadline crunch, this is a cheesy fix:
1. Add your LP's to April 2023 MSDN, integrate.
2. Download and add April or May 2023 monthly CU, integrate. No need to re-apply .NET updates.
 
You must log in or register to reply here.
Back
Top