Hi, I was actually going to post about this separately, but this reply will cover my post's intention.
I was unable to get the drivers installed by putting the drivers in sources\$OEM$. Instead, I put the drivers in $WinPEDriver$. The drivers load successfully in about 75% of the WinPE ISOs that I use. For the 25% of the WinPE ISOs that do not respond to the $WinPEDriver$ folder, I created VentoyAutoRun.bat and loaded the drivers manually using drvload "C:\Intel_Storage_Drivers\iaStorVD.inf". Note that my flash drive shows up as drive C: when booting to anything, hence the use of C: in the drvload line. I have the drivers extracted into the Intel_Storage_Drivers directory under my flash drive's root. My Drivers.zip file also sits inside Intel_Storage_Drivers.
So here is what I have that now works in 100% of Windows + WinPE ISOs:
![[Image: s2gPMKD.png]](https://i.imgur.com/s2gPMKD.png)
![[Image: ncRe9JO.png]](https://i.imgur.com/ncRe9JO.png)
![[Image: bH3KHq5.png]](https://i.imgur.com/bH3KHq5.png)
On my flash drive, under the folder Intel_Storage_Drivers. My drivers exist as files, and then the Drivers.zip archive includes the above screenshots.
![[Image: 4nqYzMd.png]](https://i.imgur.com/4nqYzMd.png)
Finally, in the ventoy.json file, you must specify the folders or ISOs for injection. Here's what mine looks like around that section:
![[Image: sgElsP9.png]](https://i.imgur.com/sgElsP9.png)
So no matter what, Drivers.zip is loaded and tries to inject the drivers. The VentoyAutoRun.bat script runs no matter what and runs drvload to load the drive (inf file). This way the drivers will load one way or another. Yes, I could test each image and determine which method to use, but it doesn't really matter, it won't hurt it to run drvload if it doesn't need it.
I was unable to get the drivers installed by putting the drivers in sources\$OEM$. Instead, I put the drivers in $WinPEDriver$. The drivers load successfully in about 75% of the WinPE ISOs that I use. For the 25% of the WinPE ISOs that do not respond to the $WinPEDriver$ folder, I created VentoyAutoRun.bat and loaded the drivers manually using drvload "C:\Intel_Storage_Drivers\iaStorVD.inf". Note that my flash drive shows up as drive C: when booting to anything, hence the use of C: in the drvload line. I have the drivers extracted into the Intel_Storage_Drivers directory under my flash drive's root. My Drivers.zip file also sits inside Intel_Storage_Drivers.
So here is what I have that now works in 100% of Windows + WinPE ISOs:
On my flash drive, under the folder Intel_Storage_Drivers. My drivers exist as files, and then the Drivers.zip archive includes the above screenshots.
Finally, in the ventoy.json file, you must specify the folders or ISOs for injection. Here's what mine looks like around that section:
So no matter what, Drivers.zip is loaded and tries to inject the drivers. The VentoyAutoRun.bat script runs no matter what and runs drvload to load the drive (inf file). This way the drivers will load one way or another. Yes, I could test each image and determine which method to use, but it doesn't really matter, it won't hurt it to run drvload if it doesn't need it.