Windows 10 RDP Client: Settings, Credentials, and Fixes for Your VPS

Windows 10 includes the Remote Desktop Connection client (mstsc) as a standard component, so connecting to a Windows VPS from Windows 10 needs no installation. What most people get wrong is not the client itself, but the credential format, the saved-session settings, and a few display options that turn a laggy session into a smooth one. This guide walks through the setup that works, step by step.

Step 1: Open Remote Desktop Connection

Press Win + R, type mstsc, and press Enter. Alternatively, search for “Remote Desktop Connection” in the Start menu. In the Computer field, enter the public IP address of your VPS. If your provider assigned a hostname, the IP is still the safer choice because it avoids DNS caching issues.

Before clicking Connect, open Show Options — every useful setting lives behind that button.

Step 2: Enter the credentials correctly

Leave the User name field empty for now; the client will prompt you at connection time. When it does, use the local-account format:

.\Administrator

The .\ prefix targets the local machine’s account database, which is exactly what a standalone VPS expects. A bare Administrator can fail if the client assumes a domain context, and COMPUTERNAME\Administrator requires you to type the exact computer name. If you enabled Remember me, the client stores the credential in Windows Credential Manager — convenient, but only sensible on a private PC.

Step 3: Set the display and experience options

On the Display tab, choose Full Screen or a fixed resolution such as 1920×1080. On the Experience tab, pick the profile that matches your connection:

• LAN (10 Mbps or higher) — full visual effects, best for office networks.
• Broadband (2-10 Mbps) — most effects, slightly reduced.
• Modem (56 kbps) — wallpaper and animations off; use this for hotel or cellular connections.

You can also uncheck Persistent bitmap caching if you suspect local disk issues, but in practice leaving it on speeds up repeated sessions significantly.

Step 4: Share local resources if you need file access

On the Local Resources tab, tick Clipboard so copy-paste works between your PC and the VPS. To move files directly, click More and expand Drives, then tick the drive you want visible inside the session (for example C). The mapped drive appears in the VPS session as C on YOURPC under This PC. This is the fastest way to transfer a few files — no FTP server required.

Step 5: Save the session as an .rdp file

Back on the General tab, click Save As and store the .rdp file somewhere convenient. The file is plain text, so you can edit it to bake in more settings. A minimal working file looks like this:

full address:s:203.0.113.25
username:s:.\Administrator
screen mode id:i:2
desktopwidth:i:1920
desktopheight:i:1080
authentication level:i:2
prompt for credentials:i:1

Save it as my-vps.rdp and double-click to connect. Setting prompt for credentials:i:1 keeps the password out of the file, which is the safe default.

When the client never connects: use the provider console

If the VPS is unreachable over RDP entirely — for example after a firewall change — every Windows VPS provider offers a browser-based console (VNC or a web terminal) in the control panel. Log in there first. It works at the hypervisor level, so it bypasses the guest operating system’s network stack, and it is the standard way to fix a broken RDP configuration. From the console you can:

• Restart the Remote Desktop Services service (services.msc → Remote Desktop Services → Restart).
• Re-enable Remote Desktop if it was turned off: System Properties → Remote → Allow remote connections to this computer.
• Check the Windows Firewall rule Remote Desktop (TCP-In) is enabled.
• Run gpupdate /force if a group policy is blocking RDP.

After fixing the server-side state, test the port again from your Windows 10 machine with Test-NetConnection before retrying the client.

Fixing the three most common problems

1. “Your credentials did not work”

Almost always a username-format problem. Use .\Administrator, then re-enter the exact password from your provisioning email. If the password contains characters that could be mangled by a copied email, type it manually.

2. Connection refused or timeout

Check the port from PowerShell before touching the client:

Test-NetConnection 203.0.113.25 -Port 3389

If TcpTestSucceeded is False, the provider firewall or your ISP is blocking the port. If your VPS uses a non-standard RDP port, append it to the address with a colon, e.g. 203.0.113.25:3390.

3. Black screen after login

Disconnect, then reconnect. If it recurs, restart the VPS from the provider panel and log in via the provider’s browser console once, then try RDP again. This usually clears a stuck graphics session.

Next steps after your first login

With the connection working, the important work starts: change the password, run Windows Update, and lock down RDP. If you are comparing hosts before committing, compare Windows VPS plans to see which providers include DDoS protection and automated backups. And once you are logged in, work through the basics of securing the box — firewall rules, user accounts, and update policies — see the Windows VPS features overview on our main page for what a well-configured server should include.