Installing Windows on a VPS is not like installing it on a laptop. There is no DVD drive, and the installer runs on virtual hardware managed by the provider. The entire process — from picking an image to logging in over RDP — takes about 15 minutes when you choose the right template, and the common failure points are almost all avoidable. This guide covers template deployment, custom ISO installs, unattended setup, and the first-boot configuration you should complete before trusting the server with real workloads.
Step 1: Pick the Right Image and Edition
Providers offer Windows templates in two flavors: evaluation editions (usually Windows Server 2022 or 2025 Evaluation) and licensed editions (Standard or Datacenter) where the license is bundled into the plan price. For production, prefer the licensed option — evaluation editions expire after 180 days and cannot be legally converted to full licensing without buying a key. If your provider only offers evaluations, check whether they supply a KMS-activated licensed image, or plan to bring your own license.
| Edition | Best for | Notes |
|---|---|---|
| Server 2025 Standard | General workloads, IIS, small SQL Server | Supports 2 Hyper-V guests |
| Server 2025 Datacenter | Heavy virtualization, large fleets | Unlimited guests, higher cost |
| Server 2022 Standard | Older .NET Framework apps | Same features, different support timeline |
| Evaluation (any) | Testing only | Expires in 180 days |
Step 2: Deploy From a Provider Template
Template deployment is a single click: the provider writes the image, Windows runs its built-in Sysprep specialize pass, and the server reboots into the desktop. Before you click create, size the plan correctly:
- Start with at least 2 vCPU, 4 GB RAM, and 60 GB disk. Windows Server idles around 1.5–2 GB RAM, and updates plus the page file need headroom.
- Choose the Windows Server image from the OS dropdown and confirm the data center region closest to your users.
- Set a strong administrator password — the template applies it on first boot and the provider emails you the credentials. Change it immediately after login.
Once the deployment finishes, you can skip ahead to Step 4 — the image is already installed and only needs configuration. If you have not chosen a provider yet, compare Windows VPS plans on our comparison table to see which plans bundle licensed (non-evaluation) Windows images as standard.
Step 3: Install From a Custom ISO (When You Must)
Some providers let you upload or select a custom ISO, which is mounted like a virtual CD. Boot the VPS from the ISO using the browser-based console (noVNC or the provider’s KVM console) and the Windows Setup wizard appears. Key settings to get right:
- Choose Custom: Install Windows only and delete any existing partitions so Setup creates a fresh one.
- Skip product key entry for now if you will activate later via KMS — select “I don’t have a product key”.
- Windows reboots several times during a custom install; keep the console open until you see the password prompt, or you may miss Setup prompts.
Step 4: First Boot Configuration
Once Windows is up, run these from an elevated PowerShell before doing anything else:
# Enable Remote Desktop
Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections -Value 0
Enable-NetFirewallRule -DisplayGroup 'Remote Desktop'
# Force a Windows Update check
wuauclt /detectnow
# Verify activation state
slmgr /xprChange the administrator password from the provider-assigned one, install pending updates, and confirm the server is activated — see our guide on fixing activation errors if slmgr /xpr reports grace mode instead of permanent activation. Also check the time zone and set it to your region; a wrong clock on a fresh server causes certificate and log timestamp problems later. If the server will host public sites, enable automatic updates so the monthly patch cycle runs unattended.
Step 5: Harden Before Going Live
- Enable Network Level Authentication (NLA) in the RDP settings.
- Create a non-admin user and use it for daily work instead of the Administrator account.
- Enable the built-in firewall and allow only RDP (3389) plus the ports your applications need.
- Take a snapshot immediately after updates — it is your clean restore point.
If you are still choosing where to host, see the full specs and pricing on our Windows VPS comparison table — licensing, RAM, and storage allowances differ significantly between providers at the same price point.
Database Mart offers pre-configured Windows Server 2022 and 2025 VPS images with the license included and same-day provisioning. Check Database Mart Windows VPS plans.
What to Do When the Install Looks Stuck
Three situations look like failures but are normal: a long pause at “Getting devices ready” (Sysprep is running — wait up to 10 minutes), multiple reboots during a custom ISO install (keep the console open), and a black screen after first boot on servers with less than 2 GB RAM (upgrade to 4 GB). If the server truly hangs for over 20 minutes, reboot it from the control panel — Windows Setup resumes from the last completed phase. Within a few minutes of the first RDP login you will have a clean, activated Windows Server ready for IIS, SQL Server, or whatever you plan to run.
