Of course in other scenarios there may be another reason for this, but when it happened to me, as other people have posted, only Windows 98's fdisk /mbr could fix this problem. A couple of weeks ago I had to restore a TI of XP and it booted but stopped just before the welcome/logon screen. During the boot process, scandisk/chkdsk wanted to check the XP partition, and I could see that it had now been allocated drive letter H instead of C . Prior to the restore, there were two Primary partitions, and I had used Partition Magic 8 to delete both and create a new one using all the free space, so it wasn't the case that there was another, old C messing things up. This appears to be because True Image doesn't backup/restore the GUID of the partition (which makes a bit of a joke of the name 'True Image'!). So when XP tries to boot, it sees that the GUID of the new partition doesn't equal the GUID already allocated to C in the registry, so it assigns the next available letter (in my case H) to the new partition. It took a whole day of panic before I stumbled across the fdisk /mbr solution. I think I danced when it worked I really think TI should copy this GUID. I don't recall ever having a similar problem when using Ghost. If this problem can't be fixed (and I don't see why not), then TI should warn the user in big letters that they will need a working 98 boot disk to successfully restore a XP boot partition image. It's also rather pathetic that XP's recovery console doesn't have a command to either do whatever 98's fdisk /mbr does, or to clear the GUID assigned to C in the registry so that on the next boot the new partition is allowed to be C.