Access / detection problemProfessional help may be needed

Drive Not Detected or Keeps Disappearing

When a drive is absent from the OS or repeatedly disconnects, first determine which layer can still see it before treating the problem as file-system damage.

First decision

Before attempting repair, determine whether the storage source is identified consistently, reports the expected capacity and can be read without severe errors, stalls or disconnects. If not, treat acquisition as the first problem.

What the symptom actually tells you

“Not detected” is not one failure mode. A device can be missing only from File Explorer or Finder while still appearing in Disk Management, Disk Utility or the system hardware tree; it can be visible to the operating system but have no mountable volume; or it can be absent even from BIOS/UEFI or the storage controller. Those states point to very different layers. A missing drive letter is usually a logical or mounting problem. A device that repeatedly drops off the bus is much more concerning for power, interface, controller, firmware or media instability.

What to observe before doing anything

Record where the device is visible, whether its model and full capacity are reported correctly, whether it remains connected, and whether reads cause freezes, timeouts or reconnects. For an external drive, note whether the enclosure powers normally and whether another known-good cable or port changes only the connection behavior. For an internal drive, a screenshot of Disk Management/Disk Utility or the controller inventory can be more useful than repeatedly rescanning it. Do not initialize, format or create a new volume merely to make the device appear in the file manager.

What changes recoverability

If the storage device is identified consistently with the correct capacity and reads normally, the problem may sit above the hardware layer: partition metadata, encryption or the file system. If identification is intermittent, capacity is wrong, reads stall badly, or the device disappears under load, acquisition becomes the first problem. HDDs may have mechanical, head, media or firmware faults; SSDs and flash devices may fail in their controller, power circuitry or translation layer. The same visible symptom therefore has very different recovery paths.

The safer recovery path

Start at the lowest layer that can still observe the device reliably. A stable device can usually be preserved with an image before logical analysis. An unstable device should not be subjected to full scans by several recovery programs; repeated enumeration and random reads can consume the remaining access window. If the device is not identified at all after basic non-invasive connection checks, software cannot recover sectors it cannot address. That is the point where hardware diagnosis may be required.

Common mistakes

Repeatedly power-cycling a clicking HDD, running CHKDSK/fsck, initializing an “unknown” disk, updating firmware as an experiment, or opening an HDD outside appropriate lab conditions can all turn a detection problem into a harder recovery. For external drives, removing the disk from an enclosure can also be non-trivial: some USB bridges perform encryption or sector translation, so preserve the original bridge and electronics even if you test another connection path.

Preserve the source

Do not save recovered files, install software, create partitions, format, initialize or run write-capable repair tools on the only copy of the affected data. When practical, work from a verified image or another preserved copy.

This page describes the general situation, not a guaranteed fix for a specific case. If the source is unstable or the data is irreplaceable, consider a professional evaluation before further attempts.