Data Recovery Case File · Formatted & Logical Faults · Look for the Leftovers
A Save Interrupted Leaves Traces, and They Have Names
His enquiry is the smallest case in this archive and among the most answerable. "I tried to save a text document — a university assignment — and at the same time my laptop froze. I had to restart it in order to do anything. Then tried to open the file and couldn't. The program I am using asked for file recovery, however it failed to recover that file." Nothing is wrong with the drive or the machine, and what he needs is very likely sitting in a folder the application uses and never shows him.
| Media | Laptop internal drive in normal working order — single document lost during an interrupted save operation; host and storage unaffected |
| Reported situation | Document being saved when the host froze · machine restarted · document not opening afterwards · application's own recovery function attempted without success · no other files or system behaviour affected · assignment content required |
| Fault class | Single-file loss from an interrupted write — application temporary and autosave artefacts likely present; no device fault |
| Equipment used | No device-level work performed · application temporary, lock and autosave locations enumerated with hidden items shown · partial file assessed for extractable content · recovery scoped to the single document |
The decode: what a save actually does, and what it leaves behind
Why saving is not one operation: most applications do not write over your existing file directly, because a failure partway would destroy both the old version and the new. Instead they write the new version to a temporary file alongside it, confirm that completed, and only then replace the original. That sequence exists precisely to survive an interruption — and an interruption is what happened.
What that means for him: depending on exactly when the freeze occurred, the folder may contain the original file intact, a complete temporary file holding the new version, or a partial one. All three are better than nothing and none of them will be visible by default, because temporary files are hidden and named unhelpfully.
Where to look, in order. First, the folder containing the document, with hidden items shown — looking for files with the same name and an odd extension, or names beginning with a symbol, or a similar name with characters appended. Second, the application's own autosave or backup location, which is separate from the document folder and configured somewhere in its preferences. Third, the system temporary folder, where some applications write during a save.
Why the application's recovery function failing does not mean much: that feature looks in one specific place for one specific kind of artefact and reports honestly when it does not find it. It does not search the folder, and it does not look for the temporary file the save routine itself created. Its failure eliminates one location, not all of them.
What to do if a partial file turns up: a document that will not open may still contain readable content. Text-based formats can be examined directly and the text extracted; compressed formats can sometimes be repaired by tools designed for that format specifically. A file that an application refuses is not necessarily a file with nothing in it.
What must not happen while looking: heavy use of the machine. Everything discussed here is a matter of small files that could be overwritten by ordinary activity — so the search should happen before the laptop goes back into general use, and certainly before anything large is installed or downloaded.
Why this is a case worth including despite its size: most people faced with this conclude the work is gone and start again. The folder is free to look in.
On the bench
No device-level work was performed, the storage and host being unaffected. Application temporary, lock and autosave locations were enumerated with hidden items shown — a save routine writing a new version to a temporary file before replacing the original, precisely so that an interruption leaves one or both intact, with those artefacts hidden and unhelpfully named by default. The partial file was assessed for extractable content, a document an application refuses still frequently containing readable text, and recovery scoped to the single document.
The outcome
The temporary and autosave locations enumerated, the partial file assessed for extractable content and recovery scoped to the one document. Free assessment, and no charge where the answer is a folder you can open yourself. The decode: saving is not one operation. Applications write the new version to a temporary file, confirm it, and only then replace the original — a sequence designed to survive exactly the interruption you had. So the folder may hold the original, a complete temporary copy, or a partial one, and all three are hidden by default.
Document lost when the machine froze mid-save
Turn on hidden files and look in the folder the document was in — that's free and it's where the answer usually is. Applications don't write over your existing file directly, because a failure partway would destroy both versions; they write the new one to a temporary file alongside, confirm it completed, then replace the original. That sequence exists to survive exactly what happened to you, so the folder may hold the original intact, a complete temporary copy, or a partial one, all hidden and named unhelpfully. Check the application's autosave location too, which is separate and set in its preferences. And stop using the machine heavily until you've looked.
Show hidden files and look in the folder — or call Guildford Data Recovery on 01483 901310; temporary and autosave locations enumerated, partial files assessed for extractable content, free assessment.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.