Without this driver, a "no drives were found" error often occurs during a clean installation of Windows 10 or 11 on newer Intel platforms. Key Feature: Storage Drive Visibility The primary function of this driver package is to provide Intel Volume Management Device (VMD) support during the initial boot phase of a Windows setup. Enables Drive Detection
Essential for 11th, 12th, 13th, and 14th Gen Intel processors to detect drives during OS deployment.
dism /Unmount-Image /MountDir:"C:\mount" /Commit F6flpy-x64 -intel-R- Vmd-.zip 12th Gen
| Property | Description | | --- | --- | | | F6flpy-x64-intel-Vmd.zip | | Target Architecture | x86-64 (64-bit) | | Supported Chipsets | Intel 600 and 700 series chipsets (Z690, H670, B660, Z790, etc.) | | Processor Generation | 12th Gen Intel Core (Alder Lake) and newer (13th/14th Gen often use similar VMD drivers) | | Deployment Method | F6 during Windows text-mode setup | | Driver Contents | iaStorVD.sys , iaStorAC.sys , TxtSetup.oem , inf files (e.g., iaStorVD.inf ) |
It is compatible with Windows 10 x64 and Windows 11 21H2/22H2/24H2. 🚀 How to Use It Without this driver, a "no drives were found"
If you try to install a fresh retail copy of Windows from a standard USB drive on an Alder Lake platform, you will likely hit a wall: a completely blank list where your Solid State Drive (SSD) should be. The drive isn't broken or missing; Windows simply lacks the out-of-the-box driver needed to see through Intel’s technology.
The Windows installer sees no drive because the NVMe controller is "hidden" behind the VMD bridge. The Windows installer sees no drive because the
Linux does not require this driver. The Linux kernel has native VMD support via the vmd module. However, some distributions (like older Ubuntu LTS) may need the kernel boot parameter pci=realloc .