When I inject local experience packs to my Windows 10 20H2 media and start installation with that media OOBE goes directly to "Select region" screen and does not allow to choose language. What is the trigger for OOBE to prompt for language?
Hello Everyone,
I want to pick up this topic, as I'm facing the same problem and have no clue how to fix that or if there is even a fix and it is just the way it works...
The goal I want to achieve is to install Windows 10 Enterprise with multiple Languages and give the user the possibility to choose the user's preferred language during the OOBE.
To achieve this I did the following:
- download a fresh ISO from VLSC (SW_DVD9_Win_Pro_10_21H2.7_64BIT_English_Pro_Ent_EDU_N_MLF_X23-15141)
- extract the content
- kicked out every image besides "Windows 10 Enterprise" using "Dism /Delete-Image"
- mounted the install.wim
- added the LXP using "Add-AppxProvisionedPackage" (I want to mention that I also tried LP + FOD, and the result was the
same)
- I did not change the lang.ini or anything else
- unmounted the image with the "commit" parameter
- created a bootable USB-stick with rufus and copied the content from the ISO including the edited install.wim to it
- installed Windows 10 from this USB-stick, during the setup I could not choose anything else but EN-US as language, which
was expected as I did not change the lang.ini
- the client boots up and shows the OOBE, but I do not get the option to choose a language, the OOBE goes straight to
"Region"
- with DISM /online /get-intl I checked the installed language and I can see the language I added under "installed languages"
- when I then press F10 and sysprep the very same client, the client restarts and shows the OOBE and I now have the option
to choose a language
Am I missing something? Is that behavior expected? Can I somehow work around that with an unattended.xml to force the OOBE to show the language menu?
Thank you very much in advance for your help!
Best regards,
Daniel
Hello and Welcome Daniel87
Try it with W10MUI:
https://github.com/abbodi1406/WHD/ra...s/W10MUI_20.7z
The package contains a ReadMe file on how to proceed.
Hello,
thank you for your reply. I tried this already, but it didn't work. When I do this I can choose the language during the setup but I still don't have the option to choose the language during OOBE.
What I just don't understand is, that I have the option after I sysprep the client. What is the difference? What does sysprep regarding the language and can I do this automatically somehow?
Best regards,
Daniel
Hello Everyone,
I did some additional testing and want to add some additional information.
I tested many scenarios with LPs and LXPs but never had a satisfying result.
What I found out is that there are different OOBE-Screens:
1. This one I see straight after installing Windows 10 from a USB drive without an unattend.xml. The screen did not change, no matter if, how, or what LPs/LXPs I injected into the install.wim.
2. This OOBE is shown when I sysprep (OOBE, Generalize) the same device. When I add more languages I see all of them in this OOBE.
3. After the same device ran into the known “OOBELANGUAGE” error, I did another yet Sysprep. This time the device came up with yet another OOBE.
This OOBE would be the absolute perfect solution for all “Localization-Problems”. The users can choose everything themselves. This would be perfect in a worldwide operating, multi-lingual company.
Is there any possibility to control/force a certain OOBE?
Quote
