Case file · Logical & corruption · BDR-2025-1117
I Deleted the Files and Stopped.
It was an error with a normal cause: accidentally deleted original data (multiple files in excel and word)
from a USB folder, the only copies, never saved onto my laptop computer
. But then things became anything but normal. She did not save anything to the USB after deleting the originals; she carefully removed the USB safely; and then completely ceased all activity with it.
Same symptoms on your desk?
01273 964902
The decode.
Deletion does not eliminate or destroy data. Instead, when you delete a file or document, the operating system flags the directory entries for those files or documents as available for use by other programs, and then releases the associated disk space (clusters) for use by another program. However, until a program overwrites the deleted files or documents, they are still sitting there intact. Her discipline in this case prevented any program from overwriting the deleted data. One flash-based detail is important to know about flash devices today: many can perform some type of house-keeping (cleaning) process on their own to erase blocks that have been freed up for use by other programs. Therefore, "don't use" really means stop powering it, not just "do not continue to write to" the device, which is what she did.
Equipment on this case.
How a job runs here →| The system | What it did on the day | Why this tool |
|---|---|---|
| PC-3000 Flash | Read the stick at a low level, with no writes and no housekeeping triggered | Reads memory chips directly, with a current chip database for automatic identification |
| R-Studio Technician | Recovered the deleted directory records and their cluster chains | Broad filesystem coverage and dependable RAID re-assembly |
| UFS Explorer Professional Recovery | Cross-checked the results and confirmed the documents' internal structure | Stronger than most on the awkward filesystems — APFS, ReFS, XFS, ZFS, Btrfs |
At the bench.
Image before recovering, even on an easy case
The stick was read once with a low-level read operation to produce a working copy. A simple low-level read operation is not merely ceremonial following a straightforward deletion; it eliminates the possibility that you may inadvertently trigger any house-keeping processes that might occur if you ran your recovery software directly against the original flash device. Using a duplicate copy during recovery removes that risk entirely.
Recover the records rather than carving blindly
The deleted directory entries remained in place, with their cluster chains intact, because nothing was written to the stick after they were deleted. Therefore, recovering using that information restored the files with original names, folders, etc., as well as timestamps. Carving by content would have given the same data back as anonymous documents.
Open every file before calling it recovered
All recovered spreadsheets/documents were opened for a check, because an Office file can be structurally present and still be damaged inside. In all cases, the Office files opened correctly. This is what you expect when nothing else has been written over those files.
Where it ended up.
As expected, every single deleted file was recovered and opened cleanly, with names and folder structure intact. The least dramatic recovery case on this page; just like it should be. Textbook loss, textbook recovery method, textbook result.
Related on the index.
More from Logical & corruption.
Recognise your own drive in this story?
Same rule as every case above: power it down, and let the diagnosis be free before any decision has to be.