I just tried the free version of Paragon BU/Rec 10.0 to clone my Win7 install. It's on a 100GB partition, but only uses about 7GB. I have three physical drives, and I just use the BIOS to pick which one to boot from. So the source partition was on one drive, the target on a second, and I'm running Paragon from the third. So there should be no problems with locking or whatever. The backup went like a dream --- took just three minutes. Tried restoring a few individual folders, the data seemed fine. Then I tried to clone it to another drive. The target partition was 50GB. Smaller than the source, but way bigger than the data. Paragon didn't complain, about that, but I had serious problems. First, even though I am doing a restore at the partition level, it was writing the files to the new partition one by one, so what took three minutes to back up took over 20 minutes to write back. Finally the progress bar hit 100%, and I was anxious to see if it worked.... but it kept writing. It went on for another ten minutes, then a Win7 error box popped up and said Paragon ended with an error, and I had the option of closing it, or looking for a solution online. I closed it. I've read that the Winsxs folder is really a maze of links and mount points that makes it look a lot bigger than it really is, and I suspect that Paragon couldn't figure it out, and was writing stuff in a loop. But I'm not going to try to verify that, because there is a bigger problem. I looked at the target partition and it seemed to have everything else right, so I tried booting from it just to see what would happen. Wouldn't boot, got "NTLDR missing." That is not a Win7 message. Win7 looks for bootmgr, not ntldr. I thought a while, and remembered that I had wiped the target partition before all this, and I left it unformatted, so Paragon had to format it. And apparently, it formatted it the way XP does, not the way Win7 does. I looked at my bootsector with a hex editor, and sure enough, it was an XP bootsector. So I formatted the target partition again from within Win7. I looked at it with the hex editor, and it had all the right bootmgr code. I started the restore again -- and Paragon says it's formatting the partition. I cancelled the restore, looked at the sector, and Paragon had reformatted it back to XP, even though it was already formatted for Win7, and otherwise empty. So, OBVIOUSLY, this is never going to work for Win7. If it just copied the partition back the way it was, it would be fine, but it's not doing that -- it's formatting the partition, then copying the files back one by one. It takes ten times as long, fails after all that time, and destroys any chance of booting with Win7. But my question is, what has been happening for the last five years? I've never used Vista, but it uses the bootmgr code, too, so Paragon would have broken any Vista partition just like it did my Windows partition. And this is a 2010 product, so what is going on? Did Paragon ever work with Vista? If it did, why doesn't the free 2010 version know about bootmgr? Is the free version something they wrote in 2001 and that's why they are giving it away?