A Merchant City architecture practice kept its project archive on a WD Elements desktop drive — years of CAD drawings, planning submissions and 3D models. One morning it spun up as usual and simply didn’t appear: not in File Explorer, not in Disk Management, not on the Mac in the corner either.
The practice manager walked it round — Bath Street is ten minutes from their studio — after a morning of cable-swapping had changed nothing. Sensible instincts had kicked in early: no recovery software, no opening the enclosure, no “initialise disk” when Windows eventually offered it. That last refusal mattered more than they knew; initialising writes a fresh blank map over exactly the structures a recovery needs.
On the bench the drive told its story: corruption in the firmware modules that let the disk announce itself, and behind that, a scatter of early-stage bad sectors — the likely trigger, since drives log and relocate failing sectors in the same firmware region that had broken. The mechanics were healthy; the drive had essentially tripped over its own paperwork. Recoverable, but only from beneath the operating system, where software running on a computer can never reach.
The corrupted firmware modules were repaired at service-area level on a hardware imaging rig, restoring the drive’s voice. Then the disk was imaged with the bad-sector map in hand: healthy regions first at full speed, the weak zones revisited last with long timeouts and gentle retries, so a struggling sector could never stall or worsen the whole job. The NTFS volume was then rebuilt and verified on the image — folder tree, filenames, dates, all intact.
One hundred percent of the archive came back — AutoCAD and Revit files, planning PDFs, renders — on a new drive with the original folder structure preserved, at the standard £300 + VAT band fixed in writing at diagnosis. A WD drive that spins but isn’t recognised is rarely dead; our WD recovery guide covers why the family fails the way it does, and why the fix is almost never another cable.
Spinning-but-not-recognised usually means firmware, not death — and firmware is bench work. Skip the initialise prompt, skip the scanning tools, and get it diagnosed free: drop it at Tay House or post it in, £300 + VAT fixed in writing.