The Windows partition screen, read slowly
The one screen in Windows setup where a misread label destroys data. What 'Drive 0 Partition 1' means, which entries belong to Windows, and when to stop and unplug drives.
Everything before the partition screen is reversible. You can reboot, abandon setup, and the original system is still there. The moment you click Delete on a partition, that stops being true. This is the single most consequential screen in a clean install, and it is presented as a plain list of numbered, near-identical rows with no warning big enough to match the risk.
This page is a reading guide for that list. It does not replace the Windows walkthrough; it sits beside it for the ninety seconds you are actually looking at the screen.
What the rows mean
Windows setup lists physical disks as Drive 0, Drive 1 and so on, and each disk's partitions beneath it. The numbering is assigned by the firmware and the controller at boot, not by anything meaningful like 'the SSD I installed last year'. Adding a USB stick can shift the numbers, which is why the backup drive should already be unplugged before you reach this point.
A normal UEFI/GPT Windows installation creates several small partitions — EFI System Partition, Microsoft Reserved Partition, the main Windows volume, and a recovery partition — plus possibly an OEM recovery partition from the manufacturer. Seeing four or five small rows on Drive 0 is expected. Seeing two disks is a reason to pause and work out which is which.
- Drive 0 is a physical disk, not a partition. Deleting it as a concept is not an option; you delete the partitions on it.
- Unallocated Space is empty space on that disk, ready for setup to create what it needs.
- Small EFI, recovery and system partitions belong to the same installation. Remove them together or leave them alone; a half-removed set produces boot problems.
- A disk you do not recognise is not automatically spare. Stop and identify it before deleting anything.
The two safe patterns
The simplest path is to select the existing Windows volume (usually the large NTFS partition) and choose Format. Setup will overwrite the system files and leave your personal files at risk of being moved into Windows.old — which is not a backup. This is quicker, but it is not a clean install in the strict sense and it is not what you want when the machine is being sold or the system is compromised.
The true clean install is: delete every partition on the target system disk until that one disk reads as a single line of Unallocated Space, then select that space and click Next. Setup creates its own EFI, system, MSR and recovery partitions. Do not create partitions manually; setup knows the layout it wants.
If there is a second physical disk in the machine that holds only data, leave it completely untouched. Windows setup does not need it, and its presence in the list is the most common cause of accidentally erasing the wrong thing. If you cannot tell which disk is which, the safest move is to shut down, physically disconnect the data disk, and start setup again.
Before clicking Delete
Say out loud which disk you are on and what is on it. Check that the backup drive is unplugged. If any row refers to a disk whose contents you cannot account for, stop here rather than guessing.
Errors that are really partition errors
"Windows cannot be installed to this disk. The selected disk has an MBR partition table" means you booted the installer in legacy BIOS mode while the disk is set up for UEFI, or the reverse. The fix is to boot the UEFI entry of the USB stick, not to convert the disk and not to disable Secure Boot.
"We couldn't create a new partition or locate an existing one" often follows an incomplete deletion, a lingering USB stick that setup tried to use as the system disk, or a disk with a stale protected partition. Rebooting setup with only the target disk attached and starting the deletion again usually resolves it.
A message about a missing media driver is a different class of problem: setup cannot see the storage controller. On some machines the vendor supplies a storage driver that has to be loaded at this screen. That driver should come from the hardware manufacturer, and it is one of the few legitimate reasons to put a file on the installer stick.
A short checklist for the screen itself
Keep this beside the machine. It is deliberately short, because the failure mode here is not lack of knowledge — it is clicking through a familiar-looking list too quickly.
- Backup drive disconnected, tested, and physically away from the machine.
- Only the target system disk and the installer USB stick attached.
- All partitions on the target disk deleted; that disk now shows one Unallocated Space line.
- No partitions on any other disk touched.
- Click Next on the unallocated space and let setup create its own layout.
If you get it wrong
Stop immediately. Do not continue installing over a disk you may have just erased by mistake, and do not write new data to it. Power the machine off and get advice before attempting recovery — deleted partitions are sometimes recoverable, but every minute of further writing reduces the chance. This is also why the tested backup is the first step of the whole process rather than the last.
If the only thing lost was a partition you intended to remove, continue. If anything unexpected disappeared, the honest answer is that a clean install cannot undo it. The site says so in the footer because it is the one outcome no guide can fix afterwards.
Mistakes to avoid
- Leaving the external backup drive plugged in and deleting its partition because it appeared as a smaller Drive number.
- Deleting only the large Windows partition and leaving the old EFI and recovery partitions, then finding the machine boots into an old recovery entry.
- Formatting instead of deleting when the goal was a genuinely clean install, then assuming personal files were gone.
- Booting the legacy entry of the USB stick to work around an MBR error, producing a layout that has to be redone later.
- Creating partitions manually because a tutorial showed a specific layout from an older Windows release.
- Continuing to install after an accidental deletion, which makes later recovery much less likely.
Questions people ask
Should I delete the recovery partition the manufacturer supplied?
For a true clean install on the system disk, all partitions on that disk are removed and setup creates its own. If you want to keep a factory recovery option, that is a different procedure — check the manufacturer's documentation before deleting.
Why is my second hard drive listed as Drive 0?
Disk numbering follows the controller and boot order, not the physical bay. Identify disks by size and contents, or disconnect the ones you do not need for the install.
Can I install to just one partition and keep a data partition on the same disk?
Technically yes, but it complicates the deletion step and offers no protection if the disk fails. A separate physical disk for data is the safer arrangement.
What is Windows.old?
A folder setup creates when an existing installation is overwritten rather than erased. It is not a backup: it can be removed automatically, and it is not a substitute for the tested external copy.
Sources and further reading
- Create installation media for Windows Microsoft Support · Official support article The authority for current prompt wording and requirements. Tutorials age; this page is updated by the vendor.
- Download Windows 11 Microsoft · Vendor download page The three options are not interchangeable. We cite this page for which one suits an upgrade, a clean install or a virtual machine, and for the rule that the image comes from the vendor.
- Microsoft Support — Windows help Microsoft Support · Official support documentation The first-party reference for activation and update behaviour after a clean install, and for the built-in troubleshooters.
- Windows 11 specifications and system requirements Microsoft · Vendor specification page We check requirements here before recommending any install. Older hardware gets an honest alternative, never a requirement bypass.
Editorial note. This article describes decision logic and checks, not laboratory results. It quotes no benchmark, no test score and no screenshot. Screen labels are reproduced so you can find them on your own device; the sources listed below are the vendor documentation they were checked against.