Skip to main content

SOLVED: Backup & Recover C: Drive -- ATI 2012 boots OK -- ATI 2016 crashes during O/S startup

Thread needs solution

On Windows 7 Home, I recently upgraded from ATI 2012 to ATI 2016.  I have bootable ATI 2012 and ATI 2016 recovery CDs.

To test that ATI 2016 would actually recover a full C: disk backup made by ATI 2016, I did the following:

  1.     With ATI 2012 still installed, I did a full backup of the C: disk to a separate HDD.
  2.     I then rebooted using my ATI 2012 recovery CD.  I did a full recovery of the C: drive using the backup just made in step 1 above.
  3.     I then rebooted to Windows 7 as usual.  This worked fine as it always has.  So I know that I a have a safe fall-back path.
  4.     I then uninstalled ATI 2012 and installed ATI 2016.
  5.     I then did a full ATI 2016 backup of the C: disk to the separate HDD.
  6.     I then rebooted using my ATI 2016 recovery CD.  I did a full recovery of the C: drive using the backup must made in tep 5 above.  The recovery indicated that it completed ok.
  7.     I then rebooted to Window 7 with the ATI 2016 recovery (step 6) but **this did not work**.  The boot started ok and the "Starting Windows" screen started showing the revolving coloured balls (although revolving unusually slowly).  ...but after a few seconds, it crashed and started rebooting back to the BIOS again.
  8.     With the ATI 2012 recovery CD, I did another recovery of the C: drive using the backup made in step 1 above.  This worked fine!

How can I get ATI 2016 to do a reliable full disk backup and recovery??  This is critical.

I would be happy keep using ATI 2012 but we have another new PC with Windows 10 on it.  So I need ATI 2016 to work there but it seems that may not be a very safe proposition.

Please help.  Thanks

Jerry

 

0 Users found this helpful

Jerry,

You are wise to verify ATI2016 operation.

Your problem probably occurred when making the backup.  Earlier versions used the term "Disk mode" or "Partition mode".  ATI2016 uses the term "Full Partition List" or "Short Partition List".  For the backup, you should use "Full Partition List" mode.  See pictures below.

Let me know if you made the backup using Full Partition List, and I will research the Restore options.

FtrPilot

Attachment Size
323344-125113.jpg 153.71 KB
323344-125116.jpg 161.62 KB

Thanks for your response.

I am about to try ATI2016 backup/recover once again and try your suggestion.

BTW, when I download the Install file, there are 2 choices:  Full and Web.  Do you know what the difference is?

Jerry

Jerry A wrote:

BTW, when I download the Install file, there are 2 choices:  Full and Web.  Do you know what the difference is?

I don't know the difference between Full and Web, unless Web refers to the Cloud version.  When I bought mine online, I bought the home version without the Cloud.  At completion of the transaction, the web site brought a page with links for the downloads.

FtrPilot

Well, I think I am on the track of what may be a very different cause of my ATI2016 recovery problem.  Here is what I found:

  1. I made another ATI2012 full backup of C:
  2. I then uninstalled ATI2012 and then installed ATI2016"Full".
    1. Uninstalling ATI2012 is not easy on my PC.  I have to use MicrosoftFixit.ProgramInstallUninstall.RNP.Run.exe
  3. During the reboot, the same boot/startup problem happened even though I didn't actually run the ATI2016 recovery -- I was just booting back into Windows7 !!
  4. I managed to recover using the ATI2012 backup from step 1 above.

So, my guess now is that the process of removing ATI2012 may have caused some serious problem with the registry or somewhere else??

I am going to try some other ways to uninstall ATI2012.  Darn, your would think it wouldn't be that difficult.

Jerry

My last post (#4) was absolutely correct.

The problem was not with ATI2016 -- neither the backup nor the recovery.

The problem was the damage done while trying to uninstall ATI2012 prior to installing ATI2016.  I suspect that using the Microsoft FixIt was the cause of some corruption, possibly to the registry;  however, I don't feel like spending yet another day tracking down the details.

If anyone else is experiencing similar problems removing ATI2012, then please carefully follow the instructions here:

https://kb.acronis.com/content/34876

...but please be very cautious about using the Microsft FixIt.  Make sure you have a useable backup and a Restore Point.

Thanks to FtrPilot for your thoughts

Jerry

Jerry,

Congrats on getting this sorted.  The one takeaway I hope everyone that reads this thread is:  Do a backup before starting any upgrade.  And for ATI 2016, practice a recovery.

Regards,

FtrPilot