| Problem | Windows Server 2022 Error 0x80300024 |
|---|---|
| Common Cause | Multiple hard drives, faulty USB port, or partition issues |
| Difficulty | Intermediate |
| Estimated Time | 15 Minutes |
What is Windows Server 2022 Error 0x80300024?
Error 0x80300024 is a common installation obstacle encountered when deploying Windows Server 2022. It typically indicates that Windows cannot be installed to the location you have selected.
This error usually stems from a hardware or software conflict involving the target hard drive. It often occurs when the installer is confused by multiple storage devices or if the partition table is corrupted.
In most cases, the installer cannot verify the destination drive’s capability to boot. This can be caused by something as simple as a USB drive plugged into the wrong port or as complex as incorrect UEFI settings.
Step-by-Step Solutions
1. Disconnect Unnecessary Hard Drives
The most frequent cause of error 0x80300024 is the presence of multiple hard drives. The installer may struggle to identify the primary boot drive among several disks.
Shut down the server and physically disconnect all hard drives except for the one intended for the Windows Server 2022 installation. Restart the process to see if the error persists.
2. Use Diskpart to Clean the Destination Drive
Residual partition data or hidden recovery sectors can block a clean installation. Using the Command Prompt during setup can clear these obstacles.
Press Shift + F10 at the installation screen to open the Command Prompt and execute the following commands:
diskpart
list disk
select disk 0
clean
exitNote: Replace “0” with the number corresponding to your target drive. Warning: This will erase all data on that specific disk.
3. Change the USB Port
If you are installing via a USB bootable media, the specific port you are using might be the culprit. USB 3.0 ports sometimes require drivers that the basic installer doesn’t load immediately.
Try plugging your installation media into a USB 2.0 port instead. If you are already using a 2.0 port, try a port located directly on the motherboard (rear of the chassis) rather than the front panel.
4. Verify Boot Order in UEFI/BIOS
The error can trigger if the target drive is not set as the primary boot device in the system firmware. The installer checks if it can actually boot from the drive it’s writing to.
Enter your BIOS/UEFI settings and ensure the target SSD or HDD is at the top of the boot priority list, immediately following the installation media. Ensure the boot mode matches your partition style (UEFI for GPT).