Windows Setup Says "We Couldn't Create a New Partition"? A Cockenzie Fix Guide

A Windows installer that keeps refusing to lay a system partition down is one of the most frustrating places a reinstall can stall. This Cockenzie guide covers what the error really means and how to get past it without wiping the wrong drive.

20 November 2026 8 min read Windows Tips Alex M.
Windows installer couldn't create a new partition fix guide for Cockenzie from PC Repair Services

A Cockenzie owner brought us a desktop tower last month that would not finish a Windows 11 reinstall at home. They had made a fresh install USB on another PC, booted from it, clicked through the language and keyboard pages, chosen the drive they wanted Windows on, and hit the message that brings most self-installs to a halt: "We couldn't create a new partition or locate an existing one." They had tried three different USB sticks, two different Windows 11 ISO downloads and had re-formatted the target drive in two different ways. The machine itself was healthy, the storage was fine, and the installer was simply refusing to lay a system partition down on it. The whole fix was about ten minutes on the bench once we worked out which disk Windows Setup was actually pointing at, and this guide walks through the same bench checks we run on any Windows reinstall that stalls at that screen — whether the machine is a home laptop in Cockenzie, a small-office tower in Prestonpans or a self-built gaming rig that has lost its boot drive somewhere along the way.

What the Error Actually Means

"We couldn't create a new partition or locate an existing one" is Windows Setup saying that it reached the point where it would normally carve the drive up into the system, recovery and main partitions it needs, and the attempt failed. On modern Windows 11 builds the same underlying failure also shows as error code 0x80300024. The message is deliberately vague because the cause can sit at any one of three layers: the installer is looking at the wrong disk, the drive it is looking at has a partition style the firmware will not boot from, or the drive itself is not usable — locked, failing, or still mounted somewhere the installer cannot evict. The order the bench works through those three is what turns a stuck reinstall into a short job.

Back Up Before You Try Again

The single most common cause of lost files from a stuck install is a frustrated owner clicking "Format" or "Delete" on a drive they thought was empty. Before any more attempts, take the laptop or tower off the install USB, boot it back into the old Windows, and copy anything important off to an external drive — or, if the machine will not boot the old system any more, bring it in and let us image the drive first. On a desktop tower you can also pull the data drive physically, label it, and reconnect it only after the install has finished. Our data recovery bench sees several of these every month where a working drive was wiped by mistake during a reinstall; a full image before you touch Setup again removes the risk completely. If the drive is already doing anything unusual — strange noises, SMART warnings or a RAW volume — read our Cramond RAW drive guide before you reinstall rather than after.

Why Setup Can't Create a Partition

There are four recurring causes behind the error, and we check them in the same order every time on the bench. The first is the wrong target disk — the installer is pointing at a disk that is not really the boot drive, usually because the USB stick, an old data drive or a plugged-in external drive has grabbed disk 0. The second is a partition-style mismatch: the firmware is set to UEFI and the target drive still has the old MBR partition table from a Windows 7 or Windows 10 era, or the other way round on an older board. The third is a residual partition the installer cannot evict — a Dell, HP or Lenovo recovery partition, a BitLocker-locked volume, or leftover Intel Optane metadata that still thinks it owns the drive. The fourth is a drive-level fault — bad sectors on an older spinning disk, a failing NVMe that reads but will not write, or a loose M.2 that drops off the bus the moment Setup tries to write to it. The first three are fixable in minutes; the fourth is a hardware problem dressed up as a software one.

The Clean Way to Get Past the Error

On the bench we work through the drive picker in a fixed sequence. First, we unplug every drive that is not the install USB and the one drive we want Windows on — a second internal SSD, an external backup drive, an SD card in a reader, any of them can make the installer see the wrong disk as disk 0. Second, we reboot the installer and watch the number next to the drives on the drive-picker page: the target install drive should be the one with the full capacity of the machine's main SSD, not the 32 GB or 64 GB number that is the USB stick. Third, if the drive picker still lists leftover partitions on the target, we delete every partition on that single drive from the Windows Setup screen so the whole disk shows as unallocated space, and then let Setup create what it needs from scratch. Four times out of five, that sequence alone clears the error.

For the fifth time, the fix is a short visit to the command line inside the installer. Pressing Shift+F10 on the drive-picker screen opens a command prompt. Typing diskpart, then list disk, shows every disk the installer can see; select disk 0 picks the first one, and clean strips every partition and signature off it. Setup then refreshes and shows the whole drive as empty, ready to accept the standard partition layout. The crucial safety step is the list disk output before the clean — the sizes next to each disk confirm which one is the boot target before any command touches it. We never type clean without reading the size column out loud first, and no owner should either; a clean on the wrong disk is instant data loss.

The GPT vs MBR Mismatch

The error that usually survives the drive-picker sequence above is the partition-style mismatch. Windows 11 expects a GPT-partitioned drive on a UEFI firmware, which is almost every PC built in the last ten years. A drive that still carries the older MBR partition table — often because it was first installed under Windows 7 or an early Windows 10 release — will accept a Windows install on an older board in legacy BIOS mode, but a modern UEFI machine refuses to put the system partition down on it. From inside Setup, Shift+F10 again, diskpart, list disk, select disk for the target, and convert gpt turns the table style over. The reverse command, convert mbr, is there for the rare older board that is set to legacy BIOS and will not accept a GPT drive. Both commands wipe every partition on that disk, so the backup step above is not optional.

If the firmware itself is in the wrong mode — legacy BIOS when it should be UEFI — the conversion will not help on its own. Rebooting into the firmware setup page, switching the boot mode to UEFI and disabling the compatibility support module usually clears the last of this family of errors. Secure Boot can stay on afterwards; it tends to be the default on a clean Windows 11 install.

When the Drive Itself Is the Problem

If every drive-picker step has been tried, the partition style matches the firmware, and the error still comes back on the same disk, the drive itself is the honest suspect. An NVMe that reads fine in the boot menu but will not accept a fresh partition is often early-stage write failure — we see this on older drives that have reached their flash wear limit, and on a few NVMes with recurring firmware bugs. A SATA SSD or spinning disk with bad sectors behaves the same way: Setup can read the drive just well enough to list it, and then times out the moment it tries to write a partition table. At that point we move the drive onto a bench rig, pull SMART data, and either quote a storage upgrade alongside the reinstall or, if the drive held irreplaceable files, route it to data recovery before any more install attempts. Our wider cloned SSD won't boot guide covers the next-step scenario where the install does complete but the drive will not boot afterwards, and the no drives found guide from Broxburn covers the sibling case where Setup cannot see the drive at all.

Doing the Reinstall Properly From the Start

If you are at the point of running Setup again anyway, it is worth making the attempt a full clean OS install rather than a patched repair — our clean install walkthrough covers the end-to-end steps from a working install USB to a finished desktop. The checks in this guide fit into that workflow at the drive-picker page, where most reinstalls actually stall. A fresh Windows 11 build with current drivers, a clean GPT partition table and a modern NVMe is also noticeably faster than the install it is replacing — part of why the owners who come in with "we're thinking of replacing the PC" in Cockenzie, Port Seton, Prestonpans and Tranent often leave with a reinstall quote instead of a new box. Our general software troubleshooting service covers the bench time for either outcome.

Reinstall Help Across Cockenzie and East Lothian

We take Windows reinstall and install-stuck jobs in from Cockenzie, Port Seton, Longniddry, Prestonpans, Tranent, Musselburgh, Haddington and the wider East Lothian commuter belt most weeks, and from the Edinburgh city stops on the same run. Most stuck-install jobs are a same-day bench visit — we image the drive if anything irreplaceable is on it, work through the drive-picker and diskpart sequence above, and hand the machine back with a finished Windows install, the owner's files restored into the new user profile, and a short note of what actually caused the error so it does not come back on the next reinstall. If the fault turned out to be a failing drive rather than a stuck installer, the replacement SSD is on the same quote and we would rather tell you that before the bench clock starts than after it. For a quick bench check on where a reinstall has stalled in Cockenzie or anywhere along the East Lothian coast, book a drop-in at the EH11 workshop or a local collection and we will have the same-day answer for you.

Last updated: 20 November 2026

Frequently Asked Questions

What Cockenzie and East Lothian owners ask us about Windows reinstalls that stall at the partition step.

Not on its own. Four times out of five the message means the installer was pointing at the wrong disk, or the drive still has a partition style the firmware will not boot from. Unplugging every drive except the target, deleting any leftover partitions on it from inside Setup, or converting the partition table with diskpart usually clears it. The drive itself is only the honest suspect once those steps have been tried and the same error comes back on the same disk.

Only on a drive you are certain holds nothing you want to keep. The Format and Delete buttons on the drive-picker page act on the exact partition they are clicked against, and they are irreversible once the install carries on. If anything on the drive matters, back it up first or bring the machine in and let us image the drive before any Format is clicked. Lost files from an impatient Format are the most common reason reinstalls end up at our data-recovery bench rather than our Windows bench.

Shift+F10 opens a command prompt from any screen in Windows Setup, including the drive picker. It is safe to use for listing disks and checking which number the installer has assigned to each one before running any command that writes to the drive. The commands that need caution are clean and convert gpt or convert mbr inside diskpart — both wipe every partition on the selected disk and both are instant. Reading the size column from list disk out loud before pressing enter on either command is the safety step that stops the wrong drive being wiped.

Usually the default UEFI settings on a modern PC are already right for Windows 11 — UEFI boot mode, Secure Boot on, TPM enabled. The settings worth checking if the partition error survives every drive-picker step are the boot mode (UEFI, not legacy or CSM) and the SATA mode (AHCI, not RAID if no RAID is in use). A board left in legacy BIOS mode will not accept a GPT drive, and a board left in RAID mode may hide a healthy NVMe behind an Intel Optane driver the installer does not have. We check both as part of a reinstall bench job.

Yes. Cockenzie, Port Seton, Longniddry, Prestonpans, Tranent, Musselburgh and Haddington are on the regular East Lothian collection round, and the Edinburgh city stops are on the same run most weeks. A stuck Windows install is almost always a same-day bench visit — we image the drive if anything irreplaceable is on it, work through the drive-picker and diskpart checks on the bench, and hand the machine back with a finished install and a short note of what actually caused the error. If it turned out to be a failing drive rather than a stuck installer, the replacement SSD is on the same quote.

Windows Install Stuck at the Partition Step in Cockenzie?

Bring it into the EH11 workshop or book a local collection across Cockenzie, Port Seton, Prestonpans, Tranent, Musselburgh and the East Lothian coast. We will image the drive first if anything matters, work through the drive-picker and diskpart checks on the bench, and hand the machine back with a finished install the same day where we can.