Skip to main content

True Image Home Won't Load

Thread needs solution

I have Windows XP Home, sp3 with latest updates. Something happened to True Image Home 2009 and now it will not load. I get the attached error message. All my other applications, of which there are many, including Acronis Disk Director 11, load and run successfully. Windows opens normally. I reloaded True Image and it didn’t help.

What has happened and how do I fix it?

Attachment Size
Error.jpg 64.1 KB
0 Users found this helpful

Did you install anyting after installing ATI? If so, does disabling that program make a diff?

Did you try uninstalling and the reinstalling ATI? to do this I'd use msconfig.exe to disable all nonMS services and all startup programs. then uninstall, then reinstall. ONly takes f ew minutes.

you can get info on using msconfig here:
http://netsquirrel.com/msconfig/index.html

After reinstalling and rebooting, try ATI to see if it loads before you turn all the services and startups back on. If it works before but not after turning servces and startups back on, then there's a software conflict and it's trial and derror with msconfig to find which one it is. But most liekly the clean unisntall reinstall will do the trick if ATI worked before.

Do you have a backup when everything was working correctly? If yes, why not restore your system back in time to that point. Before you do, be sure you have copies of anything current between then and now so you can make everything current again.

There are some hints on the DD11 forum about procedures for installing dd11 with 2009 installed.

I actually have two computers side by side. The other one is a spare that I kept just for experimenting. The spare also has ATI and it also will not start and gives the same error window.

I deleted ATI with Revo and reinstalled it in both computers. No change. Same error window. There are not that many apps in the spare, so I'll do my troubleshooting with it. Maybe easier to delete apps than to mess with msconfig. I can't think of anything recently installed except DD11.

The 64 character activation code is a real pain! Supposed to be able to copy/paste it, but the app won't accept a paste.

I did make a backup of the spare, so if all fails I will try it. Would rather find out what the problem is in the first place. Would have to use the emergency boot disk since Acronis won't start.

Try inuninstalling DD and ATI then install DD then install ATI. Also, as Grover suggested, there's more info on DD on the DD forum especially re installing it with ATI on the pc.

to copy and paste key, try CTRL-C for copy and CTRL-V for paste.

Grover, could you please point me to the hints to DD11 procedures for installation with ATI 2009 installed? I can't seem to find them.

Stuart,
My reference must have been a figment of my imagination. I cannot find it either.

Here is other links which may help but maybe support will check this posting.

http://kb.acronis.com/search/apachesolr_search?filters=type%3Aarticle%2…

In my spare computer I deleted both TI and DD. Then installed TI followed by DD. TI works fine! The problem didn't originally result from a bad load, because I had reloaded TI several times. Can't explain. Next I will delete both and reload in the reverse order, although that was not the sequence previously. If that is successful I will try it on my main computer. If that results in success I don't know what to say. Will take a few days.

I deleted and reloaded TI and DD in my main computer. This time I did it from my original disks as well as the updated software. I got the same error message. I then tried the Acronis removal tool and got the same results on reinstalling.

I then Googled "Unable to initialize snapshot manager library" and ended up in the Acronis forum #3940. There is a long discussion about this kind of problem including instructions from tech support regarding much registry editing. Apparently this is an ongoing Acronis problem. I am certainly not confident with that much registry editing and don't know what to do at this point. I am confident msconfig is not the cause.

I don't know if Acronis tech support follows this forum/thread or not. The only way I can find to get to tech support is on a pay per incident basis, and I won't do that for this kind of problem. At this point I cannot do a backup of my system which is a scary place to be. I hate to do any more playing around on my main system because I've already been to the blue screen a couple of times and a failure to start normally requiring a start from the last known configuration.

Any more ideas would be greatly appreciated.

As a last effort, I deleted TI and downloaded the latest update. Also used the TI removal tool. Then tried to install the update. Got a blue screen. Upon rebooting, the TI icon was there and the program opened but it wouldn’t do anything. Add/Remove programs couldn’t find it and neither could Revo. To get rid of it I installed TI from the original disk and then deleted it. Deletion went ok, but when I tried to reboot, Windows was completely dead. Acronis emergency boot disk wouldn’t work because of some kind of a "sync error". Windows repair disk wouldn’t work. Sent it to the shop and they couldn’t recover it either, so had to wipe the c: partition and reinstall windows. Cost me $185. Installed basic TI and restored windows to a point just before the troubles began. Now I’m back on the air with TI, build 9646. It works and I’m leaving it alone.

As a result of all this, I learned/recommend a few things:

1. Before doing anything with TI do a backup.
2. Don’t try updating TI. If it works, don’t mess with it. Don’t keep fixing it ‘til it’s broke.
3. The removal tool may be version sensitive. Didn’t look into that. http://forums.majorgeeks.com/showthread.php?t=119351 shows how to remove TI manually but I just don’t think a piece of software should have to resort to this.
4. I have several emergency boot disks from TI made from the different updates and they all seem to work differently. Make the disk from the version currently in the computer.
5. Deleting TI doesn’t completely delete it, and what is left can cause the above problems. I Googled the issue and found several references to it.