[Recreated from my comment]
tl;dr DISM injection of iaStor driver into an environment that will boot your existing Windows install into Safe Mode where you can run SetupRST.exe. I used my existing Windows Recovery Environment.
I did also create a bootable USB drive that allows access should something fail with the recovery environment, but I don't think it is totally necessary to get it running at first.
- 13th Gen i9 13900HX
- RST VMD Controller A77F
- Driver version 20.2.26.1025
- Archived installer .exe
- Archived extracted iaStor driver
- At the time of writing, this driver supported 12th - 15th gen. platforms.
- Intel documentation
- @TomCan's/this gist
- @johnthepro's comment
- ...and, as I'm writing up all of this, I find XinGuo's response on "MSLearn".
The exact name of the driver seems to vary based on the Intel platform and the version of the driver supporting the platform. In the case of 13th gen. and driver v20.2.26.1025, the name of the driver is iaStorVD.inf. On an earlier 10th generation i7-10875H, the driver installed was
21ms 2026-01-08 15:48:48 PS7> dism /online /get-drivers /format:table | select-string iastor
oem102.inf | iastorhsa_ext.inf | No | Extension | Intel Corporation | 2022-09-19 | 18.7.6.1010
oem107.inf | iastorac.inf | No | SCSIAdapter | Intel Corporation | 2022-09-19 | 18.37.6.1010
oem108.inf | iastorpinningcomponent.inf | No | SoftwareComponent | Intel Corporation | 2022-09-19 | 18.7.6.1010
oem109.inf | iastorhsacomponent.inf | No | SoftwareComponent | Intel Corporation | 2022-09-19 | 18.7.6.1010blastille's repo has extracted drivers.
If blastille's repo does not have the drivers you need, and you're able to get the correct installer from elsewhere, then the drivers are extracted from the RST installer using the following command
.\SetupRST.exe -extractdrivers SetupRST_extracted- [OPTION a)] Could also do this later in the process with
dismin [OPTION b)].- Provision the
iaStordrivers in your existing Windows install driver store usingpnputilor however is convenient for you to install the.inffrom the extractediaStordriver. - The injected drivers must include both the VMD driver and the HSA (hardware support application) driver(s). v20.2.26.1025 had 3 separate drivers,
pnputil /recursewill all 3 in a single/Add-Drivercommand.iaStore- HSA extension
- HSA component
- Provision the
- Use
diskpartto assign a drive letter making the recovery partition available. - Use
dismto inject all of the drivers into the recovery environment.- The directory structure of the recovery volume is hidden so
cmdanddir /aare your friend. dism /Mount-Imagerequires a destination directory on a fixed/non-removable drive volume via/MountDirmkdir c:\mntand remove it later.
dism /Mount-Image...dism /Image:<mount dir> /Add-Driver /Driver:<driver dir> /recursedism /Unmount-Image /MountDir<mount dir> /Commit
- The directory structure of the recovery volume is hidden so
- Enable VMD in UEFI settings.
- Attempt to boot as normal.
- Should get the usual inaccessible boot device error.
- Reboot or power-off, power-on.
- Recovery is entered automatically.
- Drives should be available now in the recovery environment since the
iaStordriver was added above.
- Drives should be available now in the recovery environment since the
- [OPTION b)] if you didn't use [OPTION a)].
- Use
dismto inject the drivers into the now available existing Windows install which should now be visible as its usual sysdrive: (default,c:). dismcommand similar to above but using/image:<drive letter of existing Windows install>: /Add-Driverinstead of mount, add driver, unmount.
- Use
- Stay in the recovery environment after exiting the recovery shell by typing "exit".
- Select "Startup Settings" from the recovery environment.
- Boot your existing install to Safe Mode.
- Run the full
SetupRST.exeinstaller. - Reboot letting Windows boot as normal and login.
- Let Windows store install the HSA (Hardware Support Application).
- Run the Intel VMD/RST/Optane hardware support application.
- Create hardware RAID volume.
- Running from the existing Windows install gives the option to preserve the contents of the installation during the creation process. This work for me for either RAID0 or RAID1. ...
- Profit
...could either,
- Create a (USB) bootable environment that has access to the drivers and perform the injections from there.
- Possibly even boot your install into Safe mode from there?
- Disable VMD/RST in UEFI settings and then follow the above process.
- Make sacrifices to the boot Gods and hope they are appeased enough to grant you access to your drives during the boot process.
..oh yeah, YMMV ;-)