If your NVMe SSD does not appear during Windows 11 setup on Intel 11th, 12th, 13th, or 14th Gen systems, Intel Volume Management Device (VMD) is active in the BIOS, obscuring the drive behind a controller that Windows Setup cannot read without extra drivers. You can fix this either by extracting and loading the Intel Rapid Storage Technology (IRST) VMD driver via a USB flash drive during setup, or by disabling the VMD Controller in your motherboard BIOS if you do not use RAID.
The Root Cause: Why Windows 11 Setup Cannot Detect NVMe Drives on Intel Boards
When installing a clean copy of Windows 11 on modern Intel platforms—including Z690, B760, and Z790 chipsets paired with 12th, 13th, or 14th Gen CPUs—the installer often halts at the “Where do you want to install Windows?” screen with an empty drive list. The physical drive is powered and recognized by the motherboard UEFI, yet the Windows Preinstallation Environment (WinPE) detects zero storage devices.
This failure is caused by an architectural layer called Intel Volume Management Device (Intel VMD), integrated into the CPU storage controllers starting with the 11th Generation (Tiger Lake) and continuing through 12th Gen (Alder Lake), 13th Gen (Raptor Lake), and 14th Gen platforms. When enabled by default in motherboard firmware, VMD remaps the PCIe root ports and direct-to-CPU M.2 lanes through the Intel Rapid Storage Technology (IRST) controller stack to aggregate RAID volumes and manage power states.
Standard Windows 10 and Windows 11 retail installation media include generic standard NVMe storage drivers, but they do not bundle the specific Intel RST VMD hardware abstraction driver (iaStorVD.sys). Because the generic Windows storage stack cannot query the drive directly behind the active VMD root bridge, it reports no usable media. Resolving the issue requires either injecting the necessary VMD driver at runtime or disabling the VMD layer entirely to expose the drive directly as a standard PCIe NVMe device.
| Intel CPU Generation | Architecture Code | VMD Driver Baseline | Required Setup Action |
|---|---|---|---|
| 11th Gen Core | Tiger Lake (TGL) | IRST 18.x | Load VMD Driver or Disable VMD in BIOS |
| 12th Gen Core | Alder Lake (ADL) | IRST 19.2.x / 19.5.x | Load VMD Driver or Disable VMD in BIOS |
| 13th Gen Core | Raptor Lake (RPL) | IRST 19.5.x | Load VMD Driver or Disable VMD in BIOS |
| 14th Gen Core | Raptor Lake Refresh / ARL | IRST 19.5.x / 20.x | Load VMD Driver, Disable VMD, or Update BIOS |
| Core Ultra (15th Gen+) | Lunar Lake | Native Architecture | Native Windows 11 24H2 Driver Stack (No IRST required) |
Method 1: Disable Intel VMD in BIOS (Fastest Fix for Single-Drive Systems)
If your desktop PC or laptop operates a single NVMe SSD and you have no intention of running hardware RAID (RAID 0, 1, 5, or 10) across multiple M.2 drives, disabling Intel VMD is the cleanest and most permanent solution. Turning off VMD removes the proprietary abstraction layer, switching the PCIe storage lanes into direct AHCI/NVMe pass-through mode so Windows uses its built-in native NVMe driver.
Disabling Intel VMD does not degrade NVMe read/write throughput or sequential transfer speeds. Standard consumer workloads, gaming, and single-drive OS installations operate with full PCIe bandwidth under the native Windows NVMe driver stack.
- Shut down your computer completely. Power it on and immediately press the BIOS entry key—typically Del or F2 on ASUS, MSI, and Gigabyte motherboards, or F2 / F12 on Dell and HP systems.
- Switch to Advanced Mode by pressing F7 (or clicking the Advanced tab in UEFI).
- Navigate to the Advanced menu, select System Agent (SA) Configuration or Storage Configuration, and open the VMD Setup Menu.
- Locate the option labeled Enable VMD controller (or Intel VMD Technology) and change the setting from Enabled to Disabled.
- If prompted with a confirmation dialog regarding RAID array degradation, click OK. Ensure that the SATA/NVMe operation mode defaults to AHCI.
- Press F10 to save changes and restart the computer. Boot back into your Windows 11 installation media; your NVMe SSD will now display immediately in the partition list.
If you already have an existing operating system installed in an Intel VMD RAID configuration, disabling VMD will render that array inaccessible and cause an INACCESSIBLE_BOOT_DEVICE bugcheck on reboot. Only disable VMD before initiating a clean OS installation or on standalone, non-RAID drives.
Method 2: Extract and Load Intel RST VMD Drivers During Setup
On select laptops (such as certain Dell Inspiron, Latitude, HP Pavilion, and Lenovo models) or high-end desktop configurations utilizing multi-drive RAID, the BIOS firmware may lock the VMD controller setting to “Enabled” without exposing an override toggle. In this scenario, you must provide the unpacked Intel Rapid Storage Technology VMD driver directly to the Windows installer using a secondary folder or separate USB drive.
Extracting the Driver Files
Motherboard vendors and Intel frequently distribute the IRST package as an executable installer (SetupRST.exe or manufacturer .exe), which cannot be run inside the Windows PE setup environment. You must unpack the raw .inf, .sys, and .cat files beforehand.
- On a secondary working PC, download the latest Intel Rapid Storage Technology (IRST) driver package matching your motherboard or CPU generation from the official manufacturer support page (e.g., ASUS, Dell, HP, or Intel Download Center).
- If downloaded as an Intel
SetupRST.exefile, open Windows PowerShell as Administrator in the download folder and execute the command:.\SetupRST.exe -extractdrivers C:\RST_Extracted. - If using a manufacturer-supplied self-extracting archive (such as Dell or ASUS IRST packages), double-click the installer, select the Extract option rather than Install, and direct the output to a temporary directory.
- Copy the resulting extraction directory—specifically the folder containing
iaStorVD.sys,iaStorVD.inf, or thef6vmdflpy-x64/VMDsubfolder—directly onto the root of your bootable Windows 11 installation USB drive (or a second FAT32-formatted flash drive).
Ensure the target USB drive is formatted as FAT32 or NTFS. UEFI setup environments and WinPE cannot reliably read files stored on exFAT or Linux ext4 partitions.
Injecting the Driver During Setup
- Insert your Windows 11 installation USB media into the target machine and boot from it in UEFI mode.
- Proceed through the initial setup screens (Language, Keyboard, “Install Now”) until you reach the screen titled “Where do you want to install Windows?”.
- Click the Load driver icon at the bottom-left of the drive management window, then click Browse.
- Navigate to your USB drive and select the folder containing the extracted IRST files (e.g.,
RST\Drivers\VMDorf6vmdflpy-x64), then click OK. - Select the recognized Intel RST VMD Controller (e.g.,
Intel RST VMD Controller 9A0Bor matching generation identifier) from the list and click Next. If no drivers appear, uncheck the box labeled “Hide drivers that aren’t compatible with this computer’s hardware” to force the enumeration of compatible INF controllers. - Once the driver initializes, the setup wizard will refresh the screen, displaying your unallocated NVMe space and existing partitions ready for Windows 11 installation.
Method 3: Verify UEFI Boot Mode and Motherboard Firmware Compatibility
If disabling VMD or loading drivers fails to reveal your NVMe SSD, verify the low-level firmware settings governing partition tables and platform initialization:
- Enforce Pure UEFI Boot: NVMe storage architecture requires UEFI boot mode. In your BIOS, navigate to the Boot menu, ensure CSM (Compatibility Support Module) or Legacy Boot is disabled, and verify that Boot Option Mode is strictly set to UEFI.
- Wipe Legacy MBR Tables: If the target NVMe SSD was previously formatted with a Master Boot Record (MBR) partition table, modern UEFI installers may reject the target. During Windows Setup, press Shift + F10 to launch Command Prompt, execute
diskpart, runlist diskfollowed byselect disk X(where X is the NVMe SSD), and issue thecleanandconvert gptcommands to enforce standard GPT partitioning. - Update BIOS for 14th Gen Processors: If installing an Intel 14th Gen CPU (such as the i7-14700K or i9-14900K) onto a first-generation Z790 or B760 motherboard shipped with early factory firmware (e.g., BIOS rev F3 or older), the platform may fail to initialize CPU-attached M.2 slots correctly. Flash the motherboard BIOS to the latest vendor revision using the integrated BIOS FlashBack or Q-Flash feature before proceeding.
Frequently Asked Questions
Why does my NVMe SSD show up in the BIOS but disappear in Windows Setup?
Motherboard UEFI firmware communicates directly with hardware buses at the pre-boot level and can detect VMD-managed hardware natively. The Windows 11 installer, however, runs inside a lightweight Windows PE environment that lacks the vendor-specific Intel VMD controller driver (iaStorVD.sys), creating a driver mismatch where the BIOS sees the drive but Windows cannot.
Does disabling Intel VMD cause any performance loss on gaming or productivity PCs?
No. Disabling VMD allows the operating system to interface directly with the solid-state drive via standard PCIe and native Microsoft NVMe controller drivers. Benchmarks show identical sequential and random read/write speeds, IOPS, and latency whether VMD is active or disabled on standalone drives.
Why did I get an Inaccessible Boot Device BSOD after installing Windows with IRST drivers?
This stop code occurs if the second phase of Windows Setup cannot load the matching storage filter driver during the first boot restart. It commonly happens if the driver package loaded during setup was mismatched to the CPU generation (such as loading an 18.x Tiger Lake driver onto a 13th Gen Raptor Lake system) or if the BIOS VMD configuration was modified mid-installation.
Is Intel VMD required if I want to install Linux alongside Windows 11?
Modern Linux kernels support VMD natively; however, dual-boot configurations are significantly more straightforward when Intel VMD is disabled in the BIOS. Operating in pure AHCI/NVMe pass-through mode prevents driver injection conflicts across both operating systems.