This guide documents the complete process of creating a Windows Server 2022 virtual machine in Proxmox VE 9.1.6. It is based on actual lab setup experience and includes all corrections and lessons learned during the build of a home lab.

📄 Download the full guide with screenshots: WS2022-in-Proxmox-VM-Creation-Guide.docx

Environment

Note: The Proxmox WebUI shows an SSL certificate warning because Proxmox uses a self-signed certificate by default. This is the motivation for setting up an internal Certificate Authority (CA) later — once the CA is in place, a proper trusted certificate can be issued for Proxmox.

Safari shows an SSL warning for macpro2013.local. This disappears once your internal CA is in place and Proxmox uses a trusted certificate.

Prerequisites

Before creating a VM, ensure the following ISO images are uploaded to Proxmox local storage (Proxmox WebUI → local → ISO Images):

• Windows Server 2022 Evaluation: Windows_2022_SERVER_EVAL_x64FRE_en-us.iso
• VirtIO Drivers: virtio-win-0.1.285.iso (or newer)

Warning: Both ISOs are required. Without the VirtIO ISO, Windows Setup cannot detect the disk and network adapter.

Naming Convention

Use consistent naming for all lab VMs so you can see what each VM does at a glance in the Proxmox panel.

To rename a VM via the Proxmox host shell (the Proxmox GUI has no rename option):

ssh root@macpro2013.local
qm set <VMID> --name <NEW-NAME>
# Example — rename VM 100:
qm set 100 --name WS2022-LAB01-AD-DNS

The Proxmox side panel after both VMs were created and renamed: WS2022-LAB01-AD-DNS as VM 100 and WS2022-TEMPLATE-BASE as VM 900.

Step 1 — Create the VM via the Proxmox Wizard

In the Proxmox WebUI, click Create VM (blue button, top right). Work through each tab in order as described below.

1.1 General Tab

1.2 OS Tab

Warning: The OS Type and Version must both be set manually. The additional VirtIO ISO checkbox adds a second CD drive — this is essential for loading storage and network drivers during Windows Setup.

1.3 System Tab

Warning: EFI Storage and TPM Storage have no default — both must be explicitly selected. Without them the VM will not boot correctly.

1.4 Disks Tab

1.5 CPU Tab

Warning: CPU Type must be set to host. The default kvm64 limits available CPU instruction sets and reduces performance.

1.6 Memory Tab

Warning: Ballooning must be disabled for Windows VMs. Set Minimum Memory equal to Memory to enforce this.

1.7 Network Tab

Tip: Leave the Proxmox firewall enabled on the network adapter. Troubleshooting through the firewall builds valuable skills that mirror real production environments.

Step 2 — Verify Hardware Before Booting

After clicking Finish, do not start the VM immediately. First verify the hardware config by clicking the VM in the left panel and selecting Hardware. Confirm all of the following:

VM 900 shown in the Hardware tab with the intended template configuration, including balloon=0, host CPU type, EFI disk, TPM state, both ISOs, and the 60 GB VirtIO-backed disk.

• Memory: 4.00 GiB [balloon=0] — balloon=0 confirms ballooning is disabled
• Processors: 2 (1 socket, 2 cores) [host] — confirms host CPU type
• BIOS: OVMF (UEFI)
• Machine: pc-q35-10.1
• SCSI Controller: VirtIO SCSI single
• CD/DVD ide0: VirtIO ISO
• CD/DVD ide2: Windows 2022 ISO
• Hard Disk: 60 GB, cache=writeback, discard=on, iothread=1
• Network: vmbr0, firewall=1
• EFI Disk and TPM State present on local-lvm

If you already created your first lab VM as well, the hardware view should look similar there too:

VM 100 hardware overview after creation. The exact role name differs, but the main VM settings remain the same.

Step 3 — Start the VM and Install Windows

Click Start and immediately open the Console. When you see the following message, click inside the console window first (to capture keyboard focus) and press any key:

Press any key to boot from CD or DVD......

Warning: If you miss this prompt, the VM falls through to PXE boot. Simply reset the VM and try again — be ready at the console before clicking Start.

If you do not press a key in time, the VM falls through to PXE boot. Reset the VM and try again.

When you catch the prompt in time, the Windows Boot Manager appears. Select Windows Setup [EMS Enabled] and press Enter to continue.

Windows Boot Manager with Windows Setup selected.

Step 4 — Edition Selection

When prompted to select an edition, choose:

Windows Server 2022 Datacenter (Desktop Experience)

Warning: Make sure to select Datacenter — not Standard. And Desktop Experience — not Core. Core has no GUI which makes it unsuitable for this lab template.

Step 5 — Loading the VirtIO Storage Driver

On the Where do you want to install the operating system? screen, the disk list will be empty. This is expected — Windows cannot see the VirtIO SCSI disk without the driver.

This is the normal empty-disk screen before the VirtIO SCSI driver is loaded.

Follow these steps to load the driver:

1. Click Load driver
2. Click Browse
3. Navigate to the VirtIO CD drive (D: or E:)
4. Open the folder: vioscsi \ w2k22 \ amd64
5. Click OK
6. Select Red Hat VirtIO SCSI pass-through controller
7. Click Next

The 60 GB disk will now appear in the list. Select it and continue. Windows installation begins.

Windows Setup after the storage driver is loaded and installation has started.

Step 6 — After Installation

After Windows installs and reboots, you will land at the Server Manager Dashboard. Close the Windows Admin Center popup (tick Don’t show this message again).

Server Manager shown after the first successful boot of Windows Server 2022 Datacenter.

The VM is now ready for the next step: preparing it as a reusable Proxmox template. Refer to the companion guide:

📄 Proxmox Lab — Windows Server 2022 Template Preparation

Summary Checklist

📄 Download the full guide with screenshots: WS2022-in-Proxmox-VM-Creation-Guide.docx

Best regards,

Martijn