Back to blog
January 19, 2026Guides

How to Install VLESS Proxy on Windows Server

Step-by-step guide on setting up VLESS proxy on Windows Server 2019/2022 using Xray-core for secure and censorship-resistant connections.

How to Install VLESS Proxy on Windows Server

While most proxy tutorials focus on Linux, many users prefer or require Windows Server for their infrastructure. VLESS works perfectly on Windows Server, and this guide will show you how to set it up using Xray-core. Whether you're running a Windows VPS from Hiddence or have a dedicated Windows server, you can deploy VLESS in minutes.

Why Run VLESS on Windows Server?

  • Familiar GUI interface for those uncomfortable with command line
  • Integration with Windows-specific services and Active Directory
  • Better compatibility with certain enterprise applications
  • Some hosting providers offer cheaper Windows VPS options
  • Easy remote management via RDP (Remote Desktop)
  • Native support for .NET applications alongside proxy

Prerequisites

  • Windows Server 2019 or 2022 (Hiddence Windows VPS recommended)
  • Administrator access to the server
  • RDP client for remote connection
  • At least 2GB RAM and 20GB storage
  • Domain name (optional, for TLS configuration)

Step 1: Download Xray-core for Windows

Download the latest Xray-core Windows release:

bash
# Open PowerShell as Administrator and run:

# Create directory for Xray
New-Item -Path "C:\Xray" -ItemType Directory
cd C:\Xray

# Download latest Xray (replace version as needed)
Invoke-WebRequest -Uri "https://github.com/XTLS/Xray-core/releases/latest/download/Xray-windows-64.zip" -OutFile "Xray.zip"

# Extract the archive
Expand-Archive -Path "Xray.zip" -DestinationPath "C:\Xray"

# Verify installation
.\xray.exe version

Step 2: Create VLESS Configuration File

Create a configuration file for VLESS with Reality or TLS:

  • Create a file named config.json in C:\Xray\
  • Open Notepad as Administrator
  • Paste a VLESS configuration (examples available in Xray documentation)
  • For Reality: Use SNI like www.microsoft.com
  • For TLS: Point to your domain and certificate files
  • Configure inbound port (recommended: 443)
  • Generate UUID using online tool or PowerShell: [guid]::NewGuid()
  • Save the config.json file

Step 3: Test Xray Configuration

Test your configuration before setting up as service:

bash
# In PowerShell, navigate to Xray directory
cd C:\Xray

# Run Xray with your config
.\xray.exe run -c config.json

# If no errors appear, press Ctrl+C to stop
# If errors appear, check your config.json syntax

Step 4: Install Xray as Windows Service

Use NSSM (Non-Sucking Service Manager) to run Xray as a service:

  • Download NSSM from https://nssm.cc/download
  • Extract nssm.exe to C:\Xray\
  • Open PowerShell as Administrator in C:\Xray\
  • Run: .\nssm.exe install Xray
  • In the NSSM GUI:
  • Path: C:\Xray\xray.exe
  • Startup directory: C:\Xray
  • Arguments: run -c config.json
  • Click 'Install service'
  • Start the service: Start-Service Xray
  • Verify: Get-Service Xray

Step 5: Configure Windows Firewall

Allow Xray through Windows Firewall:

  • Open Windows Defender Firewall with Advanced Security
  • Click 'Inbound Rules' > 'New Rule'
  • Rule Type: Port
  • Protocol: TCP, Port: 443 (or your configured port)
  • Action: Allow the connection
  • Profile: Check all (Domain, Private, Public)
  • Name: Xray VLESS
  • Click Finish
  • Alternatively, use PowerShell:
  • New-NetFirewallRule -DisplayName 'Xray' -Direction Inbound -LocalPort 443 -Protocol TCP -Action Allow

Windows Server VLESS Tips

  • Set Xray service to start automatically: Set-Service Xray -StartupType Automatic
  • Monitor Xray logs in C:\Xray\error.log and access.log
  • Use Task Scheduler for automatic config backups
  • Consider using Reality instead of TLS (no domain/certificate needed)
  • Disable Windows Update automatic restart during service hours
  • Use Remote Desktop to manage the server easily
  • Keep Windows Server updated for security patches
  • Monitor server resources using Task Manager or Performance Monitor