Searching for a VPS tells you almost nothing about whether that VPS can run Windows. “VPS” describes a resource container, not an operating system, and the same word covers a KVM virtual machine that will happily host Windows Server and an OpenVZ container that physically cannot. This article is the set of questions to ask — and the tests to run — before you pay, so you find out on the sales page rather than after the invoice.
Question 1 — What Virtualization Technology Does the Host Use?
Ask directly: KVM, VMware, Hyper-V, Xen, or OpenVZ/LXC? The answer is binary in its consequences.
| Technology | Can host Windows? | Why |
|---|---|---|
| KVM / QEMU | Yes | Full hardware virtualization; VirtIO drivers available |
| VMware ESXi | Yes | Native guest tools, best driver story |
| Hyper-V | Yes | Native; guest licence required |
| Xen (HVM) | Yes | PV drivers recommended for performance |
| OpenVZ / LXC / Virtuozzo | No | Shared Linux kernel — no Windows guests possible |
If a provider will not state the technology, that is itself the answer.
Question 2 — Is the Windows Licence Included, and Which Edition?
| Answer you get | What it means | Watch out for |
|---|---|---|
| “Windows is included” | Host rents the licence under SPLA and charges you monthly | Confirm the edition (Standard vs Datacenter) and version (2019/2022/2025) |
| “Bring your own licence” | You must supply a key that legally permits VM use | Retail OEM keys are device-bound — not valid here |
| “Licensing not included” | You will see activation nagging and hourly shutdowns after 180 days | Cost of the OS is added later; budget for it up front |
| “Windows 10/11 desktop” | Desktop SKU in a VM | Usually a licence violation for hosted multi-tenant use; session limits apply |
Also confirm the number of licensed cores. Windows Server Standard is licensed per physical core with a 16-core minimum per host, and 8 cores per VM. A provider selling “4 vCPU Windows” is relying on their own host-level licensing — get that in writing.
Question 3 — How Is Remote Access Delivered?
Windows administration happens over RDP. Confirm three things: the port, whether you get a full administrator account, and whether you can change RDP settings yourself.
:: Connect with an explicit port when the provider remaps RDP
mstsc /v:203.0.113.10:49222
:: Once in, verify RDP is actually enabled and NLA is on
Get-ItemProperty 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections
Get-ItemProperty 'HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name UserAuthentication| Access model | What you can do | Verdict |
|---|---|---|
| Full RDP as Administrator | Everything — IIS, SQL, firewall, registry | What you want |
| RDP as limited user | Only what an admin pre-approved | Avoid unless managed is the goal |
| Panel-only (VNC console) | Recovery console, no persistent session | Not an administration path |
| RDP + Gateway | Full access through a secured broker | Best for teams |
Question 4 — What Are the Real Resource Floors?
- RAM: 1 GB plans exist “for Windows” but Windows Server alone idles near 800 MB–1.2 GB. 4 GB is the practical floor for anything with IIS or SQL.
- Disk: Windows Server needs 32 GB before your data; WinSxS and the update cache routinely push 40 GB. Choose 60 GB+ and check it is SSD/NVMe.
- CPU: Windows Update and Defender scans are single-thread heavy. Two vCPU makes the first day four times less painful than one.
- Bandwidth: RDP sessions cost 50–200 kbps each when tuned; a full-screen 1080p desktop with animations can hit 2–5 Mbps.
Question 5 — What Control Do You Actually Get?
| Feature | Why it matters for Windows |
|---|---|
| ISO mounting | Needed for repair installs and offline driver injection |
| Snapshot / rollback | Your undo button before a risky update or role install |
| Power control (start/stop/reset) | Recovery from a bad boot without opening a ticket |
| Reverse DNS / PTR control | Outbound mail and certificate issuance depend on it |
| Additional public IPs | Multiple sites on separate IPs, or a separate management interface |
| Console access (VNC/KVM-over-IP) | Boot-time recovery when RDP is down |
Red Flags
- “Unlimited” RAM or CPU alongside a fixed low price — overcommit that will show up as RDP lag at peak hours.
- No stated virtualization technology anywhere on the site.
- Windows listed only as an “add-on” with no edition or version.
- No snapshot capability on a plan advertised for Windows.
- Support that cannot answer “which Windows Server version is in your template?”
A Ten-Minute Test Before You Commit
- Buy the smallest plan with a refund window, or take the trial.
- Deploy the Windows template and time how long until RDP answers.
- Log in and run
winver— confirm the edition and build meet your software’s requirements. - Run
Get-ComputerInfo | Select WindowsProductName, OsHardwareAbstractionLayer, CsNumberOfLogicalProcessors, CsTotalPhysicalMemory. - Check disk speed with
winsat disk -drive cor a large file copy. - Open Task Manager at 3 pm local time — not 3 am — and look at CPU steal and disk queue.
- Reboot from the panel and confirm the box comes back and RDP reconnects without a ticket.
Summary
Windows support is a property of the hypervisor, the licence, and the resource allocation — not of the word “VPS”. Ask about virtualization technology first, licensing second, and access model third; everything else is a sizing conversation. To compare plans that already answer those questions clearly, windows-vps.org keeps an updated breakdown, and our first-hour checklist covers what to do the moment your server answers on 3389.
