EN

Applications

Create a Windows VM with VirtIO Drivers on Proxmox VE

Install Windows 11 or Windows Server 2022/2025 in a Proxmox VE VM with UEFI, TPM 2.0 and VirtIO drivers, then configure the guest agent, the network and protected RDP access.

9 min read, updated on 18 November 2026

On this page

Your values

Enter them once and the commands in this guide update.

This guide creates a Windows 11 or Windows Server 2022/2025 virtual machine on Proxmox VE, with the VirtIO drivers that deliver the best disk and network performance.

Windows does not include these drivers: without them, the installer cannot see the virtual disk. You will therefore mount two ISOs in the VM, the Windows one and the drivers one.

Prerequisites

System Processor Memory Disk Notes
Windows 11 2 cores minimum 4 GB minimum 64 GB minimum UEFI, Secure Boot and TPM 2.0 required
Windows Server 2025 1.4 GHz, 64-bit, SSE4.2 and POPCNT compatible 2 GB minimum, 4 GB recommended with a graphical interface 32 GB absolute minimum UEFI and TPM required only for certain features
Windows Server 2022 1.4 GHz, 64-bit 2 GB minimum with a graphical interface 32 GB absolute minimum UEFI and TPM required only for certain features

These values are the minimums stated by Microsoft: plan for more in real-world use.

Step 1: Get the ISOs

Windows

Download the image from Microsoft: Windows 11 or Windows Server 2025 evaluation. Then upload it through local → ISO Images → Upload.

VirtIO Drivers

The virtio-win project publishes the signed drivers. At the time of writing, Proxmox states that it is aware of no issues with version 0.1.271. Version 0.1.302 is still being evaluated on its side. See the Proxmox page on the drivers for the current recommendation.

On the Proxmox host:

Terminal
cd /var/lib/vz/template/iso
wget https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.271-1/virtio-win-0.1.271.iso
ls -lh

You can also use local → ISO Images → Download from URL.

Step 2: Create the VM

Click Create VM and fill in the wizard.

Tab Field Value
General VM ID / Name 200 / windows
OS ISO image Your Windows ISO
Guest OS Type Microsoft Windows, version 11/2022/2025
Add additional drive for VirtIO drivers Checked, with the virtio-win ISO
System Machine q35
BIOS OVMF (UEFI)
Add EFI Disk Checked, EFI Storage: local-lvm
Pre-Enroll keys Checked
SCSI Controller VirtIO SCSI single
Qemu Agent Checked
Add TPM Checked, TPM Storage: local-lvm, Version: v2.0
Disks Bus/Device SCSI
Storage / Disk size local-lvm / 80 GB
Discard and IO thread Checked
CPU Sockets / Cores 1 / 4
Type x86-64-v2-AES
Memory Memory 8192 MB
Network Bridge vmbr1
Model VirtIO (paravirtualized)

Do not start the VM yet at the end of the wizard if you want to review its configuration in Hardware.

The same VM can be created from the command line. Adjust the name of the Windows ISO:

Terminal
qm create 200 --name windows --ostype win11 --machine q35 --bios ovmf \
  --efidisk0 local-lvm:1,efitype=4m,pre-enrolled-keys=1 \
  --tpmstate0 local-lvm:1,version=v2.0 \
  --cpu x86-64-v2-AES --sockets 1 --cores 4 --memory 8192 \
  --scsihw virtio-scsi-single \
  --scsi0 local-lvm:80,iothread=1,discard=on \
  --ide2 local:iso/windows.iso,media=cdrom \
  --ide0 local:iso/virtio-win-0.1.271.iso,media=cdrom \
  --net0 virtio,bridge=vmbr1 \
  --agent enabled=1 \
  --boot 'order=ide2;scsi0'

Check the result:

Terminal
qm config 200

Step 3: Install Windows

  1. Start the VM and open its Console.
  2. As soon as Press any key to boot from CD or DVD appears, press a key. This message is displayed for only a few seconds.
  3. Follow the installer until you reach the disk selection. On versions that ask for it, select the Custom installation. The disk list is empty: this is normal.
  4. Click Load driver, then Browse, and open the virtio-win drive.
  5. Load the drivers below one at a time, returning to Load driver each time.
Driver Folder on Windows 11 Windows Server 2025 Windows Server 2022 Displayed name
Disk vioscsi\w11\amd64 vioscsi\2k25\amd64 vioscsi\2k22\amd64 Red Hat VirtIO SCSI pass-through controller
Network NetKVM\w11\amd64 NetKVM\2k25\amd64 NetKVM\2k22\amd64 Redhat VirtIO Ethernet Adapter
Memory Balloon\w11\amd64 Balloon\2k25\amd64 Balloon\2k22\amd64 VirtIO Balloon Driver

The disk appears once the first driver is loaded. Select it and continue the installation.

Step 4: Install the Guest Tools

Once on the Windows desktop, open the virtio-win drive in File Explorer:

  1. Run virtio-win-gt-x64.msi. If you do not use SPICE, you can uncheck Qxl and Spice.
  2. Run guest-agent\qemu-ga-x86_64.msi to install the QEMU guest agent.
  3. Restart the VM.

In Device Manager, no unknown device should remain. If one does, right-click it → Update driver → Browse my computer, select the virtio-win drive and check Include subfolders.

On the host, check the agent:

Terminal
qm guest cmd 200 ping
qm guest cmd 200 network-get-interfaces

Step 5: Configure the Network

The vmbr1 bridge does not provide DHCP. Open PowerShell as administrator in the VM. Find the adapter name, then assign the address:

PowerShell
Get-NetAdapter
New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress 10.10.10.20 -PrefixLength 24 -DefaultGateway 10.10.10.1
Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses 1.1.1.1,9.9.9.9

Replace Ethernet with the name shown by Get-NetAdapter. Then test:

PowerShell
Test-NetConnection 10.10.10.1
Test-NetConnection deb.debian.org -Port 443

Step 6: Access the VM with Remote Desktop

Enable Remote Desktop in Settings → System → Remote Desktop. Windows 11 Home does not offer this feature.

The simplest approach is an SSH tunnel to the host. On your computer:

Terminal
ssh -N -L 13389:10.10.10.20:3389 root@SERVER_IP

Leave this command running and connect your Remote Desktop client to localhost:13389. The traffic goes through the encrypted tunnel, and only the host's SSH port is used.

Step 7: Finalize the VM

Remove the ISOs, boot from the disk and enable automatic startup:

Terminal
qm set 200 --ide0 none,media=cdrom --ide2 none,media=cdrom
qm set 200 --boot order=scsi0
qm set 200 --onboot 1

Finish with Windows Update and by activating your license.

Verify the Result

Check Expected result
qm status 200 status: running
qm guest cmd 200 ping No error
VM → Summary The IP address is displayed
Device Manager No unknown devices
Test-NetConnection deb.debian.org -Port 443 TcpTestSucceeded : True
Connection to localhost:13389 through the tunnel Windows sign-in screen

Updates

  • Windows: apply updates from Windows Update.
  • VirtIO drivers: mount the new ISO, then run virtio-win-gt-x64.msi and the agent installer again. Make a backup first and check the known issues listed by Proxmox.
  • Host: follow the updates section of the installation guide. The machine type of Windows VMs stays pinned at creation, because Windows is sensitive to changes in virtual hardware.

Backup

snapshot mode backs up the VM without stopping it. With the guest agent, Proxmox asks Windows to cleanly freeze the file systems through VSS. The EFI disk and the TPM state are included in the backup.

Terminal
vzdump 200 --storage local --mode snapshot --compress zstd

For real protection, send backups off the server, for example to Proxmox Backup Server.

Troubleshooting

No Disk Appears in the Installer

The vioscsi driver is not loaded, or you chose the folder for another Windows version. Also check that the controller is VirtIO SCSI single and the disk is SCSI.

The VM Does Not Boot from the ISO and Shows a UEFI Shell

The Press any key message went by too quickly. Use Reset and press a key as soon as the VM starts. Also check the boot order in Options → Boot Order.

"This PC can't run Windows 11"

Check that the VM has the OVMF (UEFI) BIOS, an EFI disk with Pre-Enroll keys, a v2.0 TPM, and at least 2 cores and 4 GB of memory.

No Network in Windows

Install the NetKVM driver, then check in Device Manager. Next, check the address, the 10.10.10.1 gateway and the DNS. The network guide details the checks on the host side.

QEMU guest agent is not running

Install guest-agent\qemu-ga-x86_64.msi, check that the QEMU Guest Agent service is started and that the Qemu Agent option is enabled on the VM. If you have just enabled it, shut down the VM and start it again.

Reset to device Events or Disk Hangs

Proxmox reports this issue with virtio-win versions 0.1.215 to 0.1.262. Move to version 0.1.266 or later.

Read Errors or Slowness on Windows Server 2025

Proxmox reports issues with version 0.1.285 under heavy disk load, notably with SQL Server. Version 0.1.271 appears to be unaffected and can serve as a workaround.

INACCESSIBLE_BOOT_DEVICE After a Controller Change

Windows does not have the driver for the new controller. Restore the previous setting, install virtio-win-gt-x64.msi, then make the change again.

References