Universal Restore Driver error

Preston,

I think your boot issue is related to your item 6 above in that UR is looking for AHCI storage drivers and not finding them.  Are you restoring a Windows 7 OS?  Is this restore to a new PC? 

I doubt that the chipset drivers will carryover into the UR.  It is designed to inject drivers that use a .inf file extension. These files are often linked to other files with other extensions such as .sys etc.  If not .inf file exists in driver package you are attempting to inject then all files of that package will be rejected.

This is a brand new HP Windows 10 laptop.  

I have tried using Universal restore without the Chipset driver and with,  neither works.

I find it weird that Windows 10 USB restore disk can find and use the drivers, but UR cannot seem to get them installed.

Also chipset appear to be in .inf format.  

Your comment got me thinking.  I decided to run the restore with Automatic Driver Search off and specifying the Mass Storage drivers.  When I do that, UR Sits on Creating Universal Restore task forever.  Never advances to the next step.  MY guess is that UR doesn't like the Intel RST VMD Controller 9A0B (TGL) driver.  Is there a generic AHCI driver I can use instead? 

Yes, Windows 10 should have a generic driver for that.  Have you tried not using UR at all?  The more I read this the more I think you are not doing something right.

UR is meant to be applied to a disk only after a backup drive image file has been restored to a disk.  Is that what you did prior to using UR?  If not then your problems are deeper than drivers.

Windows 10 is very good at booting using generic drivers and, if the PC is connected to the internet Win 10 is excellent at finding drivers via Windows Update for differing hardware.  So good that I have not used UR since Win 10 was released.  So far I've only had 1 failure out of more than 10 builds.

I tried restoring the backup with True Image originally, and just booting without using UR and got the same error.  My assumption is that UR is not compatible with the Intel drive controller driver.  I too have used this multiple times without issue, but this time it doesn't want to cooperate. I could be doing something wrong, but  I can and have followed the restore instructions exactly as they are written.

When you restored the backup image to the new drive, was that new drive installed in the laptop or did you have it attached externally? 

For what ever reason with laptops it seems the best practice is to install the new disk in the machine, then boot the machine with the recovery media and then restore the backup image to the new disk.

The inaccessible boot device error indicates that the machine bios cannot find the boot loader on the disk.  At the end of a restore operation ATI runs a partition synchronization which I am pretty sure takes care of locating the boot partition on disk.  

I recommend that you boot the laptop into the bios, locate the Boot section and make sure that Windows Boot Manager is selected as the first boot device.  If Windows Boot Manager is not listed in the boot list then you would select the new disk to be the first in the boot list.

Yes,  Everything was done internally within the machine (I did not remove the drive).  I will check the Boot order this evening.

Thanks, for your continued help.

I tried everything suggested and nothing worked. I restored the thing around 6 times trying different solutions.  Nothing worked.  I finally bought another laptop with the same drive controller and restored the backup to that laptop.  It booted just fine without having to use UR.  Very frustrating experience with UR this time around.  I think UR doesn't like the Intel RST VMD Controller 9A0B (TGL).  The Intel Chipset SATA/PCIe RST Premium Controller works fine. (that was the controller on both the old laptop and the new laptop.

I dislike resurrecting an old post but I have had the precise issue described above on two different restore tasks recently. I am using the latest version of Cyber Protect Home and I spent at least an hour last week working with Acronis support. This problem with the latest Intel RST drivers and chipsets has been around for almost 3 years and yet it has not been addressed or resolved by Acronis as far as I can tell.

I would dearly love to know the solution to this problem as restoring to dissimilar hardware is something I do fairly often in my work as a computer tech.

See forum topic: Intel VMD Raid0 drive wont show up in the True Image 2021 BootStick!

The latest build of Universal Restore for ATI 2020 is dated 26 August 2019, which is three and a half years, which suggests that it may predate the release of Intel RST VMD Controller, if the reference to 3 years is accurate. The most recent build of Universal Restor (CPHO version) is date 8 August 2020.

I have not had any luck using Universal Restore.  I Use a different procedure.

1.  Get a USB to SATA adapter

2.  Use Acronis True Image to image your old PC (Drive) to a SATA drive on the USB adapter (or restore backup to the drive)

3.  Once done, insert the USB with drive into the new hardware

4.  Start the new hardware and select to Boot to the USB drive (it will boot to the USB drive without issues in 99.9% of cases)

5.  Once booted, update all Device drivers (making sure to install the drive controller built into the new hardware)

6.  Once drivers are updated, restart the PC and use Acronis True Image to Image the USB drive to the installed drive.

7.  restart and remove the USB drive and boot to the internal drive. ( it may do a repair, but usually not, it should boot just fine, I've never had it not work.)

Hello Preston. 

Thanks for sharing the steps of resolution. Hopefully will help other users with similar hardware!