Solved Immersive ControlPanel is showing completely wrong labels (Clicking "Wi-Fi" brings you to "Display settings" etc)

Hi,

OS: Windows 11 (22H2 22621.674)
OS language: Swedish
OS regional, locale settings etc: Swedish
Installed software + other info: Most likely not relevant

I have a very strange problem. I recently downloaded the latest Windows 11 Enterprise ISO and implemented it into our Task Sequence. The Task Sequence also includes the latest available language pack for Swedish. I am now trying it out on some virtual machines and 100% of the time, after OSD is complete, Immersive ControlPanel is completely broken. I mean, it is so broken that you can see for yourself in these images how broken it is, even if you don't know Swedish!! In the first image we have of course selected "System" in the upper left. In Swedish, the label says something like "Authorization settings". Regardless, we can see that it is selected, yet the first option to the right view is "Wi-Fi". If you click Wi-Fi just for the fun of it, you will be directed to printer settings (or something).



In this image below we can see that I have CMD open and I rightclick on it in the taskbar. The option in the bottom should of course be "Close", but in this case, it is a swedish word roughly translated into literally "Most common". Clicking it will close CMD.



Now I know what you are thinking, I must have downloaded the wrong language pack, or maybe it was installed incorrectly. I have of course thought of this too and spent very many hours trying to fix this but without success. I have even imaged the computer, then ran DISM manually to install the language pack, restarted the computer but still this exact issue remains.

However... If I turn off WSUS and allow this machine to connect to Microsofts Windows Update, and download the latest updates and reboot, then this issue is fixed! It's like a 100% fully functional machine, it is so good that I am even ready to hand it out to a customer without thinking twice.

My question to you dear Elevenforums, is what do you think is the cause of this? I understand that you may "need" to look at the Task Sequence etc to give an accurate answer, but that is not possible. I am solely asking what you think is causing the corrupted labels, and why it is isolated to Immersive ControlPanel, and also what is it with Windows Update that corrects it? Regular Control Panel, Start-Menu, Explorer, webbrowser, yeah pretty much everything else is as it should, even without running Windows Update.

I have tried each of the following during imaging:
• dism.exe /image:%OSDTargetSystemDrive%\ /ScratchDir:%OSDTargetSystemDrive%\Windows\Temp /Add-Package /PackagePath:".\Microsoft-Windows-Client-Language-Pack_x64_sv-se.cab"
• dism.exe /image:%OSDTargetSystemDrive%\ /ScratchDir:%OSDTargetSystemDrive%\Windows\Temp /Add-Package /PackagePath:"Microsoft-Windows-Client-Language-Pack_x64_sv-se.cab"
• dism.exe /image:%OSDTargetSystemDrive%\ /ScratchDir:%OSDTargetSystemDrive%\Windows\Temp /Add-Package /PackagePath:Microsoft-Windows-Client-Language-Pack_x64_sv-se.cab

... And they all seem to work fine. SMSTS is not complaining that the cab-file cannot be found etc, I can actually follow the installation in real time during imaging, and I see the installation exiting with 0.

I have also tried:
• Tried to "re-install" the appxpackage for Immersive ControlPanel
• Tried to rename C:\Windows\ImmersiveControlPanel into something else and ran SFC
• Tried to go into the registry, some key in HKCU called ImmersiveControlPanel and deleted it, rebooted. The key came back, and it didn't change anything.

Any help, tips or brainstorming is very appreciated. Kind regards and have a lovely 2023.

Hello, and welcome to the forum. From what you have done trying to fix this, it appears you are a more advanced user than me. Here's my take and it's brainstorming rather than help as I do not have an enterprise version to compare with yours and I have to admit the foreign language is throwing me off a bit. I have Pro version same build as yours.

If, after a clean install and applying all updates, the immersive control panel appears correctly, it would appear that one of the updates you applied fixed a known issue with Enterprise.

You can investigate further by looking at the updates applied after install. Start>settings>system>windows update>update history. Note the KB update #. Do a simple web search of the KB # and you get something like this from the MS Support site. December 13, 2022—KB5021255 (OS Build 22621.963) - Microsoft Support You can look at the improvements and the known issues with that particular update to see if it will lead you to a reason why this is happening.

The rule for DISM integrating LP's hasn't changed in years:
Always install all languages packs, before applying any Windows CU updates. Otherwise you'll have to reinstall the CU again.

Add languages to Windows images

If you added an update package (LCU) to your image prior to adding languages, reinstall the update package to ensure all of the language resources for the update are in your image. See Add updates to a Windows image for more information.

Click to expand...

glasskuter said:

Hello, and welcome to the forum. From what you have done trying to fix this, it appears you are a more advanced user than me. Here's my take and it's brainstorming rather than help as I do not have an enterprise version to compare with yours and I have to admit the foreign language is throwing me off a bit. I have Pro version same build as yours.

If, after a clean install and applying all updates, the immersive control panel appears correctly, it would appear that one of the updates you applied fixed a known issue with Enterprise.

You can investigate further by looking at the updates applied after install. Start>settings>system>windows update>update history. Note the KB update #. Do a simple web search of the KB # and you get something like this from the MS Support site. December 13, 2022—KB5021255 (OS Build 22621.963) - Microsoft Support You can look at the improvements and the known issues with that particular update to see if it will lead you to a reason why this is happening.

Click to expand...

Thank you for your reply.

garlin said:

The rule for DISM integrating LP's hasn't changed in years:
Always install all languages packs, before applying any Windows CU updates. Otherwise you'll have to reinstall the CU again.

Add languages to Windows images

Click to expand...

This sounds spot-on. I will try it right now. Thank you so much.

garlin said:

The rule for DISM integrating LP's hasn't changed in years:
Always install all languages packs, before applying any Windows CU updates. Otherwise you'll have to reinstall the CU again.

Add languages to Windows images

Click to expand...

Hi once again, thank you for sharing this knowledge. This sounds like something that I need to remember forever, since as you mentioned, integrating LP's with DISM works the way it does. I want to report that after following your advice, the problem was solved.

So what I think happened is:
1. I extracted the correct index from a WIM
2. Injected that WIM with CU
3. Injected that WIM with LP
4. Put the WIM in a TS to output a custom WIM
5. Imaged a machine and noticed the error, created this thread

--- Back to square one ---

What I did now:
1. I extracted the correct index from a WIM
2. Injected that WIM with LP
3. Injected that WIM with CU
4. Same as the other step 4
5. Imaged a machine and it looks flawless

Again, thanks for such quick help. I learned a lot and you've saved me a lot of headache.

This rule for correct install order is why Windows is moving to LXP (Language Experience Packs), to replace LP (Language Packs).
LXP's add language support through UWP (or Store) apps, instead of requiring formal LP integration. This method has benefits and drawbacks.

Pros:
- LXP's can be downloaded from Store on any W10/11 system, separately from the installed CU or LP's
- LXP's can be updated, via WU without user help
- LXP's are available for less popular languages, not supported by LP

Cons:
- LXP's can be broken by the normal UWP headaches you see with other desktop apps
- LP's cover all aspects of Windows localization, LXP's leave some parts untranslated

Professionals can still integrate LP's for the provided languages, but they have to follow the install rules. Normal users can install local languages themselves from the Store app, and not worry about rules. In the end, it's about your preference.