Windows 11 on a VPS: vTPM Requirements, Licensing Limits, and Server 2025 Comparison

Running Windows 11 on a VPS is technically possible, but it is rarely the right choice for a server, and the reasons are licensing, activation, and hypervisor support rather than raw performance. This guide covers the real hardware requirements for a virtual Windows 11 guest, how vTPM and Secure Boot must be exposed by your provider, activation rules under Microsoft’s licensing, and how Windows 11 compares to Windows Server 2025 for RDP and .NET workloads.

Windows 11 Requirements in a Virtual Machine

Windows 11 enforces a stricter baseline than any previous client release. Inside a hypervisor, each requirement maps to a host capability that must be enabled:

Requirement	Physical PC	VPS / hypervisor mapping
CPU	1 GHz, 2+ cores, 64-bit	2 vCPU minimum; KVM/Hyper-V must expose a supported CPU model
RAM	4 GB	4 GB bare minimum, 8 GB usable with RDP sessions
Storage	64 GB	80–100 GB recommended; SSD-backed storage only
Firmware	UEFI + Secure Boot	Guest must be Gen 2 (Hyper-V) or UEFI+OVMF (KVM)
TPM	TPM 2.0	Provider must expose a virtual TPM (vTPM)
Graphics	DirectX 12 / WDDM 2.0	Not enforced in VM; RDP uses its own display driver

The blocker is almost always vTPM. Many budget providers present a BIOS/Legacy guest with no virtual TPM, and the Windows 11 installer stops at “This PC can’t run Windows 11”.

Handling a Missing vTPM

If the provider supports Gen 2/UEFI but not vTPM, you have three workarounds, in order of preference:

Enable vTPM on the host. In Hyper-V, Set-VMKeyProtector plus Enable-VMTPM -VMName Win11 provisions a virtual TPM. In KVM, add a tpm-tis device with swtpm. Ask the provider — it is a host-side change they can often make.
Registry bypass during setup. At the compatibility error screen press Shift+F10, run regedit, create HKLM\SYSTEM\Setup\LabConfig, and add DWORDs BypassTPMCheck=1, BypassSecureBootCheck=1, BypassRAMCheck=1.
Unattended answer file. Add <BypassTPMCheck>true</BypassTPMCheck> inside windowsPE in autounattend.xml for scripted deploys.

Bypassing TPM forfeits VBS/HVCI and can block quality updates that require the platform security baseline. Treat it as a lab-only measure, never a production pattern.

Licensing: The Real Blocker

Windows 11 is a client OS and is not licensed for multi-user remote access. Microsoft’s licensing terms do not permit Windows 11 to be used as a hosted desktop for unrelated users; that is what RDS Client Access Licenses on Windows Server are for. Most providers sidestep this by selling Windows Server images, where per-core licensing is included in the plan. See how that pricing works in the Windows VPS licensing guide on windows-vps.org.

Activation inside a VM also behaves differently. Retail and OEM keys usually activate against the virtual hardware fingerprint, but changing vCPU count or adding a virtual TPM after activation frequently triggers re-activation. Volume licensing via KMS is the standard approach providers use for their Windows Server images.

Performance: Expected Numbers on a VPS

On a 2 vCPU / 8 GB SSD VPS with idle load, Windows 11 uses noticeably more memory than Windows Server 2025 because of the consumer shell, Widgets, Recall indexing, and telemetry services:

Metric	Windows 11 Pro	Windows Server 2025
Idle RAM usage	~3.2–4.0 GB	~1.3–1.9 GB (Server Core lower)
Idle CPU	2–5%	1–2%
Boot to desktop	35–60 s	20–35 s
Concurrent RDP sessions	1 (officially)	2 admin + RDS CALs for more
IIS/.NET support	Works, unsupported for servers	Fully supported, tuned

Remote Desktop User Experience on Windows 11 vs Server

The RDP experience itself differs between the two families in ways that matter for remote work. Windows 11 supports Remote Desktop with a single interactive session under the Pro/Enterprise EULA, offers a modern client with multi-monitor and RemoteApp-free full-desktop access, and includes client-side features like automatic DPI scaling. Windows Server 2025 with the RDS role supports multiple simultaneous users, but only with RDS CALs and a licensing server; without them, two administrators can log in for management and nothing more.

For a single user who wants a personal Windows desktop in the cloud, Windows 11 on a VPS can be a workable, if licensing-sensitive, arrangement. For a team sharing one server, Windows Server plus RDS is the only compliant path, and on a small instance you should also plan for the memory each session consumes. Session memory is typically 150–400 MB per idle user on Windows 11 versus 80–200 MB per session on Server with Desktop Experience.

Finally, note that Windows 11 on a VPS will not receive the server-side tuning Windows Server gets for background I/O, and its telemetry and consumer services can wake the CPU during idle periods. On a metered plan, that idle churn is a measurable cost.

When Windows 11 on a VPS Actually Makes Sense

QA and compatibility testing of client software from a remote location.
A single-user remote workstation with a full desktop experience.
VBScript/PowerShell desktop-script testing that needs a client shell.

For anything server-side — IIS hosting, .NET deployment, SQL Server, RDS — Windows Server 2025 or 2022 is the correct and cheaper-in-practice choice, with proper CAL licensing and lower baseline overhead.

Bottom Line

Windows 11 runs on a VPS if the hypervisor exposes UEFI and a vTPM, or if you apply a supported bypass, but the licensing terms restrict it to single-user desktop scenarios. For production remote access, choose a Windows Server based VPS from windows-vps.org and license it correctly from the start.