Intel VMD Raid0 drive wont show up in the True Image 2021 BootStick!

Hi there,

I treated myself to a new Z690 Gigabyte mainboard including the Intel 12900k ... then created a Raid0 drive on the mainboard for 2x NVMEs and activated Intel VMD beforehand ... then I am on my Windows 11 USB stick Installation ISO and have loaded the Intel VMD driver (Intel VMD driver 19.0.0.1067) using a stick. Windows then recognized the Raid0 VMD drive I created and I was able to install Windows 11 on it.

In Windows I then created a WinPE drive using True Image 2021 MediaCreator with the help of Windows ADK and loaded the required .inf drivers from Intel VMD into it (which already worked with the Windows11 installation stick). Then I went to this generated WinPe image via the BIOS and unfortunately the Raid0 VMD drive could not be loaded! I also tried to do the whole thing with the MVP_ATIPEBuilder_v190 + Windows ADK - with custom driver injection and / or Windows driver injection - unfortunately the same result: Raid0 VMD drive is not recognized!

Intel VMD is therefore not supported and cannot be reloaded :-(

Many greetings,

Andreas

Andreas, welcome to these public User Forums.

I have no direct experience with using the technology you have invested in here and doubt that Acronis have done any testing in this area either!

The first suggestion I would make is to ensure that you have identified all the drivers that are being used for your RAID 0 configuration and ensure that you have the correct versions of these applied to the Acronis rescue media you are trying to use.

In particular, that you are adding in the correct Intel RST drivers as well as the Intel VMD drivers.

Initially, I would suggest trying the Advanced method of the Acronis media builder but using the option to take the drivers from the Windows Recovery Environment instead of using the ADK + PE option.  Add in the Intel VMD drivers to that build and test if that makes any difference or not?

You should also check whether Optane is involved here?  There are separate Intel RST + Optane drivers that would be needed.

Andreas, see forum topic: Recovery via Recovery Media failed to offer PC's drive as target that may be similar (at least in terms of Intel VMD usage).

Steve Smith wrote:

Andreas, this is a case where you may need to open a Support ticket directly with Acronis Support but unless you are going to pay for support, you would need to either install a trial copy of or upgrade to Acronis Cyber Protect Home Office and show that the same issue continues to exist, as that is the only supported version at this time.  ATI 2021 is no longer in support by Acronis.

or I just use the normal Windows build-in backup software

Your results indicate the driver you added in not complete. I downloaded the IRST version 19 drivers from the Gigabyte website selecting the Preinstall option. I see two sets of drivers included. I would add both sets to the Acronis media. One set is in the Non-VMD folder and the other set is in the VMD folder. The Non-VMD folder includes the Optane drivers.

To add the complete Non-VMD drivers you need to put them in two folders because there are two inf files. Create two folders with different names. Copy all the Non-VMD driver files to each folder. Then delete one of the inf files from the first folder. Next, delete the other inf file from the second folder. Add both folders and the VMD folder to the media under add drivers.

This will give you media that should work with the SATA mode in the BIOS set to either RAID or AHCI.

Andreas,

The Intel Gen 11 CPU support of VMD management presents a new unique driver set that offers a Hyperconverged Infrastructure architecture (HCI) thus requiring a special driver set.  What you need to do to gain this support in a boot media (WinPE) environment is locate the necessary driver files required for your hardware in the Windows system.

The exact files needed here are at this point unknown given the information you have provided so far.  Your screenshot of Device Manager helps but is not specific enough to lead to the required driver packages that support your hardware.  Having said that Device Manager does hold the keys to find your drivers.

There are 3 devices listed in the screenshot you provided and it is necessary to explore all 3 to locate3 the necessary driver files.  The process is fairly straight forward.  The 3 devices are:

• Standard SATA AHCI Controller
• Intel RST VMD Controller 467F
• Intel RST VMD Managed Controller 09AB

On each of these entries in Device Manager right click on them with your mouse and select Properties from the menu that appears.  When the Properties window opens locate the Details tab and click on it to select it.  You will see the name of your device then below that name will be a Property field which is expandable by clicking the down pointer on the right side of the field box.  Expand the Property box and locate INF name in the list and select it.  now look in the Value field and copy the result.  Collect this information for all 3 of the devices listed above and then post them back here for further instructions.

Hallo Enchantech,

Standard SATA AHCI Controller:    mshdc.inf

Intel RST VMD Controller 467F:     oem0.inf

Intel RST VMD Managed Controller 09AB:   oem0.inf

I have found the following intel entries in the autoruns program (with all scan-features enabled):

iaStorVD - Intel(R) Chipset VMD RST Controller service: Intel(R) Rapid Storage Technology driver - x64    
Intel Corporation    c:\windows\system32\drivers\iastorvd.sys    22.07.2021 14:40   

iaStorV    Intel RAID-Controller Windows 7: Intel Matrix Storage Manager driver - x64    Intel Corporation    c:\windows\system32\drivers\iastorv.sys    11.04.2011 19:48

iaStorAVC    SATA-RAID-Controller mit Intel-Chipsatz: Intel(R) Rapid Storage Technology driver (inbox) - x64    Intel Corporation    c:\windows\system32\drivers\iastoravc.sys    05.09.2019 13:07

and some other GPIO drivers that are not connected to the drive/my problem.

Mustang:
Your results indicate the driver you added in not complete. I downloaded the IRST version 19 drivers from the Gigabyte website selecting the Preinstall option. I see two sets of drivers included. I would add both sets to the Acronis media. One set is in the Non-VMD folder and the other set is in the VMD folder. The Non-VMD folder includes the Optane drivers.

 I have already think of that and done it... every new folder for each inf/sys-combo... the WinPE Rescue drive will not recognize the created Raid0 drive :-(

(I have injected it with MVP_ATIPEBuilder_v190 and with the True Image 2021 Bootable Rescue Media Builder ADK, Windows Recovery Environment) - nothing helps :-(

when Ive installed Windows 11 with the installation-stick it found 2 inf-drivers in one injected/downloaded folder... and only when all of that 2 drivers were selected and enabled, it found the drive. (it showed: Intel RST VMD Managed Controller 09AB and Intel RST VMD Controller 467F - I have selected both)... but when I inject the folder into the WinPE True Image drive it doesnt show my drive... :-(

I have uploaded my used drivers that work with the windows installation:

filehorst.de
/download.php?file=efdkwCad

Intel RST VMD Managed Controller 09AB and Intel RST VMD Controller 467F are both found in the    iaStorVD.inf     file from the driverpackage, I have posted! thats what windows shows me during the installation!!!

True Image cant handle both drivers in one iaStorVD.inf, Windows Installation can...

(I have attached the iaStorVD.inf  as a .txt file)

you can see this in the file:

PCI\VEN_8086&DEV_9A0B.DeviceDesc = "Intel RST VMD Controller 9A0B"
PCI\VEN_8086&DEV_09AB.DeviceDesc = "Intel RST VMD Managed Controller 09AB"
PCI\VEN_8086&DEV_467F.DeviceDesc = "Intel RST VMD Controller 467F"

When I unzip the driver downloaded from the Gigabyte website, I get a folder named IRST. Inside IRST I see 5 folders that contain drivers. They are:

HsaComponent

HsaExtension

NonVMD

PinnedComponent

VMD

I would try adding all of these drivers. Use the MVP Tool and replace the \Drivers_Custom\x64\IRST folder with the IRST folder from the download with the 5 folders. The MVP Tool will parse all drivers in the IRST folder and all subfolders.

Andreas,

Now that you have the 3 driver INF file names we can use those to locate the driver packages needed for injection purposes into boot media.  Below is an example command which you can run from a PowerShell Admin command prompt:

Example: Dism /Online /Get-DriverInfo /Driver:iaStorVD.inf

You should get a result like you see below:

PS C:\Windows\system32> Dism /online /Get-DriverInfo /Driver:iaStorAV.inf

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1320

Driver package information:

Published Name : iastorav.inf
Driver Store Path : C:\Windows\System32\DriverStore\FileRepository\iastorav.inf_amd64_87f761c07c99d5e7\iastorav.inf
Class Name : SCSIAdapter
Class Description : Storage controllers
Class GUID : {4D36E97B-E325-11CE-BFC1-08002BE10318}
Date : 2/8/2018
Version : 15.44.0.1015
Boot Critical : Yes

Drivers for architecture : x86

What you need from this output is the Driver Store Path information.  Copy this path to notepad and do so for each of the 3 drivers in question then save that file to your desktop temporarily.  Note that the PS command is likely to produce a long string of output, you will need to scroll back up through that output as the information I show here is what is first produced by the command.

Once you have all 3 Driver Store Paths captured you can go about building new media.  When you get to the step to Add drivers, copy and paste these Driver Store Paths one at a time into the Add drivers box if using the Acronis builder or paste the 3 paths into the appropriate folder if using the MVP builder.

...

Mustang wrote:

When I unzip the driver downloaded from the Gigabyte website, I get a folder named IRST. Inside IRST I see 5 folders that contain drivers. They are:

HsaComponent

HsaExtension

NonVMD

PinnedComponent

VMD

I would try adding all of these drivers. Use the MVP Tool and replace the \Drivers_Custom\x64\IRST folder with the IRST folder from the download with the 5 folders. The MVP Tool will parse all drivers in the IRST folder and all subfolders.

nope - my drive doesent want to show up. with your preinstalled files in the MVP Tool IRST folder and without (only with this 5 subfolders): Custom drivers -> x64 -> IRST

my injected driver for my realtek network card works like a charm in the WinPE Installation created by MVP Tool - so this feature works but not with my drive :-( 

Enchantech wrote:

Andreas,

Now that you have the 3 driver INF file names we can use those to locate the driver packages needed for injection purposes into boot media.  Below is an example command which you can run from a PowerShell Admin command prompt:

Example: Dism /Online /Get-DriverInfo /Driver:iaStorVD.inf

You should get a result like you see below:

PS C:\Windows\system32> Dism /online /Get-DriverInfo /Driver:iaStorAV.inf

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1320

Driver package information:

Published Name : iastorav.inf
Driver Store Path : C:\Windows\System32\DriverStore\FileRepository\iastorav.inf_amd64_87f761c07c99d5e7\iastorav.inf
Class Name : SCSIAdapter
Class Description : Storage controllers
Class GUID : {4D36E97B-E325-11CE-BFC1-08002BE10318}
Date : 2/8/2018
Version : 15.44.0.1015
Boot Critical : Yes

Drivers for architecture : x86

What you need from this output is the Driver Store Path information.  Copy this path to notepad and do so for each of the 3 drivers in question then save that file to your desktop temporarily.  Note that the PS command is likely to produce a long string of output, you will need to scroll back up through that output as the information I show here is what is first produced by the command.

Once you have all 3 Driver Store Paths captured you can go about building new media.  When you get to the step to Add drivers, copy and paste these Driver Store Paths one at a time into the Add drivers box if using the Acronis builder or paste the 3 paths into the appropriate folder if using the MVP builder.

doesent work either - when I search for the second oem0.inf, Powershell only finds again the same inf/inf-folder:
C:\Windows\System32\DriverStore\FileRepository\iastorvd.inf_amd64_815480839574a92b\iastorvd.inf

when I copy the path to the media builder it only finds the 09AB controller and not the 467F!

when I copy the whole folder to the desktop and change the copied iastorvd.inf and delete all "%PCI\VEN_8086&DEV_09AB.DeviceDesc% = VMD_dummy_function_inst, PCI\VEN_8086&DEV_09AB" entries and load this created folder into the media builder, it will show up the 467F controller but crash in the creating of the usb-stick. It looks like the Builder cant process 2 controllers enbetted in one .inf file! it only installs the first controller in the .inf-file! its a builder problem!

Andreas,

I had a look at the .txt file you posted earlier, hadn't noticed it before.  I find in that log that the drivers needed are for 2 devices, they are:

• %PCI\VEN_8086&DEV_9A0B.DeviceDesc% = VMD_inst, PCI\VEN_8086&DEV_9A0B

• %PCI\VEN_8086&DEV_467F.DeviceDesc% = VMD_inst, PCI\VEN_8086&DEV_467F
  

The other entry for the 09AB Dummy device shows no driver needed.  So this explains your results with the instructions I gave you.  You should try again this time using only the 2 drivers above and see what your results are.

Andreas,

You may find that only one driver folder is required for things to work based on your post where you say:

"Intel RST VMD Managed Controller 09AB and Intel RST VMD Controller 467F are both found in the    iaStorVD.inf     file from the driverpackage, I have posted! thats what windows shows me during the installation!!!"

This would indicate that both required controllers files are present in iaStorVD.inf

Enchantech wrote:

Andreas,

I had a look at the .txt file you posted earlier, hadn't noticed it before.  I find in that log that the drivers needed are for 2 devices, they are:

• %PCI\VEN_8086&DEV_9A0B.DeviceDesc% = VMD_inst, PCI\VEN_8086&DEV_9A0B

• %PCI\VEN_8086&DEV_467F.DeviceDesc% = VMD_inst, PCI\VEN_8086&DEV_467F
  

The other entry for the 09AB Dummy device shows no driver needed.  So this explains your results with the instructions I gave you.  You should try again this time using only the 2 drivers above and see what your results are.

 

the last "C:\Windows\System32\DriverStore\FileRepository\mshdc.inf_amd64_84ea762c0a90c362\mshdc.inf" is just an ordinary microsoft ahci-driver for my non-Raid-drives... it runs perfect in the WinPE drive with those normal drives...

these 2 drivers + the dummy one are all in the same folder/.inf... when I copy the path to the Mediabuilder he only finds the 9A0B driver! the Mediabuilder cant process more than one driver in a single inf-file... and I need 2 of them. thats the problem

Enchantech wrote:

Andreas,

You may find that only one driver folder is required for things to work based on your post where you say:

"Intel RST VMD Managed Controller 09AB and Intel RST VMD Controller 467F are both found in the    iaStorVD.inf     file from the driverpackage, I have posted! thats what windows shows me during the installation!!!"

 

This would indicate that both required controllers files are present in iaStorVD.inf

 yes. the MediaBuilder only shows 1 driver and installs only 1 driver (the first entry)... and I need both from the iaStorVD.inf

its not possible to install the iaStorVD.inf correctly :-(

Andreas,

Let's try this:

Navigate to the FileRepository folder that contains the iaStorV.Dinf.  If you double click on this it will open to show contents.  What do you see.

Now do the same thing with iaStorV and iaStorAVC, what do you see in these files?  If the contents are the same you have what you need is iaStorVD.

Quite frankly your drivers are in simple terms:

iaStorVD,inf  =  VMD driver

iaStorV  =  Windows 7 Raid driver

iaStorAVC  =  SATA RAID driver

Your actual driver files are: iastorvd.sys, iastorv.sys, and iastoravc.sys.  If these files are all in one folder it should work for you.  The Windows 7 driver is not needed here given your hardware.

I will try to switch my nvme drives in different slots... to just hopefully use 1 controller instead of 2.
because the 3 controllers/drivers in the iaStorVD.inf represents my 4 slots on the mainboard... 2 slots should be doing 1 controller

Enchantech wrote:

Andreas,

Let's try this:

Navigate to the FileRepository folder that contains the iaStorV.Dinf.  If you double click on this it will open to show contents.  What do you see.

Now do the same thing with iaStorV and iaStorAVC, what do you see in these files?  If the contents are the same you have what you need is iaStorVD.

Quite frankly your drivers are in simple terms:

iaStorVD,inf  =  VMD driver

iaStorV  =  Windows 7 Raid driver

iaStorAVC  =  SATA RAID driver

Your actual driver files are: iastorvd.sys, iastorv.sys, and iastoravc.sys.  If these files are all in one folder it should work for you.  The Windows 7 driver is not needed here given your hardware.

I opend the .sys files via autoruns and thats the results:

iaStorVD.sys
System32\drivers\iaStorVD.sys
SCSI miniport
@oem0.inf,%iaStorVD.ServiceName%;Intel(R) Chipset VMD RST Controller service

iaStorV.sys
System32\drivers\iaStorV.sys
SCSI Miniport
@iastorv.inf,%*PNP0600.DeviceDesc%;Intel RAID Controller Windows 7

iaStorAVC.sys
System32\drivers\iaStorAVC.sys
SCSI miniport
@iastorav.inf,%iaStorAVC.DeviceDesc%;Intel Chipset SATA RAID Controller

now I have found the folders in the FileRepository and will try to inject them...

Update: No Drive found :-(

No Drive found :-(

You are talking about the problem of having two drivers in one folder. You don't seem to understand this properly. When you say two drivers, I think you mean there are two sys files in the folder. That is NOT an issue. The issue is when there are two inf files in the same folder. This is happening in the Non-VMD folder. The Acronis Media Builder isn't handling this properly. They only install the first inf file and skip the second. This results in some of the sys files not being installed.

I gave you clear instruction in my first post on how to overcome the Acronis problem. You didn't follow those instructions with the Acronis Media Builder if some of the sys files are missing.

The MVP Tool does NOT make this mistake. All inf files in the folder and it's subfolders are properly installed. You say you built the MVP media with all of the subfolders in the IRST folder and it still didn't work. That tells me there may be a problem other than a driver problem here.

I can tell you I did build a WinPE using the IRST 19 drivers provided by Gigabyte. It worked on a RAID system that is based on an X299 chipset and an Intel 10th Gen. i9-10900X processor. I did it two ways and it worked both ways. The first was adding all the drivers in all the IRST folder. The second was only adding the Non-VMD and VMD folders.

Mustang wrote:

You are talking about the problem of having two drivers in one folder. You don't seem to understand this properly. When you say two drivers, I think you mean there are two sys files in the folder. That is NOT an issue. The issue is when there are two inf files in the same folder. This is happening in the Non-VMD folder. The Acronis Media Builder isn't handling this properly. They only install the first inf file and skip the second. This results in some of the sys files not being installed.

I gave you clear instruction in my first post on how to overcome the Acronis problem. You didn't follow those instructions with the Acronis Media Builder if some of the sys files are missing.

The MVP Tool does NOT make this mistake. All inf files in the folder and it's subfolders are properly installed. You say you built the MVP media with all of the subfolders in the IRST folder and it still didn't work. That tells me there may be a problem other than a driver problem here.

its only 1 system file... and 3 controllers enbetted in the .inf/.sys... (I need 2 of them)
just look at the files Ive uploaded. you can look into the .inf-file with a text editor.

WinPE/MediaBuilder/Windows ADK and your Tool only installs the first of the 3 controllers... the other .infs are the normal AHCI/RAID stuff True Image comes with - and yes Ive injected them additionally anyway now million times over and over again and it doesent work :-(

Ive switched now all 2 nvme-drives in all possible slots/configurations on my mainboard - it doesent help, because the mainboard always give them 2 separate controllers :-(

I have no Ideas left

Windows 11 Installation-stick has no problems to look into the .inf and give me both of the controller to install, I can even choose them from this one .inf - the 3rd controller (dummy one) doesent even appear in the options to choose!
And Windows sees my drive without a problem - it must be Windows ADK, WinPE, True Images MediaBuilder or the way they interact with... its a developer problem. And you will see more people with this problem soon :-(

I agree it's a developer problem. However, don't expect Acronis to solve it. History has proven that won't happen any time soon.

The only other thought I have for you to try relates to the possibility there is a driver conflict here. I have run into this before. I would suggest building with the MVP Tool with only the full IRST folder in the \Drivers_Custom\x64 folder. Don't add any other drivers to see if a driver conflict exists.

Mustang wrote:

I agree it's a developer problem. However, don't expect Acronis to solve it. History has proven that won't happen any time soon.

The only other thought I have for you to try relates to the possibility there is a driver conflict here. I have run into this before. I would suggest building with the MVP Tool with only the full IRST folder in the \Drivers_Custom\x64 folder. Don't add any other drivers to see if a driver conflict exists.

could you please explain your method step by step in detail?

Andreas,

Can you capture a screenshot of your Intel Storage controller as I have illustrated below, it should help in getting you the correct driver package:

In Device Manager right click on the Intel Storage Controller as shown below.

You will get a popup window as seen below, click on the Details tab as shown below.

Expand the Property field and select Inf name form the list as shown below and capture a screenshot of the output for posting here.

at the 09AB Controller (first set of pictures) you can see the text "Für dieses Gerät sind keine Treiber installiert", it means in english: "no drivers are installed for this device"... interesting... I have not noticed that ...

Ive got it running now!!!! <- but its tricky and far from optimal

tutorial to see the fuc*ing intel vmd drive:

just use the cmd-prompt in your True Image BootStick-Build with the following command:
 

pnputil -i -a c:\IRST\iaStorVD.inf

you have to put first of course your .inf/.sys/.cat/.dll/.exe driver-compilation there (directly, without a subfolder), with the exact foldername 'IRST'. Ive safed the command in a .txt file, that I open to copy and paste it with the MVP_ATIPEBuilders Notepad-App (WinRE Version!) in the CMD-Prompt/Windows-Terminal on the BootStick.

it will instantly install that damn drive-controller and load it up... AND I CAN FINALLY SEE THAT STUPID DRIVE IN TRUE IMAGE!!

but please please for god sake fix your injecting for the future

Your trying to blame us! No fuc*king way!

Mustang wrote:

Your trying to blame us! No fuc*king way!

Not at all - its true
it would be cool when you integrate that command-promt-code in your MVP ATIPE Builder as a startup-command... with the IRST-folder into the builded WinRE/WinPE-Drive via your great tool. Than it would start automatically after start ;-)

it installs in an instant...

Thanks for your time guys, bye
Andreas

Andreas,

Glad to hear you got it working, that's good.  I would like to clear up a few things here however.

First, as you found, multiple files are needed for complete functionality of device drivers.  Those files are stored in Windows at C:\Windows\DriverStore\FilkeRepository\.  If you navigate to that path and locate, in your case iastorVD.inf and copy that folder then paste that folder in either of the media building tools the tools will inject the drivers during the build process.

The trick to this is figuring out what the Original Driver File name is which I see you did, just not sure how, there are a few ways to do that.

The  use of the pnputil command will work but is not at all necessary in doing this.

Enchantech wrote:

Andreas,

Glad to hear you got it working, that's good.  I would like to clear up a few things here however.

First, as you found, multiple files are needed for complete functionality of device drivers.  Those files are stored in Windows at C:\Windows\DriverStore\FilkeRepository\.  If you navigate to that path and locate, in your case iastorVD.inf and copy that folder then paste that folder in either of the media building tools the tools will inject the drivers during the build process.

The trick to this is figuring out what the Original Driver File name is which I see you did, just not sure how, there are a few ways to do that.

The  use of the pnputil command will work but is not at all necessary in doing this.

yes it is... because true images injection is broken for the intel vmd drivers... you will see it in the future as more and more people will have this problem (if we are still alive of course^^), bye

Hi

Yesterday I've spent few hours trying to make bootable media in Cyber Protect Home for Asus Z690P motherboard with RAID enabled. Making it with creator didn't work exactly, as is described in this topic. Main problem is, that this version of Acronis bootable media has no direct option to add drivers after WinPE starts. I've checked this with Acronis 12.5 borrowed from work, and that version allow user to inject driver without an problem at all. After making yesterday this damned iso nearly 30 times, finally I've found this topic. But today I've discovered, that not only I had to manually install driver from console with pnputil /add-driver C:\IRST\iaStorVD.inf /install, but BEFORE that I had to UNINSTALL and remove badly auto preinstalled driver by the media creator (pnputil /delete-driver oem0.inf /uninstall). There should be option to add drivers as in other versions of Acronis to avoid this confusion. I am using Acronis software over 10 years now and I am really disappointed :/

who needs backups or recoveries every minute? just install that MVP ATIPE Builder tool, make an Image and load your .inf-files into your made usb-true-image-stick... from within the MVP-Image you can run a text-editor to copy and paste your terminal code into cmd... its fast, simple and costs only a minute of time more for your very rare backups...

I think even .bat files (batch script files) would be possible to activate without enter any code with that MVP-Builder-Image

If you put any .bat or .cmd files in the MVP tool 'Extra' folder for the architecture being used, i.e. Extra\x64 then it will be available in the rescue media when needed.  I have used this method for unlocking BitLocker and copy log files when needed.

just found:

Batch (create a textfile, insert the following text and change the file into .bat) :

@ECHO OFF

ECHO Installing Drivers Please wait....
for /f %%i in ('dir/b /s *.inf') do pnputil.exe -i -a %%i

Pause

or 

@echo off
%~dp0

for /f %%i in ('dir /b /s *.inf') do %SystemRoot%\System32\PnPutil.exe -i -a %%I

or

@ECHO OFF
CD C:\Drivers
ECHO Installing Drivers Please wait....
for /f %%i in ('dir/b /s *.inf') do X:\Windows\winsxs\amd64_microsoft-windows-pnputil_31bf3856ad364e35_6.1.7600.16385_none_5958b438d6388d15\pnputil.exe -i -a %%i

(don't forget to edit the path to your .inf files or just start the .bat within your .inf-folder)

you can search for your pnputil file in the cmd terminal:

where pnputil

Thanks, Ive updated my first post with that solution. I'll hope that this will help even more people in the future and make it more user-friendly :-)

- bye, Andreas

It look like I am having a similar issue. My system is an Asrock Z690 with Raid10 installed on 4 sata drives, next 2 non-raid sata drives and 3 non-raid nvme SSDs running W11.

I do need to restore my system drive, and tried Startup Recovery, however Startup Recovery does not recognize ANY of my disks, raid or nvme.

Then I made a DVD with Recue Media builder. It does not boot.
Then I made a usb with Recue Media builder. It does not boot.

How can I restore my system drive?

Help please!

The MVP tool skips Acronis If you are running Cyber Protect Home. However it does include Universal Restore if it is installed in your system.

Maybe it is possible to adapt the tool to this shortcoming in the future?

Hans

I don't understand your problem... what has your problem to launch acronis boot disk to do with a not installed device driver in an already booted up boot disk? you are in the wrong thread - pls make a new one...

when a disk can't be recognized in your boot disk than load the cmd.-prompt (in your booted boot disk) up and install your own raid drivers with the command code I've posted earlier

Andreas.

Maybe a bit of explanation from my side.

It may be fairly obvious why a system disk from a running system can’t be restored with Cyber Protect Home. That is the reason why I activated Startup Recovery Manager hoping it would enable me to restore my system disk. After activation and restarting the system I used F11 to use Cyber Protect Home (CPH). CPH starts but to my surprise does not show ANY disk.

I urge you to try it on your system using Acronis True Image, maybe it will work in the «older» version of CPH.

So this did not resolve my issue. Next possibility, in CPH, is Rescue Media Builder. It constructs the DVD and writes it but booting from the DVD does not work.

Last resort is Media Builder. I am struggling to understand your solution, it is above my level of understanding, so far I did not succeed in creating a DVD that worked for me. Creating an USB stick fails at the point where the stick is to be formatted. And now I am waiting for the next set of DVD blanks in order to try solving my issue.

Hans

My issue is partly solved.

Acronis is no longer skipped in the MVP tool after the registry changes necessary to use the tool with Cyber Protect Home, as described somewhere on this forum.

However the creation of a Bootable USB stick still fails during format. I Created the bootable USB using Rufus and the ISO created by the MVP tool.

Booting from this USB stick enables me to restore my system disk.

It is a two step solution that is acceptable for me, as it will not be needed often.

Command Prompt access in the TrueImage WinRE/WinPE is which keys sequence? Shift+F10 (Like windows setup?)