To resolve missing Intel RAID1 drivers during Windows 11 installation or restoration, you must inject the Intel Rapid Storage Technology (IRST) and Volume Management Device (VMD) drivers into the boot image. This process ensures the setup environment can detect your storage array before the OS loads, preventing "No Drives Found" errors. The solution involves using DISM to integrate these drivers into
boot.wim without requiring signature bypasses that compromise security.
Understanding the Second Stage Boot Process
The Windows installation process is divided into distinct phases. The first stage runs in a minimal WinPE (Windows Preinstallation Environment) loaded from the USB media. During this phase, the installer scans for hardware to determine which drives are available for formatting. If your system uses an Intel CPU with VMD enabled, the standard generic SATA driver does not recognize the RAID controller. Consequently, the second stage of the boot process fails to see the SSDs or HDDs configured in a RAID1 array.
Injecting drivers at this stage is critical because the base operating system files do not include every possible hardware abstraction layer. By modifying the
boot.wim file, you provide the necessary instructions for the PE environment to communicate with the Intel VMD controller. This allows the installer to enumerate the logical drives presented by the RAID metadata. Without this step, users often encounter blank drive lists or error codes indicating missing storage controllers.
Preparing the Driver Files
Before modifying any system images, you need the correct driver package extracted to a local folder. You should download the latest Intel RST driver from the manufacturer’s support page or your motherboard vendor. It is essential to extract the contents rather than running the installer executable. Look for a directory structure containing
.inf,
.sys, and
.cat files. These are the actual components required for injection.
Create a dedicated folder on your desktop, such as
C:\Drivers\IRST, and copy all extracted files there. Ensure the path contains no spaces to avoid command-line parsing errors later. Verify that the driver version matches your hardware generation; newer Intel platforms require specific VMD drivers that older versions cannot handle. Having a clean, organized source directory simplifies the DISM commands and reduces the risk of injecting corrupted or incomplete data.
Injecting Drivers via DISM
The Deployment Image Servicing and Management (DISM) tool is the standard utility for modifying Windows images. You will target the
boot.wim file located in the
\sources folder of your Windows 11 installation media. First, identify the index number of the boot image you wish to modify. Typically, index 1 is for Setup and index 2 is for Recovery. You usually want to modify index 1.
Open Command Prompt as Administrator and navigate to the directory containing your Windows media. Execute the following command to add the driver:
DISM /Image:D:\sources\boot.wim /Add-Driver /Driver:C:\Drivers\IRST /Recurse
Replace
D: with the drive letter of your USB installer and
C:\Drivers\IRST with your actual path. The
/Recurse flag ensures that subdirectories are scanned for compatible drivers. This method respects digital signatures and does not use invalid flags like
/forceunsigned, which would cause the operation to fail on modern secure boot systems. After execution, verify the output indicates success and that the driver was added to the specified image index.
Verifying and Testing
Once the injection is complete, it is prudent to check the image properties to confirm the driver is present. Use the
/Get-Drivers switch to list all injected drivers:
DISM /Image:D:\sources\boot.wim /Get-Drivers /Format:List
Look for entries related to Intel Rapid Storage Technology or VMD. If they appear, the image has been updated correctly. Safely eject the USB drive and reboot your computer. During the installation process, navigate to the drive selection screen. Your RAID1 array should now be visible and selectable. If the drive still does not appear, double-check that VMD is enabled in the BIOS settings and that the driver version corresponds to your chipset.
For additional troubleshooting regarding storage detection issues, refer to our guide on
SSD Not Found During Windows Installation and in BIOS. This resource covers common BIOS configurations that may interfere with driver recognition.
If you are preparing for a fresh installation and need to ensure all other drivers are up to date, consider reviewing
Preparing for a Clean Install of Windows 11. This article provides best practices for maintaining a stable driver environment post-installation.
Frequently Asked Questions
Why does my RAID drive disappear after Windows installs?
The drivers injected into
boot.wim only affect the installation phase. Once the OS is installed, it requires its own set of storage drivers. You must install the full Intel RST driver suite within Windows after setup completes to maintain RAID functionality. Failure to do so may result in reduced performance or loss of RAID management capabilities.
Can I use Rufus to inject drivers automatically?
Rufus does not natively support injecting custom drivers into
boot.wim during the creation of the bootable media. While some third-party tools claim to do this, manual DISM injection remains the most reliable and verifiable method. Using Rufus alone will leave the installer without the necessary VMD drivers for Intel platforms.
What if I have multiple Windows versions on the USB stick?
You must inject drivers into each relevant index of the
boot.wim file separately. Use the
/Index:1 and
/Index:2 parameters in your DISM commands to target specific editions. Skipping one index may result in the recovery environment failing to see the drives even if the main installer works correctly.
Is it safe to disable VMD in BIOS instead?
Disabling VMD forces the system to use standard AHCI mode, which Windows supports out-of-the-box. However, this disables the hardware RAID features provided by Intel. If you require RAID1 for redundancy, you must keep VMD enabled and inject the drivers. Disabling VMD is only a viable workaround if you do not need software RAID functionality.
How do I know if my driver injection was successful?
Success is confirmed when the Windows installer displays your RAID volume during the "Where do you want to install Windows?" step. Additionally, checking the driver list via DISM prior to testing ensures the files were processed without errors. If the drive remains hidden, verify that the driver files match the architecture (x64) of your installation media.