How to Fix a Proxmox VE Installer That Won't Boot or Freezes (USB, Secure Boot, and 'No Disks Found' Explained)

You burned the ISO, plugged in the USB drive, and hit boot. And now you're staring at a black screen, a frozen progress bar, or a message that says no disks were found. It's one of the most common walls new Proxmox users hit, and it has almost nothing to do with whether Proxmox VE is right for your hardware. Most of the time it's the USB stick, a BIOS setting, or a boot mode mismatch.

This guide walks through the actual causes of a Proxmox VE installer that won't boot or freezes partway through, and how to fix each one. If you haven't installed Proxmox before, note that this article assumes you already have a USB drive prepared and are past the "which hardware do I need" stage — if you want to check your hardware first, that's a separate topic. Here we're focused entirely on getting the installer itself to boot and finish.

What You Will Learn

By the end of this article you'll be able to:

• Tell the difference between a bad USB write, a BIOS boot mode problem, and a hardware detection issue
• Rebuild your installer USB the correct way on Windows, macOS, and Linux
• Fix Secure Boot and Legacy BIOS/UEFI conflicts that stop the installer from loading
• Get past "no disks found" when your storage controller isn't detected
• Read the installer's hidden log screens to see what's actually going wrong

What Is This Feature?

The Proxmox VE installer is a stripped-down Debian-based boot environment that lives entirely on the USB stick (or CD, if your server is old enough to still have a drive). When you boot from it, your computer isn't running Proxmox yet — it's running a small Linux system whose only job is to partition your disk, copy the Proxmox files onto it, and set up the bootloader. Nothing about this stage touches your operating system philosophy or long-term configuration. It's plumbing.

Because it's such a minimal environment, it's also more sensitive to certain quirks than a full desktop Linux install would be: an oddly formatted USB drive, a disk controller running in RAID mode instead of AHCI, or a firmware setting like Secure Boot can each stop it cold. None of these problems mean anything is wrong with Proxmox itself.

Why Would You Use It?

You don't have much choice — the graphical installer is the standard way almost everyone gets Proxmox VE onto bare metal for the first time. There is a manual "install via console" path (booting a plain Debian net-install and adding Proxmox packages on top), but it's more work and most beginners never need it. Getting the normal installer working is worth the ten minutes of troubleshooting, because everything else in your Proxmox journey — VMs, containers, backups, clustering — sits on top of this one step working correctly.

Prerequisites

• A downloaded Proxmox VE ISO from the official Proxmox downloads page (this guide was written against Proxmox VE 9.2, built on Debian 13 Trixie)
• A USB flash drive, at least 2 GB, that you don't mind wiping completely
• Access to your server or PC's firmware/BIOS setup screen (usually Del, F2, F10, F11, or F12 at power-on — check your motherboard manual if you're not sure)
• A second computer to re-write the USB drive if the first attempt fails
• Ten to twenty minutes, depending on how many attempts it takes

Step-by-Step Tutorial

1. Verify the ISO download before you do anything else

A surprising number of "installer won't boot" reports trace back to a corrupted download, not a bad USB write. Before you touch a flash drive, check the file size against what's listed on the Proxmox downloads page, and if you want to be thorough, compare the SHA256 checksum:

sha256sum proxmox-ve_9.2-1.iso

Compare the output against the checksum published next to the download link. If they don't match, delete the ISO and download it again — don't waste time troubleshooting a file that was never good in the first place.

2. Write the ISO to USB the right way

This is where most boot failures actually come from. Proxmox's own documentation is specific about this step, and skipping the specifics is what causes "no bootable device" errors later.

On Linux, identify your USB device first with lsblk (run it before and after plugging in the drive so you can see which device appeared), then write directly to the raw device — never a partition:

dd bs=1M conv=fdatasync if=./proxmox-ve_9.2-1.iso of=/dev/sdX

Replace /dev/sdX with your actual device, not /dev/sdX1. Writing to a partition instead of the whole disk is one of the most common mistakes here, and it produces a USB stick that looks fine in a file manager but won't boot.

On Windows, use balenaEtcher (etcher.io) or Rufus (rufus.ie). Etcher works with no extra configuration. Rufus needs one extra click: when it asks how you'd like to write the image, choose DD mode, not the default ISO mode. If Rufus asks whether to download an updated version of GRUB, say no. Avoid UNetbootin entirely — it's known to produce non-booting Proxmox media.

On macOS, convert the ISO to a DMG first, then write it with dd:

hdiutil convert proxmox-ve_9.2-1.iso -format UDRW -o proxmox-ve_9.2-1.dmg
diskutil unmountDisk /dev/diskX
sudo dd if=proxmox-ve_9.2-1.dmg bs=1M of=/dev/rdiskX

Note the rdiskX instead of diskX in the final command — the raw device node writes noticeably faster.

3. Set the correct boot mode in firmware

Reboot into your BIOS/UEFI setup and confirm two things: that booting from USB is actually enabled (some boards disable it by default), and that your boot mode matches what your drive was written for. Modern Proxmox installers boot fine under UEFI, which is what most hardware from the last several years defaults to. If your board is older or set to Legacy/CSM mode, that's usually fine too, but mixing the two — a UEFI-only image on a board hard-locked to Legacy, or vice versa — will show you either a blank menu or an immediate reboot loop.

4. Turn off Secure Boot if the installer refuses to load

Secure Boot support landed in Proxmox VE 8.1. If you're running that or newer, Secure Boot should generally work. But if the installer hangs immediately after the boot menu, or you see a message about an unsigned or untrusted image, disable Secure Boot in firmware as a first troubleshooting step. You can always re-enable it after Proxmox is installed and confirm it still boots — some boards handle the shim differently than others.

5. Watch the actual boot process for clues

If the installer boots but then freezes, don't just assume it's stuck — press Ctrl+Alt+F2 to switch to the second virtual terminal. This drops you into a shell showing the live installation log, which is far more useful than staring at a spinning graphical progress bar. Errors that are silent on the main screen are usually right there in plain text on TTY2.

6. Add nomodeset if the screen goes black or garbled

Some GPUs, particularly certain older or unusual chipsets, don't get along with the installer's default graphics driver and produce a black screen, garbled text, or a frozen splash. At the boot menu, highlight the install option, press e to edit it, find the line starting with linux, and add nomodeset to the end of it before booting. This forces a basic, compatible graphics mode and is a purely cosmetic fix — it doesn't affect anything about the eventual installation.

7. Fix "no disks found" during partitioning

If the installer boots cleanly but shows an empty list where your hard drive or SSD should be, the most common cause is a RAID or "Intel RST" mode set on your storage controller in firmware. Proxmox needs the controller running in plain AHCI mode (or, for NVMe drives, standard NVMe mode) to see the disk directly. Go back into firmware, find the SATA/storage configuration section, and switch it from RAID to AHCI. Note this will make any existing RAID array on that controller invisible to other operating systems too, so only do this on a machine you're dedicating to Proxmox.

Commands Explained

Common Errors

• "No bootable device found" — the USB wasn't written correctly, or boot-from-USB isn't enabled in firmware. Re-check both.
• Installer menu appears, then screen goes black and stays black — usually a graphics driver conflict; try adding nomodeset.
• Installer freezes at "Waiting for /dev to be fully populated" — often a bad or slow USB port; try a rear USB 2.0 port directly on the motherboard rather than a front-panel USB 3.0 hub.
• Empty disk list during "Target Harddisk" selection — your storage controller is in RAID mode; switch it to AHCI or plain NVMe mode.
• Installer boots into a text-only rescue prompt — usually means the ISO itself is corrupted; re-verify the checksum and re-download if needed.

Troubleshooting

Work through these in order rather than jumping around — most of the time the fix is earlier on this list than you'd expect.

1. Re-verify the ISO checksum. A bad download causes more of these symptoms than people assume.
2. Re-write the USB drive using the exact method above, on the raw device, not a partition. If you used a random third-party tool the first time, switch to Etcher, Rufus in DD mode, or dd.
3. Try a different USB port — preferably USB 2.0, plugged directly into the motherboard rather than through a hub or front panel header.
4. Try a different USB drive entirely. Cheap or aging flash drives fail in ways that are hard to diagnose from the symptoms alone.
5. Toggle Secure Boot off, then back on later once Proxmox is installed and running.
6. Switch your storage controller between AHCI and RAID mode if disks aren't showing up.
7. Check TTY2 (Ctrl+Alt+F2) for the actual error text instead of guessing from a frozen progress bar.
8. As a last resort, update your motherboard's firmware/BIOS to the latest version — some early UEFI implementations have real bugs with USB boot that later updates fix.

Best Practices

Always verify the checksum before writing the ISO — it takes thirty seconds and rules out an entire category of problems up front. Stick to the writing method Proxmox documents for your OS rather than whatever tool you already have installed; UNetbootin in particular is worth avoiding specifically because people keep reaching for it out of habit.

If you're installing on a server you don't have physical access to (a rented dedicated box, for example), check with your provider about their remote KVM or virtual media options before you start — the USB troubleshooting in this article assumes physical access to swap drives and change firmware settings.

Keep the USB drive around after a successful install. It's small, and being able to grab it later for a reinstall or to boot into rescue mode saves you from redoing this whole process under time pressure.

Frequently Asked Questions

Why does the installer work on one USB port but not another?

Some firmware implementations, especially on older boards, only fully initialize USB 2.0 ports early in the boot process. USB 3.0 ports, especially on hubs or front panels, sometimes aren't ready in time for the installer to see them.

Do I need to disable Secure Boot permanently?

No. Disable it only if it's blocking the installer from loading. Once Proxmox VE 8.1 or newer is installed, you can turn Secure Boot back on and confirm the system still boots normally.

Can I use a DVD instead of a USB drive?

Yes, if your server still has an optical drive. Burn the ISO as an image (not as a data file) using any standard disc-burning tool, and the same boot-mode and firmware considerations from this article still apply.

The installer boots but I can't move my mouse or use the keyboard. What's wrong?

This is almost always a USB controller mode issue in firmware, separate from boot mode. Look for a setting called "Legacy USB Support" or "USB Configuration" and make sure keyboard/mouse emulation is enabled.

Is it safe to switch my SATA controller from RAID to AHCI?

It's safe for a fresh install where you're not trying to preserve an existing RAID array on that same controller. If you have data on a RAID array you need to keep, don't make this change without backing it up first — switching modes can make the array unreadable to other operating systems.

Conclusion

None of these fixes are Proxmox-specific, really — they're the same handful of things that trip up any Linux installer: a bad USB write, a firmware setting fighting the boot process, or a storage controller in the wrong mode. Once you've been through it once, you'll recognize the symptoms immediately next time. Work through the checklist in order, check TTY2 when something looks stuck, and you'll almost always be looking at a working Proxmox VE install within a few minutes rather than a few hours.