Installing Windows 11 on Proxmox Virtual Environment is far from a simple ISO boot. Unlike many Linux guests that work out of the box, Microsoft's latest OS demands careful preparation. If you try to power through the standard VM creation wizard, you’ll hit a brick wall—the Windows installer won’t see your virtual disk, and networking will be absent. Both a detailed community walkthrough and a recent hands-on test confirm that the path to a fully functional Windows 11 VM requires three often-missed ingredients: VirtIO drivers, UEFI firmware with an EFI disk, and a virtual TPM 2.0.

Proxmox’s KVM-based architecture gives you immense flexibility, but it also means guests need paravirtualized drivers for optimal performance. Windows 11 raises the bar by mandating Secure Boot and TPM support, things desktop hypervisors often hide. This guide distills the essential steps, common pitfalls, and performance tricks—including GPU passthrough—so you can get a clean, daily-driver-ready VM without hours of trial and error.

The Hidden Complexity of Virtualizing Windows 11 on Proxmox

At first glance, Proxmox’s “Create VM” button seems tempting. But Windows 11 requires a perfect storm of firmware, driver, and security module choices that differ sharply from older Windows versions or typical Linux guests. Microsoft enforces UEFI boot (no legacy BIOS), Secure Boot readiness, and TPM 2.0 presence as baseline requirements. Proxmox provides all the building blocks, but they aren’t enabled by default.

The biggest hurdle, however, isn’t just the OS requirements. It’s the storage and network drivers. Windows installation media lack the VirtIO drivers that KVM needs for paravirtualized SCSI disks and network adapters. Skip this step, and the installer will report “We couldn’t find any drives” even though you’ve allocated storage. Networking vanishes too, leaving your VM isolated until you manually inject the correct drivers.

As one community member puts it, the process is “eminently doable” but not the “select ISO and click next” experience many expect. The reward is a VM that, with proper tuning, can rival bare-metal performance—especially if you later add GPU passthrough.

Prerequisites: What You’ll Need Before Starting

Preparation is nine-tenths of the battle. Gather these items before you launch the Proxmox web interface:

  • Windows 11 ISO: Any official release. Version-specific build numbers don’t change the core procedure, but always use the latest stable image to reduce driver compatibility surprises.
  • Latest virtio-win ISO: You can obtain it from Fedora’s repository or the Red Hat build. This ISO contains the vioscsi (SCSI), NetKVM (network), balloon, guest agent, and QXL/Spice display drivers. Driver versions evolve, and newer releases often fix installation or compatibility bugs.
  • Host readiness checks: Confirm your CPU supports hardware virtualization—look for vmx (Intel) or svm (AMD) in /proc/cpuinfo. Enable Intel VT-d or AMD IOMMU in the motherboard firmware if you plan PCIe passthrough later; also enable “Above 4G decoding” for many modern GPUs.
  • Storage space for the VM disk and the TPM state file (Proxmox stores the vTPM data persistently).

Crafting the VM: UEFI, TPM, and VirtIO SCSI

When you click “Create VM,” you must diverge from defaults immediately:

  1. General: Set “ostype” to “Microsoft Windows 11/2022” to get sensible defaults.
  2. System tab:
    - BIOS: Choose OVMF (UEFI). Legacy SeaBIOS won’t work with Windows 11.
    - Add EFI Disk: Check this box and select a storage pool. The EFI disk holds firmware boot data; without it, the VM may fail to boot.
    - TPM: Enable TPM 2.0 and pick a storage pool (commonly local-lvm). The vTPM state file is small but critical for Windows to recognize the trusted platform module. Some users report needing a subsequent UEFI reset (clear TPM keys from within the guest firmware) before Windows detects the TPM—plan for that.
  3. SCSI Controller: Select VirtIO SCSI for peak performance. You can fall back to IDE to avoid driver injection during install, but you’ll sacrifice speed. The recommended path is VirtIO SCSI plus the driver disk.
  4. Disks: Add your main virtual disk (qcow2 or raw). Then, attach two CD/DVD drives:
    - Drive 1: Windows 11 ISO.
    - Drive 2: virtio-win ISO. Check “Add additional drive for VirtIO drivers” if the wizard offers it.

After finishing the wizard, double-check the hardware overview: you should see OVMF BIOS, an EFI disk, a vTPM device, a VirtIO SCSI controller, a main disk, and two CD drives. Start the VM and open the console.

The Critical Driver Injection Moment

The Windows installer will proceed normally until the “Where do you want to install Windows?” screen. By default, no disks appear. This is expected because Windows can’t natively see the VirtIO SCSI controller.

At this point:
- Click Load driver.
- Browse to the second CD drive (often D:).
- Navigate to vioscsi/w11/amd64.
- Select the Red Hat SCSI passthrough driver and install it.

Within seconds, your virtual disk will appear. You can now partition and format it as usual.

Networking drivers can be added later, but it’s wise to install them early to avoid being stuck without internet during Out-of-Box Experience (OOBE). If you get to the network selection page and see no adapters, load the NetKVM driver by selecting “Have disk” and pointing to NetKVM/w11/amd64 on the virtio CD. With networking up, you can download updates or sign in with a Microsoft account.

Important note: If Secure Boot is enabled, driver signing issues may appear. If you encounter “no signed device drivers were found,” temporarily disable Secure Boot in the VM’s UEFI menu or re‑download a newer virtio ISO that includes updated signed drivers.

Post-Installation Tuning and Tools

Once Windows 11 boots to the desktop, the VM is still gimped. The console experience may feel sluggish, display resolution might be stuck, and advanced features like dynamic memory and clean shutdown won’t work. The fix is a single installer:

  • Open the virtio CD and run virtio-win-guest-tools (or virtio-win-guest-tools.exe). This package includes:
  • Balloon driver: Enables dynamic memory resizing.
  • QEMU Guest Agent: Allows the host to query IP addresses, initiate clean shutdowns, and improve migration behavior.
  • QXL/Spice display drivers: Boosts noVNC console responsiveness and unlocks higher resolutions.
  • Additional VirtIO drivers for any leftover hardware.

After installing the guest tools, reboot the VM. The noVNC console should feel noticeably smoother. Some users report conflicts between guest tools and certain GPU passthrough setups; if you experience freezes or black screens later, test a different virtio ISO version or install only the guest agent and balloon driver initially.

Performance Considerations and GPU Passthrough

A well‑configured Windows 11 VM with VirtIO drivers approaches bare‑metal performance for many workloads. For CPU‑demanding tasks, allocate at least 4 vCPUs and 8–16 GiB RAM. Advanced users can pin vCPUs to physical cores and isolate CPU cores from the host scheduler to reduce contention.

PCIe (GPU) Passthrough: The Ultimate Upgrade

If you need native graphics for gaming, rendering, or compute, passing a physical GPU to the VM is the gold standard. This turns the VM into a near‑native workstation. The setup is non‑trivial and requires host‑level changes:

  1. Enable IOMMU in the motherboard firmware (VT‑d or AMD IOMMU) and add the appropriate kernel parameter to /etc/default/grub:
    - Intel: GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt"
    - AMD: GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on iommu=pt"
    Then run update-grub or proxmox-boot-tool refresh.
  2. Load VFIO kernel modules by adding vfio, vfio_pci, vfio_iommu_type1, and vfio_virqfd to /etc/modules. Reboot.
  3. Identify GPU IDs with lspci -nn and bind them to the vfio-pci driver (often via a kernel parameter like vfio-pci.ids=10de:1b80,…). Rebuild initramfs and reboot again.
  4. Attach the GPU to the VM as a PCI device in Proxmox’s hardware tab.

Beware: IOMMU grouping can complicate things. If the GPU shares a group with another device (e.g., audio controller or USB hub), you may need to pass all group members. Workarounds like pcie_acs_override exist but carry stability risks. Planning for a secondary GPU (or using the host’s iGPU for console) is recommended.

Several community guides note that older AMD GPUs sometimes suffer from the “vendor reset” bug, causing black screens after a VM reboot. NVIDIA GPUs generally fare better but may require hiding the hypervisor flag to avoid driver restrictions. Both issues are deeply hardware‑dependent; test thoroughly and rely on recent QEMU/Proxmox versions.

Troubleshooting Common Tripwires

Even careful setups can go sideways. These fixes address the most frequent headaches:

  • “No drives found” during install: You forgot the vioscsi driver load step. Attach the virtio ISO and browse to vioscsi/w11/amd64.
  • No network after install: Run the NetKVM driver from NetKVM/w11/amd64 on the virtio CD.
  • TPM not detected: Reboot the VM, enter UEFI setup (press ESC during early boot), navigate to the TPM menu, and clear or reset TPM keys. Then boot Windows again. If that fails, verify the VM was created with TPM 2.0 and the storage pool is reachable.
  • Black screen after GPU passthrough: Check host logs (dmesg | grep -i vfio) for binding errors. Ensure the GPU is not in use by the host (verify with lspci -k that the driver is vfio-pci). Disable any framebuffer drivers (like efifb) at boot via kernel parameter video=efifb:off. If using an NVIDIA card, a vBIOS dump may be needed.
  • Guest tools cause instability: Try an older virtio ISO or install only the guest agent. Uninstall balloon or QXL drivers if they conflict with GPU passthrough.

Security and Licensing Notes

  • Licensing: A Windows 11 VM requires a valid license. Retail licenses typically allow transfer to VMs; OEM licenses may not. For production environments, consult Microsoft’s volume licensing.
  • TPM state: The vTPM stores cryptographic keys, including BitLocker encryption keys if you enable disk encryption. Always include the TPM state file in backups. Losing it can render encrypted drives unrecoverable.
  • Snapshots vs. backups: Proxmox snapshots are excellent for rollback but are not backups. For any important VM, maintain off‑node backups and test restoration.

Final Verdict

Windows 11 on Proxmox is a test of patience and attention to detail. The payoff, however, is immense. You get a server‑grade hypervisor with ZFS, clustering, and snapshot capabilities, hosting a fully‑featured Windows desktop that can even run AAA games via GPU passthrough.

The single most critical takeaway from both the community and external reviews is the VirtIO ISO. It’s the key that unlocks disk and network visibility. Once you master the driver injection step, the rest is systematic: OVMF, TPM, EFI disk, guest tools, and, if you’re adventurous, VFIO passthrough.

Keep your virtio ISO and Proxmox versions current. Driver improvements arrive frequently, and what fails today may work tomorrow. After your first successful boot, take a VM snapshot. It will save hours when you later experiment with advanced features or bork a driver update.

With the right preparation, your Proxmox Windows 11 VM can serve as a powerful daily driver, a sandbox, or a GPU‑accelerated compute node. The learning curve is steep, but the result is a flexible, high‑performance virtualization setup that few other platforms can match.