Data Recovery Case File · Electrical & Environmental Damage · Drying Is Not Undoing

Water Damage: Dried Out, and the SSD Still Not Recognised

His enquiry described a sensible response to an accident and an outcome that shows why it was not enough. "Water accidentally spilt onto my laptop earlier. I followed the steps to dry out the laptop, but upon reboot it appears it isn't recognising the SSD. Is it possible to recover the files from the drive?" He did what the guidance says and the machine now starts — which is genuinely encouraging, because a machine that powers up has most of its board working. But the drive is missing, and the reason exposes a gap in the standard advice that matters far more than most people realise: drying a device addresses the water and leaves the damage. Liquid causes two separate problems, and only one of them evaporates.

The decode: the two problems, and which one drying solves

Problem one — conduction. Liquid bridges circuits that were never meant to connect, current flows where it should not, and the machine misbehaves or dies. This is the immediate, dramatic effect, and it is the one drying genuinely fixes: remove the water and the unwanted connections disappear. His machine now powering up is exactly that problem resolved.

Problem two — corrosion, which drying does nothing about. Water is rarely pure. Whatever was in it — minerals, sugars, salts — remains behind as residue when the water evaporates, and that residue is chemically active. It continues to attack copper traces, component legs and solder pads for as long as it is present, and it does so faster in the presence of power. So a laptop that has been dried is not a laptop that has been cleaned: it is a laptop with the conductive problem removed and the corrosive one still running, quietly, underneath. That is why devices frequently work after drying and then fail days or weeks later, and it is why "it seemed fine at first" appears so often in these enquiries.

What the missing drive tells us: the fault is localised, which is useful. The machine reached a state where it could look for storage and found none — so processor, memory and power delivery are all working, and the damage has affected either the storage interface on the board, or the drive itself. Both are addressable, and neither describes data being destroyed: liquid damages electronics, not the contents of flash memory.

Why the reboot was a risk: said without reproach, because everyone does it. Applying power to a board carrying active residue is how corrosion damage spreads — current accelerates the chemistry, and a circuit that was marginal can be finished off by exactly the test intended to check whether it survived. The instruction from here is to stop restarting it.

What actually helps: corrosion is removed by cleaning rather than drying, at board level, under inspection. If the drive is a removable module it may lift out and read perfectly on separate equipment, which sidesteps the machine's damaged interface entirely — that is the quickest route and it should be established first. And the encryption question belongs before any physical work, because on many machines a perfectly extracted module reads as noise without a lawful key.

On the bench

The machine was not restarted again. The board was assessed with the liquid's path traced and corrosion documented, with particular attention to the storage interface — since the drive's absence pointed there — and to whether residue had reached the drive's own connector or components. Where the module proved removable, it was lifted out and read write-blocked on native equipment, which removed the damaged machine from the question entirely; where storage was integrated, the board was cleaned and its affected paths restored under inspection until the machine could address its own storage. The encryption position was established before any expectation was set, and imaging ran on first successful access. His files were verified by opening and delivered on fresh media.

The outcome

The corrosion mapped, the drive read independently of the damaged interface, and the contents verified and delivered. Free assessment, one fixed written figure including VAT; where a drive has to be opened or a chip removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode, for anyone who has dried out a spill: liquid causes two problems and drying solves one — conduction disappears with the water, while corrosive residue stays behind and keeps attacking traces and pads, faster when power is applied; that is why devices work after drying and fail weeks later; a machine that powers up but cannot see its drive has localised damage at the storage interface or the drive itself, neither of which destroys what is written in flash; and the reboot you used to check is itself a risk, so stop restarting it and have the board cleaned rather than dried.

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.