Bootloader setup errors: unable to install initramfs means the Proxmox installer can’t build the initramfs for the target disk. It’s almost always disk layout, encryption, or missing initramfs-tools. Here’s the checklist.

Check the disk layout first
If you’re installing to a disk that already has partitions, especially with leftover LVM or ZFS signatures, the installer can get confused. It may try to install to a partition that’s too small or has a weird filesystem. Boot the installer, switch to another console (Ctrl+Alt+F2), and check what’s on the disk:
lsblk -f
blkid
If you see old LVM or ZFS labels, wipe them. For LVM:
vgremove -f vgname
pvremove /dev/sdX
For ZFS, use wipefs -a /dev/sdX or zpool labelclear -f /dev/sdX. Then rerun the installer.
Encryption is a common culprit
If you enabled encryption during install, the initramfs needs cryptsetup and the right hooks. Sometimes the installer misses them. If you’re doing a custom encrypted setup, make sure cryptsetup-initramfs is installed and the cryptroot hook is enabled in /etc/initramfs-tools/hooks/. You can also try installing without encryption first to see if that’s the issue.

Missing initramfs-tools on the installer
The installer environment should have initramfs-tools, but sometimes it’s broken. From the installer console, check:
dpkg -l initramfs-tools
If it’s not there, install it:
apt update && apt install initramfs-tools
Then run update-initramfs -u to test if it works. If that fails, you’ll see the actual error.
My take
Most of the time it’s leftover disk signatures. The installer isn’t great at telling you that. Wipe the disk and try again. If you’re still stuck, check the installer log at /var/log/installer/ for the real error. And if you’re doing something exotic like ZFS on root with encryption, keep it simple for the first install—you can always redo it later.
Related: Should I Install Proxmox on My 4TB SSD RAID 5 Setup? No, Use a Separate Boot Disk