This problem (or feature) has been referenced before, but not in much detail. Several posters has run into problems with this, mostly in the DD forum when trying to setup multi-boot systems. When using the latest build of TI 10 (4,942) and doing a restore, TI places the restored partition into the same partition "slot" as it was when it was backed up. If the original image was taken from the partition stored in position 1 of the partition table, then it is restored back to that same "slot" even when restored into a different partition. Furthermore, TI also automatically changes any XP boot.ini files in any affected partitions to reference the correct partition entry. This causes a lot of confusion when multi-booting when you're not expecting this to happen. Here is an example of the procedure and how the changes are made. The test image was created from an image of XP created in the FIRST partition (boot.ini referencing partition(1)). The test hard drive has three partitions, 20GB, 40GB and 60GB. These are shown like this in DD after restoring the XP image to the first partition (the 20GB partition): The original partition table looks like this: The boot.ini file in the 20GB partition is referenced as partition(1). Now you restore the same image into the second partition (the 40GB partition). The partition table is updated to the following: As you can see, the original second partition is now first in the list and the original first partition in the list is now second. The third partition in the list has not moved. The boot.ini file in the 20GB partition (now the second partition in the table) has been modifed to partition(2). The boot.ini file in the 40GB partition (now the first partition in the table) has been left as partition(1). Now you restore the same image into the third partition (the 60GB partition). The partition table is updated to the following: The original third partition is now first in the list. Then entire partition table order has now been reversed. What started as 1,2,3 is now 3,2,1. And all the boot.ini files have been updated automatically by TI to reference the correct entry in the partition table. Now, if you again restore the image to the first partition (the 20GB partition) then this is what you get: Physical partition one is now back in the first position in the partition table. Note that partitions 2 and 3 are still reversed. Again the boot.ini files are updated automatically to be correct. What does this mean? It means that if you're using TI to setup a multi-boot system, that you'll have to understand these changes because the boot manager may or may not allow the system to boot correctly. Most boot managers are not expecting the partition table order to change. More to the point, why doesn't TI only change the restored partition? If you restore an original partition(1) image into the third physical partition (partition table entry 3), then TI should just modify that boot.ini file to reference partition(3) instead of placing it into the first "slot", reordering other partitions and modifing boot.ini files. These changes are also not noted in any of the build "change logs" by Acronis. This causes even more confusion since the different builds work differently. TI 9, build 3,677 DOES NOT change the partition table order, nor does it change any boot.ini files. This build leaves everything as expected. You must modify the boot.ini file manually. TI 9, build 3,854 changes the partition table order, but DOES NOT update any boot.ini files. TI 10, build 4,942 changes BOTH the partition table order AND updates all affected boot.ini files. These are exactly the kind of changes that should be included in a detailed change log for new builds. Acronis has posted that they will include detailed changes with new builds, but it remains to be seen if they'll follow through with it.