Acronis True Image 2021 Universal Restore - PCI Drivers
Hello
Universal Restore to dissimilar hardware after motherboard failure
Old Motherboard Gigabyte Z68AP-D3
New Motherboard Gigabyte Z390 UD.
New Tower case, memory, motherboard, SSD and 4TB HDD installed and running Win 10 Pro successfully
Want to be able to boot from old Operating System Windows 7 Home Premium 64 bit on 2TB Barracuda hard drive until I move things across to new drives. I can be read 2TB drive and have backed-up (with True Image 2021) after hardware failure. 2TB HDD will not boot in new hardware. Have attempted multiple repairs in Windows 7. Attempted Windows7 reinstall keeping existing files and apps but the process requires a bootable drive.
True Image 2021 installed on second 4TB hard drive running Win10. The second drive is in a separate bay. It boots up.
Created recovery USB disk from Win 10 Pro HDD (booting on same hardware). I believe I copied all the drivers from the new HDD but a bit unsure and maybe I need the INF files as well. Not sure how I extract these from WIN7, WIN 10 & Gigabyte install disks and which drivers are critical.
Booted Universal Restore from recovery USB disc. OS Win 7 Home premium is recognised on 2TB target drive. Added folders for Automatic Driver Search and added Mass Storage Drivers to install (this is where it becomes too complex for me).
When Universal Restore runs it stalls at around 55% (message activities that need user interaction), if I click 'Ignore all' the process completes successfully with the following two yellow warning messages:
Cannot find device driver 'PCI\VEN_8086&DEV_A36D&SUBSYS_50071458&REV_10
Cannot find device driver 'PCI\VEN_8086&DEV_A352&SUBSYS_B0051458&REV_10
After running Universal Restore I'm still unable to boot because I'm missing one or two device drivers mentioned above.
Any help or clues would be greatly appreciated.
Thank you
Steve


- Log in to post comments

These drivers are not supplied for Windows 7 so Universal Restore is hanging due to those drivers not finding the correct drivers for your hardware.
The first drive in your list is a USB 3.0 Extensible Host Controller driver which you will find at the link below:
Intel Download Center USB 3.0 driver
The second driver missing is an AHCI storage controller driver. The missing driver version identified by the Hardware ID in your post is 16.0.2.1086. Both of these drivers are hard to find because of Win 7 support being deprecated. I checked the Intel download site for the AHCI driver and it is no longer offered. I did find it at Station Drivers link provided below:
I recommend running an antivirus scanner any downloads from non-manufacturer sites.
- Log in to post comments

Thank you for your valuable advice Steve Smith and Enchantech. I will follow your instructions and let you know how I go.
- Log in to post comments

Steve Smith and Enchantech,
Progress report.
1) Using 7-Zip I extracted drivers from y old Win 7 Home Premium install CD,
2) I also extracted drivers from Intel zip file
https://downloadcenter.intel.com/download/28680/Intel-Management-Engine-Driver-for-Windows-7-
Driver Intel Management Engine Driver for Win 7 300 Chipset - ME_SW_1909.12.0.1237.zip
3) As suggested, I installed Win 7 Home Premium on a new 4TB hard drive and extracted the drivers to a file using Double Driver. I've applied all the Win updates. It is working perfectly, if only I could export my existing applications and files across from the old drive.
On the new install I soon discovered that there are no Win 7 USB drivers for the latest Motherboards like Gigabyte Z390 UD. Both Microsoft & Intel haven't written any. This is a bit of an annoyance but there is a guy in China who has apparently developed one. I will worry about that later.
Armed with separate collections of drivers (1), (2) & (3) , I returned to True Image Universal Restore. I ran a number of passes using both 'Automatic Driver Search' and 'Mass storage drivers to install'.
Knowing there are no USB drivers available, I ignored the warning message 'PCI\VEN_8086&DEV_A36D&SUBSYS_50071458&REV_10, as it should not prevent the restored drive from rebooting.
Unfortunately, no matter which collection of drivers I present to Universal Restore the error message about 'PCI\VEN_8086&DEV_A352&SUBSYS_B0051458&REV_10 continues.
Questions
- If the driver on the disk to be restored and the driver in True Image Universal Restore have the same name (but are different versions), is the driver overwritten? Does True Image verify that the correct driver has been presented?
-If the Universal Restore attempt fails, can I assume the original disk image is not updated and it is a simulation only? Each time I run Universal Restore it is only a simulation.
Would I be better off deleting the suspected drivers on the ' to be restored disk' and letting Universal Restore add them?
Thanks for your help
Steve
- Log in to post comments

Questions
- If the driver on the disk to be restored and the driver in True Image Universal Restore have the same name (but are different versions), is the driver overwritten? Does True Image verify that the correct driver has been presented?
-If the Universal Restore attempt fails, can I assume the original disk image is not updated and it is a simulation only? Each time I run Universal Restore it is only a simulation.
Would I be better off deleting the suspected drivers on the ' to be restored disk' and letting Universal Restore add them?
I would expect that AUR will select the most recent driver when more than one copy of the same driver at different versions are available but the key point is that a correct driver is installed.
The original backup disk image remains as a read-only file where no changes are possible, so any changes, if any are made, are only to the restored image on the target disk.
Just running AUR without applying changes is simply providing information on the actions that would be taken or of drivers that are missing / needed to complete actions.
Not sure what you mean by 'deleting the suspected drivers on the ' to be restored disk' - if drivers were included in the backup image that was used to do the restore to the target disk, then they will be on that disk but may not be being used if there is no matching hardware that needs them. Any additional drivers should be added to the AUR media or provided to the AUR app from other media when requested by that tool.
3) As suggested, I installed Win 7 Home Premium on a new 4TB hard drive and extracted the drivers to a file using Double Driver. I've applied all the Win updates. It is working perfectly, if only I could export my existing applications and files across from the old drive.
Unfortunately, Acronis cannot be used to migrate existing applications from one OS to be migrated to a different OS. You would need to do a new install of those applications on the new OS. You should be able to restore any user data to the new PC providing you are not going to overwrite any OS type data in the process.
On the new install I soon discovered that there are no Win 7 USB drivers for the latest Motherboards like Gigabyte Z390 UD. Both Microsoft & Intel haven't written any.
That is often the case with new PC's or Motherboards that are released after the end of life for an older version of Windows, and after the Makers have stop producing drivers for the old OS versions!
- Log in to post comments

Let me jump in here. You've had some very good help from both Steve and Enchantech. It looks like you're very close to having a solution to get the old Windows 7 disk to boot on the new hardware. All you should need is to successfully inject the driver for the AHCI controller into the old system. It's very good that you have a fresh install of Windows 7 running on the new hardware. That's the best source to obtain the driver you need. Follow this to get instructions to extract the driver from then new Windows 7 system.
Now all you need to do is inject the driver into the old Windows 7 system. I would not use Acronis Universal Restore to do this. I've found it doesn't work very well. You should inject the driver manually. You do this by booting WinPE recovery media and using the command line program dism.exe to add the driver. You need to determine two drive letters while in WinPE (the letter of the location where the driver is stored and the letter of the Windows 7 system where you want to inject the driver). Then issue the following command while booted into WinPE:
dism /image:C: /Add-Driver /Driver:F:\full_ path_to driver_folder /recurse
Where C: is the WinPE letter to the Windows 7 system and F: is the letter where the driver folder is stored.
- Log in to post comments

Thank you Steve Smith and Mustang for you help and advice, I really appreciate it.
Sorry for not getting back to you sooner. I've spent the last few days reading and learning all about drivers, the more I read the more I realise how much I didn't know.and still don't know eg windows stores multiple versions of the same driver eg atapi.sys for different devices.
By referring back to device manager on new Win7 drive, I'm able to locate the correct inf file and related drivers and version for the Standard Sata AHCI Controller.
amd64_mshdc.inf_31bf3856ad364e35_6.1.7601.18231_none_3b457059383c66e6
The drivers listed in device mgr of new install are not in the System 32 / drivers folder but in the Windows / winsxs folder. Not sure how Windows chooses which drivers to use.
I'll get back to you when I do a bit more research and I try Mustang's suggestion.
I did try to load the new inf and drivers into True Image Universal Restore but again for some reason it did not pick them up.
I may try creating a Universal Rescue DVD rather than a USB just to see if there is any difference.
Now that I have a fresh install of Win 7 on a new drive I may also look at migration software to move applications, files and seeings across.
Thank you
Steve
- Log in to post comments

What you're saying about the driver files not being in Windows\System32\Drivers is wrong. Windows will use the files in System32 and System32\Drivers.
I looked at a Windows 7 system using the Standard AHCI 1.0 Serial ATA Controller. I agree it is using mshdc.inf. You will find that inf file in Windows\inf. When I open mshdc.inf and look at the [SourceDisksFiles] section I see it requires the following 11 files:
msahci.sys
intelide.sys
cmdide.sys
viaide.sys
aliide.sys
amdide.sys
storprop.dll
atapi.sys
ataport.sys
pciidex.sys
pciide.sys
All 10 of the sys files are found at Windows\System32\Drivers
The one dll file is found at Windows\System32
You need to put the inf file from Windows\inf, all 10 of the sys files from Windows\System32\Drivers and the dll file from Windows\System32 in one folder. That will be the driver you need to inject.
- Log in to post comments