Unable to run oobe or msoobe on clean Win 11 install

x509 · Apr 13, 2023

I'm trying to do a clean Win 11 install, completely clean of all the accumulated Windows 10 cruft from my old Wkindows. So the first thing I did with the Win 11 USB installer was wipe the drive clean. Then I started to do a clean install, and got as far as the screen "Let's connect you to a network." But I don't want to connect to a network. I have fresh, latest version drivers that i want to install BEFORE connecting to the web. When I was doing Win 10 installs, this was not an issue.

If it matters, I'm trying to install Win 11 on a system that already has a digital license for Win 10 Pro 64.

This tutorial Custom Install Windows 11 Tutorial says to use oobe \bypassnro or msoobe \bypassnro.

If you don't have an Internet connection and none of the above worked for you, then press the Shift + F10 keys to open a command prompt. Copy and paste the OOBE\BYPASSNRO command into the command prompt, and press Enter. This will restart the computer, and take you back to step 15. You should then be able to click/tap on I don't have internet when you get back to this step, and go to step 23D to set up a local account. (see bottom screenshot)

If the OOBE\BYPASSNRO command doesn't work for you, then copy and paste the MSOOBE\BYPASSNRO command into the command prompt, and press Enter. This will restart the computer, and take you back to step 15. You should then be able to click/tap on I don't have internet when you get back to this step, and go to step 23D to set up a local account. (see bottom screenshot)

However, neither command was recognized. Even plain oobe or msoobe was not recognized. What do I do now?

I'm posting this thread from a system still running Win 10 Pro.

Try3 · Apr 13, 2023

So run a Dir command to check what the subfolders are called.
You should be in Windows\System32 and one of its subfolders contains the file bypassnro.cmd
OOBE used to be the only known subfolder containing bypassnro.
Then an HP user reported the subfolder MSOOBE contained bypassnro.
Perhaps there are more variations - just find the subfolder containing bypassnro.

And do please report back with what you find. I'm getting a new laptop next week and hope to benefit from your investigation when I'm in the OOBE stage.

Best of luck,
Denis

NavyLCDR · Apr 13, 2023

x509 said:
I'm trying to do a clean Win 11 install, completely clean of all the accumulated Windows 10 cruft from my old Wkindows. So the first thing I did with the Win 11 USB installer was wipe the drive clean. Then I started to do a clean install, and got as far as the screen "Let's connect you to a network." But I don't want to connect to a network. I have fresh, latest version drivers that i want to install BEFORE connecting to the web. When I was doing Win 10 installs, this was not an issue.

Use Audit Mode.

Boot Windows to Audit Mode or OOBE

learn.microsoft.com

cineman195 · Apr 13, 2023

Probably you should have used Rufus to write the USB that bypasses all those quirks !

x509 · Apr 13, 2023

cineman195 said:
Probably you should have used Rufus to write the USB that bypasses all those quirks !

How so? I had no problem with booting from the USB for installing Win 11. And for Win 10 never again problems either.

kgarrett67 · Apr 13, 2023

Try3 said:
So run a Dir command to check what the subfolders are called.
You should be in Windows\System32 and one of its subfolders contains the file bypassnro.cmd
OOBE used to be the only known subfolder containing bypassnro.
Then an HP user reported the subfolder MSOOBE contained bypassnro.
Perhaps there are more variations - just find the subfolder containing bypassnro.

And do please report back with what you find. I'm getting a new laptop next week and hope to benefit from your investigation when I'm in the OOBE stage.

Best of luck,
Denis

Oddly, I did a clean install on a Dell XPS laptop with the Tuesday's update and was prepared to use oobe/bypassnro, but upon arriving at the screen to Shift + F10, the option was available to opt that I did not have internet.

x509 · Apr 14, 2023

Try3 said:
So run a Dir command to check what the subfolders are called.
You should be in Windows\System32 and one of its subfolders contains the file bypassnro.cmd
OOBE used to be the only known subfolder containing bypassnro.
Then an HP user reported the subfolder MSOOBE contained bypassnro.
Perhaps there are more variations - just find the subfolder containing bypassnro.

And do please report back with what you find. I'm getting a new laptop next week and hope to benefit from your investigation when I'm in the OOBE stage.

Best of luck,
Denis

@Try3

the good news and the bad news. The Good News is that there is an oobe subdirectory in Windows\System32, with an msoobe executable.

The Bad News is that running this program with the \bypassnro option did not accomplish anything useful. To be clear, I wasn't connected to the web. what I got was a spinning circle for over 10 minutes. So I rebooted. Windows wanted me to log into account default0, but that login required a password. What password?

So I had to reinstall yet once more and try @NavyLCDR suggestion for Audit Mode, which did work.

x509 · Apr 14, 2023

NavyLCDR said:
Use Audit Mode.

Boot Windows to Audit Mode or OOBE

Boot Windows to Audit Mode or OOBE

learn.microsoft.com

Yeah, that worked.

NavyLCDR · Apr 14, 2023

x509 said:
Yeah, that worked.

Of course audit mode worked. But what you were initially looking for is the BypassNRO.cmd located in the C:\Windows\System32\oobe folder:

idgat · Apr 14, 2023

x509 said:
How so? I had no problem with booting from the USB for installing Win 11. And for Win 10 never again problems either.

x509 said:
But I hafta wonder. Why is Microsoft making a Win 11 clean install such a pain in the tuchus? Win 10 clean install was very straightforward.

Huh ???

Post 1 : Win 11 good, Win 10 bad

Post 2 : Win 10 good, Win 11 bad

(with apologies to George Orwell)

Try3 · Apr 14, 2023

x509 said:
The Bad News is that running this program with the \bypassnro option did not accomplish anything useful.

What did you type in as your command?
oobe\bypassnro - is correct
oobe \bypassnro- is wrong

All the best,
Denis

Try3 · Apr 14, 2023

kgarrett67 said:
upon arriving at the screen to Shift + F10, the option was available to opt that I did not have internet.

Did you take a screenshot or photo by any chance?
I have not heard of the option you mentioned.

Denis

idgat · Apr 26, 2023

Probably could add this comment to any number of threads on this topic, but this was the first one that came up in a search ...

Tks for this solution. Worked a treat and solved my problem.

As another contributor suggested, I always use a Rufus USB set to bypass/ignore every obstacle that MS tries to put in place for a clean install, whether on a "compliant" device or a "non-compliant" device.

This time, I decided to try that good ole fashion original method using a boot USB newly created with Windows Media Creation Tool ({sniff} {sniff} pure nostalgia, haven't done this for ages {sniff} {sniff}), and of course I struck the you-must-have-an-MS account brickwall. I reverted to the former practice of Shift+F10 > cmd window > taskmgr > enter > look for the network etc entry in running processes > end task. Damn and blast if MS hasn't stopped that. Now a continuous loop of : you've lost the internet > try again > shift+f10 etc > you've lost the internet > try again > loop-de-loop adinfinitum

Then I remembered seeing something about oobe, searched, found this thread, bingo! Gotcha ... User 1 MS 0. Note there is a post above that refers to the command as oobe{space}\nopassnro. That didn't work but the same command without the space nailed it!!
(EDIT : Oops, just read @Try3 post above. Sorry for duplication)

Bree · Apr 26, 2023

x509 said:
The Good News is that there is an oobe subdirectory in Windows\System32, with an msoobe executable.

The Bad News is that running this program with the \bypassnro option did not accomplish anything useful.

You do not run msoobe.exe, you run a .cmd script in the OOBE folder called BypassNRO.cmd.

fg2001gf11F · Tuesday at 5:07 PM

I just used oobe\bypassnro on a clean install of Build 26200.5001 with no internet connection and it still worked and let me use a local account instead of a MS Account.

if connected to the internet, using a fake email address to bypass the MS account requirement is not working anymore.

After getting the message "oops something went wrong" and pressing next it still asks for a valid MS Account or to create a new MS Account.
Looks like they closed one more door for bypassing the requirement.
The only way around was by disconnecting from the network, press Shift + F10 and then entering the command oobe\bypassnro.
No idea if MS plans to get rid of that option too. Still worked for now.

I hope that installing without internet option will remain available.

hsehestedt · 2024-04-24T01:06:47-0400

As usual, there are so many ways to skin a cat. If you absolutely do not want to connect to a network and you want to create a local user account only, another super easy way to do so is to create a simple unattended answer file (autounattend.xml). While there are many ways to configure such an answer file, there are two main configurations that I use:

1) Fully unattended. As the name implies, this type of answer file results in a 100% unattended installation. Boot your system from this media and come back in a little while. When you return you will find that Windows has been completely installed from start to finish with no input from you. Networking is disabled and a local account only has been created, no Microsoft account has been created.

2) Going the opposite direction, you can create an answer file that does the opposite - the installation is 100% manual, requiring the same user interaction as a manual installation EXCEPT that the answer file automatically bypasses the need for having the network enabled and it will create a local user account for you automatically. Other than this, the user is still guided through the setup just as with any manual installation.

Another reason that I like using answer files to install Windows is the complete versatility. I can automate parts of the installation while leaving other parts manual. I can customize just about every aspect of the installation. It also saves an amazing amount of time.

fg2001gf11F · 2024-04-24T02:06:45-0400

hsehestedt said:
As usual, there are so many ways to skin a cat. If you absolutely do not want to connect to a network and you want to create a local user account only, another super easy way to do so is to create a simple unattended answer file (autounattend.xml). While there are many ways to configure such an answer file, there are two main configurations that I use:

1) Fully unattended. As the name implies, this type of answer file results in a 100% unattended installation. Boot your system from this media and come back in a little while. When you return you will find that Windows has been completely installed from start to finish with no input from you. Networking is disabled and a local account only has been created, no Microsoft account has been created.

2) Going the opposite direction, you can create an answer file that does the opposite - the installation is 100% manual, requiring the same user interaction as a manual installation EXCEPT that the answer file automatically bypasses the need for having the network enabled and it will create a local user account for you automatically. Other than this, the user is still guided through the setup just as with any manual installation.

Another reason that I like using answer files to install Windows is the complete versatility. I can automate parts of the installation while leaving other parts manual. I can customize just about every aspect of the installation. It also saves an amazing amount of time.

It may help if you could provide the exact procedure and a sample of the answer file for the fully unattended install.
Every new Build sems to need a different procedure to bypass the obstacles.

hsehestedt · 2024-04-25T02:53:31-0400

fg2001gf11F said:
It may help if you could provide the exact procedure and a sample of the answer file for the fully unattended install.
Every new Build sems to need a different procedure to bypass the obstacles.

I'll follow-up with some samples tomorrow (Thursday).

hsehestedt · 2024-04-25T15:13:47-0400

I create my Answer Files following the steps outlined by @Kari in this tutorial:

Create media for automated unattended install of Windows 10

Once I have an answer file, if I am only making minor modifications, I will simply edit the file directly since it is simply a text file. However, for anyone not terribly familiar with answer files, you might want to load it into the Windows SIM as Kari instructs in the tutorial I linked to above.

Below are several sample answer files (as requested). I give a brief summary of each answer file prior to the file posting, but the comments within each answer file have a lot more detail.

This first answer file is FULLY UNATTENDED. It will wipe disk 0 when media with this answer file is booted without asking you are prompting you in any way. Be careful with this one!.

XML:

<?xml version="1.0" encoding="utf-8"?>
<!--
************
* WARNING! *
************

This answer file will cause Windows setup to WIPE disk 0 without any warning and to begin installation
to that disk. Change the disk number if installing to a disk other than disk 0.

******************
* END OF WARNING *
******************

Notes about this answer file:

It includes a Windows 10 / 11 Pro key.

It will install Windows to Disk 0.

It creates an Admin level user named "WinUser", full name "Windows User" with an initial password of "Password1".

Locale settings are set to United States English.

Time zone is set to US Central Time. Change this if needed.

It includes settings to bypass Windows 11 system requirements.

The size of the Recovery Tools partition created by this answer will be larger than normal at 2 GB. Change this if you are very short on space or prefer a smaller Recovery Tools partition.

This answer file can be used with both Windows 10 and 11. The settings to bypass
Windows 11 system requirement checks will have no effect on Windows 10.

END OF NOTES
-->
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-International-Core-WinPE" 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">
            <SetupUILanguage>
                <UILanguage>en-US</UILanguage>
            </SetupUILanguage>
            <InputLocale>en-US</InputLocale>
            <SystemLocale>en-US</SystemLocale>
            <UILanguage>en-US</UILanguage>
            <UILanguageFallback>en-US</UILanguageFallback>
            <UserLocale>en-US</UserLocale>
        </component>
        <component name="Microsoft-Windows-Setup" 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">
            <ImageInstall>
                <OSImage>
                    <InstallTo>
                        <DiskID>0</DiskID>
                        <PartitionID>4</PartitionID>
                    </InstallTo>
                    <!--
Below you will find 6 lines that are commented out. These lines will allow you to specify a specific Windows edition to install
in those case where your Windows image has more than one of the same edition. As an example, suppose that you have more than
one Windows Pro edition. Maybe one of these is a standard Windows Pro edition, and another has Windows Pro with drivers added
for use in a specific system. If you are specifying a generic Windows Pro key for installation, setup will pause and expect
you to specify which Windows Pro edition to install since there is more than one. By uncommenting the section below, you
are telling setup exactly which one of these to install. Make sure to update the index value to the correct value for
your situation. You can ignore this if you are using a standard retail Windows installation media.

Note that you can also change the value for "key"  to /IMAGE/NAME or /IMAGE/DESCRIPTION to specify the edition to be
installed by NAME or DESCRIPTION rather than by index number.
-->
                    <!--
                    <InstallFrom>
                        <MetaData wcm:action="add">
                            <Key>/IMAGE/INDEX</Key>
                            <Value>6</Value>
                        </MetaData>
                    </InstallFrom>
-->
                </OSImage>
            </ImageInstall>
            <UserData>
                <ProductKey>
                    <Key>VK7JG-NPHTM-C97JM-9MPGT-3V66T</Key>
                </ProductKey>
                <AcceptEula>true</AcceptEula>
            </UserData>
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>2</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>3</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>4</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
            <DiskConfiguration>
                <Disk wcm:action="add">
                    <CreatePartitions>
                        <CreatePartition wcm:action="add">
                            <Order>1</Order>
                            <Size>2048</Size>
                            <Type>Primary</Type>
                        </CreatePartition>
                        <CreatePartition wcm:action="add">
                            <Order>2</Order>
                            <Size>260</Size>
                            <Type>EFI</Type>
                        </CreatePartition>
                        <CreatePartition wcm:action="add">
                            <Order>3</Order>
                            <Size>128</Size>
                            <Type>MSR</Type>
                        </CreatePartition>
                        <CreatePartition wcm:action="add">
                            <Extend>true</Extend>
                            <Order>4</Order>
                            <Type>Primary</Type>
                        </CreatePartition>
                    </CreatePartitions>
                    <ModifyPartitions>
                        <ModifyPartition wcm:action="add">
                            <Format>NTFS</Format>
                            <Label>WinRE</Label>
                            <Order>1</Order>
                            <PartitionID>1</PartitionID>
                            <TypeID>DE94BBA4-06D1-4D40-A16A-BFD50179D6AC</TypeID>
                        </ModifyPartition>
                        <ModifyPartition wcm:action="add">
                            <Format>FAT32</Format>
                            <Label>System</Label>
                            <Order>2</Order>
                            <PartitionID>2</PartitionID>
                        </ModifyPartition>
                        <ModifyPartition wcm:action="add">
                            <Order>3</Order>
                            <PartitionID>3</PartitionID>
                        </ModifyPartition>
                        <ModifyPartition wcm:action="add">
                            <Format>NTFS</Format>
                            <Label>Windows</Label>
                            <Letter>C</Letter>
                            <Order>4</Order>
                            <PartitionID>4</PartitionID>
                        </ModifyPartition>
                    </ModifyPartitions>
                    <DiskID>0</DiskID>
                    <WillWipeDisk>true</WillWipeDisk>
                </Disk>
            </DiskConfiguration>
        </component>
    </settings>
    <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>en-US</InputLocale>
            <SystemLocale>en-US</SystemLocale>
            <UILanguage>en-US</UILanguage>
            <UILanguageFallback>en-US</UILanguageFallback>
            <UserLocale>en-US</UserLocale>
        </component>
        <component name="Microsoft-Windows-Shell-Setup" 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">
            <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                <ProtectYourPC>1</ProtectYourPC>
                <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
            </OOBE>
            <UserAccounts>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>UABhAHMAcwB3AG8AcgBkADEAUABhAHMAcwB3AG8AcgBkAA==</Value>
                            <PlainText>false</PlainText>
                        </Password>
                        <DisplayName>Windows User</DisplayName>
                        <Group>Administrators</Group>
                        <Name>WinUser</Name>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
            <TimeZone>Central Standard Time</TimeZone>
            <AutoLogon>
                <Enabled>true</Enabled>
                <LogonCount>1</LogonCount>
                <Username>WinUser</Username>
                <Password>
                    <Value>UABhAHMAcwB3AG8AcgBkADEAUABhAHMAcwB3AG8AcgBkAA==</Value>
                    <PlainText>false</PlainText>
                </Password>
            </AutoLogon>
            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <CommandLine>reg add &quot;HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon&quot; /v AutoLogonCount /t REG_DWORD /d 0 /f</CommandLine>
                    <Order>1</Order>
                </SynchronousCommand>
            </FirstLogonCommands>
        </component>
    </settings>
    <settings pass="specialize">
        <component name="Microsoft-Windows-Shell-Setup" 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">
            <OEMName></OEMName>
            <TimeZone>Central Standard Time</TimeZone>
            <ComputerName></ComputerName>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="catalog://godzilla/data/windows/windows tools and deployment apps/assets and tools for deployment/catalog files for windows sim/windows 11 22h2 catalog files/install_windows 11 pro.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

This next answer file does nothing other than to bypass the Windows 11 system requiremements:

XML:

<?xml version="1.0" encoding="utf-8"?>
<!--
Notes about this answer file:

The purpose of this answer file is to simply bypass the Windows 11 system requirement checks. It does NOT perform
an unattended instalation of Windows.

It includes a Windows 10 / 11 Pro key.

It includes settings to bypass Windows 11 system requirements.

This answer file can be used with both Windows 10 and 11. The settings to bypass Windows 11
system requirement checks will have no effect on Windows 10.

END OF NOTES
-->
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-Setup" 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">
            <ImageInstall>
                <OSImage>
                    <InstallFrom>
                        <Path>\install.wim</Path>
                        <!--
Below you will find 4 lines that are commented out. These lines will allow you to specify a specific Windows edition to install
in those case where your Windows image has more than one of the same edition. As an example, suppose that you have more than
one Windows Pro edition. Maybe one of these is a standard Windows Pro edition, and another has Windows Pro with drivers added
for use in a specific system. If you are specifying a generic Windows Pro key for installation, setup will pause and expect
you to specify which Windows Pro edition to install since there is more than one. By uncommenting the section below, you
are telling setup exactly which one of these to install. Make sure to update the index value to the correct value for
your situation. You can ignore this if you are using a standard retail Windows installation media.

Note that you can also change the value for "key"  to /IMAGE/NAME or /IMAGE/DESCRIPTION to specify the edition to be
installed by NAME or DESCRIPTION rather than by index number.
-->
                        <!--
                        <MetaData wcm:action="add">
                            <Key>/IMAGE/INDEX</Key>
                            <Value>6</Value>
                        </MetaData>
-->
                    </InstallFrom>
                </OSImage>
            </ImageInstall>
            <UserData>
                <ProductKey>
                    <Key>VK7JG-NPHTM-C97JM-9MPGT-3V66T</Key>
                </ProductKey>
                <AcceptEula>true</AcceptEula>
            </UserData>
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>2</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>3</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>4</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="catalog://godzilla/data/windows/windows tools and deployment apps/assets and tools for deployment/catalog files for windows sim/windows 11 22h2 catalog files/install_windows 11 pro.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

This next answer file is just like the last one above except that in addition to bypassing Win 11 requirements, this one will also create a local user account for you automatically.

XML:

<?xml version="1.0" encoding="utf-8"?>
<!--
Notes about this answer file:

The purpose of this answer file is to bypass the Windows 11 system requirement checks, create a local user account, and
eliminate the need for an internet connection during setup. It does NOT perform an unattended installation of Windows.

It includes a Windows 10 / 11 Pro key.

It will create a local user account named "WinUser" with a full name of "Windows User" and a password of "Password1".

This answer file can also be used to setup Windows 10 since the setting to bypass Windows 11 requirement checks will
have no effect upon Windows 10 setup.

END OF NOTES
-->
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-Setup" 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">
            <ImageInstall>
                <OSImage>
                    <InstallFrom>
                        <Path>\install.wim</Path>
                        <!--
Below you will find 4 lines that are commented out. These lines will allow you to specify a specific Windows edition to install
in those case where your Windows image has more than one of the same edition. As an example, suppose that you have more than
one Windows Pro edition. Maybe one of these is a standard Windows Pro edition, and another has Windows Pro with drivers added
for use in a specific system. If you are specifying a generic Windows Pro key for installation, setup will pause and expect
you to specify which Windows Pro edition to install since there is more than one. By uncommenting the section below, you
are telling setup exactly which one of these to install. Make sure to update the index value to the correct value for
your situation. You can ignore this if you are using a standard retail Windows installation media.

Note that you can also change the value for "key"  to /IMAGE/NAME or /IMAGE/DESCRIPTION to specify the edition to be
installed by NAME or DESCRIPTION rather than by index number.
-->
                        <!--
                        <MetaData wcm:action="add">
                            <Key>/IMAGE/INDEX</Key>
                            <Value>6</Value>
                        </MetaData>
-->
                    </InstallFrom>
                </OSImage>
            </ImageInstall>
            <UserData>
                <ProductKey>
                    <Key>VK7JG-NPHTM-C97JM-9MPGT-3V66T</Key>
                </ProductKey>
                <AcceptEula>true</AcceptEula>
            </UserData>
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>2</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>3</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>4</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>
    </settings>
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-Shell-Setup" 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">
            <UserAccounts>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>UABhAHMAcwB3AG8AcgBkADEAUABhAHMAcwB3AG8AcgBkAA==</Value>
                            <PlainText>false</PlainText>
                        </Password>
                        <DisplayName>Windows User</DisplayName>
                        <Group>Administrators</Group>
                        <Name>WinUser</Name>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
            <OOBE>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
                <HideEULAPage>true</HideEULAPage>
                <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                <ProtectYourPC>1</ProtectYourPC>
            </OOBE>
        </component>
    </settings>
</unattend>

Hopefully the above examples give you some ideas. If you have any specific questions related to this, let me know and I will try my best to answer.