Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0x80300024

0x80300024 and 0x80042405: Setup cannot use the selected disk or partition

11 min read Updated October 5, 2026 Windows Update & Setup

Fix it now

Two of these four codes have published meanings and two do not. 0x80042405 is VDS_E_OBJECT_NOT_FOUND from the Virtual Disk Service – the object asked for was not found. 0xC1900112 is MOSETUP_E_TARGET_DRIVE_NOT_FOUND, no target drive letter. Both are about the installer not finding what it expects, and the usual reason is a partition style that does not match the firmware.

From the Setup screen press Shift+F10 and run these – clean erases the selected disk, so confirm the disk number first

diskpart
list disk
select disk 0
clean
convert gpt
exit
  1. Press Shift+F10 at the Setup screen to open a command prompt without leaving the installer.
  2. Run diskpart and list disk. If the target disk is not listed at all, Setup has no storage driver for the controller and no amount of partition work will help.
  3. Read the GPT column in the list disk output. A machine booted in UEFI mode needs a GPT disk; one booted in legacy BIOS-compatibility mode needs MBR. Microsoft’s published error text for the mismatch is ‘Windows cannot be installed to this disk. The selected disk is not of the GPT partition style’.
  4. If the two disagree, either restart the PC in legacy BIOS-compatibility mode to keep the existing style, or convert the disk to GPT. Those are Microsoft’s two published routes.
  5. To convert an installed Windows without losing it, boot into that Windows instead and run MBR2GPT /validate /disk:0 /allowFullOS before MBR2GPT /convert /disk:0 /allowFullOS.
  6. To install fresh, run the block above, close the prompt, and choose Custom installation. The drive appears as unallocated space; select it and continue.

clean erases the entire partition table of the selected disk with no further prompt and no undo. Confirm with list disk and detail disk that you have the right one and that everything on it is expendable.

If Setup accepts the disk and starts copying, you are through. If it does not, the next section covers the states Setup refuses and what the codes do and do not tell you.

Why it happens

Windows Setup will not write to a target it cannot address in the way the firmware expects. Microsoft’s rule is explicit: a PC booted in UEFI mode requires the GPT partition style, and one booted in legacy BIOS-compatibility mode requires MBR. Most of what is filed under these codes is that single mismatch, and the machine is not faulty at all.

0x80042405 is worth reading carefully because its published meaning is narrower than the way it gets described. It is VDS_E_OBJECT_NOT_FOUND from the Virtual Disk Service error list: ‘The specified object was not found.’ That is a statement about something the disk service asked for and could not find – a disk, a volume, a partition object – rather than a general refusal to use a disk. It is why the code turns up when a device drops off the bus, when a controller is invisible to the installer, and when a volume disappears between one operation and the next.

0xC1900112 is MOSETUP_E_TARGET_DRIVE_NOT_FOUND: ‘Could not find a target drive letter.’ Again, not found rather than refused. Together those two codes describe an installer looking for something that is not there, which is a different search from ‘the layout is wrong’ even though the two often share a cause.

0x80300024 and 0x800701E3 have no published meanings at all. 0x80300024 returns nothing from Microsoft’s documentation. 0x800701E3 carries the 0x8007 prefix that marks a Win32 error, and its low word is 483 decimal, which is not present in Microsoft’s published system error code list. Describe them by what you observe – Setup declining the location you chose – and diagnose from the disk state rather than from an invented definition.

The partition style and the firmware mode disagree

You have this one if The disk is visible in diskpart but Setup will not accept it, and list disk shows no asterisk in the GPT column on a UEFI machine.

  1. Decide which way to go. UEFI with GPT is the right answer on any machine that supports it, and Secure Boot requires it.
  2. To keep an installed Windows, boot into it and convert with MBR2GPT after validating.
  3. To install fresh, use the diskpart block above and let Setup create the partitions.
  4. Set the firmware to UEFI and disable CSM so the two agree, and confirm afterwards with msinfo32 that BIOS Mode reads UEFI.

Setup has no driver for the storage controller

You have this one if No disks appear in the list at all, on a recent laptop or a machine with an add-in controller.

  1. Download the storage driver from the machine manufacturer – usually listed as a rapid storage, VMD or RAID driver – and extract it to a second USB stick.
  2. At the disk selection screen choose Load driver, browse to the folder and select the INF.
  3. If no driver is available, change the controller mode in firmware from RAID or VMD to AHCI and refresh the list.

Changing the controller mode on a machine that already has Windows installed on that disk stops it booting until the matching driver is enabled. Do this before an installation, not after.

The disk is offline, read-only or dynamic

You have this one if list disk shows the disk offline, detail disk reports the read-only attribute set, or the disk type is Dynamic rather than Basic.

  1. In diskpart, select the disk and bring it online, then clear the read-only attribute.
  2. For a dynamic disk holding data you need, boot into a working Windows and back the data up first; there is no lossless conversion to basic from inside Setup.
  3. For a dynamic disk you can wipe, clean it and convert it to basic before returning to Setup.

Another disk is confusing the boot layout

You have this one if The machine has several disks and Setup either refuses the chosen one or puts the boot files somewhere unexpected.

  1. Disconnect every disk except the target before installing. It is the most reliable way to get a clean layout on a multi-disk machine.
  2. Install, then reconnect the other disks once Windows is up.
  3. Confirm with bcdedit /enum that the boot entries point at the disk you intended.

Microsoft documents multiple system partitions as a cause of partition analysis failures during upgrade, with the remedy of disconnecting or disabling the drives holding the unused ones. The same logic applies to a clean install.

The source media is the real problem

You have this one if The error appears part way through copying rather than at selection, or the same USB stick fails on more than one machine.

  1. Rebuild the installation media on a different USB stick, and try a USB 2.0 port if the machine has one.
  2. Verify the ISO before writing it: Get-FileHash -Path .\Windows.iso -Algorithm SHA256 and compare with the value published where you downloaded it.
  3. If you are upgrading rather than installing, copy the ISO to an internal disk and mount it instead.

Full reference

What each code is worth

Code Documentation status
0x80300024 Not published by Microsoft
0x80042405 VDS_E_OBJECT_NOT_FOUND: the specified object was not found
0x800701E3 Not published; the Win32 low word 483 is absent from the system error code list
0xC1900112 MOSETUP_E_TARGET_DRIVE_NOT_FOUND: could not find a target drive letter

Matching the symptom to the cause

What you see at Setup Where the fault is
The disk is not listed at all No storage driver for the controller, or an unsupported controller mode
The disk is listed but cannot be selected Partition style does not match the firmware boot mode
list disk shows the disk offline or read-only Disk attributes, cleared from diskpart
The disk shows as Dynamic Setup will not install to a dynamic disk
The error appears part way through copying Source media rather than the target disk

What MBR2GPT checks before it changes anything

MBR2GPT validates the layout and geometry first, and refuses if any check fails. The published checks are that the disk is currently MBR; that there is room for the primary and secondary GPTs – 16 KB plus two sectors at the front and 16 KB plus one sector at the end; that there are at most three primary partitions; that one is active and is the system partition; that there is no extended or logical partition; that the BCD store on the system partition has a default OS entry pointing at an OS partition; that volume IDs can be retrieved for every lettered volume; and that all partitions are of MBR types Windows recognises or are mapped with /map.

Option What it does
/validate Runs the validation only and reports whether the disk is eligible
/convert Validates and then converts if every check passes
/disk:<n> Chooses the disk; the system disk is used if omitted
/logs:<dir> Where the logs go; the directory must already exist
/map:<source>=<destination> Adds partition type mappings between MBR and GPT
/allowFullOS Allows the tool to run outside Windows PE

The part of the conversion people forget

Run with /allowFullOS, the existing MBR system partition is in use and cannot be reused, so MBR2GPT creates a new EFI system partition by shrinking the OS partition. And after the conversion the firmware must be reconfigured to boot in UEFI mode – the tool’s own output says so. A converted disk with the firmware still set to legacy boot is a machine that will not start, which is why the image backup matters more than it usually does.

If Setup still will not take the disk

  • Read detail disk as well as list disk; the read-only attribute is easy to miss and stops everything.
  • Check the disk in the firmware setup screen. A disk the firmware cannot see is not a Setup problem.
  • Try a different port or cable on a desktop before concluding the drive has failed.
  • Remember that a genuinely failing disk announces itself with read errors and stalls rather than with a polite refusal at the selection screen.

Every code this article covers

Code What it points at Source
0x80300024 Seen when Setup declines the location chosen for the installation; no acceptable source publishes a meaning, so diagnose it from the disk state not published by the vendor
0x80042405 VDS_E_OBJECT_NOT_FOUND: the Virtual Disk Service could not find the specified object Microsoft Learn
0x800701E3 A Win32-prefixed code whose low word, 483, is not in Microsoft’s published system error code list; no meaning is published not published by the vendor
0xC1900112 MOSETUP_E_TARGET_DRIVE_NOT_FOUND: could not find a target drive letter Microsoft Learn

Confirm the fix worked

  1. list disk shows the target as Basic and online, with the partition style matching the firmware boot mode.
  2. detail disk shows the read-only attribute cleared.
  3. Setup accepts the partition and begins copying files.
  4. After installation, msinfo32 reports BIOS Mode UEFI on a machine you intended to convert.
  5. The machine boots without the installation media attached.

Questions people ask about this

Do I need to buy anything to fix this?

No. Everything here uses tools already on the installation media or already in Windows. A disk Setup will not accept is a layout or driver problem.

Is MBR2GPT safe on a machine with data on it?

It is designed for exactly that and validates the layout before changing anything. The risk is not the conversion but the firmware change that has to follow it: a converted disk with the firmware still set to legacy boot will not start. Take an image backup and suspend BitLocker first.

Should I use MBR to keep life simple?

Only if the machine cannot do UEFI. MBR means no Secure Boot, which means the machine will not pass the Windows 11 requirements check later. Converting now is less work than converting after you have installed.

What does 0x80300024 mean?

Nothing that any acceptable source publishes. It appears when Setup declines the location you chose. Diagnose it from the disk state – style, attributes, whether the disk is even listed – rather than from any definition you find for the number itself.

The disk appears in the BIOS but not in Setup. Is it dead?

Almost certainly not. Setup needs a driver for the controller, and the firmware does not. Load the manufacturer’s storage driver from a second USB stick, or switch the controller from RAID or VMD to AHCI before installing.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error 0x80248015 and 0x8024002E: an expired service registration or a policy block License Error 0xC1900200 and 0xC1900201: this PC does not meet Windows 11 requirements License Error 0xC1420127 and 0xC1900403: the upgrade rolls back every single attempt License Error 0x800F0906 in DISM: Windows cannot download the repair source files
โ† Back to Knowledge Base