How to Install Windows via 1-Click Reinstaller

To install Windows via 1-click reinstaller, choose a Windows template in the VPSLake control panel, complete the first-boot wizard in VNC, and reconnect over RDP. The rebuild usually takes several minutes, followed by a short setup and security check.

Prerequisites

• A VPSLake VPS with enough resources for the selected template; 2 GB RAM and 40 GB of disk is a practical starting point for Windows Server, while Windows 11 Pro is more comfortable with 4 GB RAM.
• Access to the VPSLake Windows RDP service and the VPSLake client area at https://my.vpslake.com.
• The account email and client-area password, plus a separate computer with an RDP client.
• A backup of every file you need. Reinstalling formats the VPS disk and removes the current operating system, applications, users, and files.
• The server’s public IP address. You will also create a strong Administrator password during setup; use a unique password in place of YOUR_STRONG_PASSWORD if a credential prompt asks for one.

Step 1: Back up the VPS and open its control panel

Reinstallation is destructive, so save files and note any custom ports or DNS records before starting the rebuild.

1. Sign in to https://my.vpslake.com.
2. Open Services → My Services, select the Windows VPS, and choose Manage.
3. Open the VPS Control Panel link to launch Virtualizor.
4. Record the public IP and any information you need after the reinstall. Do not rely on a screenshot of the old Windows desktop as a backup.

If the control-panel link is missing, open a client-area ticket with the service ID. Do not cancel or recreate the service just to obtain a panel link.

Step 2: Start the one-click Windows reinstall

The reinstall template determines which Windows image is written to the VPS, so select the version that matches the software you plan to run.

1. In Virtualizor, open Manage → Reinstall.
2. Under the Windows section, select the required image, such as Windows 10 Pro, Windows 11 Pro, or Windows Server 2019, when listed for your service.
3. For a Windows Server image, choose Desktop Experience if you need a graphical desktop and local Server Manager. Choose Server Core only if you are prepared to administer the machine with PowerShell or remote management. Microsoft explains the difference in its Server Core and Desktop Experience documentation.
4. Read the warning, confirm that the disk can be erased, and select Reinstall or Start Reinstall.
5. Confirm the final prompt. The VPS may shut down, reboot, and disappear from RDP while the image is being deployed.

The task or VPS status should change to a rebuilding state. Wait for the task to finish before trying to connect; repeated reboot clicks can interrupt a deployment.

Step 3: Wait for deployment and open VNC

VNC works at the console level, so it lets you finish Windows setup even before Remote Desktop is available.

1. In Virtualizor, open Manage → Tasks or the task-log view and wait until the reinstall reports completion.
2. Open Manage → VNC, then select Launch VNC. If the console is blank, wait a minute, refresh it, and use the panel’s Power Control → Reboot action once.
3. When Windows Setup appears, select the country or region, preferred language, and keyboard layout, then continue.
4. Accept the license terms when prompted.
5. Set the built-in Administrator password. Use a long, unique password with upper- and lowercase letters, numbers, and symbols; never reuse the VPSLake client-area password.

For Windows Server, select the edition and installation option presented by the image. The graphical option is normally labeled Desktop Experience. Windows desktop templates may use a slightly different first-boot screen, but they still require regional settings and an administrator credential.

Step 4: Sign in locally and confirm networking

The VNC console proves that Windows finished booting; checking the address and edition prevents you from troubleshooting RDP against the wrong server.

1. In VNC, use Send Ctrl+Alt+Del or the equivalent console button.
2. Sign in as Administrator with the password you just created.
3. Open Settings → System → About on Windows Pro, or Server Manager → Local Server on Windows Server, and confirm the expected Windows edition.
4. Open PowerShell as administrator and run:

Get-ComputerInfo -Property WindowsProductName,WindowsVersion,OsBuildNumber
Get-NetIPConfiguration | Format-Table InterfaceAlias,IPv4Address,IPv4DefaultGateway
Test-NetConnection -ComputerName 1.1.1.1 -Port 443

You should see the selected Windows product, a non-empty server IPv4 address, and a successful TCP test:

WindowsProductName : Microsoft Windows Server 2019 Standard
TcpTestSucceeded  : True

If the address is missing, reboot once from the panel and check the virtual network adapter again. Do not manually assign the old server’s address unless VPSLake has provided static network settings for the service.

Step 5: Connect over Remote Desktop

RDP is the practical management path after the console setup, but the first connection should verify both the address and the Windows firewall rule.

From a Windows computer, press Windows key + R, enter mstsc, and select OK. Enter the VPS public address as SERVER_IP or SERVER_IP:3389, select Connect, and sign in with the Administrator account and the new password. On macOS, Linux, Android, or iOS, use a Microsoft Remote Desktop client and create a connection for SERVER_IP.

If you want to test the port before opening the full client, run this from another Windows computer:

Test-NetConnection -ComputerName SERVER_IP -Port 3389

Expected output includes:

ComputerName     : SERVER_IP
RemotePort       : 3389
TcpTestSucceeded : True

Microsoft’s Remote Desktop access guide covers the Windows-side access setting. Keep Network Level Authentication enabled unless a legacy client genuinely requires another configuration.

Verify the new Windows installation

After the first RDP login, install Windows updates, confirm that the clock and time zone are correct, and verify that the Administrator account is not using a temporary password. In an elevated PowerShell window, run:

Get-Service TermService | Format-Table Status,Name,DisplayName
Get-NetFirewallRule -DisplayGroup "Remote Desktop" | Where-Object Enabled -eq 'True' | Format-Table DisplayName,Profile,Enabled,Action

The service should show Running, and at least one enabled Remote Desktop allow rule should be present:

Status  Name        DisplayName
------  ----        -----------
Running TermService Remote Desktop Services

Troubleshooting

The reinstall option is missing

The service may not support the selected Windows template, or you may be viewing the billing service instead of its Virtualizor control panel. Open Services → My Services → Manage → VPS Control Panel and check Manage → Reinstall; if it is still absent, send the service ID to VPSLake support.

VNC shows a black screen or does not reach Windows Setup

The VM may still be deploying, or the console session may have opened before the first reboot completed. Wait for the task log to finish, refresh VNC, and use Power Control → Reboot once. If the task is failed rather than running, keep the error text for a support ticket.

TcpTestSucceeded : False on port 3389

First confirm that Windows has finished booting and that TermService is running. Then check Windows Defender Firewall with Advanced Security → Inbound Rules for the enabled Remote Desktop – User Mode (TCP-In) rule; also check for an upstream firewall or a VPS control-panel rule blocking TCP 3389.

The Administrator password is rejected

Use the exact password created in the first-boot wizard and check Caps Lock. If it is definitely lost, use the VNC console while signed in locally to set a new password with Computer Management → Local Users and Groups → Users → Administrator → Set Password; do not guess at credentials through repeated RDP attempts.

Hardening

• Install current Windows updates before deploying applications.
• Change the RDP port only after creating and testing the matching inbound firewall rule, and keep a VNC recovery path available.
• Restrict RDP to your trusted public IP in the Windows firewall or provider firewall when your work location has a stable address.
• Create a standard daily-use account and reserve the built-in Administrator account for administration.

FAQ

Does a one-click reinstall keep my files?

No. It replaces the operating system and normally erases the VPS disk. Copy files, application data, licenses, and configuration off the VPS before confirming the reinstall.

Which Windows image should I choose?

Choose Windows 10 Pro or Windows 11 Pro for a single-user desktop workflow, and Windows Server for server roles or multiple concurrent administrative sessions. For Windows Server, choose Desktop Experience when you need a graphical interface; Server Core is intended for command-line and remote management.

Can I use RDP immediately after starting the reinstall?

No. RDP is unavailable while the image is being written and while the first-boot wizard is waiting for input. Finish the setup in VNC, wait for Windows to reach the login screen, and then test the public address on TCP 3389.

Will reinstalling change my VPS IP address?

A normal OS reinstall does not require you to change the service’s assigned address, but the address shown in the client area is the one you should use after deployment. Confirm it in Virtualizor and in Windows before updating any DNS records.