Installation using Media Creation Tool - UEFI issue

Why doesn't Rufus create a Windows installation USB that can be booted in dual BIOS/UEFI mode?
If you are using a Windows ISO that can be dual booted in UEFI or BIOS mode, you may find that the USB
created by Rufus does not preserve the dual UEFI+BIOS boot feature.

Especially, the Windows 8 or later installation ISOs, that support both UEFI and BIOS boot, will be converted
to either one or the other mode, depending on the option you selected under Partition scheme and Target type:
If you select MBR and BIOS or UEFI-CSM, the USB will be bootable in BIOS-mode only (even on UEFI systems),
and if you select GPT then the USB will be bootable in UEFI mode only (and not bootable on a BIOS system at all).

This is done to avoid confusion, as it can be difficult for non-expert users to know whether they actually booted in
UEFI or BIOS mode when a USB Flash Drive can be booted in both modes, and installation is meant to be a one-off
operation, targeting a very specific machine and boot mode. You probably don't want to go through a full Windows
installation, only to realize that it was installed in BIOS mode when all you really wanted was UEFI mode.

By ensuring that only one or the other can be used for Windows installation, there is no room for error with regards to
which mode was used.

Note that this does not apply for Windows To Go and that you can also enable dual UEFI+BIOS boot by using the
Alt-E cheat mode (see below) with Rufus 2.0 or higher. Also, if your UEFI firmware integrates an NTFS driver natively,
then you may also find that you can dual boot a USB created in Rufus, even if only BIOS-CSM was specified.

<?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 installation of Windows.

It includes a Windows 11 Pro key. If you want to install Windows 11 Home, change the key to
YTMG3-N6DKC-DKB77-7M9GH-8HVX7

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>
                    </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>
</unattend>