When a Windows VPS is the runtime for IIS and .NET, the server version decides which runtimes still receive updates, which TLS ciphers are on by default, and how much RAM the OS itself consumes before your application starts. Comparing Server 2016, 2019, 2022 and 2025 is therefore a support-lifecycle question first and a performance question second.
.NET Runtime Support Matrix
ASP.NET Framework 4.8 is the last framework release and ships in-box from 2019 onward. ASP.NET Core runs anywhere the host runs, but the specific .NET version that Microsoft still patches differs by OS. Older servers cannot always run newer .NET branches because the runtime declares a minimum OS version.
| Server | In-box Framework | .NET 8 | .NET 9 | .NET 10 |
|---|---|---|---|---|
| 2016 | 4.6.2 (4.8 installable) | Supported | Not supported | Not supported |
| 2019 | 4.7.2 (4.8 installable) | Supported | Supported | Test only |
| 2022 | 4.8 | Supported | Supported | Supported |
| 2025 | 4.8 | Supported | Supported | Supported; default |
If your application targets .NET 10, only 2022 and 2025 are viable. If it is Framework 4.8 only, all four work – the decision shifts to patching cadence and TLS defaults.
The runtime support table is not the whole story. Each ASP.NET Core branch also declares a minimum Windows build in its runtimeconfig.json targets, and the hosting bundle refuses to install when that floor is not met. A .NET 10 hosting bundle on Server 2019 will install silently but fail at first request with HTTP Error 500.0 - ANCM In-Process Start Failure. Check dotnet --list-runtimes after install rather than trusting the installer exit code.
Installing IIS Over an Existing Site
When you move an existing site between server versions, the IIS configuration export format is compatible from 2016 forward, but the applicationHost.config schema version is not. Export with %windir%\system32\inetsrv\appcmd list site /config /xml > sites.xml, then import with appcmd add site /in < sites.xml on the new host and compare the bindings afterwards.
Application pools that ran under v4.0 on 2016 still exist on 2025, but the managed runtime pipeline is the same Framework 4.8 engine. There is no "v4.5" pool - the label is cosmetic and misleading in older documentation.
TLS and Cipher Defaults
Server 2016 supports TLS 1.2 but leaves TLS 1.0 and 1.1 enabled, plus RC4 and 3DES in the cipher order. 2019 disables 3DES by default but keeps the old protocol versions. 2022 disables TLS 1.0 and 1.1 by default and vendors prefer TLS 1.3 support via Windows Update. 2025 removes RC4 and TLS 1.0/1.1 from the default list entirely.
- 2016:
HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocolsmust be edited to turn off TLS 1.0. - 2019: edit protocols, leave ciphers to
ssl cipher suite orderpolicy. - 2022: TLS 1.0/1.1 off out of the box; enable TLS 1.3 via
DisabledByDefault=0underSCHANNEL\Protocols\TLS 1.3. - 2025: TLS 1.3 default; verify with
Get-TlsCipherSuite -Name "TLS_AES_256_GCM_SHA384".
IIS binds to the OS default cipher list. A server 2016 host that passes a scan last quarter can fail one this quarter after a cipher-order change from a rollup, so pin the order with a policy and test annually.
SMB Signing Defaults
SMB signing is a direct attack-surface control on any VPS that shares files or backs up over SMB. The default moved from "optional" to "required" across the four releases.
| Server | SMB1 default | SMB signing (server) | SMB signing (client) |
|---|---|---|---|
| 2016 | Installed, enabled | Optional | Optional |
| 2019 | Installed, enabled | Optional | Optional |
| 2022 | Installed, not started | Required on DCs only | Enabled |
| 2025 | Removed from default install | Required | Required |
If your backup target is a NAS that only supports SMB1, moving to 2025 requires either a firmware upgrade or a proxy share on an older server. Plan that before you upgrade the host.
End-of-Life Dates That Force the Decision
- Server 2016: mainstream support ended 11 January 2022; extended support ends 12 January 2027.
- Server 2019: extended support ends 9 January 2029.
- Server 2022: extended support ends 13 October 2031.
- Server 2025: released November 2024; support through 2034.
A VPS billed monthly can be rebuilt in an hour. Choose the version whose support end is at least as far out as your code will reasonably live, and make an upgrade path part of the deployment plan rather than an accident.
RAM and CPU Footprint
Baseline memory on a 2 vCPU instance after a clean boot and current patches, measured with Get-Counter '\Memory\Available MBytes' after 15 idle minutes:
| Server | Idle RAM | Disk footprint | Notes |
|---|---|---|---|
| 2016 | ~900 MB | ~12 GB | Fewest background services; older core scheduler. |
| 2019 | ~1.0 GB | ~13 GB | Similar footprint; better container support. |
| 2022 | ~1.3 GB | ~15 GB | More telemetry and Defender features. |
| 2025 | ~1.6 GB | ~18 GB | Additional auth stack and TLS 1.3. |
On a 2 GB VPS, 2025 alone can consume most of the ceiling before IIS starts. Size the plan so that Available MBytes never drops below 256 MB under peak load - the paging that follows shows up as a 300 ms response-time spike, not a crash.
Measure with the application deployed, not just the bare OS. An IIS worker process with a .NET 8 site and 20 concurrent users typically adds 250-400 MB. On 2025 that puts a 4 GB instance at roughly 60 percent committed under normal load, which is a reasonable ceiling; on 2016 the same workload runs comfortably in 2 GB, but you inherit the end-of-support date.
Comparing Support Windows and Upgrade Cost
An upgrade between adjacent versions is an in-place setup, which on a VPS rarely finishes in one window: the setup disk needs 20 GB free plus a working console session. A side-by-side build on a second instance with appcmd export and import is slower to script but faster to roll back. Budget four hours for in-place on 2019 to 2022 and treat 2016 to anything newer as a rebuild.
Choosing for a Small Deployment
For a single IIS site behind a TLS terminator, a 2019 or 2022 VPS on 4 GB is the sweet spot: modern cipher defaults, Framework 4.8 in-box, and a support window into the next decade. 2025 makes sense only when the application needs .NET 10 or TLS 1.3 and the RAM budget allows, while 2016 should be treated as a migration target, not a destination. Our Windows VPS platform supports all four images, and the support team can confirm availability of a specific build before you commit.



