VIRTLIX LICENSE MANAGER
Home Features Docs Pricing Changelog About Contact Login
🚀 Getting Started
Installing Virtlix on a Fresh Server Server Requirements & Partition Layout Activating Your License Your First VPS
🖥️ VPS Management
Creating and Configuring a VPS Cloning and Rebuilding a VPS Creating a Reusable Template from a VPS Resource Plans and Per-VM Limits Windows Guest Support
🌐 Networking & Firewall
IP Pool and Network Modes VPS Firewall Rules Server-Level Firewall Plans Console Access: noVNC and the Web Terminal
💾 Backups & OS Templates
Automated Backups and Backup Destinations Managing OS Templates Uploading and Using ISOs Media Groups
🔑 Multi-Server & Licensing
Understanding Your License and VPS Limits Master Configuration and Security Settings Registering and Controlling Remote Servers Webhook Callbacks
❓ Troubleshooting & FAQ
Console Shows "Connection Lost" License Shows as Suspended or Expired VPS Won't Start After Creation Common Questions
Docs / VPS Management / Windows Guest Support

Windows Guest Support

Windows Server guests (2016 through 2025) work like any other OS template - pick one when creating a VPS and Virtlix handles the rest. There's no cloud-init for Windows, so first-boot configuration is injected offline instead: the Administrator password, static IPv4/IPv6, DNS, timezone, and RDP are all set up automatically, and the initial Windows setup wizard (OOBE) is skipped entirely - the customer's first real interaction is signing in with the password you set, not clicking through a setup wizard. Password and hostname changes apply live through the QEMU Guest Agent when it's running inside the guest, or automatically on the next restart otherwise - no manual RDP session required either way. Building your own Windows template uses the same Blank + ISO Install path as any custom OS template: create a VM with no OS template selected, attach a Windows Server ISO, and boot straight into Setup through the console exactly like installing on real hardware. A virtio driver ISO is attached automatically so Setup can see the virtual disk (use its "Load driver" button and pick viostor for the matching Windows version). Once Windows is installed and you've signed in, run sysprep /generalize /oobe /shutdown from an elevated command prompt to generalize the image, then use Create Template from VPS to turn it into a reusable, enabled OS template. Requirements for a template you bring yourself: it must already have the QEMU Guest Agent and virtio network driver installed, and be sysprepped with /generalize /oobe so first boot re-runs the out-of-box experience Virtlix's injection hooks into. Only virtio-blk disks are supported for Windows guests today - virtio-SCSI isn't yet wired up.