I have a new Intel Z170 motherboard and am using the Intel RST RAID controller in the UEFI to create a Windows 10 boot drive.  It's 3 M.2 SSDs in RAID0.

When I installed Windows 10 I had to provide the Intel RST RAID driver during the installation process.  When I try to provide that exact same driver to Macrium rescue media creator for the  "Intel Chipset SATA RAID Controller" device it says "No driver found".

The relevant KB article isn't one of the most articulate that Macrium has produced, but it's basically about the need for the Reflect WinPE builder "wizard" to be able to find all of the driver files located together in a proper arrangement for the installer process.  If the driver files are contained in a .ZIP or .EXE package, they may need to be extracted (including any subfolder arrangement) to some accessible location so that the "wizard" can be pointed to the .INF file which will, in turn, locate all the rest for installation.

Alternatively, it may be possible to find and use the appropriate subfolder under \Windows\System32\DriverStore\FileRepository\ for manual addition to the WinPE build, but the "wizard" usually finds them there automatically if they were installed that way for the main operating system.  I suspect the driver installer source files were located somewhere else in this case.
__
P.S.:  I'm jealous. Three M.2 SSDs in RAID on a Z170 mobo!  Overclocked I7-6700K processor, I presume.  Is it fast enough? 


Regards, Richard V. ("Arvy")

I'm using the exact INF files I had to use during the Windows 10 fresh install to get it to recognize the RAID drive.  The issue is when I point the rescue media creator wizard to those same files for the missing RAID device it doesn't match the missing device.  I contacted Macrium support and they suggested I skip the error and manually copy the driver to C:\boot\macrium\Drivers\Disk which I did and I'm now able to boot with the USB rescue device and see the RAID drive.

Yep, using an ASRock Z170 OC Formula to get 3 GB/s SSD and 4.6 GHz CPU pretty easily.  Once I get the backups in good shape I'll start to push it

That is strange for sure.  AFAIK, the Reflect "wizard" gets its device info straight from Windows and uses Windows own DISM for adding drivers to its WinPE build.  So why it wouldn't match them up properly is beyond my admittedly limited abilities to explain.  Oh well.  Whatever works to get the job done is fine, I guess.

Sounds like you're having fun with that Z170 rig.  Keep it cool ... literally.


Regards, Richard V. ("Arvy")

My guess is that the recovery media is based on WinPE 5 which is based on Win 8.1 while my computer is Win 10.

I suppose that could possibly have something to do with it.  Just as an experiment, I did try (this forum thread) using the latest ADK PE5.1 components to replace the PE5 items that Reflect normally finds and uses under the \ProgramData\Macrium\Reflect\Windows Kits\8.1 folder.  Didn't seem to make any significant difference in my case, but I wasn't using a RAID configuration at the time.  Not sure if Macrium plans to update to PE5.1 soon or not.

Regards, Richard V. ("Arvy")

Apologies if I'm intruding on a thread here but I believe I'm facing a similar issue with the 64 bit RAID drivers for my Highpoint RR640L. During the creation of the rescue medium, it prompts to add drivers for this device and I point it to the folder in which the correct drivers are stored - 64 bit drivers but 'no drivers are found'. I can point it to the folder above which contains the 32 bit and 64 drivers and it seems to pick up the 32 bit drivers but obviously when I boot the rescue medium, the RAID arrays controlled by the RR640L are nowhere to be seen.

I have raised a support ticket for this case but maybe it's the same issue you are having?

The rescue media creation tool is not allowing the correct drivers to be selected. It's adding the 32 bit drivers!

I seem to recall a similar problem in the past with Reflect's WinPE builder "wizard" wanting to load 32-bit drivers instead of the correct 64-bit drivers, but I can't seem to find the forum thread,  If memory serves (and it's getting a bit shaky at my age) Macrium issued a fix for that previous issue, but a similar problem may have crept back in for some RAID driver packages.  In any case, I think you're probably going to need to follow up the ticket that you opened for this one.  It appears to be related to the "wizard's" misreading of some .INF file structures and, if so, it will require some corrective action by Macrium directly.

Regards, Richard V. ("Arvy")

Hi gringopig,

I have replied to your ticket.

Kind Regards

Stephen

See our reviews on

Thanks Stephen. Your workaround was successful. Much obliged. However I think the rescue media creation tool suffers from the issue that Arvy describes. I believe I remember that too actually although my memory is also not the best!
EDIT: it was actually Norton Ghost that loaded the wrong drivers for me. This is the first time I've had an issue with Macrium.
:-)