Windows VPS Explained: Virtualization, RDP Sessions, and Licensing in Plain Terms

Most explanations of a Windows VPS start with “it is a virtual machine” and stop there, which leaves you unable to answer the questions that actually matter: why does RAM cost more than on Linux, why do some plans come with a license and others do not, and why does your RDP session slow down at 6pm. This primer covers the three layers — hypervisor, Windows Server role, and licensing — and what each one means for a real deployment. If you are still choosing a provider, compare Windows VPS plans by RAM and license model before reading the sizing sections.

Layer one: the hypervisor does not care what OS you run

Underneath every Windows VPS is a Linux host running KVM, Hyper-V, or a container-based platform. The hypervisor allocates vCPUs, a slice of RAM, virtual disks, and a network interface. Windows has no idea it is not on bare metal unless you look closely.

Two consequences follow. First, vCPU is a time slice, not a core — a “4 vCPU” plan on an oversold node may deliver less than two physical cores of throughput during peak hours. Second, disk IOPS are shared. On Windows, that matters more than on Linux because Defender scans, Windows Update, and the pagefile all hit the same virtual disk.

You can verify what you actually got from inside Windows:

1. Run Get-CimInstance Win32_ComputerSystem | Select NumberOfLogicalProcessors,TotalPhysicalMemory to see allocated CPUs and RAM.
2. Run Get-PhysicalDisk | Select FriendlyName,MediaType,Size to see whether the backing disk reports SSD or HDD behaviour.
3. Run a short disk test with winsat disk -drive c to get a sequential and random IO baseline; record the number so you can compare after a host migration.

Layer two: which Windows SKU you are actually getting

“Windows VPS” is not one product. The image you get determines what you can install and how many people can connect.

The single most common surprise: Windows Server licenses two administrative sessions for management, not for end users. If three colleagues need a desktop, you need RDS and CALs, not a bigger VPS.

Layer three: licensing, in one page

Windows Server is licensed per core, with a minimum of 16 cores per physical server, plus client access licenses for users or devices. On a VPS, the host abstracts the physical cores, so providers sell you one of three arrangements:

• License included (SPLA). The host pays Microsoft monthly for your instance and bundles it into the price. You pay $5–$15 per month more, but nothing to manage.
• Bring your own license. Cheaper monthly, but you need a qualifying subscription or volume agreement, and you are responsible for correctness.
• Evaluation / MSDN. Fine for development, not for production. The 180-day evaluation clock does not pause.

CALs are the part people forget. A file server used by 25 staff needs 25 user CALs or 25 device CALs, regardless of how small the VM is.

What RDP actually costs in resources

A single idle RDP session on Server 2022 with Desktop Experience costs roughly 250–400 MB of RAM and negligible CPU. It is when people use it that numbers move:

• Opening a browser: +400–900 MB.
• Running Office or a rich client: +300–800 MB.
• Streaming video or heavy scrolling: significant CPU on the RDP encoder plus 2–8 Mbps per session.
• Printer redirection with a large driver: a surprisingly common cause of session hangs.

That is why a 2 GB VPS “works” until someone opens Edge, and why 4 GB is the practical floor for interactive use.

Three workloads and what they need

Single IIS site. Server Core, 2 vCPU, 2–4 GB, 60 GB disk. Remove the GUI entirely and you cut both RAM use and the patch surface. Manage it over WinRM or SSH.

Small Active Directory. Two domain controllers on separate VPS instances is the minimum for a realistic setup; a single DC on one VM is a lab, not a domain. Budget 4 GB each and keep the time sync hierarchy correct.

SQL Express plus an app. 2–4 vCPU and 8 GB, with SQL capped at 4–6 GB max server memory to leave room for the OS and IIS. Remember the Express edition caps databases at 10 GB and buffer pool at 1.4 GB, so a “faster” plan will not fix a data-size limit.

What to check before you buy

1. Which Windows build is the default image, and can you reinstall a different one at no cost?
2. Is the license bundled, and does the price change if you add vCPUs?
3. Are snapshots included, and how many can you keep?
4. Is there a console or rescue mode if RDP stops responding? Without it, a bad firewall rule locks you out permanently.
5. What is the outbound bandwidth allowance, and what does Windows Update count against?

Putting it together

Pick the image first, because Server Core versus Desktop Experience changes your RAM budget by 500 MB to 1 GB before you install anything. Then size RAM for the workload, not the OS, and finally confirm the license model so the monthly figure is real. Review the core-based licensing and CAL rules for Windows Server if the provider pricing table is vague about what is included.

Once those three layers are clear, most “why is my VPS slow” questions answer themselves: it is nearly always RAM exhaustion from the GUI, a shared disk at peak, or a license variant that forbids the multi-user setup someone assumed was included.