Data Recovery Case File · Mac & Apple Ecosystem · The Password She Couldn't Type

Not locked out — shut out: why "it won't let me type my password" is an input fault rather than a data fault, the free checks that sometimes end the case in five minutes, and the documents extracted with her own credential

Her enquiry was matter-of-fact and, read closely, more hopeful than she knew. "I'm a uni student and my laptop is preventing me from typing in my password and logging in to my laptop (MacBook Air). I've purchased a new laptop, and I'm desperate to get my documents back. There isn't much on there — just some documents and a few apps." The wording is the diagnosis: she is not saying the password is wrong, nor that the machine reports corruption — she is saying the machine won't accept typing. That is a fault of input or of the login screen, sitting far away from her storage; her documents are almost certainly untouched, and the case may not even need a laboratory. This page covers the distinction that decides everything, the free checks worth running before spending anything, the honest role her password plays if extraction is needed after all, and the small scope correction her own list invites — because documents recover beautifully, and apps don't recover at all.

The decode: three suspects, the free tests, and the key she already owns

What "won't let me type" actually points at: three ordinary suspects, none of them her data. The keyboard itself — a failed keyboard flex or a stuck key can leave a machine that appears to boot fine but accepts nothing at the password field (a well-known failure on slim laptops of several makes and eras). The login window — the greeter software can hang while looking perfectly alive: cursor blinking, keystrokes going nowhere. An input path fault after a spill or knock. All three are machine problems; none of them touches the storage, which explains why her instinct that the documents still exist is correct. It also explains the cruel appearance of the failure: nothing looks broken, so it feels like being locked out of one's own life by a password one is typing perfectly.

The free tests worth running first: this archive would rather save a student a bill than earn one, so the cheap checks come first. Attach an external keyboard — wired if possible — and try the password again: if it types, the built-in keyboard is the fault, she is back into her own machine immediately, and the whole case evaporates into a repair decision she can take at leisure. If an external keyboard also types nothing, the login window or input path is the suspect, and a clean restart before further attempts is worth one try. Where the machine's era supports it, accessibility keyboard and startup options can also confirm whether input is reaching the system at all. Five minutes, no cost, and a meaningful chance of ending the enquiry.

If extraction is needed — her password is the key: where the machine stays shut, the route depends on generation, exactly as this volume's other Mac cases describe: earlier machines yield a removable blade module read on a native interface; later ones require the machine-side road through their own encryption. In either case, one point is worth stating plainly because it is the archive's fixed doctrine: her password is not an obstacle to be defeated; it is the legitimate key that makes the recovery possible. Encrypted storage is opened with credentials the owner holds, never by claiming to break encryption — which no honest lab does. She should therefore keep that password safe and to hand: the very thing the broken keyboard prevented her from typing is the thing that unlocks her documents on the bench.

The scope note, kindly: her list — "documents and a few apps" — deserves one gentle correction. Documents, photographs and project files recover fully. Applications do not meaningfully recover: they are installed software tied to the system they were installed into, and the right answer on a new laptop is simply to install them again. It slightly shrinks the job, which is good news for a student's budget.

On the bench

The free checks were offered before any handover, and the case proceeded only where they left something to do. With the machine confirmed shut but its storage unimplicated, the era-appropriate route was taken: the module read on its correct native interface, or the machine-side extraction performed with her password supplied — the legitimate credential, the only key this bench turns. A complete image was taken on first access, the volume mounted from the copy, and her document set — coursework, drafts, the small pile that actually mattered — was verified by opening and delivered onto media her new laptop reads. The applications were left where they belonged: on the internet, waiting to be downloaded again.

The outcome

Her documents recovered and delivered verified, with the applications honestly excluded and the free checks offered before any charge arose. Free assessment, one fixed written figure including VAT, no recovery, no fee. The distinction, posted for everyone shut out of a machine they can't type into: "it won't accept my password" is an input or login-window fault, not a storage fault and not a forgotten credential — your files are almost certainly fine; an external keyboard is a free five-minute test that sometimes ends the whole problem; your password remains the legitimate key to encrypted storage, so keep it safe rather than assuming it's now useless; and apps are re-downloaded, never recovered.

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.