Skip to main content

Acronis 2016TI, Build 6589 Clones fine (HD to SSD/Nvme) in my Windows 7 pro system

History:

I have been using my Acronis True Image 2016, Build 6589, for cloning (disc to disc) since 2016.  It has worked fine and never had any issues, and I back up (clone) every 2 weeks or more if doing something.  I am running Windows 7 Pro X64, 32gb ram, intel processor on my Gigabye GA-X99p-SLI motherboard... and have been using my Western Digital Gold Enterprise drive (1tb).... with 2 external USB backup units (rotating)....  I have not upgraded 2016 ti since there was no reason. I use the actual clone disc method and make bootable.

I am also using old school and using MBR (despite limits of 2TB)., NO UEFI or Secure Boot (my choice) for about 8 years guessing - have it disabled.

Reason:  years ago when I had my ASUS MB running my Windows 7 Pro,  Microsoft had an update that totally trash my MB Bios info and/or UEFI, and also placed my drives on some "block" list in my bios/uefi, so no matter what I did I could not use any of my drives, not even by backups ... and lost a lot of data, took a while to recover.  My software is legal and I have my MS disc with SP1 as well and my oem key. 

This never happened in my life (in my 60's).  Despite complaint to MS and MS denying any problems..... 3 months later,  MS admitted a conflict with ASUS Mb's and MS's update. ASUS was working on a fix but too late.... so went to Gigabyte MB and never had any issues thereafter.  Hence, the reason I stayed with MBR vs UEFI and Secure Boot (that are now turned off).

Since then,  I have not used UEFI...  Since I am not going over 1tb nowadays anyway, the speed has been fine, and I have a Qnap server anyway for large storage.

OK, that said.  All my drives are the typical SATA drives and all work fine.  I decided to to finally break  down and get a PCIe NVMe SSD. My Gigabyte GA-X99p-SLI board supports the M2 / 32gb/sec SSD and is running Gen 3 x 4 2280.

The new ssd is a Samsung 970 Evo Plus and is acknowledged by my Windows 7 op system and is formatted unused at this moment. I was told my Acronis TI should work on cloning,  but checking Acronis web site I saw the 2014, 2015, 2017 and on up supporting the SSD, but no mention of Acronis 2016TI.  Others have said it will clone fine, and others reserved.....  I have backed up my SATA drive this evening 2 times..... used my 2 USB backups and cloned both of them just to have on hand for 'what-if " problems. Cloned disc to disc.

I will be cloning MBR to MBR from my Sata drive to the SSD Samsung 970 Evo Plus.

 I was told my M2 PCIe SSD will only work with UEFI but that seems to be incorrect at this moment as it is running, formatted and ready.

2016 Acronis TI Worked Fine and using my SSD drive right now to post this info !!!!!!!!!!!!

Summary:

1) Installed my Samsung 970 Evo Plus, Gen 3 x4 SSD (NVMe) drive. (power off of course)

2) Boot and Set my bios to makes sure I only booted to my existing WD bootable drive with Windows 7 on it.

3) Upon boot,  Windows 7 acknowledge the new 970 Evo Plus SSD.

4) Installed SSD drivers from Samsung, reboot again.

5). Set the new Samsung SSD to an MBR (not Gpt) for reasons above. Also Gpt needs UEFI and do not want.

6) Formatted the drive in literally 500 milliseconds

7). Ran Acronis TI in Admin mode

8). Selected clone (clone disc to disc).

9). Use options to keep drive and partitions the same.... so it is bootable.

10). Selected my Western Digital Gold Enterprise drive (primary "C") from...

11) Chose my new Samsung 970 Evo Plus as my drive to clone (to) and use.

12) Start.

13) System shut down and cloned perfectly in about 30 mins due to the slower HD (I think).

14) When finished, system powered off as desired (use the check box to power down upon complete)

15). Shut computer power off.  Disconnect internal HD and left inside computer for emergency.

16). Reboot, entered BIOS and set the new Samsung as bootable and boot option 2 (disabled).

17 Computer started and booted to windows 7 perfectly in about 2 seconds or less....

Writing this post with the new drive right now.  Clone went fine.

I know most are using UEFI, but wanted to let others know my 2016TI worked fine for me.  Also, I never upgrade software like this.  I will purchase new software and uninstall any old software.  I have heard of issues after upgrading vs a clean install using Acronis.

Hope this helps others.

Norm

 

 

0 Users found this helpful

Norm, welcome to these public User Forums.

Thanks for updating your topic with all the further details of your successful clone, glad that it is all working well for you!

Glad to hear it too!  Unfortunately, so many motherboards/bios can be quite finicky so a lot of people who try to clone from legacy drives to UEFI PCIe NVME are not able to boot so it probably varies by system, but ultimately, is not a reliable method when converting.  

However... at least with more current version of ATI (2020-2021) when you clone from WinPE or a fully booted OS running True Image, the clone will always convert the boot method based on the OS the Clone started from.  In some cases, this can be good (as would be here).  In other cases, this can be bad... for instance if you are wanting to clone a legacy/MBR drive but have started the WinPE in UEFI mode or booted into True Image on a UEFI Windows OS - the clone will be converted from legacy/MBR to GPT/UEFI.

Personally, I prefer that a clone always match the original drive exactly and then use backup/restore to manipulate changing a source legacy/MBR drive to GPT/UEFI if/when needed.