If you search this forum for the word "corrupt," you will get 1,000 hits (the maximum allowed by the search function). Trueimage is clearly the best backup software for Windows, but it may be the worst restore software, because of this bug. Obviously, backup without restore is like write-only memory: Not very useful. The purpose of this post is to collect, from all users, ideas and workarounds that can help avoid this problem, or can help deal with it once you are stuck trying to restore from an archive that is probably still OK, but which TrueImage is insisting on calling "corrupt." I'll start by sharing what I have learned, and then summarize at the end of the post what I recommend. If you respond to this thread, please try to limit those responses to things you have tried that worked, or seemed to work. There are lots of other threads where people bash Acronis. I'm trying to fix problems here, not pile on. Here is what I have learned from my own experience, and from reading dozens of those 1,000+ posts that mention the word "corrupt." 1. Validating the backup at the time of the backup provides absolutely no assurance that you can use the backup. After first experiencing the "corrupt archive" problem earlier this summer, I then changed my backup practice so that I ALWAYS verify/validate the backup. However, when it came time to use the backup, the validate failed. 2. Copying the backup from an external USB drive to an internal drive will often (but not always) cause it to validate correctly. I have over ten external USB drives, and this problem of failing validation on an external drive does not seem to be associated with any particular chipset. Also, I have tried this on my desktop computer as well as several laptops, and found the same problem, so I don't think it is associated with any USB chipset on the computer (all were from different vendors). Also, each computer had different versions of XP (Pro, Home, Media, with SP1 on some and SP2 on others). So, my preliminary conclusion is that USB support in TrueImage is flaky. What I cannot understand is how the image can validate correctly at the time of backup and then fail validation at a later time. Is there a date/time check of some sort that is failing? (I helped the Second Copy people track down something like this many years ago). 3. Corollary to #2: Copying the TIB to a Firewire drive sometimes will make it validate correctly. I have a FAT32 formatted Firewire drive and was able to copy a "corrupt" TIB file from my USB drive to the Firewire drive. It validated just fine, and I was then able to restore my computer from this copy (this is how I finally solved my problem this morning). 4. Bad memory is a red herring. Many responses from Acronis ask the user to test memory using Memtest86. I have done this and verified, of course, that my memory is just fine. I have an EE degree and have run three software companies. Believe me, if memory is flaky, you KNOW it, and it will show up, usually as crashes with BSOD, when running all sorts of programs. Also, I doubt that thousands of people are having memory problems that only show up with one application. I am certain that somewhere in the past few years, Acronis tech support did actually have a user with corrupt memory, but let's face it, all the corrupt memory computers didn't suddenly find there way to this one forum. Also, I defy anyone to find even one user in these forums that wrote back and said that their validation/corruption problem had been cured by changing memory. This, despite the fact that this suggestion is given in almost every post about this problem, and many of the poor users dutifully let memtest86 run overnight, and then report that they still have the problem. 5. Backups which validate when using the Windows version of the software FAIL validation when trying to do a restore from the Acronis boot media. This is particularly nasty. This morning, while trying to restore my C: drive, I ran into all the problems already listed, but finally managed to get a reasonably recent image to validate. However, when I booted using the recovery media and ran the full version (not the safe version) of Acronis TrueImage, and I asked to restore the image, I chose to first validate the image file, and this validation failed. That validation failed, even though that exact same image, residing on that drive, had passed validation just minutes before, when validated from the main Windows version of TI. I am using TI 9.0, build #3854, but based on posts in this forum and elsewhere on the Internet, version 10 doesn't seem to have fixed these fundamental problems. Unlike others, I have had a reasonably good experience with tech support, although they are extremely slow to respond, sometimes taking weeks. However, they really don't seem to be on top of this one, and it is going to ruin this product if it doesn't get fixed. Read the reviews on Amazon and elsewhere and you'll see what I mean. Acronis employees: If you want to still have a job, you've got to fix this!! This is the sort of thing that causes software companies to cease operations. My purpose in writing this post is to ask anyone if they have discovered a pattern to these problems so that we can try to develop some workarounds. Such workarounds often can help the vendor figure out a permanent solution to the problem. So far this is my one workaround: 1. Copy the archive to another drive, preferably internal. Firewire also seems to work better, although my only Firewire is formatted with FAT32, so that may have something to do with it. So, does anyone else have something that has definitely worked, and is something they themselves have tested?