Found deleted files, but no file name, unable to recover. HELP!

[samshi]

Hi,

 

 Cause: delete files by mistake, then copy some files to this disk, then delete again.

 

 Recovering :  step 1,  deep scan with default setting, Recuva can't find the files I need.

                       step 2,  deep scan with all the options checked on actions tab, Recuva found the files I need. But the file names is empty so that Recuva can't recover these files. it shows a dialog with the unsuccessful reason is " The system can't find the directory properly ".

see attached pics.

 

pls help! thx.

 

 

 

[Augeas]

You could try unchecking 'Restore Folder Structure' in the Options box. You do not need to rescan. Try the recovery again.

 

The directory structure is held in the MFT. If the MFT record for the directory is overwritten then the structure can't be recreated. I don't know whether what you recover will be valid, though.

[samshi]

You could try unchecking 'Restore Folder Structure' in the Options box. You do not need to rescan. Try the recovery again.

 

The directory structure is held in the MFT. If the MFT record for the directory is overwritten then the structure can't be recreated. I don't know whether what you recover will be valid, though.

 

Yes, I unchecked   'Restore Folder Structure' in the Options box. But the files still can't be recovered. I guess, because these founded files haven't  file names, Recuva can't create the target recovered file . You can see in my attached pic, the filename column is empty.  Other files with filenames can all be recovered successfully.

[Augeas]

I can reproduce this. After doing part of a deep scan I found some files with no filename and no path. and with some data (Usually these no-name files are zero bytes). When I attempt a recovery I get the message 'The system cannot find the path specified' which I guess is more or less the same as your translation. But I can do an overwrite, of a few of them. And even copy some of the smaller images to the clipboard.

 

The files that show images have recognisable signatures, so I don't know why they aren't given a default file name, such as [001234].png, as other un-named files found in a deep scan are. A mystery, but I don't think much more can be done with Recuva.

[Alan_B]

How about the new release

    Recuva v1.51 is ready to download!

    Added Ext2 and Ext3 file system support
    Added recovery from volumes without GUID
    Improved SSD detection and support
    Improved Secure Overwrite on Windows XP
    Optimized FAT32 volume deep scan algorithm
    Improved partition detection on VHD images (Recuva Professional only)
    Improved Show drives options
    Minor GUI improvements
    Minor bug fixes

 

http://forum.piriform.com/index.php?showtopic=40660

[samshi]

I can reproduce this. After doing part of a deep scan I found some files with no filename and no path. and with some data (Usually these no-name files are zero bytes). When I attempt a recovery I get the message 'The system cannot find the path specified' which I guess is more or less the same as your translation. But I can do an overwrite, of a few of them. And even copy some of the smaller images to the clipboard.

 

The files that show images have recognisable signatures, so I don't know why they aren't given a default file name, such as [001234].png, as other un-named files found in a deep scan are. A mystery, but I don't think much more can be done with Recuva.

 

 

Yes. I agree that the english error message is  'The system cannot find the path specified' . Since the file has no filename, I think that is why Recuva can't recover these files.

[samshi]

How about the new release

http://forum.piriform.com/index.php?showtopic=40660

 

 

I tried this release, however, the result is same.  can't recover these no-name files.

[Augeas]

Since the file has no filename, I think that is why Recuva can't recover these files.

 

Recuva won't recover those files, but it's strange that it finds the clusters alright when doing a secure delete or copy to clipboard. After all very few files (if any) found during a deep scan have filenames, as the file name is held in the MFT not in the data clusters. Recuva handles those by creating a default filename. Why it won't on these few is a mystery.