Data Recovery Case File · Solid State & Flash · Cancelling Stops the Rest
A Bulk Deletion Processes Items One at a Time, and Cancelling Does Not Reverse the Ones Done
Her enquiry describes an action she thought she had stopped in time. Pictures and videos being deleted accidentally, where she "cancelled the deletion process, however the files are nowhere to be seen on the laptop or in the recycling bin." Cancel prevents the remaining items from being processed — it does not restore the ones already done, and where they went depends on how the deletion was issued.
| Media | Solid-state system drive in a laptop — bulk deletion of images and video interrupted by cancellation; affected files absent from both their folder and the recycling area |
| Reported situation | Bulk deletion of pictures and video begun in error · deletion cancelled by the owner during the operation · affected files not present in their original location · affected files not present in the recycling area · content held on a solid-state system drive · recovery sought |
| Fault class | Partially completed bulk deletion with bypassed recycling — entries removed and blocks released; recoverability governed by block-release processing and subsequent writing |
| Equipment used | Cancellation understood as halting remaining items rather than reversing completed ones · machine removed from use before assessment · imaged write-blocked at the block level before any scanning · unallocated regions examined for retained content · translation layer state assessed for block-release processing |
The decode: what cancel did, and why the recycling area is empty
How a bulk deletion actually runs: as a sequence. The system works through the selected items one after another, and at any moment some are done and the rest are pending.
What cancelling therefore achieves: it stops the pending ones. The operation ends where it had reached, and everything already processed stays processed — which is why some of her files are gone and, quite possibly, others are not.
Why she may not have noticed the survivors: a partially completed deletion leaves a folder looking wrong rather than empty. It is worth checking carefully what is still present before assuming the whole selection went.
Why the recycling area matters, and why it is empty: ordinary deletion moves items there rather than removing them. An empty bin after a deletion means the items bypassed it, which happens in several specific circumstances.
What those circumstances are: a deletion issued with the modifier that skips recycling, items larger than the bin's configured capacity, deletion from removable or network storage, or a bin already at its limit. Any of those sends files straight past it, and large video files trip the size condition routinely.
Why that changes the position: a file in the bin is trivially restored. A file that bypassed it has had its entry removed and its space marked available, which is an ordinary deletion at the filesystem level.
Why the drive being solid-state is the important complication: deletion issues a notice releasing those blocks, and the controller erases them in the background. Content can be genuinely gone within minutes rather than merely unreferenced.
Why that makes this urgent in a way the same mistake on a spinning drive would not be: time is doing the damage rather than usage alone. A powered machine continues processing releases even while idle, so leaving it on to think about it costs material.
What she should do immediately: stop using the machine and shut it down. Not run recovery software, not search, not browse — each of those is more activity on the drive holding the content.
What is worth checking first, from another device: whether the images were synchronised anywhere. Phone and desktop photo services frequently hold copies, and a deletion on one machine does not always propagate immediately.
On the bench
Cancellation was understood as halting remaining items rather than reversing completed ones — bulk deletion running as a sequence so that cancelling ends the operation where it had reached. An empty recycling area indicates items bypassing it, which occurs with the skip modifier, with items exceeding the configured capacity, from removable or network storage, or where the bin is at its limit. On solid-state media deletion issues a block-release notice acted on in the background. Translation layer state was assessed for release processing.
The outcome
Cancellation understood as halting rather than reversing, the machine removed from use, and unallocated regions examined for retained content. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: cancel stopped the rest and could not undo the done. And an empty bin means those files bypassed it — which large videos do routinely.
Immediately after a deletion you tried to cancel
Shut the machine down rather than searching for the files, because on a solid-state drive deletion tells the controller those blocks are free and it erases them in the background — so a powered machine is losing content even while idle. Cancelling only stopped the items not yet reached; anything already processed stayed processed, so check carefully what actually survived. An empty recycling bin means those files bypassed it, which happens with large videos, removable storage, or a bin at its limit. Check from another device whether the images synchronised anywhere.
Shut the machine down — call Manchester Data Recovery on 0161 871 0788; cancellation understood as halting rather than reversing, imaged at the block level, translation layer assessed for release processing.
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.