Skip to main content

ATI 2010 v6053 recovery boot CD crash (immediate reboot) when clicking What To Exclude, Backup Options, or Comments

Thread needs solution

I have sadly had to "upgrade" to ATI 2010 (v6053) from ATI 8, which has worked so well for me for years, and has a far superior interface (such as, the keyboard support actually works for the most part).  But I just built a new PC, and ATI 8 can't see the SSD drive (AHCI on or off).

I am trying to make a backup of my system from the ATI 2010 boot CD (so that I have the system state captured before anything is installed, even ATI).  But as soon as I click on What To Exclude, Backup Options, or Comments in the backup section, ATI immediately reboots my system.

I have tried this on 2 completely different computers with the same exact result.

I was able to do a backup, but it is not sufficient because I cannot add comments or set the compression level that I want.

Acronis:  How can you put out software that obviously did not go through even a few minutes of testing of such important functionality?  And when will you have this fixed? Can you give me ANY reason that I should not call my credit card company to have them refuse the charge?

0 Users found this helpful

I used the same build (6053) and had experienced the same problem with both the Linux and WinPE based ATI 2010 boot CDs.

I've spent over 40 hours trying / testing ATI 2010 Home (build 6053), and I can say for sure, there are a lot of bugs in it.

For this particular problem, what worked for me, is:

Before you click on What to Exclude, etc.

Be sure to select "Full" as the backup method. The default is "Incremental", and unless its changed to "Full" (at least for the first backup) it will crash when you click on What To Exclude, Backup Options, or Comments.

I was able to do an Incremental on an existing archive, but ran into two other bugs.

Also, if you click back onto "Backup Method" afterwards it sometimes crashes as well.

There are a lot of touchy work-arounds.

I had to request a refund because of these bugs.

Hello John and James,

Let me clarify this issue for you.

First of all, I would like to apologize for the inconvenience you experienced. I have checked our database for the similar issue and found several similar requests. As soon as we received the first request, we have forwarded it to our QA team and they were able to reproduce it. Then we forwarded the issue to our Development Team.

For now, this issue is fixed and already included to the next build of the product, which will be released soon.

For now, you can use a workaround given by James (thank you for that!).

Additionally to this, you are welcome to ask me any other questions concerning Acronis, and I will assist you further.

Regards,