Universal Restore Problem - Restore to Dissimilar Hardware
I'm not new to this process, so don't need a full education. I'm just stuck on the Universal Restore - can find some drivers and so when I reboot, I get a system error (before Windows 7). Here's a few details:
1. Motherboard - gigabyte 970a-dp3p
2. All drivers have been extracted from compressed file on the CD and put on a USB drive - I have added the top level folder and a few selected sub folders
3. Files it says it can't find:
PCI\VEN_1002&DEV_4390&SUBSY_B0021458&REV_40
PCI\VEN_1002&DEV_4396&SUBSYS_50041458&REV_00
PCI\VEN_1002&DEV_4397&SUBSYS_50041458&REV_00
PCI\VEN_1002&DEV_4399&SUBSYS_50041458&REV_00
PCI\VEN_1106&DEV_34838&SUBSYS_50071458&REV_01
4. In BIOS, SATA Type is set to Native IDE - I also tried AHCI (backup was not RAID)
That's it. Any help is greatly appreciated.


- Log in to post comments

Previous motherboard was almost identical - gigabyte 970a-dp3
I don't see those drivers on the CD at all either. I was able to find two of the drivers - 4390 (Sata) and 4396 (PCI to USB Host Controller). Can't find the others (4397, 4399 and 3483).
I changed it back to AHIC tried the whole thing again and same result.
- Log in to post comments

I suspect they are loaded by one of the numerous *.inf files, but not clear which one.
If worst comes to worse; you could do a clean install of Windows 7, run the chipset installation file, and then look for the drivers. Hopefully doing a clean install will not ask for any drivers in addition to the obvious ones. USB 3/3.1 are obvious, but you may be able to get to bootable stage without them.
Ian
- Log in to post comments

I checked most (if not all) of the inf files and didn't see those drivers. I am going to do a fresh install. With this computer it's not that big of deal since it's a gaming only computer and doesn't have many programs to reinstall. Disappointing though that the universal restore didn't use the new drivers.
- Log in to post comments

Glad that it is not too painful to do the installation. One advantage of using Windows 10 is that it usually has all the drivers you need (even for rather old systems). Looks like old and new motherboard have different chipsets.
Ian
- Log in to post comments

So, isn't the point of Universal Restore that you can restore to a MB with a new chipset? I've done that with other computers where the MB was a different manufacturer. Can't understand why it didn't work this time. All dissimilar hardware will have a different chipset. Again, disappointing.
- Log in to post comments

George, Universal Restore does provide the tools to try to prepare your backup from one set of hardware to work on a different set of hardware, but a lot seems to depend on how great the differences between the two sets of hardware are, and of course on the capabilities of the OS that is involved.
As Ian has already said, this is one area where Windows 10 lead the way in terms of its flexibility to work with different hardware.
Normally, you should only need to provide the new chipset and disk controller drivers to Universal Restore, and often, even these may not be needed, but there is no hard & fast rule that can be applied here!
- Log in to post comments

My question is how does Universal Restore know which drivers to use?
From my IT experience, I would think that either it has the data in a file, it somehow gets it from a chip on the motherboard or it gets it from Windows. In any case, it should know the exact drivers to load. For it to try to load the wrong drivers tells me that something is out of date. In my case it was clearly trying to load the wrong drivers since those drivers did not exist on the CD that came with the motherboard.
My problem is solved (by doing a fresh install), but would love to know exactly how Universal Restore determines the correct drivers. Any ideas?
- Log in to post comments

George, I understand the question but am not aware of any specific documentation that describes the inner working of AUR, so doubt that Acronis have either produced or published such details other than in their internal databases for their developers to use.
I have not know any other reports in these forums where users have had problems with incorrect device drivers caused by AUR.
The recommended approach when using AUR is to just create the media and don't include any additional drivers at first. Boot from that vanilla AUR media (after restoring the OS backup image to new hardware) then see what AUR says it needs to be provided for additional drivers, if any are needed.
- Log in to post comments
In reply to George, I understand the… by truwrikodrorow…

Thanks for the reply!
Your approach is what I did and it's worked two other times for me. Just didn't this time.
Thanks again.
- Log in to post comments