This is the page that can save your data. The GPT and MBR fixes all pass through one dangerous moment: typing select disk, then clean. With two drives installed — a fast SSD for Windows and a big HDD for files is the classic setup — DiskPart shows two nearly identical lines, and clean erases whichever one you selected. Completely. This page teaches the identification discipline that makes that moment safe.
Every DiskPart disaster story has the same shape: the user meant the 256 GB SSD, the data lived on the 1 TB HDD, list disk showed two lines, a number was guessed — and clean did exactly what it was told, erasing the entire wrong disk, every partition and every file, with no undo. Disk numbers in DiskPart are not identities; they are just the order Windows happened to enumerate the drives this boot. The only reliable identifier on that screen is size, backed by one physical trick that removes guessing entirely.
Technicians and YouTube comments alike say "select disk 0" as if 0 always means the Windows drive. It does not. DiskPart numbers drives in the order the firmware and Windows enumerate them, and that order changes when you add a drive, move a cable to another SATA port, install an NVMe drive, or sometimes simply between boots. Your install USB also appears in the list, usually as a small disk of 14 GB, 29 GB or similar — one more line to misread.
Treat the number as a label you must re-verify every single time, on every single machine, by the one property that cannot move: the disk's capacity.
list disk and match by Size, never by positionselect disk 1 — then run detail disk. This shows the drive's model name and its volumes. A drive full of named volumes with your data folders is your data drive, whatever its number iscleanThe professional's shortcut is physical. If the PC has a data drive that must survive the install untouched:
list disk shows only the target drive (plus the USB). There is nothing left to confuseOn a laptop with two drives this means opening the back cover once. Compare that cost with the cost of cleaning the wrong disk. There is no comparison.
Sometimes both drives are the same model and same size — two identical 512 GB SSDs, for example. Size and model then cannot separate them. Your remaining clues:
detail disk on each: the volumes and drive letters of the data disk reveal itlist volume tooA delayed install is an inconvenience. A cleaned data drive is a catastrophe. When in doubt, the correct command is no command.
clean erases the entire selected disk the instant it runs — all partitions, all files, no confirmation prompt, no recovery from this screen. With two drives installed, 'I think it is disk 0' is not identification. Size, detail disk, or a physically unplugged data drive — one of the three, every time.Watch the video's DiskPart steps with fresh eyes after this page — you will see exactly which line in list disk matters, and why pausing on it is the mark of a careful technician.
▶️ Watch Full VideoYes, it appears in list disk at its USB size (for example 29 GB for a 32 GB stick), and clean would wipe your installer — annoying but not tragic, you just recreate it. The size gap makes it easy to spot: your USB is far smaller than any internal drive.
Stop using that disk immediately — do not install anything onto it. Clean removes partition information; the underlying data often still sits on the platters or cells until overwritten, and recovery tools run from another machine sometimes retrieve a great deal. There is no guarantee, which is exactly why the identification discipline on this page exists.
Because enumeration order is not fixed identity. Adding hardware, swapping a SATA cable to a different port, firmware updates, or an NVMe drive appearing can all reorder the list. Windows itself does not promise stable disk numbers across boots — verify by size and detail, every time.