The cruellest version of this error: one physical disk, several partitions — Windows on one, years of photos, accounts and work files on another — and the only fix the internet offers starts with a command that wipes the whole disk. This page explains why conversion threatens ALL partitions, not just the Windows one, and lays out the three honest ways out.
First, the fact everything else depends on: a partition style belongs to the whole physical disk, not to individual partitions. There is no such thing as a GPT C: partition beside an MBR D: partition on the same drive — the disk is GPT or it is MBR, entirely. And DiskPart converts only empty disks, so its route is clean — which deletes every partition on the disk at once: the Windows partition, the data partition, the recovery partition, everything, with all files in them. Running it to fix an install error on a shared family or office disk is how data partitions that 'were not even involved' get destroyed. Here is how to keep them.
If the data partitions matter, this is almost always the correct answer, and it touches nothing on the disk:
Your data partition rides through untouched because the disk was never modified. Note the one honest caveat: installing Windows onto the C: partition still replaces what is on C: itself — files stored on the Windows partition need their own backup regardless of any conversion question.
When conversion genuinely must happen — say this disk is moving to a UEFI-only machine as GPT — do it as a planned migration:
clean and convert — erasing a disk whose value you already hold elsewhereSlow, unglamorous, and incapable of ending in disaster. This is the route professionals use on other people's machines, because 'the tool said it would keep the partitions' is not an acceptable explanation for a client's lost accounts data.
One specific situation has a supported in-place answer. If the disk is MBR, contains a working Windows 10/11 system, and your goal is GPT for a move to UEFI boot, Microsoft's mbr2gpt converts the system disk in place, partitions and data included — run from inside that Windows, after mbr2gpt /validate /disk:0 /allowFullOS passes, with at most 3 partitions and no extended/logical partitions on the disk.
Its limits are as important as its promise: system disk only, MBR to GPT only, working Windows required. It does nothing for a bare disk at an install screen, and nothing at all for GPT to MBR. And even here, a backup first is the professional standard — 'designed to keep your data' is not the same as 'cannot fail'.
Search results will suggest partition tools that promise in-place style conversion keeping all partitions. Sometimes they work. Understand the gamble precisely: such a tool rewrites the disk's master partition map while your data sits beneath it, and a crash, power cut or unhandled layout midway leaves a disk that may need professional recovery. Factories and forums are full of both outcomes.
The decision rule is simple. If losing the data partition is an annoyance, a reputable tool with the PC on a UPS is a defensible risk. If losing it is a disaster — business records, only copies of family photos — the defensible options are exactly the three above, and all of them share one feature: at no point does your only copy of the data sit under a rewriting partition map.
clean does not erase 'the Windows partition' — it erases the entire physical disk and every partition on it, including data partitions you never selected. On a disk whose D: drive holds anything irreplaceable, conversion at Setup is simply not your fix. Change the boot mode, or move the data first.Watch the video knowing this page's warning — you will see the conversion happen on an empty disk, which is the only kind of disk it should ever happen on.
▶️ Watch Full VideoNo — partition style is a property of the whole disk, not of single partitions. A disk is GPT or MBR in its entirety. Any conversion process therefore concerns every partition on that physical drive, which is why the data partition is at risk even though the install error only mentions installing Windows.
Yes, in the normal case. Installing Windows touches only the partition you select for installation (plus small system partitions Setup manages). The standard precautions still apply: select the partition carefully by size and label, and keep a backup of anything irreplaceable — installs are routine, but no operation on a disk is ever literally zero-risk.
Clean erases it along with everything else. On an old machine that recovery partition may be your only factory restore source. A Windows install USB does the same job better today, but if the machine's recovery partition matters to you, that is one more reason to choose the boot-mode fix over conversion.