Getting RST Drivers Working on Server 2022
Intel Rapid Storage Technology Driver Windows Server 2022 isn't something you install from the server installation media. Microsoft doesn't bundle all of Intel's storage controller drivers, and RST VMD (Volume Management Device) controllers are one of the ones that gets left behind. If you're trying to install Server 2022 on a machine with an 11th-gen Core or newer CPU, you'll hit the "no drives found" screen at the disk selection step. This is a well-known issue that comes up constantly in forums, and the workaround isn't especially well-documented by Intel. Here's how you actually deal with it, based on what I've done this enough times that it's now just muscle memory.
Intel Rapid Storage Technology Driver Windows Server 2022
First, download the driver. Intel's website is a maze, but the correct file is the Intel Rapid Storage Technology Driver for Intel VMD Controller. The current version number is somewhere in the 20.x range as of mid-2024. Make sure you grab the one labeled for VMD Controller, not the standard VMD driver. The distinction matters because the VMD Controller variant includes the f6floppy or f6driver files you need during installation. Unpack the downloaded executable. Intel packages these as self-extracting archives, so double-click it and point it to a folder on a USB drive or your desktop. Inside, you'll find a subdirectory structure that looks something like vmd\win10x64 or f6flpy-x64. That's your actual driver content. Intel doesn't make this obvious, which is annoying.
The Installation Process
When you're at the disk selection screen during Server 2022 setup and there are no drives showing, press Shift+F10 to open a command prompt. Navigate to the folder where you extracted the driver. Your USB drive letter might be D:, E:, or something else — check with dir if you're unsure. Run infntinstall.inf or whatever the equivalent INF file is in that directory. Right-click it and select Install. If it installs cleanly, close the command prompt and click the refresh button on the disk selection screen. Your drives should appear. This works about 80% of the time on the first attempt. The remaining 20% involves a quirk I ran into specifically on a Supermicro X13SVN-F board with an 11th-gen Xeon processor. After installing the driver and refreshing, the drives still didn't show up. What was happening is that the VMD controller was in a weird state — it had initialized but the storage devices behind it weren't being enumerated properly by the server setup environment. The fix was to enter the BIOS, go to the Intel VMD configuration section, temporarily disable VMD mode (which switches the drives to AHCI), complete the Windows Server installation, then re-enable VMD in the BIOS after the OS was loaded. Once the OS was running, I installed the RST driver from within Windows, and everything stabilized. Took about 25 minutes total instead of the usual 10.
Get the Full Details
This isn't the only edge case. Another thing I've seen: if you're doing a PXE boot or network-based installation, the driver won't load the same way. You need to inject it into your WIM or boot image using DISM before you even start the install. The process is dism /Add-Driver /Image:C:\mount /Driver:C:\drivers\infntinstall.inf and then rebuild your boot media. I learned this the hard way on a deployment of four servers where three went fine and the fourth stubbornly refused to see any storage because I'd only injected the driver into the install image and not the boot image. Both need it.
Post-Installation Setup
Once you're past the OS install, you need the full Intel RST software stack, not just the driver. The driver handles the hardware. The Intel RST application gives you the management interface. Download the latest version from Intel's website and install it. You'll get a system tray icon and access to RAID configuration if you're running any arrays. If you're on a single drive in RAID 0 or just using Intel Optane, the RST software is where you configure those settings. Without it, you're flying blind on things like drive health monitoring and cache status. I always recommend installing it before you migrate any data or create any volumes, since some configuration changes require a reboot and can interrupt active operations.
What This Driver Doesn't Do
Let me be clear about the limitations so you don't run into trouble later. Intel RST for Server 2022 does not support every RAID level that the older desktop versions did. Specifically, RAID 10 is not supported on Server 2022 with this driver. If you need RAID 10, you're looking at either a hardware RAID controller or Windows Server's built-in Storage Spaces, which handles it natively. Also, Windows Server 2022 doesn't have the same level of automatic driver update integration that Windows 10 or 11 has. You need to manually check for driver updates through Intel's website or set up a scheduled task to poll for them. There's no Windows Update channel for this driver on the server OS. I set a quarterly reminder in my calendar for this exact reason. You will forget, and then you'll get a support ticket about a performance issue that turns out to be an old driver bug. Another practical limitation: if you're running VMware or Hyper-V with virtualized Intel storage controllers, the RST driver inside the VM won't see the physical drives. The hypervisor abstracts the storage away. RST on Server 2022 only manages physical drives connected to the Intel VMD or SATA controller. This is obvious if you know virtualization, but I've seen people waste a day trying to configure a software RAID inside a VM that couldn't possibly see the underlying hardware.
Where to Get It
The official source is intel.com/content/www/us/en/download. Search for "Intel Rapid Storage Technology Driver." The file is typically named something like i9afwin.exe or similar. Avoid third-party driver sites. The Intel version includes the correct WHQL signing certificates, which matter for Server 2022's driver validation. A mismatched or outdated driver can cause Windows to refuse installation with error 0x800B0109, which is a code-signing verification failure, not a driver corruption issue. That error sent me down the wrong path twice before I realized it was a signature problem. If you need the driver for a bare-metal reinstall and you don't have internet access on the server, keep a copy on a USB stick. The driver package is small — usually under 200MB. It's worth having ready because the next time you need it, you'll probably be in the middle of a restore operation with nothing else working.
