Using TI 9.3677 in Boot Mode to restore Files and Folders (F&F) to a new location produces some corrupt files & directories. I'm testing with the file: TrueImage9.0 User Guide.pdf TI validates the F&F archive, and reports the restore operation as successful. But, as the Screen Shot below shows, the TrueImage PDF file is corrupt and unreadable, and won't open. And, the newly created directory "Drive (H)" is corrupt, and cannot be deleted, at least not in Windows. I've tested this several times to both internal SATA hard drives and an external USB hard drive with the same results. Corrupt directory, and a PDF file that looks fine, until I try to open it, then the error message below. Interestingly, a small text file restored in Boot Mode on the same restore operation came thru intact, and opens fine. So size may matter here TI9.0 UserGuide.pdf is 2.2 MB, while the Adaptec USB Driver Readme.txt is 9 KB. Boot Mode TI can restore the PDF file to the original location successfully. TI running in Windows XP can also restore the PDF file to a new location intact, with no corrupt directory. Boot Mode TI can restore the drive partition image with the PDF file successfully. In fact, the only way I've found to clean up the corrupt directory is to either backup the rest of the files and folders on the partition (leaving out the corrupt directory), reformat the partition, and then restore the files and folders, or, to use TI to quickly restore a clean Image of the Partition. Is this a known issue, and will it be resolved in the next build? I've searched these forums, and found a few related reports, but not this exact issue. I'd like to know if this is unique to my system -- though I doubt that it is. Seems related to the original or new location, and not hardware dependent. If anyone is up for a test, please try using TI Boot Mode to restore a .pdf file to a new location, from a Files and Folders Archive. If you do, either use a partition you have nothing important on, or be prepared and make an Image of the partition before you run tests. When I first encountered this, it was on a full partition with 70 GB of TI Archives. Cleaning that up took some time. Windows' support website suggested the cleanup option of backup intact files/format partition/restore. Here's a Microsoft support link to what might be a similar corrupt directory problem: http://support.microsoft.com/default.aspx?scid=kb;en-us;246026 Windows Support says Checkdisk won't see the Master File Table naming issues, and Checkdisk did not resolve them here. The drives are NTFS. File security settings (preserve or not, on creation or restoration) don't affect these results...File ownership didn't effect the corrupt directory.