You booted the stick, reached the disk screen, clicked your drive — and setup refuses: "Windows cannot be installed to this disk." The message is not about a broken disk. It is setup telling you the boot mode of your stick and the style of the disk disagree.
This error appears in two mirror-image forms. One says the disk is of the GPT partition style; the other says the disk has an MBR partition table and that on EFI systems Windows can only be installed to GPT disks. Both mean the same thing: Windows setup installs in the mode it was booted in. Boot the stick in UEFI mode and setup demands a GPT disk. Boot it in legacy mode and setup demands MBR. The disk is not faulty — the pairing is. You have two honest fixes: change how you booted, or change the disk. Choose by which one holds data you care about.
👆 The genuine setup wording. Read the last line slowly — it names exactly which side of the pairing is which.
This fix changes nothing on the disk at all. It is always the first try when the disk holds an existing Windows or data you have not backed up.
For a fresh install on a disk whose contents do not matter, converting is clean and permanent. First the honesty: the conversion below wipes the entire disk, not one partition. If anything on it matters and is not backed up, stop and use Fix One or the MBR2GPT route instead.
diskpart, then list disk — identify your disk by size, carefullyselect disk 0 (use your disk number), then cleanconvert gpt for a UEFI install — or convert mbr for a legacy installexit twice, close the prompt, and continue setupIf the disk is new, or already erased, you can skip conversion commands entirely. On the disk screen, delete every partition until the whole disk shows as Unallocated Space, select it, and click Next. Setup creates the style that matches how it was booted — GPT under UEFI, MBR under legacy — and builds the right system partitions itself. This is why the error never appears on truly empty disks: there is no existing style to argue with.
The professional habit: decide the install mode when making the USB, not when standing at the error. Modern PC, clean install → GPT stick, boot its UEFI entry, disk becomes or stays GPT. Old PC or preserving an MBR install → MBR stick, legacy entry. The error is setup protecting you from a half-matched install that would fail to boot later — treat it as a signpost, not a fault, and it stops costing you time.
clean command does not ask twice. In DiskPart, one wrong disk number erases the wrong drive completely. Read the size column twice before pressing Enter — especially on PCs with two similar disks fitted.
The video covers this pairing from the stick-making side, in Rufus and Ventoy, so the error never gets a chance to appear — the full walkthrough is in the video above.
▶️ Watch Full VideoBecause setup was booted in legacy mode, likely from an MBR stick or the plain (non-UEFI) boot entry. Legacy setup cannot install to GPT. Reboot and choose the UEFI: entry for your USB and the same disk is accepted immediately, untouched.
From inside a working Windows, yes — the MBR2GPT tool converts a system disk without data loss, and there is a dedicated page for it in this series. At the setup screen, no: DiskPart conversion is destructive. If the data matters, leave setup and convert from Windows instead.
That is a different problem from this error — a missing disk means a storage driver or connection issue (common on new Intel machines that need their RST driver loaded). This page covers disks that appear but refuse the install. Load the driver or check the disk connection first.