Salta al contenuto principale

Problem restoring windows 10 MBR full backup to GPT

Thread needs solution

Hello,

I'm trying to restore a full backup of my windows 10 mbr to gpt with this tutorial but no sucess http://www.acronis.com/en-us/support/documentation/ATI2017/index.html#26852.html

My installation is restore to mbr and not gpt, i don't understand.

Plesae help me

Best regards

0 Users found this helpful

Check if you started your recovery media with EUFI option not CSM (check bios for UEFI/CSM boot)

I would make sure you can restore it as MBR first and make sure that works.  Are you restoring to the same system or trying to move to another computer?

Once you're sure that restoring in the original MBR is working, then try to restore as GPT (it's actually UEFI which uses GPT formatting).  However, in order to restore an MBR OS as UEFI..

1), your system must support UEFI,

2) the bios must be set to allow UEFI booting and usually requires secure boot be disabled too

3) and once the system is restored in UEFI, you need to go into the bios and make sure the Windows bootmanager order shows "windows boot manager" as the first option and not the SATA disk #, or some other media like a USB flash drive or the DVD rom

Hello,

yes i'm starting with uefi boot my recovery medi

my system is windows 10 ans asus x99 deluxe 2 so yes it support uefi

but aconis not restore in UEFI only MBR

The system is the same also same SSD

The only possibility i have find is to reinstall windows 10 in uefi mode to create GPT disk , uefi partition and recovery partion and restore my only C partition at same place that windows install => so my system boot in uefi.

In tutorial acronis can do this in one step but not good result => BUG ?

 

 

When you select the partitions to be recovered in the Recovery Media do you get a messsage the the disk will be converted to GPT?  If not then that means that the disk is already GPT formatted or, you did not boot the machine in UEFI mode.

If your target disk is formatted MBR, you boot the Recovery Media in UEFI mode (note: UEFI should precede the name of the boot media shown in the system bios when you select what to boot), and the image you are restoring is that of a 64bit OS install then you will get the message about conversion of the disk to GPT and the result will be a UEFI boot.

If this is not working for you then my suggestion would be to covert the target disk to GPT first prior to the restore using Windows Diskpart.  You still mut insure that you boot the machine to the Recovery Media in UEFI mode.

I had to do what Oliver did too. Picking the complete MBR always restored back to MBR. The Acronis recovery software was absoutely in UEFI mode (it booted via the UEFI interface). I had Disparted the drive and made it GPT prior to the restore. Tried it many different ways, but it always came back as MBR. So I installed Win 10 and restored just C: and that got me much closer.

For anyone else that might have this problem, there was an added twist to mine. I was also going from RAID to ACHI. I noted here

Acronis states "Your old and new hard drives work in the same controller mode (for example, IDE or AHCI)." So that could have been my problem, I was going from RAID to ACHI. There is a really simply way to fix the change in Windows from RAID to ACHI - found it here

  1. Right-click the Windows Start Menu. Choose Command Prompt (Admin).
  2. Type this command and press ENTER: bcdedit /set {current} safeboot minimal
  3. Restart the computer and enter BIOS Setup (the key to press varies between systems).
  4. Change the SATA Operation mode to AHCI from either IDE or RAID (again, the language varies).
  5. Save changes and exit Setup and Windows will automatically boot to Safe Mode.
  6. Right-click the Windows Start Menu once more. Choose Command Prompt (Admin).
  7. Type this command and press ENTER: bcdedit /deletevalue {current} safeboot
  8. Reboot once more and Windows will automatically start with AHCI drivers enabled.

 

 

 

Well, I have never had a failure like that.  When booting the recovery media making the boot media first in the boot order (there might be 2 entries shown for the boot media, one is preceeded by UEFI which is the one you want to use to do this) and booting the machine in UEFI mode has always resulted in a UEFI/GPT converted disk for me.

I would suggest that if this is not the case for you that you open a support ticket about the issue.

I absoutely booted from and in UEIF recovery. As noted in my post, the Acronis recovery media notes UEFI. I got this working (no need to open a case) by following the steps I posted. I posted to help others that might have the same issue. You may not have been going from a RAID controller configuration to a ACHI controller configuration, as I also noted in the post. The Acronis documentation for going from MBR to GPT states:

"Your old and new hard drives work in the same controller mode (for example, IDE or AHCI)."

I think there is an issue of it converting to GPT when the controller changes. So it can be done, but not as easily as if the hardware controller is not changed. In such a case, what worked for me was - controller set to ACHI, install Win10 to fresh GPT, Acronis recovery of only the C: partiton to the fresh Win10 install, boot Win10 to recovery mode (which happens automaticlly because Win10 still can not boot, I assume because it is still configured to run from a RAID controller), Go to Advance/DOS and use the steps above to set Safeboot/Minimal, Reboot Win10 (Win10 now starts in safe mode with basic Disk I/O), go to Admin/DOS and set boot mode back to normal. Which as noted HERE is how you would do it if you were just changing controllers.

I'm guessing the easier method might have been to change the controller from RAID to AHCI FIRST using the method referenced, then backup and go from MBR to GPT using the Acronis recovery.

I do appreciate you posting back!

Yes, if you change the controller / SATA mode in the bios - you should prepare the OS before making the change in the bios.  Windows 10 handles this much better than previous OSes, but still not always guaranteed.  Here is the MS KB Article about this: 

https://support.microsoft.com/en-us/kb/922976