When TI 11 restores an image of a C: drive (Windows XP) it always changes the system registry hive C:\WINDOWS\system32\config\system. This can be seen by comparing a hex view of the restored file against the file in the archive (mounted on a virtual drive). Usually it chops the end off the file, often just zeros but sometimes non-zero values. Occasionally it also changes values throughout the hive. This happens even when restoring the image to its original partition . Things are even worse when restoring to a different partition. Not only does it make extensive changes to the system hive but it also changes all the boot.ini files it can find, even on completely different drives. It may have made other undocumented unwanted changes that I haven't found yet. I have a multi-disk multi-boot system and am able to make the necessary changes to the registry and boot.ini files myself when restoring images of the C: drive to different partitions, but I don't want to also have to find and undo the changes that TI has inflicted. TI changes these files even when doing a sector-by-sector restore from a sector-by-sector backup. How can force it just to restore the 'true image' without any unwanted side effects? I changed the post restoration command from "Use commands set by default" to "Use commands" with no command specified, but this had no effect. When I specified a command to rename the file to "not_system" to prevent TI from recognising it this ran OK, but too late because TI had already changed the file. Is there any way round this problem in TI 11? Can TI 2009 restore a 'true image' without changing critical system files?