My hard drive isn't detected

Start here if you don't yet know where the drive stops being visible. Work the three layers in order: BIOS/UEFI (does the board electrically see a disk?), Disk Management (does Windows see the disk?), and File Explorer (does it have a letter you can open?). The first layer it's missing at is your focus — a drive missing from BIOS is a hardware or connection problem, while a drive that's in Disk Management but not Explorer is almost always a missing drive letter, an Offline disk, or a partition problem that's quick and safe to fix.

The second thing to settle is how aggressive you're allowed to be. If the drive may hold irreplaceable files, you work non-destructively: check connections, look in Disk Management without changing anything, read the drive's health, and preserve data before you do a single write. If the drive is empty or brand-new, you can move directly to setup. Everything on this page is written for the first, safer case by default, because that's the one where the "obvious" fix can cost you your files.

Use the diagnostic selector at the top to jump straight to your state, or read the categories in order. The quick map turns each state into a next step, and the checklist condenses the whole process into ticks you can work through.

Three checks, in order, split the whole problem in two. First, File Explorer: is there a drive letter for it? If yes, it's fully detected and the issue is something else. If no, open Disk Management (right-click the Start button and choose Disk Management, or run diskmgmt.msc) and look for a disk number you'd expect — a row for disk 0, 1, 2, and so on. If the disk is there, Windows sees it and the problem is the volume layer. You can also list what Windows sees from the command line with Get-PhysicalDisk in PowerShell, which also shows each disk's health.

How to read the result: a disk that appears in Disk Management (even as Offline, Unallocated, or Unknown) means the hardware and the basic connection are fine, so stop hunting cables and move to the disk-layer fixes — letter, Online state, partition. A disk that does not appear in Disk Management at all means the problem is below that layer: the BIOS/hardware level, a storage driver, or the controller — and that's where the BIOS and hardware sections of this guide come in. This single check is what keeps you from fixing the wrong layer.

A brand-new drive "not showing up" is usually not a failure at all — it's a drive that's correctly waiting for setup. A fresh disk has no partition, no file system, and no drive letter, so it's supposed to be absent from File Explorer until you create them. In Disk Management it should appear as a disk marked Online, Unallocated (or, on some drives, "Unknown" until you choose a partition style). If you see that, the drive is detected and healthy; it just hasn't been initialized and partitioned yet.

The safe setup path for a drive you know is empty: initialize it (choosing GPT for a modern or large drive), create a partition, format it, and assign a letter — or simply let Windows' "New volume" wizard do all of that in a few clicks. Because the drive is empty, none of this risks data. But if this is a used drive you've moved to a new machine, stop here — it has data, and initializing or creating a volume would destroy the existing partition. That's the data-protection path instead of the setup path.

File Explorer only shows drives that are mounted with a drive letter and a readable file system. So a drive can be completely healthy and absent from Explorer for three reasons, none of which mean it's dead: it has no drive letter, it's set Offline, or it has no healthy partition/file system. The fix for each is quick and, for the first two, non-destructive.

Open Disk Management and find the disk. If it has a partition and a file system but no letter, assign a drive letter — that alone usually makes it appear in Explorer instantly. If it's Offline, bring it Online. If it shows Unallocated or Unknown, you've reached the data-risk line: if there may be files, read the data-protection section before you touch anything, because the "fix" for Unallocated (create a volume) overwrites whatever partition was there.

Disk Management is the graphical view of Windows' disk layer. Open it by right-clicking the Start button and choosing "Disk Management," or by running diskmgmt.msc. It lists every disk Windows knows about, each with a status (Online, Offline, or Read-only), its partitions, the file system on each, and its drive letter. For a missing drive, you're looking for a disk number you expect to see but that either has no Explorer letter or shows an unusual status.

Reading it is a four-step read: present? (is there a disk row at all), Online? (or Offline/Read-only), partitioned? (a partition box, or "Unallocated"/"Unknown"), and lettered? (a drive letter in the partition). Work whichever step is failing. One caution worth repeating: the same right-click menu here is where Initialize, Delete Volume, and Format live. Looking is safe; those three actions are the destructive ones, so on a drive with data, look first and go to data protection before you choose any of them.

A missing drive letter is one of the safest fixes in this whole guide, because assigning a letter only changes a mapping — it doesn't touch the data on the disk. If a partition has a file system but no letter, it will never show in File Explorer. In Disk Management, right-click the partition and choose "Change Drive Letter and Paths," then "Add," pick any unused letter, and confirm. The drive should appear in Explorer immediately.

A few caveats so the fix doesn't mislead you. Don't pick a letter that's already in use. Some disks (recovery and system partitions) intentionally have no letter and aren't meant to be browsed, so their absence from Explorer is normal. And if the partition isn't showing a valid file system, a letter won't help — that's a partition or file-system problem, not a letter problem. If assigning a letter makes it appear but you then can't open it, the issue has moved to permissions or file-system damage.

"Offline" means Windows has disabled the disk — it's present but won't mount, so it shows no drive letter and nothing in File Explorer. Windows sometimes sets a disk Offline automatically after you move it to a new machine (a protection against accidentally mounting the wrong disk), and it can also happen from a policy or manual change. The disk and its data are usually exactly as they were; it's just switched off.

The fix is to bring it Online: in Disk Management, right-click the disk (the "Disk 0" box on the left, not the partition) and choose "Bring Online." That's safe and non-destructive — it re-enables the disk without touching data. After that, the disk should show its partition and, if it has a letter, reappear in Explorer. One important branch: if the disk is Offline and shows Unallocated and may hold data, bring it Online first, then stop and read data protection before you do anything to the partition. "Bring Online" is the safe step; what you do next is where the risk lives.

"Unallocated" means the disk has raw space with no partition on it. That's where two completely different situations live, and telling them apart is the whole of this problem. Case A: a brand-new or wiped drive. It's correctly Unallocated, and setting it up is a normal, safe step. Case B: a drive that previously held data and now shows Unallocated. Here the partition table is missing or damaged, and the data may still be on the disk — it's just not described anymore. This is the situation where the obvious fix is the dangerous one.

The warning, plainly: choosing "New Simple Volume" or formatting Unallocated space overwrites the drive, and in Case B that erases the partition and the files on it. If you're sure the space is empty (Case A), go ahead — create a partition, format it, assign a letter. If it may have held files (Case B), do not create a volume. Instead, use partition-recovery software to scan for the old partition layout and recover the files first, or image the disk — see approaching data recovery. The difference between "set it up" and "recover it" is exactly whether there's data on the line.

"Unknown" or "Not Initialized" means Windows can see the disk but doesn't recognize its partition layout — specifically, the disk's partition style (MBR or GPT) isn't set in a way Windows will use. You'll see this often on a brand-new, large drive, or on a drive that was just connected to a machine for the first time. It's a setup state, not necessarily a fault.

The step to resolve it is to Initialize the disk, choosing GPT for most modern and large drives (MBR for older or small ones). On an empty new drive that's a normal, safe setup step. On a drive that previously held a partition and data, though, initializing can destroy the existing partition table and with it the files — so if there's any chance of data, stop and read data protection before you initialize. Same pattern as Unallocated: the action is identical, and only the presence of data changes whether it's safe.

Windows talks to drives through a stack of drivers, including the storage controllers (SATA, NVMe, USB) and the disk class driver. If a controller driver is missing, failed, or mismatched, a physically connected drive can simply not appear. Open Device Manager (right-click Start → Device Manager, or run devmgmt.msc) and expand "Storage controllers" and "Disk drives." A yellow warning triangle on either is a strong signal that the driver, not the drive, is the problem.

The safe fix is to update or reinstall the offending driver: right-click it and choose "Update driver" (let Windows search), or "Uninstall device" and then use "Scan for hardware changes" so Windows reinstalls it. Windows Update is also a legitimate source for updated storage-controller drivers. Two cautions: avoid third-party "driver updater" utilities, which are a common source of new problems — use Microsoft or the hardware maker's own driver; and know that if a driver change makes things worse, Windows can usually roll it back. If a drive is in BIOS but not Windows and the controller shows a warning, this is very often the missing piece.

You can inspect a drive's health and look for errors without wiping it, and that's the right first move. Reading the drive's SMART health status is entirely non-destructive: in PowerShell, Get-PhysicalDisk shows each disk's health, and most drive makers ship a small tool that reads the same data in more detail. You can also look at file-system integrity the read-only way before deciding anything about repair. Reading is safe; it's the next step — writing — that carries risk.

Here's the line to hold: Windows' "check for errors" can run with write options (the repair flags, often /f or /r) that fix file-system problems by modifying the volume's metadata. On a healthy drive that's fine. On a drive that may be failing and holds important files, running write-repair can make recovery harder, because it changes the very structures a recovery process relies on. So the order is: read the health first, and only run a write-repair on a drive you've already backed up or that you've accepted the risk on. That's "check for errors" done without rushing straight to format.

A SATA SSD fails to appear for the same reasons as any disk — no drive letter, set Offline, no partition — plus a couple of SSD-specific ones: a SATA port on the board that's disabled, or a brand-new SSD that's simply Unallocated and waiting to be set up. Nothing about being solid-state changes the diagnostic path; it's the same Disk Management read as everything else.

Open Disk Management and read the disk: status, partition, letter. If it's a new empty SSD, set it up normally (initialize, partition, format, letter) — no data risk. If it previously held data and now shows Unallocated or Unknown, you're at the same data-risk line as any drive, so go to data protection before you create a volume. If it's a different form factor — an M.2 NVMe drive — the path is different and covered in its own guide below.

BIOS sees the drive and Windows doesn't is a useful state, because it rules the hardware out. The motherboard confirms the disk is electrically present, so the failure is somewhere in the Windows disk layer or its configuration: a missing or failed storage driver, a controller-mode mismatch (the board is presenting AHCI but Windows expects RAID, or vice versa), the disk set Offline, or simply no partition/volume set up for Windows to show.

Work the Windows side in order: Device Manager first, looking for a warning under "Storage controllers" (that points at a driver — check and reinstall storage drivers); then confirm the controller mode in BIOS matches what Windows was installed with (storage settings); then Disk Management, to see whether the disk is Offline or just unpartitioned. This is the most common "it's there but I can't use it" case, and it's almost always a settings or driver fix rather than a dead drive.

If the drive isn't in BIOS, the motherboard isn't seeing it electrically, and the causes come in a specific order: it's not actually connected (a loose or missing SATA data cable or power connector, or a USB drive not seated), it's in a port the board has disabled, the SATA controller is off in BIOS, or the drive itself is dead. Start with the cheapest and most common: the connection.

The path: power off, and reseat both the SATA data and power cables at both ends (for an external, try a different USB port and a known-good data cable, and plug in the power adapter for a 3.5" drive). Try a different SATA port on the board, and confirm the port and the SATA controller aren't disabled in BIOS. If the drive never appears after those, it's the drive or the board port. And here's the important caveat: if this drive holds data and you're at the "still not in BIOS" point, stop cycling it — repeated power-ons of a marginal drive can make it worse. That's when you move to is it failing and data protection.

NVMe is a different physical and logical path from SATA: it's an M.2 drive that plugs straight into a slot on the board, with no separate data or power cable, and it needs the board's NVMe/RST controller to be enabled. That changes the common misses. An NVMe drive that isn't detected is often: not fully seated in the M.2 slot, in a slot the board has disabled or that needs a BIOS update to recognize, in a slot set to the wrong mode, or (in Windows) missing the board's NVMe driver.

The path: confirm the M.2 module is fully seated and screwed down, in a slot the board says supports storage (some M.2 slots are for Wi-Fi only), and check the board's notes — a few boards disable a SATA port when a particular M.2 slot is used. Then check BIOS for the NVMe device and that the controller is enabled, and update the BIOS if the drive is new and the board is old. On the Windows side, confirm the NVMe controller driver is present (Device Manager). If BIOS doesn't list the NVMe drive after it's properly seated, you're at a slot, board, or drive hardware question.

A drive that worked on an old board and not on a new one almost always means the environment changed, not that the drive died. The new board's storage mode (AHCI vs RAID/RST) is likely different from the old one, it may present its SATA ports differently, and the storage controller driver the old install relied on may not match the new board. The disk is fine; the platform it's sitting on changed.

The path: set the new board's SATA mode to AHCI (the most compatible default), try a different SATA port on the new board, and install the new board's storage driver if the manufacturer provides one. Then check Disk Management to see the disk. The key thing to avoid: if the drive has data, don't reformat it to "fix" the detection — a controller-mode mismatch can make Windows fail to mount the existing partition, and the fix is to correct the mode, not to wipe the disk. Get the mode and driver right first.

The storage controller mode — AHCI, IDE, or RAID/RST — is a BIOS setting that tells the operating system how to talk to the disks. It sits underneath the driver layer, and when it doesn't match what Windows expects, disks can disappear or the system can fail to boot. It's the "storage settings" answer to a drive that's physically present but the OS can't use.

The practical guidance: AHCI is the safe default for a normal single-disk setup and is what most installs expect. Don't flip an existing, working Windows install between AHCI and RAID on a whim — doing so can make Windows unbootable, because the storage driver changes underneath it. On a new build, set the mode before you install the operating system. If you're diagnosing a missing drive and the controller mode looks wrong for the install, correcting it (carefully, with the understanding it affects boot) is often the fix that no amount of driver reinstalling achieves.

Run the external-specific checklist, cheapest first. Power: a 3.5" external drive needs its external power adapter — a 2.5" drive runs from the port, but a 3.5" one will not work on bus power alone. Cable: is it a data cable? A lot of "not detected" external drives are on a cable that carries power but not data. Port: try a rear port directly on the motherboard, and a different one if the first fails. A drive that spins on every cable and port but never enumerates has a problem in the enclosure's bridge or the drive's controller.

To isolate, try the drive on a different computer: if it works there, the problem was your port, cable, or that machine's USB stack; if it fails everywhere, the problem is the drive or its enclosure. Watch the data caveat throughout — if the drive holds important files and it's marginal, don't spend an hour reseating it repeatedly. Each connect of a failing drive is a little more risk, so get the cable, port, and power sorted in a couple of tries, then move to preserving the data if it's not clearly a simple connection fix.

An internal SATA drive needs two separate connections: a SATA data cable (from the drive to the board) and a SATA power cable (from the power supply). A loose, bent, or failed data cable, or a dead power connector, means the drive is physically present but the board never sees it. Both are common, both are cheap, and both are worth checking before you suspect the drive. (A SATA SSD uses the same data cable and the same power connector.)

The path: power the machine off, and reseat both cables at both ends — a half-seated SATA data connector is a classic. Then try a different SATA data cable and a different power connector from the PSU, and a different SATA port on the board. If the drive appears after any of those, that was it. If it still doesn't appear with a known-good cable and a working port, the problem has narrowed to the drive itself or that particular board port — and if the drive has data and feels marginal, that's the moment to slow down and read is it failing.

The physical-failure signs are specific, and learning them is what separates "keep troubleshooting" from "stop and preserve." Listen and watch for: clicking, ticking, or grinding (the classic sign of a head or spindle problem — the "click of death"), the drive not spinning up at all, repeated disconnects, a large area suddenly appearing Unallocated, and a health status that reports the drive as Failing or shows a growing number of reallocated or uncorrectable sectors.

Why these matter: they mean the media or the mechanism is degrading, and a degrading drive loses readability over time. Continued use — and especially repair commands that write to it — can destroy what's still readable. So if you see these signs and the drive has data, the correct move is to stop troubleshooting and go to preservation or professional recovery, not to run more fixes. Reading the health is safe and worth doing: Get-PhysicalDisk in PowerShell shows the health column, and a vendor's tool reads the same data in more detail. Reading is fine; the next write is the risk.

"Windows can't detect it but there's data" splits into two branches, and the branch determines everything. Branch A: the drive is healthy but misconfigured — no drive letter, set Offline, or a lost partition. Recovery here is mostly about finding and restoring the partition, and partition-recovery tools can often scan for the old layout non-destructively and recover the files before anything is written. Branch B: the drive is physically failing — clicking, not spinning, failing health. Recovery here is about reading what's left before it's gone, which is often best done by professionals with the right equipment.

The practical order: if the drive is readable in any form, the gold standard is to make a bit-for-bit image (a sector-by-sector copy) — because once you have an image, you can work on the copy and stop touching the fragile original. If you must recover a lost partition, use a tool that scans for the existing layout first, and don't let it write or format until you've confirmed what it found. And never run a "recovery" that starts by formatting — that's the one action that turns a recoverable situation into a lost one. When the drive is failing and the data is irreplaceable, understand that professional service is a cost-and-value decision, and it's often the right one.