Your BIOS can see the NVMe drive. Windows Setup cannot. That gap is a setting, not a fault
If your motherboard lists the NVMe drive in the BIOS and the Windows installer still says it cannot find any drives, the drive is not missing and it is not broken. On an Intel board it is most likely sitting behind the Intel Volume Management Device controller, and Windows Setup has no driver for that controller until you give it one. You have two ways forward: load the Intel Rapid Storage Technology driver during setup, or switch the VMD controller off in the BIOS. The first keeps the RAID capability, the second gives it up. Both are decisions to make before Windows is installed, not after.
Three different problems get described as "my drive is not showing up", and they have almost nothing in common. Before you change a BIOS setting, work out which one you have, because two of the three are covered on a different page.
| The BIOS does not list the drive either | The board has not found it. Nothing on this page will help. Go to M.2 SSD not detected in the BIOS — the usual causes are slot keying and lane sharing. |
| The BIOS lists it, but Windows Setup shows an empty drive list | This page. The board found the drive and handed it to a controller the installer cannot read. |
| The BIOS lists it, Windows is installed and running, but it is absent from File Explorer | Usually an uninitialised disk rather than a firmware setting. See in BIOS but not File Explorer. |
The distinction that matters here is the first one. If the drive appears in the BIOS, the motherboard, the slot, the keying and the lanes have all already done their job. Whatever is wrong happens later, inside the Windows installer, and it is a driver problem rather than a hardware one.
Intel describes the technology in one sentence: "Intel® VMD is the new way to configure 11th Generation and greater Intel® Core™ Processor-based platforms for Intel® RST management of RAID and Intel® Optane™ memory volumes." It is the mechanism by which the platform hands your NVMe drives to Intel Rapid Storage Technology rather than presenting them individually.
That is useful if you want a RAID array. It is also the reason the installer comes back empty, and Intel says why in equally plain terms: "The VMD driver will need to be installed to detect the drives being managed by Intel® RST under the Intel® VMD Controller."
So the drive is not hidden by a fault. It is behind a controller, and Windows Setup does not ship with the driver for it. Intel adds two constraints worth knowing before you start: the driver has to be a recent one — "The Intel® Rapid Storage Technology (Intel® RST) driver version 18.0 and later support Intel® Volume Management Device (Intel® VMD) technology capable platforms" — and the install has to be a UEFI one, since "Intel® RST functionality requires a UEFI OS installation."
Intel warns against reading capability off marketing: "Platforms that are noted as Intel® Optane™ Memory Ready on a sticker or vendor site do not necessarily mean they support Intel® VMD or the proper BIOS described in this guide." Whether your board exposes a VMD menu is a question for your own BIOS and your own manual, not for a badge on the box.
ASUS documents both routes for exactly this symptom, and they are genuinely alternatives — you do one or the other, not both.
This keeps VMD enabled and hands Windows Setup what it is missing. ASUS states the requirement up front: "For the Intel CPU platform, you need to manually install Intel Rapid Storage Technology (IRST) driver during the Windows installation process." The driver comes from your own board's support page — ASUS says to "download the Intel Rapid Storage Technology (IRST) driver from the Chipset category" — and it has to be extracted onto the USB stick before you start, because the machine you are fixing has no working operating system to download it with.
From there the steps are short. ASUS: "Connect the USB flash drive containing the Windows 11/10 installation media and the extracted Intel Rapid Storage Technology (IRST) driver". Then, at the point the install stalls, "When you see the screen 'Where do you want to install Windows' and Windows cannot find any drives, please click [Load driver]", "select the [RST] folder", and "Select [Intel RST VMD Controller], and then click [Next]".
If your download does not lay itself out as a folder called RST, Intel names the file to look for instead: "Browse to the location of the iaStorVD.sys file", which "should be under ../Drivers/VMD/ within the driver files copied in the USB key media."
Intel also notes one step after the install finishes: "Once the system boots into the OS, install the SetupRST.exe file downloaded in Step 1." That is what gives you the management application rather than just the boot-time driver.
The alternative is to stop the platform handing the drives to RST in the first place, which makes them ordinary NVMe drives the installer can see unaided. ASUS heads this section "Disable Intel Volume Management Device (VMD) technology" and states the cost in one line: "Disable VMD technology will make your device can't utilize RAID Array."
That is the whole trade. For a single-drive build with no interest in RAID, turning VMD off is the shorter path and costs you a feature you were not going to use. If you want a RAID array, or you are managing an Intel Optane memory volume, route one is the one that keeps it.
Intel is explicit that the VMD driver is not optional housekeeping once Windows is running on it: "The Intel® RST VMD driver should not be uninstalled/removed after installation." The consequence it names is not a minor one — "This could result in an Inaccessible Boot Device blue screen and potential data loss." Intel also notes that "The VMD device is always enabled on a platform where VMD device is deployed", and that "There is a possible configuration where VMD does not own any device", which is why it recommends installing the driver on such a platform regardless, "to avoid a yellow bang device in Window's Device Manager".
The storage mode is an install-time decision. Flipping it under a Windows that is already on the drive is the most common way readers turn a working-but-annoying machine into one that will not boot at all.
Intel documents the equivalent case on the older SATA-mode setting in language that leaves no room: "The operating system was previously installed with the 'SATA mode' in AHCI, and now the system will not boot if this is changed to Intel RST or RAID mode." Its instruction is to get the mode right first — "The 'SATA mode' in BIOS must be set to Intel RST/RAID mode before installing the operating system" — because "The Intel RST driver is not compatible with AHCI mode."
Those two sentences are about the SATA-mode option rather than about VMD, and we are not going to claim they describe the VMD setting as well, because Intel does not say so. But the shape of the problem is the same on both settings, and Intel's own VMD warning above — an Inaccessible Boot Device blue screen when the driver stops being there — points the same way. If Windows is already installed and working, the safe answer is to leave the storage mode where it is.
Everything on this page is aimed at the moment before the operating system exists. If you are mid-install and the drive list is empty, both routes are open to you at no cost. That stops being true as soon as Windows is on the disk.
ASUS publishes two routes to the same option, depending on which firmware interface your board presents.
In the standard UEFI interface, ASUS's steps are to "Go to [Advanced] screen, and then select [VMD setup menu]", then "Select [Enable VMD controller], and then select [Disabled]", and finally "Click [Ok] to disable Intel Volume Management Device (VMD) technology."
On boards presenting the MyASUS in UEFI interface, the route in is different but the destination is the same: "press Hotkey[F7], or use the cursor to click [Advanced Settings]", then "select [VMD setup menu]", then "Select [Enable VMD controller], and then select [Disabled]".
Note that the same Enable VMD controller entry is what you would set the other way if you were configuring the platform for RST rather than escaping it. Intel's setup guide describes that direction as three things to do in the firmware: "Enable the VMD controller", "Enable the available storage ports that contain the devices to be managed by the Intel® RST driver", and "Select SATA Controller to enable this to be managed by the Intel® VMD controller."
The Advanced screen, the VMD setup menu page, the Enable VMD controller entry and the F7 route into Advanced Settings are all ASUS's names, quoted from ASUS's own support article. MSI, GIGABYTE and ASRock each lay their firmware out differently and use their own wording for the storage-mode option. We could not source those names from those vendors, so we have not guessed at them — on a non-ASUS board, look for a VMD, RAID or SATA-mode entry in the equivalent advanced or storage section, and take the key names from the prompts your own BIOS prints on screen. This is the same limit we state on our onboard audio guide, and for the same reason.
ASUS's article carries one sentence that would change the advice above if it applies to your board, and we are reproducing it exactly rather than summarising it: "For Intel 15th generation (Lunar Lake Core Ultra) series processors or newer platforms, Windows now utilizes the native NVMe storage architecture, and manual installation of the IRST driver is no longer required."
Two things about that sentence are worth stating plainly, because getting them wrong is expensive on a page people follow during an install.
The practical version: do not assume the driver step has gone away. If you are on a recent Intel platform and the drive list is populated, nothing on this page is your problem. If it is empty, the two routes above still work, and route one costs you a five-minute download rather than an argument about which generation you are on.
Intel scopes VMD to its own silicon — "11th Generation and greater Intel® Core™ Processor-based platforms" — so none of it reaches an AMD board. Most of the boards we review are AM5 or AM4, and on those there is no VMD controller, no IRST driver to load during setup, and no menu entry matching the ones quoted above.
That leaves an obvious question we cannot answer here. An AMD builder who reaches "no drives were found" in the Windows installer is in a real situation, and it is a different one. We could not source a procedure for it: amd.com did not respond on three fetch attempts across two working sessions, and we are not going to describe an AMD storage driver, a menu path or a RAID mode from memory on a page whose entire purpose is to be checked against.
So this page is Intel-side, and says so. If you are on AM4 or AM5 and the installer shows no drives, the useful next step is to confirm the board itself has found the drive — our M.2 SSD not detected guide covers the board-side causes, and if the BIOS does not list the drive either, that is where the answer is.
Every quoted sentence on this page comes from the three vendor and platform documents linked below, read on 10 September 2026. Nothing here is a test result: no board was booted, no Windows installation was run, no BIOS menu was opened and no driver was loaded. The BIOS menu names are ASUS's, on the boards ASUS used to illustrate its article, and are reproduced as examples rather than as rules that hold across vendors. We could not source the MSI, GIGABYTE or ASRock wording for the equivalent setting, any Windows version number for the native-NVMe claim, whether that claim covers the desktop LGA 1851 boards we review, or any AMD-side procedure — so this page states none of those four.
[Load driver] and [Intel RST VMD Controller] steps, the cost of disabling VMD, both UEFI routes to the VMD setup menu, and the Intel 15th generation native-NVMe sentenceiaStorVD.sys path, the firmware enable steps, the Optane-sticker caveat, and the warning against removing the driverPublished 10 September 2026. All vendor and platform documentation quoted above was read on 10 September 2026.