A WD My Passport that no longer appears. A My Book that spins up and stops. An Elements drive that Windows suddenly wants to format. Western Digital drives fail in a very particular way — and in a great many cases the disk inside is completely healthy. The part that died is the board it talks through, which is why so many WD drives are written off when they did not need to be.
Western Digital sells more consumer storage than anyone, which means WD drives turn up on our bench more than any other brand — not because they are worse, but because there are simply more of them. The names matter, because each fails in its own way: the My Passport portable, the My Book desktop drive, the plain Elements enclosure, the WD Blue / Black / Red / Purple internal drives, and the My Cloud NAS.
Here is the single most useful thing to know about WD portables. Inside a My Passport or an Elements, the drive is often not a normal SATA disk with a USB adapter bolted on. The USB controller is soldered directly onto the drive’s own board, and on many models the data is hardware-encrypted by that controller as a matter of course, whether or not you ever set a password.
That has two consequences. First, when the drive stops being detected, the fault is very often the bridge board, not the disk — the disk inside is perfectly healthy and simply has no way to speak. Second, you cannot simply pull the drive out of its case and plug it into a SATA port: without its own controller, the data is unreadable ciphertext. This is why so many people conclude the drive is dead when it is not, and why a competent recovery starts by testing which of the two has actually failed.
Beyond the bridge board, WD drives fail the way all drives fail. Clicking is a head problem — the heads are damaged and re-seeking endlessly, and every power-on drags them across the platters again. Not spinning at all points at the motor or the board. Slow, freezing, or dropping out mid-copy means bad sectors, and every further read is a read you may not get back. A My Cloud that vanishes from the network is a NAS problem, not a disk one, and needs the volume rebuilt from images.
Whatever the fault, the order is the same. The drive is write-blocked, then cloned sector by sector on our DeepSpar imager, which reads a weak drive gently instead of hammering it. Where the bridge board has died, the disk is read through matched WD electronics with its own encryption keys intact. Where the heads have gone, the drive is opened under a laminar-flow hood and a matched donor head stack is fitted. Where the firmware is corrupt, the service area is rebuilt on the PC-3000. Every repair afterwards runs against the image, never the patient.
We wrote one of these up properly — a WD Elements that reported “access denied” and turned out to be corrupt NTFS permissions rather than encryption. Worth reading if that is your symptom: the WD Elements case file.
If a WD drive is clicking, not detected, or asking to be formatted: unplug it. Do not run recovery software over it, do not shell it out of its case, and do not keep re-plugging it to see if it comes back. The free diagnostic tells you which fault you actually have — bridge board, heads, firmware or file system — before anyone quotes you a penny. Drop it at our Leeds address on Albion Street, or post it insured from anywhere in the UK.