Jump to content
CCleaner Community Forums


  • Content Count

  • Joined

Everything posted by Augeas

  1. It means, in the most basic terms, that what you are trying to play is not a video file. What has been recovered will be faithfully what is on the storage device. What is on the storage device is therefore not a playable video file (you can replace video with any type of file). Why is this so? It could be because the file has been overwritten, it's FAT32, it's greater than 4gb, it's an SSD, or it's some kind of coding that needs decoding (I have no idea how Kodak holds its files), or something else I don't know about. Can these files be recovered? There's not enough info (there's not
  2. The file count whilst running includes live as well as deleted files. If you are not seeing any deleted files in the l/h pane then possibly there is some selection criteria entered which does not match any file found. It sounds as if you were running a deep scan which I don't think finds RAW files.
  3. I am not confused. Thank you for your compliments, who knows whether CC commits to disk? I would say that it does. Misinterpreting on purpose? The phrase 'SSds were built with many writes to the MFT in mind' certainly implies some constructional abilities. It's actually nonsense, as it's NAND flash that holds the MFT (and all other files) and is either robust or not. On reflection I think you may mean robust in a software sense, and that is entirely down to the file system, in this case NTFS. The SSD knows nothing of the MFT and just doesn't come into it. I'm no
  4. It would be better for both brevity and comprehension if if HDDs were left out of this thread, as the title refers to SSDs. I said that CC will fill the disk, not write and delete files one by one. However, as described in detail in the link, zero-byte pages are maped to a default zero-byte page, the SSD doesn't write millions of zero-filled pages. Writing random data certainly will fill the addressable pages on the disk, and deleting them will return to the default zero-filled page mapping, just as you were if you hadn't bothered to do all that in the first place. The MFT is a file
  5. It is effectively random, as the existing data has been randomised before writing, and the overwriting pattern of zeroes is also randomised, so there is no concept of overwriting a one with a zero etc as many think (at least not in the last 30 years).
  6. To answer your question CC will, if you absoultely force it to, fill the disk with zero-filled files, and then delete them. However CC will warn against this, and indeed it is utterly pointless, achieves nothing, and will hammer the MFT and other system files. It does not even 'fill' the device. It is not, as you imply, 'the ONLY way to "erase" anything from solid state memories'. There is no way, using O/S software. TRIM will do it all for you. There's a lot here that is shall we say contentious, but I'm not going to get into a lengthy exposition. If you want you could read through http
  7. On the SSD the clusters will be mapped to a zero-filled page on delete with TRIM, so you will be recovering zeroes. There's not enough info on the attached USB drive to make a guess.
  8. It's been suggested a few times before, and although there is a likelyhood that some file will be modified or unavailable on a restart, that also applies to a certain extent when running Recuva anyway. I doubt if will be implemented, given how many times Recuva has been updated recently (around zero). I can't see any real reason why you should not work on your system drive whilst running Recuva. It will slow things down a bit but I'm sure you can live with that.
  9. Well, I can't open my files is pretty unspecific, and we're not clairvoyant. At a guess I would say that the files do not contain a correctly formatted header. Recuva copies clusters bit by bit with no alterations, so what's recovered is what's on the source disk. The reasons why the header is not what is expected could well be found in the somewhat slighted file (which saves typing it out every time we get this question). But I'm no expert.
  10. Read through this, the answer might be in there. http://kcall.co.uk/recovering files.html
  11. In advanced mode open Options/Actions and check boxes 1, 2, 3 and 5. Do not apply any filter to the search.
  12. You can put whatever extension you wish in the File Name/Path box, e.g. *.mp4
  13. That facility isn't available. You could filter by Video, which should drop some of the chaff.
  14. You're not doing anything wrong. With TRIM, which I would expect most O/S and drives have now, deleted clusters on an SSD are immediately mapped to a default zeroed cluster. The deleted data cannot be recovered by any means. Recuva will find the deleted file names and cluster addresses in the MFT, but the data has gone forever. If you look at the Recuva Info pane in Advanced Mode then the headers will contain zeroes. Unfortunately nothing and no-one can retrieve it.
  15. Augeas

    lost files

    Oh I dunno, you could always put .txt in the Filename/Path box (in advanced mode).
  16. Augeas

    lost files

    Deep scan will not find text files as they do not have a file signature thus the scan can't identify them as files. A normal scan (which runs before the deep scan) can find them (if the MFT record still exists) as it scans the MFT and the MFT holds the file name and cluster addresses of all files on the drive. If the text files aren't being picked up by the normal scan then there's little hope of retrieving them.
  17. None of us would be so fooish to wipe free space on an SSD, would we? We don't really know the mechanics of wiping free space (CC's mechanics) but we're pretty sure it allocates a large enough file to fill the disk and then deletes it. How is that file allocated? I would hope in big chunks for a start, but CC's code dates back to cro-magnon times so we can't really be sure. If it allocates initially in 1 gb chunks then the MFT record will very soon be full, and an extension record allocated. And another, and another, and then an index record, holding all the addresses of all the MFT recor
  18. In Advanced Mode select Options/Actions, check Restore Folder Structure. If a ? appears in a path then the folder info is missing and the path can't be completed.
  19. The MFT record for a folder contains the addresses of the MFT records of all the files in the folder. The MFT record for a file contains the address of the owning folder. When a folder is deleted NTFS removes the addresses of the files. Recuva reads the folder address in a file's MFT record to locate the owning folder, chaining back all the way to the root (if the chain is still extant). If a ? is shown as a folder it means that the backwards chain to the root cannot be completed, probably because the MFT record for that folder has been overwritten. Nobody knows whether you can recov
  20. It appears to have located a folder. Recuva doesn't list folders explicitly, but lists files and then builds up the folder structure (if required and requested) in a chain-back process. Deleted folders, as far as I can establish, are cleared of their list of files by NTFS, so finding a deleted folder is of little use, it's just a name. You are of course free to use whatever software you want to aid any file recovery.
  21. Augeas

    Ignored Files

    By default Recuva will ignore non-deleted, system and zero-length files.
  22. The first image shows no file system, the second shows NTFS. The odds of recovering a huge file after a partition and format are about the same as England winning a test match.
  23. Simple cleaning appeared recently. I decided to use it, but I did not think that after that all accounts and the history of visited sites would be cleared. I am very upset, now I will again have to recover all logins and passwords for autocomplete. When using simple cleaning, I did not see a single indication of such consequences, it was not indicated what would be cleaned when using it. I suggest you display a warning about clearing browsers data.
  24. Where did you read that? It is nonsense, Recuva reads files only. What was the state of the external drive? Why were you recovering files? How large is it? Were you running a deep scan? You can't see what Recuva is finding until it has finished the scan. How could you see files if it was 'almost done'? Do you mean scanning or recovering?
  25. How were they erased? It's rather a lot to lose by accident.
  • Create New...