Windows Licensing Inside a Proxmox VM What You Actually Need

Proxmox VE is free and open source. Windows is neither, and installing Windows inside a virtual machine does not change its licensing in any way. A Windows VM is an installation of Windows, and Microsoft's terms treat it like one: it needs a genuine licence of its own, and it activates against Microsoft's servers the same way a physical PC does - which is why a properly licensed VM activates and updates normally, and why the install guide never has to touch activation tricks.

Treat any advice that starts with it is only a VM, so... as a warning sign about the adviser, not as information about licensing.

For Windows 10 and 11 guests, the licence type you own decides what is legal:

1. Retail (boxed or bought) licences can be transferred - including into a VM - as long as the licence is only running in one place at a time. Uninstall or retire the old installation; one licence, one live Windows.
2. OEM licences - the copy that came preinstalled on a laptop or PC - are tied to that original hardware for life. Moving one into a VM on your server is outside the licence terms, whatever the activation page happens to allow technically.
3. The same key on the host and in its VM is two installations, not one clever reuse.

For a testing lab, remember Windows also offers time-limited evaluation editions of Windows Server, and Windows desktop installs run unactivated with restrictions - legal ways to practise without buying anything.

Windows Server plays by a different and stricter rulebook, and this is where offices get surprised:

1. Server licensing counts the physical cores of the host server (with a minimum of 16 cores licensed per server), no matter which hypervisor runs on it - Proxmox included.
2. Standard edition then covers up to two Windows Server VMs on that fully licensed host; Datacenter covers unlimited VMs. Running a third Server VM on Standard means licensing the host's cores again.
3. People connecting to services like Remote Desktop Services need CALs on top - the server licence alone does not cover its users.

The honest consequence: before installing three Windows Server VMs on a big Proxmox host because the hardware can take it, price the licences - on a many-core server they, not the hardware, may be the real cost of the design.

Expect activation to notice big virtual hardware changes. Moving a VM to a very different host, or changing several core settings at once, can make Windows ask to reactivate - the same reaction a motherboard swap causes on a physical PC. Keeping the VM's settings stable (another reason not to fiddle with machine type casually) and keeping your licence documentation with the VM's notes turns a reactivation from a crisis into a five-minute formality. Version-specific terms do change over time, so for anything beyond a home lab, confirm your exact scenario against Microsoft's current licensing documents.