External Hard Drive Not Showing Up? Safe Steps Before Data Recovery

If an external hard drive contains important files and suddenly disappears, do not initialize, format, erase, or repair it just to make it visible again. First determine whether the computer can still identify the physical device and its correct capacity. That distinction decides whether a simple connection check, a byte-for-byte image, recovery software, or a professional lab is the safer next step.

The 60-second safety checklist

Disconnect the drive and pause if any of these are true:

It was dropped, hit, exposed to liquid, or connected after an electrical event.
A mechanical HDD now makes repeated hard clicks, grinding, or clunking sounds.
It repeatedly connects and disconnects, freezes the computer, or disappears during reads.
Windows or macOS reports the wrong capacity, 0 B, or No Media.
The files are unique enough that one unsuccessful DIY attempt would be unacceptable.

Do not:

Accept an Initialize, Format, Erase, or New Simple Volume prompt.
Run CHKDSK, Disk Utility First Aid, or another repair tool on the only copy before preserving the data.
Install recovery software on the affected drive.
Save an image or recovered files back to that drive.
Open a sealed HDD, freeze it, hit it, or repeatedly power-cycle it.

If the drive is quiet, stable, and was not physically damaged, one controlled connection check is reasonable. The goal is to observe it, not to repair it.

“Not showing up” can mean four different things

What you see	What it usually tells you	Safer next move
Missing from File Explorer or Finder, but visible with the correct size in Disk Management or Disk Utility	The physical device is detected; a mount, drive-letter, partition, or file-system issue may exist	Record the exact status before changing anything
Visible as a healthy volume with a recognized file system, but no drive letter	Windows may simply lack a usable drive-letter assignment	Assign a letter only if the volume and capacity are otherwise correct
Visible as RAW, Unallocated, Not Initialized, or macOS asks to initialize the disk	The device is detected, but the expected file-system or partition metadata is not being mounted	Do not initialize or format; image a stable device or seek help
Missing from every hardware and disk utility, shows the wrong capacity, or repeatedly drops offline	The problem may be below the file-system level	Stop DIY scans and consider a professional evaluation

The same symptom in Explorer or Finder can therefore lead to opposite advice. Recovery software needs the operating system to communicate with the storage device. If the device never appears with a stable, plausible capacity, changing recovery applications will not fix the hardware path.

Step 1: Rule out obvious connection problems once

For a drive that has not been dropped and makes no abnormal sound:

Shut down or safely disconnect the drive.
Connect it directly to another USB port on the computer, not through a hub.
If possible, try a known-good compatible data cable.
For a desktop external drive, confirm that its correct power adapter is connected.
Try one other computer to separate a host USB problem from a drive problem.

Seagate’s USB External Troubleshooter recommends checking another port, cable, and computer, and checking power for desktop drives. It also says that a RAW or Unallocated drive containing needed data should move toward data recovery rather than formatting.

Do not turn this into dozens of retries. If the drive becomes less stable, starts making new noises, or disconnects during reading, stop.

A note about clicking

An occasional soft activity click can be normal for a working HDD. Repeated hard clicking, clunking, or grinding is different. Seagate’s hard-drive sound guidance says persistent hard clicking or repeating clunking likely indicates a physical issue and advises contacting data recovery services before troubleshooting when the data is essential.

External SSDs and flash drives have no moving parts, so clicking from the enclosure, power supply, or nearby hardware must be diagnosed differently. The absence of noise does not prove that an HDD, SSD, USB bridge, or power circuit is healthy.

Step 2: Check whether the operating system sees the device

This is an observation step. Take a screenshot or write down the model, reported capacity, partition status, and file system before making changes.

Windows: use Disk Management

Open Disk Management and find the external device by model and capacity, not only by drive letter.

Microsoft’s Disk Management troubleshooting guide distinguishes several useful states:

Online + Healthy + recognized file system: the volume exists.
Healthy volume without a drive letter: a drive letter may be added.
RAW: Windows cannot identify a usable file system.
Unallocated: Windows does not see the expected partition in that region.
Not Initialized, Unknown, Offline, or Missing: more investigation is required before writing metadata.

If the partition is RAW or Unallocated and you need its files, Microsoft explicitly says not to format it or create a new volume. Those actions are for an empty disk, not a recovery case.

macOS: use Disk Utility and System Information

Open Disk Utility, choose View > Show All Devices, and look for the physical drive with its containers or volumes underneath. If it is absent, check whether USB or Thunderbolt hardware sees it in System Information.

Apple’s Disk Utility guidance says to check the cable, connections, and power when an external device does not appear, and notes that a device missing from Disk Utility may need service.

Apple recommends having a current backup before running First Aid. If this drive contains the only copy and data recovery is the goal, preserve or image the data before attempting file-system repair.

Step 3: Interpret the status before acting

Case A: The volume is healthy but has no Windows drive letter

If all of the following are true, assigning a drive letter may be appropriate:

Disk Management shows the expected physical drive and correct capacity.
The volume is Healthy and has a recognized file system.
It is not an EFI, Recovery, or other system partition.
There are no abnormal sounds, read errors, freezes, or repeated disconnects.

Microsoft documents the process in Change a drive letter. Do not use drive-letter advice when the space is RAW, Unallocated, or the device reports the wrong size; those are different cases.

Once the volume mounts, copy the irreplaceable files to another physical device first. Do not assume that visibility means the drive is healthy enough for continued use.

Case B: Windows says Not Initialized or Unallocated

Do not click Initialize Disk merely because Windows offers it. Microsoft’s Initialize new disks procedure is for a new disk with no existing data and warns that initialization of a disk already in use erases data.

If this was a working drive with files yesterday, the prompt is evidence of a problem, not proof that the drive is empty. For a stable device reporting the correct capacity, preserve a byte-for-byte image before recovery attempts. For an unstable device, stop and consider a lab.

Case C: The drive is RAW or asks to be formatted

Do not format it. A format may create new file-system structures on space that recovery software needs to analyze.

If the drive is stable and reports the correct size, scanning a full image is safer than repeatedly scanning the source. If you have not selected a recovery path yet, use the recovery assessment and compare software recovery with professional service.

If the loss followed an accidental format on a stable removable drive, our formatted USB recovery guide explains the no-write workflow. The same principles apply to many external drives, but the exact file system and device type still matter.

Case D: The capacity is wrong, reads stall, or the device keeps disconnecting

Stop treating this as a normal file-system problem. A recovery scan can generate hours of sustained reads, which is a poor first test for an unstable device.

Wrong capacity, 0 B, No Media, repeated disconnects, severe slowness, or I/O errors can point to a USB bridge, controller, firmware, media, head, or power problem. The exact cause cannot be diagnosed from one status label. If the data matters, preserve the current state and seek a specialist rather than cycling through software.

Should you make a byte-for-byte image?

A disk image copies addressable sectors to an image file on another healthy device. A disk-to-disk clone copies them to another physical disk. Neither is the same as dragging visible files into a backup folder.

Imaging is often the safer DIY starting point when:

The device is stable and consistently reports the correct capacity.
There are no abnormal mechanical sounds or signs of physical damage.
The problem appears logical, such as RAW, a lost partition, an accidental quick format, or deleted files.
You have enough healthy destination space and can confidently identify source and destination.

Imaging is not automatically safe when the source clicks, drops offline, freezes, returns many read errors, or was physically damaged. In those cases, additional power-on time and reads can consume the remaining opportunity for a professional recovery.

The GNU ddrescue manual explains why its recovery-oriented copy process reads good areas first, uses a mapfile, and recommends repairing a copy rather than the failing original. It is an advanced tool: confusing the source and destination can overwrite the wrong disk. If you are not comfortable verifying device identifiers and destination capacity, do not improvise with a command copied from a forum.

After imaging, keep one untouched master if the data is important. Scan a working copy or the image file, preview representative files, and save recovered files to a separate healthy location.

Should you run CHKDSK or Disk Utility First Aid?

Repair and recovery have different goals:

File-system repair changes structures so the volume may mount consistently.
Data recovery tries to extract useful files while preserving evidence of the previous structure.

A repair can be reasonable on a disposable copy or after a verified backup. It is not the best first move on the only copy when losing directory information or changing metadata would matter.

Apple says to have a current backup before First Aid. Microsoft says not to format RAW or Unallocated space when recovering files. GNU ddrescue recommends copying a failing drive and repairing the copy. Together, these sources support a simple rule: preserve first, repair second.

When can recovery software help?

Software is worth evaluating when the drive is stable, the computer identifies it with the correct capacity, and the problem is logical. Examples include a lost partition, RAW file system, accidental quick format, or deletion from a healthy HDD.

Use a free scan or preview before paying. Check several important file types and both small and large files. A filename, thumbnail, reported size, or a large “found data” total does not prove that the content is complete.

Do not install the program on the affected drive, and never recover files back to it. If the external device is an SSD, TRIM and controller behavior may change what is recoverable; read whether deleted files can be recovered from an SSD with TRIM before assuming HDD-style results.

What recent user reports have in common

Public discussions are useful for discovering questions, not for proving technical claims. Three recent examples show why the first decision matters:

In an external WD drive discussion, the drive asked to be formatted and the user lacked enough space for a full image. The real need was not another product name; it was a safe plan for source, image, and recovery destinations.
After an external HDD was dropped, another user asked whether to run ddrescue or stop and seek professional recovery. Physical history changes the advice even when the on-screen symptom looks similar.
In an accidental-format case, the user worried that a recovery attempt had caused corrupt output. That question highlights why tools, outputs, and the source drive must be kept separate.
Two public X posts described a drive that still had power but would not spin or appear to software and another that suddenly stopped being recognized with a film collection on it. Both express the same urgent need: determine whether the device is detectable and stable before trying software.

These cases do not establish recovery odds. They show that “not showing up” is too broad to answer until device type, exact model, capacity, file system, physical history, and current behavior are known.

A practical decision table

Current state	DIY connection check	DIY image	Recovery software	Professional evaluation
Healthy volume, correct capacity, missing drive letter	Yes	Optional after copying essentials	Usually unnecessary	Usually unnecessary
RAW / Unallocated, stable, correct capacity, no physical event	Yes, once	Often appropriate	Scan the image	Consider if data is unique
Accidentally quick-formatted, stable, no further writes	No repeated tests	Often appropriate	Scan the image	Consider for high-value data
Dropped, liquid exposure, new hard clicking or grinding	No	No DIY image	No	Yes
Wrong capacity, `0 B`, `No Media`, freezes, repeated disconnects	One observation only	High-risk without specialist tools	No	Yes
External SSD with deleted files or format	One observation only	May preserve the current state but cannot reverse TRIM	Results depend on controller and TRIM	Consider if irreplaceable

Information to record before asking for help

Exact brand and model printed on the device.
HDD, SSD, USB flash drive, or unknown device type.
Advertised capacity and capacity currently reported by the operating system.
Windows, macOS, Linux, NAS, camera, or another original host.
NTFS, exFAT, APFS, HFS+, or other known file system.
Exact event before failure: deletion, format, unplug, drop, update, power loss, or nothing obvious.
Current sounds, disconnects, error messages, and Disk Management or Disk Utility status.
Everything already attempted, including repairs, scans, installations, and where outputs were saved.
Whether another independent copy or backup exists.

Frequently asked questions

Should I initialize an old external drive so Windows can see it?

No, not when it contains needed files. Initialization is intended for a new disk without existing data. Preserve the device and investigate why its previous partition information is unavailable.

Can I assign a drive letter without formatting?

Yes, but only when Disk Management already shows a healthy, recognized volume without a letter. A RAW or Unallocated region is not a missing-letter problem.

Why does the drive appear in Device Manager but not File Explorer?

Device Manager can recognize USB or storage hardware even when Windows cannot mount a usable volume. Check Disk Management for capacity, partition, file-system, and drive-letter status.

Can a different USB cable fix the problem?

It can fix a connection or power-path problem. Try a known-good compatible cable and direct port once. Stop if the drive is physically damaged, unstable, or develops abnormal sounds.

Should I format the drive and then recover the files?

No. Formatting writes new structures and is unnecessary for a recovery scan. Recover or image first; reformat only after the data question is resolved and the hardware is known to be reusable.

Does a full image require another drive?

Yes. An image file needs healthy storage roughly large enough for the addressable source, and recovered files need a safe destination as well. Do not place either on the source.

What if the external drive is clicking but still appears sometimes?

Occasional soft activity sounds can be normal, but persistent hard clicking, clunking, or grinding with detection trouble is a stop signal. If the files matter, disconnect it and seek a professional evaluation.