Back to Blog
System Administration

How to Install Windows Server 2022 on Proxmox

10 December 2020 5 min read System Administration
How to Install Windows Server 2022 on Proxmox
System Administration

Updated June 2026 — commands and versions refreshed for current releases. Windows Server 2016 reached end of mainstream support, so this guide now targets Windows Server 2022 (or 2025); the Proxmox workflow is identical.

Overview

This guide covers setting up a Windows Server virtual machine on Proxmox VE, part of a larger series that culminates in an SAP Business One 10 installation on SAP HANA 2.0. While the original article used Windows Server 2016, that release has reached the end of its support window, so we now provision Windows Server 2022 (Windows Server 2025 works the same way). The Proxmox steps are unchanged.

VM Requirements

How to Install Windows Server 2022 on Proxmox

Microsoft publishes a low floor for Windows Server, but a real-world SAP-bound host needs headroom. Use the recommended column.

  • RAM: minimum 512 MB, recommended 16 GB
  • HDD: minimum 32 GB, recommended 200 GB
  • CPU cores: minimum 1, recommended 4

Download the ISO

Download the latest Windows Server release (2022 or 2025) from the Microsoft Evaluation Center, then upload the ISO to your Proxmox node so it is available when creating the VM.

# From your workstation, push the ISO into Proxmox local storage
scp WindowsServer2022.iso root@your-proxmox-host:/var/lib/vz/template/iso/

You should also download the latest VirtIO drivers ISO (stable) from the Fedora project so Windows can see the paravirtualized disk and network devices during install.

Create the VM

In the Proxmox web UI, click Create VM and work through the wizard:

  • OS: Select your Windows Server ISO. Set Guest OS Type to "Microsoft Windows" and version to "11/2022/2025" (on older Proxmox builds choose "10/2016/2019").
  • System: Set the SCSI controller to VirtIO SCSI single. Enable the QEMU Agent. For Windows Server 2022/2025 enable a TPM (v2.0) and set the BIOS to OVMF (UEFI) with an EFI disk.
  • Disk: Use bus type VirtIO Block (or SCSI) sized per the table above.
  • CPU/Memory: 4 cores and 16 GB to match the recommended setup.
  • Network: Use the VirtIO (paravirtualized) model on your chosen bridge.

Before first boot, add the VirtIO drivers ISO as a second CD/DVD drive so the installer can load the storage and network drivers.

Install Windows Server

  • Start the VM and open the console. Boot from the Windows ISO.
  • Choose "Windows Server 2022 Standard (Desktop Experience)" (or your edition of choice).
  • Select the Custom install option.
  • When no disk appears, click "Load driver" and point the installer at the VirtIO drivers ISO (the vioscsi or viostor folder for your OS version). The virtual disk now appears; continue the install.

After Windows boots, install the remaining VirtIO drivers and the QEMU guest agent from the drivers ISO so networking, ballooning, and clean shutdowns work.

Network Configuration

Open the network adapter settings and configure the IPv4 properties for your environment. A typical static setup using an additional subnet looks like this:

  • IP Address: from your additional subnet
  • Netmask: 255.255.255.255 (point-to-point, as provided by many hosting providers) or the netmask for your LAN
  • Gateway: your main IP address
  • DNS servers: e.g. 8.8.8.8 and 8.8.4.4, or your internal resolvers

Post-Installation Tasks

  • Run Windows Update until the server is fully patched.
  • Install a browser such as Chrome or Edge.
  • Install WinSCP for file transfer.
  • Install firewall/antivirus software. Microsoft Defender ships with Windows Server, but confirm it is active and consider an endpoint protection product.

Enabling Remote Desktop

Open Server Manager, select Local Server, then enable "Allow remote connections to this computer" in the Remote Desktop settings dialog. Restrict RDP to known IPs at the firewall and never expose 3389 directly to the internet without a VPN or jump host.

Security Note

Always keep antivirus protection installed and current on the server, apply updates promptly, and limit administrative access. With the VM in place you are ready for the next article in the series: installing SAP HANA 2.0 ahead of SAP Business One 10.

Indivar Software Solutions

SAP Business One consulting and custom software development since 2009. Offices in India, New Zealand, and the USA.

Related Articles

More on System Administration

Need Help with SAP Business One?

Whether you need implementation support, custom add-ons, or strategic ERP advice, our team is ready to help. over 17 years of SAP B1 experience across India, New Zealand, and the USA.