Hi MudCrab, I'm sure my Vista had been previously repaired. It's been through the wars of multiple testing. I know it's been restored with TI many times and also with Vista's Backup solution at least once. I have VistaBootPro installed and it shows some interesting information. On the screen that shows BCD Settings I see thee different sections for Windows Boot Loader. Two of the three are labled (recovery) in the desription. You need to check the "All" radio button to see them. This led me to the registry at HKLM\BCD00000000. You can drill down to see Objects. These Objects seem to represent identifiers, resume objects and resume from hibernation objects amoung others. I did a fresh install of Vista on a wiped drive. On first boot I looked in the registry and found there was no BCD hive. The system then downloaded some updates and wanted to reboot. I let it. When it came back up, I looked in the registry again. Now there was a BCD hive. It showed 11 Objects. I did a ful disk backup to test your senario. I got the same result as you. Restoring the system partition and the MBR (not the entire disk) on top of the existing Vista partition produced a winload.exe missing error. Restoring the entire disk worked. This showed that my previous results were better because the sytem had been repaired before the image was made. Next, I created a logical data partition on the fresh Vista disk for data. I backed up just the system partition and the MBR with both TI10 and Paragon Hard Disk Manager 8.5. There was no way to get TI to restore the system partition on top of the existing partition without doing a Vista Statup Repair. Paragon Hard disk Manager 8.5 restored just the system partition without a hitch. I noticed the last message it gave during the restore process was something about updating the Boot Configuration Data registry hive. Vista booted up like nothing had happened. I looked at the BCD hive and I only found 11 objects. VistaBootPro still only showed one entry under Windows Boot Loader. Then I went back and restored with TI and ran a Vista "Startup Repair". Vista booted up and found new hardware and required a reboot. After I rebooted, I looked at the BCD registry hive. Now there were 13 objects. VistaBootPro now showed two Windows Boot Loader entries. The one labled as (current) also showed as (recovered). Aparently, these two extra objects are helping TI handle a restore after you take a new image. These new results are somewhat disappointing. Paragon HDM is looking pretty good. It also runs nicely under BartPE in case the Linux Recovery CD doesn't support your hardware.