Windows 11 OOBE bypass not working - English (International)

CraigR

CraigR

Member
Messages
58
Reaction score
7
I am using the International windows 11 ISO and using the "unattended" part of ntlite to bypass all the questions, However when installing it still is asking me for a language then keyboard layout then wants me to connect to the internet and log in to Microsoft. It's like I'm not even using the bypass. I tried this 3 times to make sure I did not mess things up. TIA for any help.
 

Attachments

Please attach your preset, after removing any user passwords or license key.
 
OOBE is stopping because you didn't select the UI Language. Anything you don't specify in Unattended mode, OOBE has to ask you.

Code: 
        <settings pass="oobeSystem">
                <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                        <InputLocale>0409:00000409</InputLocale>
                        <SystemLocale>en-US</SystemLocale>
                        <UserLocale>en-US</UserLocale>
                </component>
Code: 
        <settings pass="oobeSystem">
                <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                        <InputLocale>0409:00000409</InputLocale>
                        <SystemLocale>en-US</SystemLocale>
                        <UILanguage>en-US</UILanguage>
                        <UILanguageFallback>en-US</UILanguageFallback>
                        <UserLocale>en-US</UserLocale>
                </component>

View attachment 13780

If the BypassNRO setting isn't working, check if it's part of your preset. Which is why I asked for a preset, and not the autounattend.xml.
 
I
CraigR said:
All again.
Click to expand...
It looks like you have applied everything but when putting the modified image into a "for example a thumb drive" you are saying it's not saving the image and going back to vanilla.
 
I create the ISO then burn it to a USB with Rufus like I have done many times. And loading it to a laptop that's what it does.
 
CraigR said:
I create the ISO then burn it to a USB with Rufus like I have done many times. And loading it to a laptop that's what it does.
Click to expand...
When you're using Rufus, do you enable the bypasses for HW requirements or signing up for a MS Account? The way Rufus writes its own unattended file can interfere with the autounattend.xml created by NTLite.
 
garlin said:
When you're using Rufus, do you enable the bypasses for HW requirements or signing up for a MS Account? The way Rufus writes its own unattended file can interfere with the autounattend.xml created by NTLite.
Click to expand...
I just recently tried this any it looks like Rufus did not apply anything that was done in Ntlite iso and just does the vanilla install(with the bypasses however it worked)
 
garlin said:
When you're using Rufus, do you enable the bypasses for HW requirements or signing up for a MS Account? The way Rufus writes its own unattended file can interfere with the autounattend.xml created by NTLite.
Click to expand...
I have tried with and without and get the same results.
 
I did have a look at your pictures
And did notice at something is unclear if you wanted to use

<UILanguage>en-US</UILanguage> or
<UILanguage>en-GB</UILanguage>


it can also bee that you want to use
but under components name="Microsoft-Windows-International-Core-WinPE"
<SetupLanguage>
<UILanguage>en-GB</UILanguage>
</SetupLanguage>



But if you wanted to use UILanguage inside autounattened.xml you want to add this under components name="Microsoft-Windows-International-Core-WinPE"
or components name="Microsoft-Windows-International-Core"


if going only en-GB it shuld look something like this

<InputLocale>0809:00000809</InputLocale>
<SystemLocale>en-GB</SystemLocale>
<UILanguage>en-GB</UILanguage>
<UILanguageFallback>en-GB</UILanguageFallback>
<UserLocale>en-GB</UserLocale>

In one of the images you can also see that UILanguage en-GB is used.

I edit it the way i know it add end use en-us as standard inside "Microsoft-Windows-International-Core"
and "Microsoft-Windows-International-Core-WinPE"

I did take one of my own autounattend.xml that can bee use direct to root to usb-stick but you are free to edit the way you want to Please note that it is adapted for 23H2 and installation to the hard drive is not automatic.

"in the Unattended section, just choose {English - en-001) wherever applicable (system locale)....however, it's a false debloat as stated above by Garlin."

Is your iso file called something similar to this? "Win11_24H2_EnglishInternational_x64.iso"
You may also have used a version N to get fewer pre-installed apps.

I agree to disagree as i have been tested this alot and it does work

it not true that just "three legitimate HW bypasses exist"

all this legitimate HW bypasses exist and do work

I did notice this
Set-WinDefaultInputMethodOverride -InputTip "0409:00000409" #set default keyboard en-US(International)

Can change language from powershell but to make this to work 100% you have to test it out in In all different situations so that nothing unexpected happens
 

Attachments

Last edited:
I want to use en-US. Under Setup UILanguage the only choices are en-GB there is nothing else to pick from. Also in the unattended I manually edited all the en-GB to en-US and still get the same results.
 
There is no en-US option because English International ISO is for UK or Commonwealth countries that speak English. It's an entirely different distribution than the English (US) ISO. Windows is Windows, but each of the separate language versions has a different set of integrated Language Packs and resources.

While you could add English (US) Language Packs to English Int'l, or vice versa... it makes sense to just download the right ISO in the first place.
 
I use that because it does not have all the extra crap they put in the US version. But thanks for your help and advise!
 
CraigR said:
I use that because it does not have all the extra crap they put in the US version. But thanks for your help and advise!
Click to expand...
That's a debunked myth. I have covered this topic on this forum, and on ElevenForum.

https://www.ntlite.com/community/index.php?threads/removing-bloat.4424/post-43047
https://www.ntlite.com/community/index.php?threads/guide-optimized-image.2990/page-21#post-42539
https://www.elevenforum.com/t/local-windows11-clean-install.21588/post-400035

The only effect the "trick" (or bug) does is to inadvertently break your Start Menu so you don't have pinned apps. Otherwise the "missing" apps are still taking up space on your system. You would get the same results if you manually unpinned every app from the Start Menu.

Sorry it's just an illusion. NTLite can do the same thing by removing Content Delivery Manager, and by removing the included Apps.
 
Well ok, now I downloaded a fresh copy of the US version and went through it all from scratch and guess what... the same thing!
 
ChAn said:
I did take one of my own autounattend.xml that can bee use direct to root to usb-stick but you are free to edit the way you want to Please note that it is adapted for 23H2 and installation to the hard drive is not automatic.

"in the Unattended section, just choose {English - en-001) wherever applicable (system locale)....however, it's a false debloat as stated above by Garlin."
Click to expand...
Several of your RunSynchronousCommands for HW bypasses are duplicated in multiple places, and often unnecessary.

For the record:
1. Only three legitimate HW bypasses exist, all others are bogus. It's been proven by a strings check on the Setup DLL's.
BypassTPMCheck, BypassSecureBootCheck & BypassRAMCheck.​
​
HW bypasses don't work outside of the "windowsPE" pass. Copying them to "specialize" is a mistake.​

2. AllowUpgradesWithUnsupportedTPMOrCPU only works if you're running an in-place upgrade on a live Windows system.
It doesn't do anything for a clean install.​
 
You must log in or register to reply here.
Back
Top