0x80300024: Fix Windows Install Error

Error code 0x80300024 appears during a Windows installation or upgrade when the setup program cannot write the boot files to the target disk, usually because the disk’s partition style or boot configuration is incompatible with the selected firmware mode. The fix is to either convert the disk to the correct partition style (GPT for UEFI, MBR for legacy BIOS) or delete and recreate the target partition so Windows can set it up fresh. This guide explains what causes the error, how to resolve it step by step, and how to avoid it on future installs.

What Does 0x80300024 Mean?

Windows setup uses a component called the Windows Boot Manager (BOOTMGR) to start the operating system. When you install Windows, setup must place boot files on a small, dedicated partition (the System Reserved partition on MBR disks, or the EFI System Partition on GPT disks). Error 0x80300024 is a generic setup failure that occurs when setup cannot create, format, or write to that boot partition. The most common triggers are:

The disk is MBR (Master Boot Record) but the PC is booted in UEFI mode, or the disk is GPT (GUID Partition Table) but the PC is booted in legacy BIOS mode.
The target partition is already marked as active or contains a previous Windows boot loader that conflicts with the new one.
The disk has a hidden system partition that is too small or corrupted.
Another drive in the system is interfering with the boot device order.

Because the error message itself does not say which of these is the problem, you have to check the disk layout and the firmware mode before you can fix it.

Check Your Firmware Mode and Disk Partition Style

Before changing anything, determine whether your PC uses UEFI or legacy BIOS, and what partition style your target disk uses. This is the single most important diagnostic step.

Boot into your current Windows installation (if you have one) or open a command prompt from the Windows setup screen by pressing Shift+F10.
Type diskpart and press Enter, then type list disk.
Look at the Gpt column. If it has an asterisk (*), the disk is GPT. If it is empty, the disk is MBR.
To check the firmware mode, restart the PC and enter the UEFI/BIOS setup (usually by pressing Del, F2, F10, or Esc during boot). Look for a setting called “Boot Mode,” “UEFI/Legacy,” or “CSM” (Compatibility Support Module). If it says UEFI, you need a GPT disk; if it says Legacy or CSM, you need an MBR disk.

If the disk style does not match the firmware mode, that is almost certainly your problem. For example, a new PC with UEFI firmware will refuse to install to an MBR disk with error 0x80300024.

Fix 1: Convert the Disk to the Correct Partition Style

If your disk is MBR but you are booting in UEFI mode, you can convert it to GPT without losing data using the built-in MBR2GPT tool, but only if the disk has no more than three primary partitions and has enough unallocated space for the EFI system partition. Here is how to do it from a Windows 10 or 11 installation USB:

Boot from the USB and press Shift+F10 to open Command Prompt.
Type diskpart, then list disk to find the disk number of your target drive (e.g., Disk 0).
Type exit to leave diskpart.
Run mbr2gpt /validate /disk:0 (replace 0 with your disk number). If the validation succeeds, run mbr2gpt /convert /disk:0.
Restart the PC, enter the UEFI setup, and ensure boot mode is set to UEFI (disable CSM). Then boot from the USB again and try the installation.

If you are in legacy BIOS mode and the disk is GPT, you have two options: either switch the firmware to UEFI mode (if your hardware supports it) and keep GPT, or convert the disk to MBR using a third-party tool or by wiping the disk. If the disk is empty, the simplest route is to delete all partitions during setup and let Windows recreate them in the correct style.

Fix 2: Delete and Recreate Partitions During Setup

If converting is not possible or you do not need to keep any data on the disk, the most reliable fix is to wipe the target disk during Windows setup. This removes any conflicting boot records and lets setup create the partitions it needs.

Boot from the Windows installation USB and proceed to the “Where do you want to install Windows?” screen.
Select each partition on the target disk (especially the small System Reserved or EFI partition) and click Delete. Repeat until the disk shows as “Unallocated Space.”
Select the unallocated space and click Next. Windows will automatically create the correct partition structure (GPT with EFI, or MBR with System Reserved) based on the firmware mode.

This method always works if the disk itself is healthy. If you have important data on the disk, back it up first, because deleting partitions erases everything.

Fix 3: Check for Other Drives and Boot Order

Sometimes the error is not about the target disk at all, but about another drive in the system. For example, if you have an old hard drive with a Windows boot manager, setup might try to write boot files to that drive instead of the SSD you selected. To rule this out:

Disconnect all drives except the one you want to install Windows on, then run setup again.
If the installation succeeds, reconnect the other drives and change the boot order in UEFI/BIOS so the new drive is first.
If you cannot disconnect drives (e.g., on a laptop), use the diskpart command to clean the target disk before starting setup. This removes any existing boot loader that might interfere.

To clean a disk with diskpart:

Open Command Prompt with Shift+F10.
Type diskpart, then list disk.
Type select disk X (replace X with the target disk number).
Type clean and press Enter. This removes all partitions and the boot loader.
Type exit and close Command Prompt, then continue with setup.

Common Mistakes and Misconceptions

One of the most common mistakes is trying to install Windows to a partition that is already marked as “Active” on an MBR disk. Windows setup usually handles this, but if the partition has a previous Windows installation, the new boot files may conflict. Deleting the partition and letting setup create a new one avoids this.

Another misconception is that error 0x80300024 means the disk is failing. While a failing disk can cause any setup error, this specific code is almost always a partition style or boot configuration issue. If you have verified the disk style matches the firmware mode and you still get the error, then you can suspect hardware, but not before.

Also note that error 0x80300024 is different from error 0x80300002, which is a more general “cannot access the disk” error. The 0x24 suffix specifically points to boot configuration, so focus on boot files and partition style first.

How to Avoid This Error on Future Installs

To prevent 0x80300024 from happening again, follow these best practices when installing Windows:

Always check the firmware mode (UEFI vs. Legacy) before creating installation media. If you are unsure, use the Windows Media Creation Tool, which creates media that works in both modes.
If you are installing to a new SSD, let Windows create the partitions automatically by selecting unallocated space.
If you are cloning an existing Windows installation to a new drive, use a cloning tool that handles partition style conversion, or manually convert the disk to the correct style before cloning.
Keep the UEFI/BIOS boot mode consistent with the disk style. If you switch from Legacy to UEFI, you must convert the system disk to GPT.

By understanding the relationship between partition styles and firmware modes, you can diagnose and fix this error in a few minutes rather than spending hours trying different installation methods.

Frequently Asked Questions

Will I lose my data if I fix 0x80300024?

It depends on the method. Converting MBR to GPT with mbr2gpt preserves your data if validation passes. Deleting partitions or using clean will erase everything on the target disk. Always back up important files before attempting any fix.

Can I fix this error without reinstalling Windows?

If the error occurs during an upgrade (not a clean install), you may be able to fix it by running the setup again after converting the disk to the correct partition style. If the error occurs during a clean install, you must correct the disk configuration before setup can proceed.

Why does my USB drive show as a boot device but the installation fails?

This usually means the USB is bootable but the target disk is not compatible with the firmware mode. For example, a UEFI boot of the USB will not install to an MBR disk. Check the disk style and convert it if needed.

Is error 0x80300024 the same as “Windows cannot be installed to this disk”?

No. The “Windows cannot be installed to this disk” message usually appears when the disk is GPT on a BIOS system or MBR on a UEFI system, and it tells you directly. Error 0x80300024 is a more generic code that can appear even when the disk style is correct, though the underlying cause is often the same boot configuration issue.

Does this error affect both Windows 10 and Windows 11?

Yes, both versions use the same setup engine and can produce error 0x80300024. Windows 11 has a stricter requirement for UEFI and GPT, so the error is more common if you try to install it on a legacy BIOS system.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →