Skip to main content

AUR can't find OS

Thread needs solution

Hi All,

I'm trying to migrate my son's PC to a newer (but not new!) motherboard, CPU, drives and Graphics card.

Old is a Gigabyte 890a with a 945 and new is a FX6100 on a 970A-UD3.

He lives about 30 miles away and I didn't want to leave him without a PC so I used ATI to back up his PC to an HDD and brought it home.

I couldn't Rescue Media Builder to create a USB Media that didn't randomly reboot the PC so I attached the new drives to another PC and used Backup to restore the drives and dropped them back into a case.  I followed all the steps for this on the Acronis website.

I'm now trying (and failing) to get AUR to find the OS on the new drive.  The drive can be seen but isn't recognised.

Any suggestions gratefully accepted!

Regards

Mark

0 Users found this helpful

Mark, the most likely cause of the OS not being found here is that the old and new(er) systems use a different BIOS boot mode for the Windows OS, i.e. one uses Legacy, the other uses UEFI.

On the original computer, run the command msinfo32 from within Windows and check what is shown for the BIOS mode used by Windows.  If this isn't shown, then you will need to go into the BIOS settings and check what is set for the Boot priority or device.  For UEFI systems, this will show as Windows Boot Manager, else for Legacy systems, it will show the actual disk drive.

Your newer computer needs to support the same BIOS mode, and when restoring the backup, the Acronis Rescue Media needs to be booted using the same mode too to avoid converting the backup.

See KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media

Hi Steve,

 

OK success.  I made sure the BIOS Modes matched and recreated the Rescue Media.  This time I used the Linux Based Bootable media not Windows based.  I also turned off most of the Intergrated Peripherals in BIOS that I didn't need like the sound system.

I then restored my backup directly via the new motherboard rather than attaching the drives to my main PC.  I still couldn't  get AUR to see the OS, but when I tried to boot without using it, Windows 10 just said updating drivers and booted sucessfully.  I guess going from a Gigabyte 890 to a Gigabyte 970 board, the critical components were close enough to work.

Thanks for your help.

Regards

Mark

Mark, thanks for the update / feedback.  AUR tends to be needed less with Windows 10 systems as it is more capable of handling hardware changes & differences than earlier versions.