Definitive Guide to Installing Windows 11 on NVMe SSD: BIOS Settings & Driver Setup

Root Causes of NVMe Detection and Boot Failures in Windows Setup

Modern NVMe solid-state drives interface directly with system PCIe lanes rather than legacy SATA host controllers. This architecture bypasses traditional AHCI protocol overhead, achieving lower latency and higher sequential throughput across PCIe 4.0 and 5.0 buses. However, this direct connection shifts storage management responsibilities directly to the motherboard UEFI firmware and specific platform storage drivers.

When the Windows 11 installer loads via UEFI media, it queries storage adapters using its inbox driver stack. If the motherboard abstracts the PCIe lanes through a proprietary storage management controller—most notably Intel Volume Management Device (VMD)—the installer cannot see the raw NVMe physical endpoints. The operating system kernel requires an intermediate driver to translate VMD container addressing into addressable logical unit numbers (LUNs).

A secondary failure occurs during bootloader handoff. If firmware boot flags contain legacy BIOS emulation components—such as the Compatibility Support Module (CSM)—the Windows setup engine may write bootloader metadata under legacy Master Boot Record (MBR) assumptions or fail to register an EFI System Partition (ESP) entry within NVRAM. The system will copy installation files successfully, but the motherboard firmware will fail to register “Windows Boot Manager” upon the initial restart cycle.

Pre-Installation UEFI BIOS Configuration

Prior to booting the Windows 11 installation media, you must align motherboard firmware parameters to meet Windows 11 storage and security specifications. Incorrect firmware settings prevent NVMe initialization at the pre-boot execution environment (PXE/UEFI) layer.

1. Disabling the Compatibility Support Module (CSM)

Windows 11 strictly mandates the Unified Extensible Firmware Interface (UEFI) specification. CSM allows legacy operating systems to boot on modern hardware by intercepting INT 13h BIOS interrupts, but it prevents the Windows installer from properly provisioning UEFI-compliant GUID Partition Table (GPT) data structures on NVMe storage.

When CSM is active, firmware interfaces can present NVMe drives under legacy INT 13h emulation. If you install Windows under this hybrid state, setup may fail during the first reboot phase because the motherboard UEFI firmware cannot locate an active master boot code sector on a GPT drive.

1. Power on the system and repeatedly press the BIOS hotkey (typically Del or F2; F11 or F12 for boot menus).
2. Press F7 to switch from Easy/Basic Mode into Advanced Mode.
3. Navigate to the Boot or Security menu tab.
4. Locate CSM (Compatibility Support Module) or Launch CSM and set the value to Disabled.
5. Set Boot Mode Select strictly to UEFI.

2. Secure Boot and Key State Provisioning

Secure Boot verifies the digital signature of the UEFI bootloader (bootmgfw.efi) against keys stored in the motherboard NVRAM. Windows 11 requires Secure Boot capability, though specific factory bare-metal configurations (such as laptops preloaded with FreeDOS) exhibit driver signature conflicts when the Microsoft installer initially mounts storage controllers.

If your system features pre-loaded factory keys, ensure Secure Boot is toggled to Enabled and the Secure Boot Mode is set to Standard. If the system fails to load storage drivers or blocks the initial Windows PE media bootloader, temporarily switch the mode to Custom and select Install Default Secure Boot Keys to restore baseline Microsoft certificates.

3. Intel VMD (Volume Management Device) & SATA Controller Configuration

On Intel 11th Generation (Tiger Lake), 12th Generation (Alder Lake), 13th Generation (Raptor Lake), and 14th Generation (Arrow Lake / Raptor Lake Refresh) platforms, Intel motherboards frequently ship with Intel VMD Technology enabled by default. VMD maps direct CPU PCIe lanes into an internal storage controller to facilitate hardware RAID arrays and Intel Optane caching.

Because the stock Windows 11 installer image lacks modern Intel Rapid Storage Technology (IRST) VMD controllers out of the box, the installer cannot detect raw NVMe drives behind this VMD bridge. You have two operational paths: supply the VMD storage driver during setup, or disable the VMD controller in BIOS entirely.

If you are not deploying a multi-drive hardware RAID array, disabling VMD passes raw NVMe PCIe lanes directly to the operating system kernel, enabling native Microsoft inbox NVMe drivers:

1. In UEFI Advanced Mode, navigate to the Advanced or System Agent (SA) Configuration tab.
2. Select VMD setup menu (or VMD Configuration).
3. Locate Enable VMD controller and set it to Disabled.
4. Under SATA/Storage Configuration, verify the storage controller protocol is set to AHCI rather than RAID or Intel RST Premium.
5. Press F10, select Save & Exit Setup, and confirm with OK.

PCIe Lane Allocation and Motherboard M.2 Slot Topology

NVMe SSD detection can fail at the hardware electrical layer due to PCIe lane bifurcation and chipset lane sharing. Motherboards route M.2 storage slots through two distinct physical topologies: CPU-direct lanes and Chipset-downlink lanes (PCH).

On high-end motherboards (such as the ASUS ProArt X670E Creator WiFi), secondary M.2 slots (such as M.2_3) share trace bandwidth with lower PCIe x16 slots. If a capture card, secondary GPU, or PCIe add-in card occupies the shared PCIe slot, the motherboard multiplexer drops the M.2 slot to PCIe x2 mode or drops controller detection entirely during pre-boot initialization.

Always install your primary NVMe boot SSD in the M.2_1 slot, positioned physically between the CPU socket and the primary PCIe x16 graphics card slot. This ensures direct communication with the CPU memory controller without passing through high-latency chipset bridges or encountering multiplexer drops.

Bypassing “No Drives Were Found”: Driver Extraction and Setup Injection

If hardware RAID is required, if your laptop OEM BIOS hides the VMD toggle (frequent in Acer Nitro, Dell Inspiron, and HP Envy models), or if you are running an Intel 11th–14th Gen platform with VMD retained, you must load the storage controller driver manually during Windows Setup.

Extracting Intel Rapid Storage Technology (IRST) Drivers

Manufacturers distribute storage drivers inside unified setup executables (such as SetupRST.exe or HP SoftPaq sp146929.exe). The Windows 11 setup environment cannot execute standard Win32 .exe installation packages; it strictly reads uncompressed INF, SYS, and CAT driver packages. You must unpack the raw driver payload beforehand.

1. On a secondary functioning PC, download the official Intel Rapid Storage Technology (IRST) Driver package from your motherboard/laptop support portal or Intel’s Download Center.
2. Open PowerShell or Command Prompt with administrative privileges.
3. Navigate to the folder containing the downloaded executable and execute the driver extraction command:
   ./SetupRST.exe -extractdrivers SetupRST_extracted
   (If using an HP SoftPaq like sp146929.exe, execute the program, choose Extract Only, and locate the output inside C:\SWSetup\sp146929\F6).
4. Open your bootable Windows 11 installation flash drive in File Explorer.
5. Create a dedicated directory in the root of the flash drive named Drivers.
6. Copy the extracted driver folder (which contains critical storage manifest files, including iaStorVD.inf and iaStorVD.sys) directly into this Drivers directory.

Loading Storage Drivers in the Windows 11 Setup Environment

Once your USB media contains the raw INF structure, proceed through the setup wizard to inject the driver into the active Windows PE runtime kernel.

1. Insert the Windows 11 installation media into your system and boot from the USB drive via the UEFI boot menu.
2. Select your language, keyboard layout, and time format, then click Install Now.
3. When prompted, accept the license terms and select Custom: Install Windows only (advanced).
4. On the screen titled “Where do you want to install Windows?”, if the list is blank or states “We couldn’t find any drives,” click Load driver in the lower left corner.
5. Click Browse, expand your USB drive, and navigate to the Drivers folder containing your extracted RST files.
6. Select the appropriate controller manifest—specifically Intel RST VMD Controller (or select iaStorVD.inf).
7. Uncheck “Hide drivers that aren’t compatible with this computer’s hardware” if no list populates automatically, select the detected VMD controller, and click Next.

The Windows PE kernel will load the driver directly into memory. The storage bus resets, and your NVMe drive will immediately populate in the disk selection window with its full unallocated capacity.

Disk Geometry Provisioning via Diskpart

Residual partition structures from previous operating system installations, OEM recovery layers, or hybrid MBR formatting frequently corrupt the Windows 11 installation routine. Initializing the disk clean via the diskpart command-line utility ensures strict GPT alignment and eliminates boot sector ambiguity.

1. On the Windows Setup screen (“Where do you want to install Windows?”), press Shift + F10 to open the administrative Command Prompt.
2. Launch the disk management utility by typing:
   diskpart
3. Query all physically attached storage devices:
   list disk
4. Identify your target NVMe drive based on storage capacity (e.g., Disk 0, Disk 1). Select the drive:
   select disk X (replace X with the correct NVMe disk index)
5. Erase all partition tables, dynamic volume metadata, and boot sectors from the selected drive:
   clean
6. Explicitly initialize the disk structure to the GUID Partition Table format:
   convert gpt
7. Exit the diskpart environment and close Command Prompt:
   exit
exit
8. Click Refresh in the Windows Setup window.

Resolving Post-Installation Boot Order & Setup Loops

A frequent point of failure occurs immediately after the Windows installer finishes copying files. The system displays a 10-second countdown and initiates a hardware restart. If the motherboard boot priority retains the USB flash drive as the primary boot target, the system reloads the Windows 11 installation media from scratch, trapping the builder in an installation loop.

1. As soon as the installer reaches 100% on the “Finishing up” phase and triggers the automatic reboot sequence, physically remove the USB installation drive from the computer.
2. Allow the system to complete its POST cycle. The motherboard firmware will pass boot control directly to the NVMe drive’s newly provisioned EFI System Partition.
3. If the system displays “Reboot and Select proper Boot device” or re-enters BIOS automatically, enter the UEFI Setup menu.
4. Navigate to the Boot Priority list.
5. Ensure that Windows Boot Manager (pointing to your NVMe model) is set as Boot Option #1, rather than the raw hardware ID of the NVMe drive.

In a UEFI implementation, the firmware does not boot a raw physical disk sector (LBA 0); it executes an EFI bootloader file located at \EFI\Microsoft\Boot\bootmgfw.efi inside the FAT32 EFI System Partition. Setting the raw SSD as boot priority instead of “Windows Boot Manager” will prevent the system from initializing the Windows boot environment.

Manual Bootloader Reconstruction via BCDBoot

If an installation halts mid-stream (frequently reported at roughly 77% progress on systems with unstable BIOS configurations) or if the motherboard fails to populate “Windows Boot Manager” in the NVRAM boot priority menu, reconstruct the BCD store manually using the installation media recovery environment.

1. Boot into the Windows 11 installation media and press Shift + F10 to open Command Prompt.
2. Launch diskpart and list system volumes:
   diskpart
list volume
3. Locate the 100MB FAT32 EFI System Partition. Assign it an unused drive letter (e.g., V:):
   select volume Y (replace Y with the volume index of the 100MB FAT32 partition)
   assign letter=V
4. Locate the large NTFS primary partition containing the Windows directory and verify its assigned letter (typically C: or D:).
5. Exit diskpart:
   exit
6. Execute the BCD bootloader repair command to rebuild EFI boot files from the Windows directory directly onto the EFI System Partition:
   bcdboot C:\Windows /s V: /f UEFI
   (Ensure C:\ matches the drive letter of your Windows OS volume identified in step 4)
7. Verify the output reports: Boot files successfully created.
8. Restart the machine and enter BIOS to confirm “Windows Boot Manager” is now populated in the UEFI boot options list.

Troubleshooting Stop Errors and Inaccessible Boot Devices

If Windows 11 installs cleanly but crashes during the initial secondary stage boot or following a mandatory Windows Update, the failure stems from storage driver corruption or platform-specific firmware handshakes.

1. Stop Code: INACCESSIBLE_BOOT_DEVICE

The INACCESSIBLE_BOOT_DEVICE bug check indicates the Windows kernel lost I/O communication with the system boot volume during the phase-1 kernel initialization transition. This frequently manifests on systems running Intel VMD when Windows Update forces an incompatible Intel RST driver package (such as RST 20.2.6.1025.2 updating over motherboard vendor package 20.0.0.1038) or when the Windows Recovery Environment (WinRE.wim) driver staging branch corrupts.

If this occurs on an Intel system where VMD is enabled:

1. Reboot into the motherboard UEFI BIOS.
2. Disable the VMD controller entirely under Advanced > VMD setup menu.
3. Save changes and reboot. Disabling VMD forces the kernel to bypass the corrupted VMD filter driver and mount the drive using the native Microsoft PCIe NVMe driver stack.

2. Motherboard-Specific NVMe Controller Incompatibilities

Specific hardware pairings exhibit handshake timeouts during UEFI driver enumeration. On select AMD AM5 motherboards (such as the MSI Pro B650-P WiFi or Gigabyte Gaming B650 X AX V2 running early BIOS revisions), specific DRAM-less or proprietary NVMe controller configurations (e.g., Lexar NM790 with Maxio MAP1602 controllers or Western Digital WD_Black SN770) may fail to register in UEFI mode despite working perfectly as non-boot storage drives in existing Windows environments.

To remediate these controller timeouts:

• Flash the motherboard BIOS to the latest stable vendor release using the manufacturer’s USB Flashback or EZ-Flash utility. Early AM5 BIOS revisions contained known AGESA storage enumeration bugs that failed to initialize PCIe link states on specific third-party NVMe SSDs.
• Update the NVMe SSD controller firmware via the manufacturer’s management dashboard (e.g., Samsung Magician, Western Digital Dashboard, or Crucial Storage Executive) on a secondary working machine before installing the OS.
• If cold-boot detection fails, perform a hardware power cycle: disconnect the power supply cable, depress the chassis power button for 30 seconds to drain motherboard decoupling capacitors, reseat the M.2 SSD firmly at a 30-degree angle, and tighten the M.2 mounting screw to factory specification.

Frequently Asked Questions

Why does my NVMe SSD appear in the BIOS storage list, but the Windows 11 installer says no drives were found?

Your motherboard storage controller is operating in Intel VMD or AMD RAID mode. The BIOS uses its own firmware-level driver to query the drive, but the Windows 11 installation media lacks the necessary intermediate VMD/RAID driver. To resolve this, disable VMD in the BIOS Advanced settings or download the extracted Intel RST driver (iaStorVD.inf) onto your USB drive and select Load driver during setup.

Should I format my NVMe SSD as MBR or GPT for Windows 11?

You must use GPT (GUID Partition Table). Windows 11 requires UEFI and Secure Boot, which cannot boot from an MBR-partitioned drive. If your drive was previously formatted as MBR, boot the installer, press Shift + F10, run diskpart, select your disk, and enter clean followed by convert gpt.

Will disabling Intel VMD reduce my NVMe SSD’s read/write performance?

No. Disabling VMD connects the NVMe SSD directly to the CPU’s PCIe lanes using the native Microsoft NVMe driver stack. Performance remains at the drive’s full rated PCIe 4.0 or PCIe 5.0 specifications. VMD is primarily designed for multi-drive enterprise RAID configurations and legacy Intel Optane memory caching.

Why did my computer enter a loop, asking me to install Windows 11 again after restarting?

The motherboard boot order is still set to prioritize the USB installation flash drive over the newly provisioned internal storage. When the installer finishes its file-copying phase and initiates the first restart, physically remove the USB flash drive from your PC so the system boots into Windows Boot Manager on the NVMe SSD.

What is the difference between selecting “Windows Boot Manager” and the NVMe drive name in the BIOS boot order?

“Windows Boot Manager” points to the validated UEFI bootloader file (bootmgfw.efi) inside the drive’s 100MB FAT32 EFI System Partition. Selecting the raw NVMe drive name attempts a legacy sector-zero boot, which is unsupported on UEFI-only Windows 11 systems and will result in a boot failure.