Data Recovery Case File · Mac & Apple Ecosystem · Obsolescence, Not Failure
The Reset Route Closed Because the Machine Is Old
This enquiry describes being locked out by time rather than by any fault. A 2014 laptop not logged into since 2017: "I forgot the password. I tried to reset it with my account but as the machine is running an old system it won't connect to the server to verify and allow me to reset my password. The error message is 'cannot connect to WiFi' even though it is" connected. Nothing is broken. And the account password may not stand between the owner and the files at all, because a login password and encrypted storage are two different things that people reasonably assume are one.
| Media | 2014 laptop internal storage module — account password forgotten; online reset unavailable owing to the age of the installed operating system |
| Reported situation | Machine not used since 2017 · account password forgotten · online password reset attempted · system unable to complete verification with the vendor's servers · connection error reported despite a working network connection · files required |
| Fault class | No device fault — account lock with the online reset path closed by protocol obsolescence; storage accessibility determined by whether disk encryption was enabled |
| Equipment used | Disk encryption status established before any route was proposed · storage module removed and read on a generation-matched adapter where unencrypted · imaged write-blocked · contents verified by opening |
The decode: the misleading error, and the distinction that matters
Why it says it cannot connect when it plainly can: the message is being generated by a component that failed at a later stage than the wording suggests. The machine has a working network connection — what it cannot do is complete a secure connection to the vendor's authentication service. Old operating systems support the encryption standards and trust the certificate authorities that were current when they were written, and those get retired. A server that has moved on will refuse a connection the old system cannot upgrade, and the system reports the failure in the most general terms it has. The network is fine; the handshake is not.
Why that closes the reset route permanently: this will not resolve by trying again or by changing networks. The machine cannot reach the service and the service cannot lower its standards, so any recovery path requiring the vendor to verify an identity from that machine is unavailable. Recognising that quickly saves a great deal of wasted effort, because everything about the error invites more attempts at the network.
Now the distinction that decides the case. An account password controls logging in. It does not, by itself, encrypt anything. Unless full-disk encryption was switched on, the storage is not scrambled at all — it is an ordinary readable volume, and the password protects the session rather than the data. So a machine nobody can log into may still be a machine whose files come out easily, by removing the storage and reading it elsewhere. That distinction is not obvious and it is the difference between a locked-out machine and a lost one.
Why that works well on this generation: machines of that era carry storage on a module with a proprietary connector that unclips from the board and reads on an inexpensive matched adapter. The machine's condition and its login state become irrelevant. Newer machines are entirely different, with storage soldered down and encrypted to the board.
The one thing to establish first: whether disk encryption was ever enabled. If it was, the module read elsewhere returns ciphertext and the password genuinely does matter — at which point the recovery key becomes the object of the search, not the password. On a machine of that age it was optional and frequently left off, but it should be checked rather than assumed.
The local route worth knowing: that generation also supports resetting a password from its own recovery environment, without any online verification, which sidesteps the server problem entirely.
On the bench
The disk encryption status was established before any route was proposed, since it decides everything — an unencrypted volume is readable regardless of the account lock, while an encrypted one makes the recovery key rather than the password the object of the search. Where the volume proved unencrypted, the storage module was removed and read on a generation-matched adapter, taking the machine and its login state out of the question entirely. It was imaged write-blocked and the contents verified by opening.
The outcome
The encryption position established first, the storage read independently of the machine and the contents verified. 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, for anyone locked out of an old machine: the connection error is misleading — your network is fine and what fails is the secure handshake, because the encryption standards and certificates that system trusts have been retired. That route will not reopen. But a login password protects the session rather than the data, so unless disk encryption was on, the storage is an ordinary readable volume.
Old machine you can't log into
Find out whether disk encryption was ever switched on — that single answer decides everything. A login password controls signing in; it doesn't encrypt anything by itself. So unless full-disk encryption was enabled, your storage is an ordinary readable volume and the files come out by removing it and reading it on another machine, with no password involved at all. On laptops of that era the storage is a module that unclips and reads on an inexpensive adapter, which makes the locked account irrelevant. Don't keep fighting the connection error either: your network is fine, but old systems trust certificate authorities and encryption standards that have since been retired, so the secure handshake with the reset server fails and won't start working. There's usually a local reset route too.
Check whether encryption was on — call Newcastle Data Recovery on 0191 406 1051; encryption position established first, storage read on a matched adapter independently of the machine.
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.