Dead SSD recovery · Windows

How to Recover Data From a Dead SSD in Windows? 5 Methods

A “dead” SSD can mean anything from a bad USB bridge to failed controller electronics. Start by avoiding writes, then choose a method based on whether Windows or BIOS can still see the drive.

By Pjirc Blog Editorial Team Published
Quick answer

If Windows still detects the SSD with the correct capacity, image it first, then scan the image with Disk Drill. If BIOS cannot see it, test one known-good connection plus a careful power cycle. A truly undetected SSD needs a recovery lab, not another software scan.

!

Stop using the SSD now. Do not initialize, format, repartition, optimize, or run CHKDSK on it. Never recover files back onto the same SSD. Extra writes plus TRIM activity may make deleted data impossible to retrieve.

Jump to methods Compare methods
★ Editorial pick ★ 4.4 / 5

Create an Image, Then Scan It → Disk Drill

Captures a byte-level backup before recovery · Previews found files · Runs on Windows plus macOS

✓ Available since 2011 ✓ Windows plus macOS ✓ File preview included
Try the scan →

What “Dead SSD” Means in Windows

An SSD can be logically damaged yet physically readable. Windows may show it as RAW, unallocated, missing a drive letter, or unable to open. Recovery software may help in those cases.

A physically failed SSD behaves differently. It may vanish from BIOS, report zero capacity, disconnect under load, or freeze the computer. Software needs stable hardware communication, so no recovery app can scan a device that the controller never exposes.

When to Stop DIY Recovery on a Dead SSD

Stop if the SSD becomes unusually hot, repeatedly disconnects, reports a wildly incorrect capacity, or causes long system lockups. The same applies to files tied to legal evidence, a business database, or the only copy of important family records.

A scan is not harmless on unstable hardware. It reads large portions of the SSD, which can push a weak controller or NAND package past its remaining operating window.

Choose the Right Dead SSD Recovery Method for Windows

Match the method to what BIOS plus Windows can still detect.

Method Best for Time Success rate
1. Create an Image, Then Scan It With Disk Drill TRY FIRST Detected SSDs with missing or inaccessible files ~30 min+ ● 75%
2. Check the SSD Connection in BIOS and Windows Cable, port, enclosure, or power faults ~10 min ● 65%
3. Power-Cycle the SSD Controller Sudden disappearance after power trouble ~20 min ● 45%
4. Run Windows File Recovery Stable, readable volumes with deleted files ~30 min+ ● 55%
5. Send the SSD to a Recovery Lab Undetected or physically failed SSDs Several days ● 60%

Top 5 Methods to Recover Data From a Dead SSD in Windows

01

Create an Image, Then Scan It With Disk Drill

Best first move when Windows still detects the failing SSD

~30 min+
Difficulty Easy
You need Disk Drill plus a healthy destination drive
Works for Windows 10, Windows 11

If the SSD appears in Disk Management with roughly the correct capacity, capture a byte-for-byte image before searching for files. This limits repeated reads from unstable hardware, plus it gives you a safer source for recovery attempts. Disk Drill includes disk imaging, file preview, scan filters, plus recovery-chance estimates. (disk-drill.com)

  1. Connect a healthy external drive with free space greater than the used capacity of the dead SSD. Do not install Disk Drill on the SSD you need to recover.
  2. Download Disk Drill from the official Disk Drill website, then install it on your Windows system drive or another healthy disk.
  3. Open Disk Drill, select Byte-to-byte Backup, choose the failing SSD, then save the image to the healthy external drive.
  4. Return to the recovery screen, attach the image as a recovery source, then run Search for lost data.
  5. Filter the results by file type, date, or name. Preview several important files before committing to recovery.
  6. Select the usable files, click Recover, then save everything to a different physical drive.
My thoughts after testing Disk Drill and why other recovery tools didn’t help ↗
i If the SSD disconnects, reports the wrong capacity, or makes Windows freeze, stop the scan rather than forcing another long read.
Visit Disk Drill for Windows
02

Check the SSD Connection in BIOS and Windows

Useful when a bad port, cable, enclosure, or power feed looks like drive failure

~10 min
Difficulty Easy
You need Spare cable, port, or enclosure
Works for SATA, M.2 SATA, NVMe, external SSDs

A missing SSD is not always electronically dead. A loose SATA plug, damaged cable, weak USB enclosure, disabled controller, or faulty port can prevent detection. Seagate specifically lists BIOS settings, controller support, cables, plus drive faults as common causes. (seagate.com)

  1. Shut down the PC fully, switch off the power supply if present, then unplug the computer.
  2. Reseat the SSD. For a 2.5-inch SATA model, check both the data plug plus the wider power plug. For an M.2 drive, remove it carefully, then reinstall it flat in the correct socket.
  3. Replace the SATA or USB cable. Try a rear motherboard USB port instead of a front-panel hub.
  4. Enter BIOS or UEFI during startup, then look for the SSD under storage, NVMe, or SATA devices.
  5. If BIOS detects it, start Windows, right-click Start, open Disk Management, then check whether the SSD appears with its expected capacity.
  6. If Windows can see the physical SSD, leave any RAW or unallocated space untouched. Move to Method 1 rather than initializing it.
i Do not change SATA controller mode from AHCI to RAID, or the reverse, without understanding the boot consequences.
03

Power-Cycle the SSD Controller

Worth trying after a crash, outage, failed resume, or sudden disappearance

~20 min
Difficulty Moderate
You need Direct connection or powered adapter
Works for Controller lockups, intermittent detection

An SSD controller may lock after abrupt power loss, leaving the drive invisible even though the flash memory is not necessarily damaged. Crucial documents a non-destructive power-cycle procedure that can give the controller time to rebuild its mapping tables. (crucial.com)

  1. Connect the SSD to power without copying files, formatting it, or running repair utilities. A direct SATA connection or a reliable powered adapter is preferable.
  2. Leave the SSD powered in an idle state for at least five minutes. If using an internal drive, remain in BIOS or UEFI so Windows does not write to it.
  3. Turn the computer off cleanly, wait 30 seconds, then power it back on.
  4. Check BIOS or UEFI for the SSD. If it appears, boot Windows, then check Disk Management.
  5. Once detected with the correct capacity, create an image immediately using Method 1. Avoid browsing the SSD or opening files directly.
i This approach can help a locked controller, but it cannot repair burned electronics, broken NAND chips, or corrupted firmware.
04

Run Windows File Recovery

A free fallback for a stable SSD volume that Windows can still read

~30 min+
Difficulty Moderate
You need Windows File Recovery plus a second drive
Works for Visible NTFS, FAT, exFAT, or ReFS volumes

Microsoft's Windows File Recovery is a command-line option for lost files when no backup is available. It supports SSDs, though it cannot communicate with hardware that is absent from BIOS or Disk Management. (support.microsoft.com)

  1. Install Windows File Recovery from the Microsoft Store. Save the app to a healthy disk, never the source SSD.
  2. Connect a separate destination drive. The source plus destination must use different drive letters.
  3. Open Windows Terminal as administrator.
  4. Run a targeted recovery first. For example, winfr D: E: /regular /n *.docx /n *.xlsx searches drive D, then saves matching files on drive E.
  5. If the normal pass finds nothing, use the extensive mode: winfr D: E: /extensive /n Users\ .
  6. Open the recovery folder on the destination drive, then test important documents, photos, archives, plus videos.
i Command-line recovery causes read activity. Skip this method if the SSD disconnects repeatedly or stalls the whole PC.
Read Microsoft's Windows File Recovery guide
05

Send the SSD to a Recovery Lab

The realistic option when no computer detects the device correctly

Several days
Difficulty Easy to arrange
You need A reputable SSD recovery service
Works for Controller, firmware, PCB, NAND, or encryption faults

Software cannot scan storage that never identifies itself to the computer. A lab may work around controller, firmware, circuit-board, or flash-memory faults using specialist hardware. Results can still be limited by encryption, NAND damage, wear, or missing translation data.

  1. Disconnect the SSD once normal cable, port, enclosure, plus power-cycle checks fail.
  2. Write down what happened before failure, including outages, spills, overheating, firmware updates, error messages, or repeated disconnects.
  3. Record whether BIOS showed the model name, correct capacity, zero capacity, or no device at all.
  4. Choose a lab that offers an evaluation, written quote, privacy terms, plus a clear policy for unsuccessful recovery.
  5. Pack the bare SSD in an antistatic bag with firm padding. Do not open its casing, heat it, freeze it, or swap circuit boards.
  6. Ask the lab to return recovered data on a new encrypted drive. Keep the failed SSD until you verify the recovered files.
i If the files are irreplaceable, going to a lab early is usually safer than putting a degrading SSD through repeated scans.

Which Dead SSD Recovery Method Should You Use?

Create an image, then scan it with Disk Drill when Windows detects the SSD with its proper capacity. That approach reduces direct work on unstable storage while letting you preview possible results. Try connection checks or a power cycle when the device disappears suddenly. If BIOS never identifies it, stop DIY attempts, then contact a lab.

Top pick Disk Drill
Give the SSD one careful detection test, then make an image or disconnect it. Repeated restarts rarely improve a physical fault.

Dead SSD Recovery Questions for Windows Users

Can data really be recovered from a dead SSD?
Sometimes. Recovery is more likely if the SSD still appears with the correct capacity. An SSD that is completely absent from BIOS usually requires lab equipment.
Can Disk Drill recover data from an SSD that BIOS cannot detect?
No software can scan a drive that the computer cannot communicate with. Disk Drill becomes useful after the SSD appears in Windows or as a readable disk image.
Should I initialize an SSD when Disk Management asks me to?
No, not if it contains needed data. Initialization writes new disk metadata, which can complicate recovery.
Should I format a RAW SSD before scanning it?
No. Formatting changes the file-system structures that recovery tools may need. Scan the existing device or its image first.
Is CHKDSK safe for a failing SSD?
Not as a first recovery step. CHKDSK changes file-system metadata, so it may remove damaged entries or make later recovery harder.
Why does my SSD appear in BIOS but not File Explorer?
It may lack a drive letter, contain a damaged partition, use an unreadable file system, or appear as unallocated space. Check Disk Management without accepting initialization or formatting prompts.
What if the SSD shows zero bytes or the wrong capacity?
That often points to controller, firmware, or translation-layer trouble. Avoid lengthy scans, since software will not fix incorrect hardware reporting.
Does changing the USB cable really help?
Yes, especially with portable SSDs or SATA-to-USB adapters. A failed cable, weak port, or unreliable enclosure can make a working SSD look dead.
Can I put an internal SSD in a USB enclosure?
Yes, if the enclosure matches the exact interface. M.2 SATA plus M.2 NVMe use similar-looking modules but require different enclosure support.
Does the freezer trick work on SSDs?
No. Condensation can damage the electronics, while cooling does not repair flash memory or controller firmware. Keep the SSD dry at normal room temperature.
Can I swap the SSD circuit board myself?
Usually not. SSD boards can store unique controller data plus encryption material, so a matching-looking board may not make the flash readable.
Why are deleted SSD files difficult to recover?
SSDs may process TRIM commands after deletion. Once the controller clears those flash pages, software cannot reconstruct the original content.
Should I disable TRIM before recovery?
Stopping further use matters more than changing settings after the loss. Disabling TRIM cannot restore pages the SSD has already cleared.
Can I recover files to the same SSD?
No. Saving recovered data to the source can overwrite material that has not been found yet. Use a different physical drive.
Should I clone the SSD before scanning?
Yes, if it remains stable enough to read. A byte-for-byte image preserves the current state, reducing the need for repeated direct scans.
How much free space do I need for an SSD image?
Plan for space close to the SSD's full advertised capacity. Keep additional room for the files recovered from that image.
Can Windows File Recovery fix a dead SSD?
It can search for lost files on a drive that Windows can access. It cannot repair electronics, unlock broken firmware, or detect a drive missing from BIOS.
Will a firmware update recover my data?
Do not update firmware before securing the files. Firmware updates can reset settings, fail on unstable hardware, or alter how the SSD behaves.
How do I know when professional recovery is worth it?
Use a lab when the SSD is undetected, unstable, physically damaged, encrypted with failing hardware, or holding the only copy of high-value files.
What affects a professional SSD recovery result?
The controller model, encryption, NAND condition, firmware damage, prior write activity, plus available donor parts all matter. No reputable lab can promise success before evaluating the device.