Skip to main content

Unable to start computer after installing TIH 2010

Thread needs solution

Hello all,

I already am using TI(H) since version 7 and mostly error free!

A few days ago I bought the upgrade to TIH 2010 (version 13.0.5055). When installing on my system (Windows 7 RTM Ultimate 64-bit) the installation doesn't work. Then I'm ordered to restart my computer in order to continue the installation of TIH 2010... Alas, All I get is a BSOD! I cannot even start in safe mode in order to remove the program or parts of the program...

As you might imagine, I am not really amused with such a result.

What can I do to startup my computer? And how do I remove TIH 2010 completely from my system?

I'll go back to using TIH 2009, which works more than good enough (with a few caveats).

HansDZ

0 Users found this helpful

For the BSOD, if you have any media card readers connected to the computer, try disconnecting them.

If you created a backup image just prior to trying TI 2010, the easiest way to revert would probably be to restore that image.

Hi MudCrab,

That's just what I did. Restored the backup I had (lucky me). And yes, I have media card readers installed. Don't want to disconnect them, so I'm reverting back to a previous version of ATIH (the 2009 one, which worked fine enough)

This is the first time I've had such an issue. Lesson learned (or confirmed) make regular backups, in case it goes wrong

HansDZ,

If you have multiple drive letters assigned to the card readers, consider removing the drive letter assigned to any card reader you do not use. You can use Windows Disk Management to remove any unwanted drive letters.

GroverH,

Thanks for the additional info. I'll give this a go.

One question: when the installation of TIH 2010 works via this way, what will happen afterwards when I assign the drive letters again to the multiple card reader?

The problem with media card readers/drives will exist until Acronis gets it fixed. If removing the letters allows TI 2010 to work, I would guess putting them back would cause the error again.