Retiring a drive or PC: wipe it properly before it leaves

Verified 2026-10-293 min read

Which wipe method matches the medium, how BitLocker changes the calculus, and the checks before selling or recycling a Windows machine.

Tested onPro (26H2) / Server · Build 26300.9457 / 26100.33650 · x64

Build: 26300.9457 / 26100.33650
Edition: Pro (26H2) / Server
Architecture: x64
Support: Documentation (E1)
Evidence: E1Official documentation
Verified: 2026-10-29
Page type: Checklist

The short answer

The right wipe depends on the medium and on who gets the device:

Target	Method
SSD (SATA/NVMe)	ATA/NVMe secure erase (vendor tool) or crypto-erase
HDD	overwrite with random data, at least one full pass
Encrypted drive (BitLocker)	destroy the key — a crypto-erase — then format
Phone/tablet	factory reset with encryption enabled
Whole PC, resold	wipe the disk and reset firmware/TPM state

A single “quick format” is not a wipe. It removes the file table and leaves the data.

SSD: overwriting is not enough

On flash, overwriting does not reliably reach every cell — wear levelling and spare blocks mean old data can persist outside the logical address space.

Use one of:

Manufacturer secure-erase tool (ATA Security Erase / NVMe Format with crypto erase) — fastest and most thorough.
Crypto-erase — if the drive was encrypted (BitLocker, Opal), destroying the key renders the data unreadable even if the ciphertext remains.
Full overwrite as a fallback — cipher /w or a third-party tool; slower and weaker than secure erase, but better than a format.

# check whether the volume is encrypted before you start
manage-bde -status C:
# overwrite free space (not the whole disk) - a fallback, not a secure erase
cipher /w:C:\

cipher /w writes to free space only; it does not touch existing files. It is useful after deleting data, not instead of a wipe.

HDD: overwrite properly

One full pass of random data is enough for any realistic threat model. More passes are superstition for modern densities.

# destructive: this erases the whole disk
Clear-Disk -Number 1 -RemoveData -RemoveOEM -Confirm:$false

Clear-Disk removes partitions and data structures; it does not overwrite the whole surface. For a true wipe, use a dedicated tool that writes every sector.

The crypto-erase shortcut

If the drive was fully encrypted with BitLocker (or is a self-encrypting Opal drive with BitLocker managing the key):

Confirm encryption covered the whole volume (manage-bde -status).
Destroy the key — clear the TPM, delete the recovery key, or run the vendor’s crypto-erase.
The remaining ciphertext is useless without the key.

This is the standard approach for SSDs in managed fleets: fast, and it does not wear the drive.

Caveat: if the drive was only partially encrypted, or “used space only”, unencrypted leftovers may remain.

Whole-machine checklist before it leaves

Sign out of accounts — Microsoft account, Entra join (dsregcmd /status should show not joined).
Remove the device from management — Autopilot/Intune/MDM; otherwise the next owner cannot complete OOBE.
Wipe every drive, including secondary and any SD card.
Reset firmware — clear TPM, reset BIOS/UEFI to defaults, remove BIOS passwords.
Check for hidden storage — eMMC, Optane modules, USB drives left inside.
Clean externally and note any faults honestly.

Get-Disk | Select-Object Number,FriendlyName,Size,BusType
Get-PhysicalDisk | Select-Object FriendlyName,MediaType,Size,HealthStatus
dsregcmd /status
Get-Tpm | Select-Object TpmPresent,TpmReady

What not to do

Do not rely on “Reset this PC” alone — it can keep files with the “keep my files” option, and its wipe is not a secure erase.
Do not sell a drive that held credentials without a crypto-erase or secure erase.
Do not bin lithium batteries — take them to e-waste.

Lab boundary

E1. The commands and BitLocker behaviour are Microsoft-documented. No drive was wiped for this page; the destructive commands are described, not executed here.