I had previously used Acronis True Image Home, call it TI, v8, v9, v10, and V11, and never had a problem restoring images made with any of them, until I purchased a new state-of-the-art computer with factory installed Windows Vista. At first I noticed that virtually none of my TI Vista partition's backup image files were validating. Then I discovered that validation failure invariably led to image restoration failure. That was disquieting, so I downloaded Acronis Disk Director v10, call it DD, to enable me to move and copy partitions directly. Then I did two experiments using DD and TI. I used DD to copy my Vista boot partiton to another partition on another drive. Except for the Vista Volume ID and the much smaller partition size, I reasoned that the copied partition should be identical to the Vista boot partition, which was verified by running Chkdsk /r /x on the copy, getting no errors, and making certain that the copy's total bytes and numbers of files and folders were exactly the same as those of the Vista drive just before the copy was made. Then after rebooting, using Sysinternals VolumeID utility to modify Vista copy's Volume Id to make it identical to that of Vista's boot partition except for its size, thus creating a virtual clone of it, booting DD using its recovery CD, securely wiping Vista's boot partition, copying the virtual cloned partition to it, restoring the boot partition's size in the process, booting using Vista's DVD, and selecting repair Vista, I was very much relieved when I was given the choice of repairing either the Vista clone or the much smaller virtual Vista clone. After booting back into Vista, having found no errors after a Chkdsk /r was run, I made a new TI backup file of the error free Vista boot partition, mounted that file to a drive letter, and ran Chkdsk /r /x on it. To my dismay, an error was found in one of the mounted partition's clusters. To make matters worse, Chkdsk announced that the error could not be repaired because there was insufficient space on the drive. So while Chkdsk could find and localize the errors, it could not be used to repair them. I did manage to correct the filename of the otherwise perfect copy of a system file, but the unmounted image still would not validate. Thus either my system was introducing errors or TI was introducing errors in TI's partition backup file. For the last two weeks, I have been doing nothing but running diagnostic and stress testing programs on all my computer's hardware and software. I am eliminating sources of error one by one, hoping that I can find the cause of the TI backup file's corruption. I now have a shiny six week old computer that I can't trust. I have spoken on the phone with my new computer's technical support group, and they claim the fault must be with Acronis not being able to handle one of the new computer's hardware drivers, that the imaging software they are using works perfectly, and they have not had a single instance of a similar computer producing a Chkdsk error because of their intensive one week long "burn in" testing program. I have emailed Acronis support repeatedly about this problem for more than 30 days, using the same title as this thread, (the actual case number has not been listed due to privacy concerns), mentioned my computer manufacturer's claim 14 days ago, and have repeatedly asked if Acronis would be willing to help me determine the cause by providing either diagnostic or debugging software, but that request has not been responded to and no other helpful suggestions have been forthcoming thus far.