Hard Drive Not Detected on Windows 11? Complete Fix

Right-click Start, open Disk Management. This shows every drive Windows can detect, including ones File Explorer hides because they don’t have a drive letter or have an unreadable file system. If your “missing” drive appears here with a size but no letter, right-click the partition, Change Drive Letter and Paths, Add, pick any letter. It shows up in File Explorer immediately. That’s maybe 15% of the tickets we close on this issue and it takes thirty seconds.

If the drive shows “RAW” instead of NTFS, the partition table or boot record corrupted but the data is probably intact. Don’t format it when Windows offers to. If it shows “Not Initialized” on a brand-new drive, that’s normal — new drives ship blank. Right-click, Initialize Disk, choose GPT, then right-click the unallocated space and create a New Simple Volume. If an older drive suddenly shows Not Initialized, don’t initialize it — that wipes the metadata you’d need for recovery.

A photographer called us in panic last spring. Her 4TB Seagate external had been backing up client photos for three years — about 280,000 images, a year of paid work not yet uploaded to cloud. Drive icon vanished from File Explorer overnight. Status LED was solid blue, so it had power. Disk Management showed the drive at 3.6TB (normal — manufacturers count in decimal, Windows in binary) but the status was RAW. We ran TestDisk from a USB stick, it found the original NTFS partition by scanning sector-by-sector, rebuilt the partition table, and all 280,000 files came back. Ninety minutes total.

About 60% of “drive not detected” tickets fix in fifteen minutes by either assigning a drive letter or reseating a connection. If it’s specifically an external USB drive not showing up, cable and port issues cause the majority of those.

BIOS and Cables

If Disk Management doesn’t show your drive at all, restart and check BIOS — F2 on most Dell, HP, Lenovo laptops, Del on desktop motherboards. Look for Boot Order or Storage Configuration. If your drive’s model number shows up there (like “Samsung 970 EVO 1TB” or “WDC WD10EZEX”), BIOS sees it and the problem is purely Windows-side. If BIOS doesn’t see it, the connection or the drive itself is dead.

Before opening the case, try loading BIOS defaults first — Exit tab, Load Optimized Defaults, Save & Exit. I’ve seen maybe a dozen cases where a BIOS update or an accidental toggle in storage settings hid a perfectly good drive, and resetting defaults fixed it in thirty seconds.

For SATA drives, power off, unplug from the wall, then unplug both the SATA data cable (thin, 7-pin) and SATA power cable (wider, 15-pin) from the drive. Plug them back firmly — you should feel a small click. Also reseat the data cable at the motherboard end. For M.2 NVMe drives, remove the single mounting screw, the drive pops up at about 30 degrees, pull it out gently, push it back in, press flat, retighten the screw. M.2 drives are held by one screw and that screw is frequently under-torqued by builders. The drive works fine for months, then a thermal cycle causes it to slip slightly out of contact and vanish from BIOS. About 20% of “new build won’t see drive” tickets trace to that screw.

One thing that catches PC builders constantly — most consumer motherboards share PCIe lanes between the secondary M.2 slot (usually labeled M.2_2) and two SATA ports (typically SATA_5 and SATA_6). Installing an NVMe in that slot automatically disables those SATA ports. A customer added a second NVMe for his game library and his 4TB Seagate Barracuda with years of files disappeared. His SATA cable was in port 5, which his ASUS B660 board disables when M.2_2 is populated. Moved the cable to port 1, everything came back.

If you have a mechanical drive, listen to it during boot. A soft steady hum is healthy. Repeating click-click-click means the read/write heads are failing. Grinding or scraping means platter damage. If you hear either, power off immediately — every additional power cycle risks the heads scarring the platter surface.

RAW and Unknown Drives

If Disk Management shows your drive as RAW or Unknown, the hardware is fine but the partition table or file system metadata is corrupted. The right tool is TestDisk — free, open-source, doesn’t need installation.

If this drive has irreplaceable data, image it first before doing anything. TestDisk writes directly to the partition table during repair. Clone the entire drive sector-by-sector using Macrium Reflect Free to a separate disk. If the repair goes wrong, you restore from the image and try again instead of losing your one shot. For data you can afford to lose, skip the clone.

Download TestDisk on a working computer, extract to a USB stick, plug into the affected machine, run testdisk_win.exe as Administrator. Select the affected drive, Proceed, choose partition table type (Intel for older, EFI GPT for newer), Analyse, Quick Search. When TestDisk finds your old partition, press P to list files — verify you see your real folders. If the files look right, press Enter then Write to commit the recovered partition table. Reboot, and the drive should come back with everything intact.

We’ve recovered dozens of customer drives this way. Success rate is roughly 80% if you catch the drive before any reformatting or repartitioning attempts. If TestDisk can’t find a valid partition, PhotoRec (bundled with it) can carve out individual files by signature even when the partition is destroyed — slower and produces files with generic names, but recovers content when nothing else can. For broader recovery scenarios, our recover deleted files guide covers the full tool comparison.

Drivers, SATA Mode, and Windows Update

If BIOS sees the drive but Disk Management doesn’t, check Device Manager. Right-click Start, Device Manager, expand Disk drives. Yellow triangle on your drive means right-click, Update driver, Search automatically. If that doesn’t help, Uninstall device and restart — Windows reinstalls the driver on boot. Also check Storage controllers for yellow triangles, because a failing storage controller driver hides every drive on that controller.

On modern Intel boards (12th gen and newer), check for VMD — Volume Management Device. It’s enabled by default and bundles NVMe drives behind an Intel controller that requires the Intel RST driver. Without that driver, Windows can’t see any NVMe drives on VMD-controlled lanes. Either install Intel RST from your motherboard manufacturer’s support page, or go into BIOS, Advanced, VMD Controller, Disable. We see this roughly once a week on new Intel builds where someone installed Windows with VMD disabled, updated BIOS which re-enabled it, and the boot drive “vanished.”

BIOS SATA mode matters too. If it’s set to IDE or RAID when you’re not using RAID, switching to AHCI usually makes drives visible. The catch — changing SATA mode after Windows is installed can cause a BSOD because Windows loaded the wrong storage driver during installation. If that happens, change back, boot Windows, set the registry key at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci Start value to 0, reboot into BIOS, change to AHCI, and it’ll boot correctly.

Windows 11 24H2 had a specific bug where drives with certain Phison firmware controllers disappeared after updating — an HMB overallocation issue affecting some WD SN770, Kingston NV2, and Crucial P3 models. Microsoft fixed it in KB5064081. If your drive vanished right after a Windows Update, check Update history, uninstall the suspect update, and install all available updates afterward.

Download CrystalDiskInfo to check SMART health if the drive is behaving strangely — slow transfers, occasional disappearances, file corruption or blue screens. Blue “Good” means healthy, yellow “Caution” means back up your data soon, red “Bad” means replace within days. Reallocated Sectors Count rising means active failure. SMART warnings precede about 70% of mechanical drive failures by hours to days — checking when a drive starts misbehaving gives critical lead time. If your computer also freezes randomly alongside drive issues, a dying drive is often the common cause, and we can pull SMART data and examine Disk Management state remotely to tell you whether it’s a software fix or hardware replacement.