Windows installs almost like a normal PC on Proxmox - except for two screens that stop every beginner. This guide walks the full install and fixes both, the right way.
You have a Proxmox server and you want a proper Windows machine running on it - for remote work, testing, or a small office service. The install itself is easy, but it has two famous traps: Windows Setup finds no disk, and later it finds no network. Both traps have the same cause - the missing VirtIO drivers - and this guide handles both at the exact moment they appear.
Every Windows install on Proxmox needs two ISO files on the server, not one. Upload both to your ISO storage first: in the Proxmox web panel, select the storage, open ISO Images and use Upload.
Honest note: the virtio-win disc is not optional decoration. It carries the storage driver, the network driver and the QEMU guest agent that this whole guide depends on.
Click Create VM in the top right of the Proxmox panel and walk through the wizard:
Win11. Note the VM ID Proxmox assigns.vmbr0. Setup will not see this network card until its driver is installed - that is expected, and fixed below.Select the new VM, click Start, then open the Console. When the screen asks, press any key to boot from the CD. Windows Setup starts exactly like a normal PC install: pick your language, click Install now, choose the edition your licence covers, and accept the licence terms.
Then comes the screen in the picture above: Where do you want to install Windows? - with an empty list. Do not panic and do not rebuild the VM. Nothing is broken. Windows simply has no driver for the VirtIO storage controller yet, so the disk is invisible to it.
This is the one step that makes a Proxmox install different from a physical PC install:
vioscsi\w11\amd64 - use the folder matching your Windows version, for example w10 for Windows 10 or 2k22 for Server 2022. (If you had chosen a VirtIO Block disk instead, the folder is viostor.)The disk appears in the list within seconds. Select it, click New if you want Setup to partition it, then Next - from here the installation is a completely normal Windows install.
Because the network card is also VirtIO, Windows Setup cannot see it either, so Windows 11 may stop at the Let us connect you to a network screen. This is the second expected hurdle, not a failure. You have two clean ways through:
virtio-win-guest-tools.exe - it installs every driver including the network driver, and the network screen clears.One honest warning: Microsoft keeps changing the offline-setup behaviour between builds, so do not treat any single bypass command as permanent. The driver install route always works, because it fixes the actual cause.
The moment you reach the Windows desktop, open the virtio-win CD in File Explorer and run virtio-win-guest-tools.exe. One installer gives the guest everything it was missing:
Restart once, then open Device Manager: no yellow warning marks should remain. In the Proxmox Summary page for the VM, the IP addresses should now be listed - that is your proof the guest agent is alive.
A short honest word before you build habits on this VM. Windows 11 or 10 is right for a personal desktop, testing and single-user remote work. Windows Server is right when the VM must serve others - file shares, Active Directory, or several people connecting at once, because desktop Windows allows only one interactive remote session and is not licensed or built as a multi-user server. Both install exactly the same way in this guide. Both also need their own proper Windows licence - a VM does not make Windows free, and this guide's licensing page explains what that means in practice.
vioscsi at the disk screen, install virtio-win-guest-tools.exe on the desktop, and both disappear for good.
Every screen of this install - the VM wizard, the Load driver moment and the guest tools setup - is shown live in the Technical Anshu video.
Watch Full VideoBecause the virtual disk sits on a VirtIO storage controller and Windows has no driver for it built in. Click Load driver on that screen, browse the virtio-win CD, open the vioscsi folder for your Windows version (for example vioscsi\w11\amd64), load the Red Hat VirtIO SCSI controller driver, and the disk appears immediately.
Only Windows 11 insists on them: it needs OVMF (UEFI), an EFI disk and a TPM 2.0 in the VM settings. Windows 10 and Windows Server install happily with the same settings too, so using OVMF and q35 for everything keeps all your VMs consistent.
The VirtIO network card also needs its driver. Run virtio-win-guest-tools.exe from the virtio-win CD on the Windows desktop - it installs the NetKVM network driver along with all the other drivers and the QEMU guest agent in one go.