Skip to main content

Back up fails with unspecified C++ runtime error

Thread needs solution

For a year or so I've been using True Image Home 11 successfully to back up a whole disk image of my C:drive. Recently I decided to move all of my photos to a separate internal drive on my PC and intended to set up a scheduled Acronis backup of the photos folder here to an external hard drive (different from the one I back my C:drive up to).

But after 29% of the backup done it fails (every time) and I just get an uninformative "C++ runtime error" dialog come up.

I would welcome some advice on this please.

0 Users found this helpful

When you say True Image Home 11, are you talking about ATI v11 or ATI 2011?

So that you know, both products are not supported any longer. The standard fix would be to uninstall, reboot and reinstall. With 2011, you should also run the cleanup utility before rebooting http://kb.acronis.com/content/14871 .

If you don't solve it this way, I am afraid you will have to upgrade or do your backups from the recovery CD.

Strictly speaking, 2011 is supported, and will be until TI 2013 is released. However new updates to this version are not released, so when the problem is crash, and solutions like reinstall don't help, the ultimate solution from the support (after you buy PPI) may be free upgrade to 2012.

Thanks for the replies both. I'm not sure what the difference between "ATI v11" and "ATI v11" is. The Help>About file says:

Acronis True Image Home version 11.0 (build 8,101)

What is PPI?

To be more specific, the dialog box that comes up is title "Microsoft Visual C++ Runtime Library". There is a button with no label and the body of the dialog has no text - just a cross icon on a red background.

PPI is 'pay per incident' that is only support option (other than recovery issue) available for 'consumer' products (not subscription-based like Backup & Security or online backup) after initial 30-day period. But as you have version 11.0 (not 2011) it is not supported at all. Even if there is an issue with program code that can't be resolved with reinstallation or verifying you RAM with memtest, support (most likely) will suggest you to upgrade to 2012.