--- title: "How to Install Windows Server 2025 on a CubePath VPS" description: "Install Windows Server 2025 on a CubePath VPS from the ISO in the control panel, set a static IP address, enable Remote Desktop and connect to it over RDP." category: "vps" language: en source: https://cubepath.com/docs/vps/how-to-install-windows-server-2025-on-your-vps updated: 2026-10-11 --- # How to Install Windows Server 2025 on a CubePath VPS Windows Server 2025 can run on any CubePath VPS by booting the installer from an ISO in the control panel. The Windows Server 2025 ISO that CubePath provides already includes the VirtIO drivers, so the installer sees the disk and network card without loading extra drivers. In this tutorial you will mount the ISO, install Windows from the web console, configure the static IP address the VPS needs to reach the internet, and enable Remote Desktop so you can manage the server over RDP. ## Prerequisites To follow this guide you need: - A CubePath VPS with at least **2 vCPU**, **4 GB RAM** and **40 GB of disk**. - Access to the [CubePath control panel](https://my.cubepath.com). - The public IPv4 address of the VPS, shown in the **Overview** tab of the VPS dashboard. - A valid Windows Server 2025 license if you plan to use the server beyond evaluation. - A Remote Desktop client on your computer: **Remote Desktop Connection** (`mstsc`) on Windows, or **Windows App** on macOS. > Warning: Installing Windows erases the VPS disk. Back up anything you need from the current operating system before you start. ## Step 1 - Mounting the Windows Server 2025 ISO In the VPS dashboard, open the **ISOs** tab, search for **Windows Server 2025** and click **Mount** on **Windows Server 2025 Standard (EN)**. Confirm the dialog. The VPS restarts automatically with the ISO attached. The ISO is about 8 GB, so it can take several minutes to be copied to the server. **Wait about 10 minutes** and then click **Restart** in the VPS dashboard so the VPS boots with the full ISO available. ## Step 2 - Booting the installer from the console Click the **Console** button in the top right corner of the VPS dashboard. A new window opens showing the VPS screen. ![Console button in the VPS dashboard](https://cdn.cubepath.com/img/docs/9be73c72-a2d9-4876-9e57-162199a17c3c.png) When the message **"Press any key to boot from CD or DVD..."** appears, click inside the console window and press any key. The prompt only waits a few seconds; if you miss it, the VPS keeps retrying and the message shows up again, so press a key the next time you see it. ![Press any key to boot from CD or DVD](https://cdn.cubepath.com/img/docs/eae86aab-9835-4e6b-b17f-94d0cf1cde02.png) You know it worked when the Windows logo and then the **Windows Server Setup** window appear. ## Step 3 - Running Windows Server Setup Windows Server 2025 uses a new Setup with one choice per screen. Go through them in order: 1. **Select language settings**: choose the **time and currency format** and click **Next**. 2. **Select keyboard settings**: choose your **keyboard layout** and click **Next**. The keyboard layout matters because it is the layout the console uses when you type the Administrator password later. 3. **Select setup option**: choose **Install Windows Server**, check **I agree everything will be deleted including files, apps, and settings** and click **Next**. 4. **Product key**: if Setup asks for one, enter your key, or click **I don't have a product key** to install now and activate later. 5. **Select image**: choose an edition that ends in **(Desktop Experience)** and click **Next**. The other editions install Server Core, which has no graphical desktop and no Server Manager window, so the network and Remote Desktop steps below would not look the same. 6. **Applicable notices and license terms**: click **Accept**. ## Step 4 - Preparing the disk The **Select location to install Windows Server** screen lists the partitions left by the previous operating system. For a clean installation: 1. Select each partition and click **Delete partition**, confirming each time, until only **Disk 0 Unallocated Space** remains. 2. Select the unallocated space and click **Next**. Setup creates the partitions Windows needs on its own. 3. On the **Ready to install** screen, click **Install**. If the list is empty and shows no disk at all, the VirtIO storage driver was not loaded. Check that you mounted the Windows Server 2025 ISO from the **ISOs** tab and not a different image. ## Step 5 - Waiting for the installation Setup copies the files and installs Windows. It takes about **10 to 20 minutes** and the VPS restarts on its own one or more times. You don't need to press any key during these restarts: if you see the "Press any key to boot from CD or DVD..." message again, ignore it and let the VPS continue booting from the disk. ## Step 6 - Setting the Administrator password When the installation finishes, the **Customize settings** screen asks for a password for the built-in **Administrator** account. Use a long, unique password: this account will be reachable over RDP from the internet once you enable Remote Desktop. Click **Finish**. ## Step 7 - Logging in from the console The lock screen asks for **Ctrl+Alt+Del**. Pressing it on your own keyboard would be caught by your computer, so click the **Send CtrlAltDel** button at the top of the console instead. Enter the Administrator password and press **Enter**. On the first login Windows asks about **diagnostic data**. Choose **Required diagnostic data** and click **Accept**. **Server Manager** then opens automatically. ## Step 8 - Unmounting the ISO Go back to the **ISOs** tab in the VPS dashboard and click **Unmount** on the Windows Server 2025 ISO. This restores the normal boot order, so the VPS boots straight into Windows from now on and you won't see the "Press any key" prompt again. ## Step 9 - Configuring the static IP address Windows does not get its address automatically on the VPS, so the server has no internet access until you configure the IP by hand. You need these values: | Field | Value | |-------|-------| | IP address | The VPS IP shown in the **Overview** tab | | Subnet mask | `255.255.255.0` (prefix length `24`) | | Default gateway | The VPS IP with the last number changed to `1`. For example, if the IP is `194.26.100.28`, the gateway is `194.26.100.1` | | Preferred DNS server | `1.1.1.1` | | Alternate DNS server | `8.8.8.8` | ### Option A: from the graphical interface Windows Server 2025 moved most network settings into the new **Settings** app, but the classic adapter window is still the quickest way to set a static IP: 1. Right-click the Start button, choose **Run**, type `ncpa.cpl` and click **OK**. 2. Right-click the **Ethernet** adapter and select **Properties**. 3. Select **Internet Protocol Version 4 (TCP/IPv4)** and click **Properties**. 4. Select **Use the following IP address** and **Use the following DNS server addresses**, and fill in the values from the table. 5. Click **OK** on every open window to apply the settings. ### Option B: from PowerShell If you prefer the command line, open PowerShell as Administrator (right-click the Start button and choose **Terminal (Admin)** or **Windows PowerShell (Admin)**). First confirm the name of the network adapter: ```powershell Get-NetAdapter ``` ```output Name InterfaceDescription ifIndex Status MacAddress LinkSpeed ---- -------------------- ------- ------ ---------- --------- Ethernet Red Hat VirtIO Ethernet Adapter 6 Up BC-24-11-XX-XX-XX 10 Gbps ``` Assign the address and gateway, replacing `your_server_ip` and `your_gateway` with your values: ```powershell New-NetIPAddress -InterfaceAlias "Ethernet" -IPAddress your_server_ip -PrefixLength 24 -DefaultGateway your_gateway ``` Set the DNS servers: ```powershell Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses 1.1.1.1,8.8.8.8 ``` ### Verifying connectivity Whichever option you used, check that the gateway and the internet are reachable. In PowerShell run: ```powershell Test-NetConnection cubepath.com -Port 443 ``` ```output ComputerName : cubepath.com RemoteAddress : 104.21.x.x RemotePort : 443 InterfaceAlias : Ethernet SourceAddress : 194.26.100.28 TcpTestSucceeded : True ``` `TcpTestSucceeded : True` means routing and DNS both work. If name resolution fails but `Test-NetConnection 1.1.1.1 -Port 443` succeeds, review the DNS servers. ## Step 10 - Enabling Remote Desktop The web console is fine for the installation, but Remote Desktop is faster and supports copy and paste and a proper screen resolution. From the graphical interface: 1. In **Server Manager**, click **Local Server**. 2. Click the **Disabled** link next to **Remote Desktop**. 3. Select **Allow remote connections to this computer**. Leave **Allow connections only from computers running Remote Desktop with Network Level Authentication** checked. 4. Click **OK**. Enabling it this way also opens the Remote Desktop rules in Windows Defender Firewall. To do the same from an elevated PowerShell window instead: ```powershell Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections -Value 0 ``` ```powershell Enable-NetFirewallRule -DisplayGroup "Remote Desktop" ``` The `-DisplayGroup "Remote Desktop"` name applies when Windows is installed in English. Check that the service is listening on TCP port 3389: ```powershell Get-NetTCPConnection -LocalPort 3389 -State Listen ``` ```output LocalAddress LocalPort RemoteAddress RemotePort State AppliedSetting OwningProcess ------------ --------- ------------- ---------- ----- -------------- ------------- 0.0.0.0 3389 0.0.0.0 0 Listen 1120 :: 3389 :: 0 Listen 1120 ``` ## Step 11 - Connecting over RDP On your computer, open **Remote Desktop Connection** (`mstsc` on Windows) or **Windows App** on macOS, enter the VPS IP address and log in as `Administrator` with the password you set in Step 6. Accept the certificate warning the first time: Windows uses a self-signed certificate for RDP by default. Once you are connected, open **Settings > Windows Update** and install the pending updates before exposing any services on the server. ## Troubleshooting - **The console shows the old operating system instead of the installer.** The ISO was still being copied when the VPS rebooted. Wait a few more minutes, click **Restart** again and watch for the "Press any key" prompt. - **The installer shows no disk.** You booted a different ISO. Unmount it and mount **Windows Server 2025** from the **ISOs** tab. - **No internet after setting the IP.** Compare the IP, mask and gateway against the table in Step 9. A wrong gateway is the most common mistake: it must be in the same `/24` as the VPS IP and end in `.1`. - **RDP times out.** Check that Remote Desktop is enabled, that `Get-NetTCPConnection -LocalPort 3389` shows a listener and that the firewall rules for the **Remote Desktop** group are enabled. ## Conclusion Your CubePath VPS now runs Windows Server 2025 with a static IP address and Remote Desktop enabled, and you can manage it over RDP instead of the web console. Good next steps are installing all Windows updates, creating a separate administrator account instead of using the built-in `Administrator` for daily work, and adding server roles such as IIS from **Server Manager > Add roles and features**. If you run into a problem that isn't covered here, [contact our support team](https://my.cubepath.com/tickets/create/support).