Why Cheap VPS Providers Don’t Offer Windows

01The Question Behind the Question

You have probably already tried the obvious route. You go to a hosting provider, pick the cheapest plan, and look at the operating system dropdown. A dozen Linux distributions, a couple of BSD options, and no Windows anywhere. Ask support and you get the same answer every time, phrased politely: we do not offer Windows.

DigitalOcean is unusually direct about it. Their own documentation says, without hedging:

“No, you cannot use Windows on a Droplet. We do not provide Windows images for Droplets and do not support Windows custom images.”

What makes that interesting is that it is not a technical limitation. You can run Windows on that hardware. The server does not care what kernel you put on it. What the provider cannot do is sell it to you, and those are two completely different problems.

There are two walls in the way, and they get confused with each other constantly. One is a licensing wall, which is about money and contracts. The other is a virtualization wall, which is about how modern hosting infrastructure moves machines around. A provider hits the first wall before they even get to the second.

02What Windows Actually Costs a Provider

A hosting provider cannot simply buy a Windows licence and hand you the machine. Microsoft draws a hard line between you licensing Windows for yourself and a company licensing Windows in order to host it for somebody else. The second activity has its own programme, and it is the only one that permits it.

That programme is called SPLA — the Services Provider License Agreement. It works differently from anything you have bought before:

• It is a monthly subscription, not a purchase. You never own it.
• Usage is reported every month through an authorised SPLA reseller, not bought once.
• The licensee has to operate its own infrastructure. You cannot resell hosting you are yourself renting from somebody else.
• It has to be signed, and it has to be reported.

The practical numbers are roughly these. Windows Server Standard under SPLA runs around 15 dollars per virtual machine per month, with a sixteen-core minimum on the physical server and an eight-core minimum for each VM. Datacenter, which removes the per-VM count limit, is closer to 50 dollars. If customers are going to connect to a desktop rather than a console, Remote Desktop Services licences add roughly 5 to 15 dollars per user on top, and ordinary Windows Server client access licences add a couple more.

And then the rules changed in October 2025

On 1 October 2025, Microsoft restricted SPLA on what it calls Listed Providers. The list is short and familiar: AWS, Microsoft Azure, Google Cloud and Alibaba Cloud. Service providers can no longer cover customer workloads running on those platforms with their own SPLA licences.

Hosters running on their own hardware — the DigitalOceans, Hetzners, Lincodes, Contabos and OVHs of the world — are not affected. But a small provider who built their platform on top of AWS just lost the ability to license Windows that way, and that is a story that has quietly reshaped the market over the past year.

Route to legally offer Windows	Who can use it	Cost shape
SPLA	Hoster on its own infrastructure	~$15/mo per VM
CSP via a hoster	Buying from a cloud provider	~$15-40/mo per VM
Your own licence	You, for your own machine	One-off, per core
Include it and eat the cost	Nobody at this price point	More than the plan

03Per-Core Licensing, Explained Without the Jargon

Windows Server stopped being licensed per processor a while ago. It is licensed per physical core, and there is a floor underneath it. You do not get to buy four cores because your virtual machine only uses four.

Rule	Number	What it means in practice
Minimum per physical server	16 cores	Every host has to be fully licensed up to 16 cores at least
Minimum per virtual machine	8 cores	A small VM does not reduce the licence
Standard covers	2 virtual machines	Two Windows VMs per Standard licence
Datacenter covers	Unlimited	Why it costs several times more
Client access licences	Per user or device	Separate from the server licence entirely

That rule about Standard covering two virtual machines is worth sitting with, because it explains the price of everything above it. A hoster running thirty Windows VMs on one physical server does not buy thirty licences; they buy core licences for the host and, if they are on Standard, they need enough of them to cover pairs of VMs. Datacenter removes that arithmetic, which is exactly why it is the more expensive product and why the difference is not a marketing trick.

For comparison, a retail sixteen-core Standard pack is around 970 dollars, Datacenter around 6,100, an ordinary client access licence around 45, and a Remote Desktop Services licence around 155. Those are list prices for buying outright, not the subscription a hoster pays, but they show the scale.

04Where Desktop Windows Is Barred Entirely

Everything so far has been about Windows Server. Windows 10 and Windows 11 are a different story, and a shorter one: a provider cannot sell you those for the purpose of remote use. Microsoft’s terms do not permit desktop operating system licences to be used to deliver a hosted desktop to third parties. That is a category of activity Microsoft does not license on the retail product at all.

This is the reason the market for Windows 10 and 11 on a VPS looks the way it does. There is no provider offering it as a product, because there is no clean way to license it as a service. What exists instead is a large number of individuals installing it themselves on hardware they rent, and taking responsibility for their own licence. Different activity, different rules.

Where that leaves you is the same place it leaves everybody: the licence is yours to arrange, and the practical question is which of the routes in section 07 actually fits what you are doing.

05The Technical Reason They’d Rather Not

Suppose a provider solved the licensing problem and decided to offer Windows. They would walk straight into the second wall, and this one has nothing to do with money.

When you rent a VPS, you get a virtual machine. If that machine is going to run Windows, the Linux VM you are sitting on has to be able to run a hypervisor of its own — QEMU, in the case of a self-installed Windows. That is called nested virtualization, and it requires the host to pass the CPU’s virtualization flag through to your VM. Without it, the CPU has no hardware acceleration to offer and the Windows guest falls back to emulating every instruction in software.

Enabling that flag is a single setting. So why would a provider leave it off?

Live migration is the reason

Large hosting platforms move running virtual machines between physical hosts. They do it during maintenance, to rebalance load, and to drain a machine before patching it. To your server it is invisible: the machine keeps running, on different hardware, without a reboot.

Now put a virtual machine inside your virtual machine. The migration has to move a guest that is itself running guests. If the destination host has a different CPU generation, or simply has the virtualization flag configured differently, the inner machine either fails to resume or resumes broken. What was a routine maintenance operation becomes a support incident, on a platform with thousands of customers.

Akamai, which runs Linode, says the quiet part out loud: nested virtualization is not supported because it interferes with live migration. That is the whole answer. Not that it is impossible — that supporting it removes the ability to move machines without downtime, and that ability is worth more to them than the Windows market.

06What They Sell Instead

Some providers do sell Windows. It is worth understanding how, because the model explains the price difference you see on their pricing pages.

Vultr is a good example, because their documentation is clear about it in both directions. On the one hand, a Windows licence is automatically included when you provision a Windows server. On the other, the base monthly price does not include it — an additional licensing fee is applied based on the size of the compute plan you picked. And one more line that matters: existing Windows Server licences cannot be transferred to them.

So you are not buying Windows. You are renting a licensed machine, at a price that goes up with the plan, and the licence stays with them. That is a perfectly reasonable product. It is also the reason the same box costs meaningfully more with Windows than with Linux: Linux has no licence to pass through, so the Linux price is the hardware price.

Provider stance	What you get	Who it suits
Sells licensed Windows	The VM plus a licence, priced in	Businesses that want one invoice
Sells Linux only	A cheaper machine with no OS licence	Anyone willing to license separately
Offers nested virt	Linux that can run a hypervisor inside it	Self-installed Windows, accelerated
Refuses nested virt	Linux only, host-level virtualization	Self-installed Windows, emulated

The two middle rows are the interesting ones, and they exist because of the wall in section 05. A provider might refuse nested virtualization for the live migration reason and still be a perfectly good place to run Windows, because emulation works. You just pay for it in speed rather than in licence fees.

07Your Options, Honestly

Four routes exist. They are not ranked by quality; they are ranked by what you are optimising for.

08Frequently Asked Questions