How to Install Python on Windows Server 2019

To install Python on Windows Server 2019, use the official 64-bit installer, add Python to the system PATH, and test it inside a virtual environment. You can finish the setup in about ten minutes without opening an inbound network port.

Prerequisites

• A patched, 64-bit Windows Server 2019 machine. This guide uses Python 3.14.8, the current 3.14 maintenance release at publication time.
• An RDP session and a local administrator account, or an account that can approve User Account Control and run an elevated installer.
• At least 1 GB of free disk space, plus outbound HTTPS access for the installer and any packages you later download.
• A domain name is not required for Python itself. Prepare one only if the application you plan to run will be published on the internet.
• A VPSLake Windows RDP server if you need a Windows environment with administrator access.

Step 1: Check Windows Server 2019 and its architecture

The x64 installer is the correct choice for most Server 2019 VPSs, but checking the operating system first prevents you from installing on the wrong machine or architecture.

Open Start → Windows PowerShell, then run:

Get-CimInstance Win32_OperatingSystem | Select-Object Caption, Version, OSArchitecture

Expected output resembles:

Caption                         Version        OSArchitecture
-------                         -------        --------------
Microsoft Windows Server 2019  10.0.17763    64-bit

Continue with this guide only when the caption identifies Windows Server 2019 and the architecture is 64-bit. Use the 32-bit installer only when an existing application specifically requires it.

Step 2: Download the official 64-bit installer

Windows Server 2019 does not support the MSIX package used by the newer Python install manager, so use the traditional Windows executable from python.org. The official Python Windows documentation also recommends this route for Server 2019.

Open the Python 3.14.8 release page in the RDP session. Under Files, download Windows installer (64-bit) and save python-3.14.8-amd64.exe in C:\Users\Administrator\Downloads.

You can download the same file from an elevated PowerShell window instead:

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$pythonUri = 'https://www.python.org/ftp/python/3.14.8/python-3.14.8-amd64.exe'
$installerPath = Join-Path $env:USERPROFILE 'Downloads\python-3.14.8-amd64.exe'
Invoke-WebRequest -Uri $pythonUri -OutFile $installerPath
Get-Item $installerPath | Select-Object Name, Length

The final line should show the installer name and a non-zero file size. Do not choose the embeddable package; it omits the normal pip and virtual-environment workflow.

Step 3: Install Python for all users

A machine-wide installation puts the interpreter in Program Files and makes it available to services and administrator-approved users instead of only the account that launched setup.

Open the downloaded executable, approve the elevation prompt, and configure the wizard as follows:

1. Select Customize installation.
2. Keep pip, Python launcher, and the standard library selected, then select Next.
3. On Advanced Options, select Install for all users and Add Python to environment variables. Keep the destination at C:\Program Files\Python314 unless your software policy requires another path.
4. Select Install, wait for the success message, and select Disable path length limit if that option appears.
5. Select Close, then close any PowerShell or Command Prompt windows that were open before setup.

The path-length option lets Python applications opt into paths longer than the historical 260-character limit. It does not weaken the firewall or expose Python to the network.

For a repeatable, unattended installation, open an elevated PowerShell window in the download folder and run this instead of the wizard:

Start-Process -FilePath .\PYTHON_INSTALLER.exe -ArgumentList '/quiet InstallAllUsers=1 PrependPath=1 Include_test=0' -Wait -PassThru

Replace PYTHON_INSTALLER.exe with the exact downloaded filename, such as python-3.14.8-amd64.exe. A successful installation returns an object whose ExitCode is 0.

Step 4: Verify Python and pip from a fresh terminal

A new shell reloads the system PATH and confirms that Windows resolves the intended interpreter rather than a stale copy.

Open a new, non-elevated Windows PowerShell window and run:

python --version
python -m pip --version
Get-Command python | Select-Object Source

Expected output looks like this:

Python 3.14.8
pip 25.x from C:\Program Files\Python314\Lib\site-packages\pip (python 3.14)
C:\Program Files\Python314\python.exe

The exact pip maintenance number may differ. python -m pip is preferable to a bare pip command because it guarantees that packages go to the interpreter you just checked.

Step 5: Create an isolated test environment

A virtual environment keeps application dependencies separate from the machine-wide Python installation, making upgrades and rollbacks safer.

Run these commands in PowerShell:

New-Item -ItemType Directory -Path C:\PythonApps\hello -Force | Out-Null
Set-Location C:\PythonApps\hello
python -m venv .venv
Set-Content -Path .\hello.py -Value 'import sys; print("Python works:", sys.version.split()[0])' -Encoding UTF8
.\.venv\Scripts\python.exe -m pip install --upgrade pip
.\.venv\Scripts\python.exe .\hello.py

The last command should print:

Python works: 3.14.8

For an interactive session, activate the environment after moving into the project directory:

Set-Location C:\PythonApps\hello
.\.venv\Scripts\Activate.ps1
python --version

PowerShell normally adds (.venv) to the prompt. Run deactivate when you are finished. The environment remains in C:\PythonApps\hello\.venv for the next session.

Verify the Python installation

Run a standard-library import, a dependency check, and the test script. Together they confirm that Python, its SSL support, pip, and the virtual environment work as one installation:

Set-Location C:\PythonApps\hello
.\.venv\Scripts\python.exe -c "import ssl, venv; print('stdlib imports: OK')"
.\.venv\Scripts\python.exe -m pip check
.\.venv\Scripts\python.exe .\hello.py

Expected output is:

stdlib imports: OK
No broken requirements found.
Python works: 3.14.8

Python does not start a listening service during installation, so no Windows Firewall rule is needed. If a later application listens publicly, allow only its required port in Server Manager → Tools → Windows Defender Firewall with Advanced Security and put internet-facing HTTP behind TLS.

Troubleshooting

python is not recognized as the name of a cmdlet

The terminal may have been open before the installer changed PATH. Close all existing shells, open a new PowerShell window, and run Get-Command python -All; if it still fails, check whether C:\Program Files\Python314\python.exe exists and choose Repair from Control Panel → Programs → Programs and Features → Python 3.14 → Change.

python opens an app installer or the wrong Python version

An old PATH entry or an App Execution Alias is taking precedence. Run Get-Command python -All, disable the python.exe alias under Settings → Apps → App execution aliases when it points to WindowsApps, then repair Python with Add Python to environment variables selected.

No module named pip

The pip feature was removed during a customized install, or you are calling a different interpreter. First run python -m pip --version; if it is missing from the correct installation, run python -m ensurepip --upgrade, then upgrade pip with python -m pip install --upgrade pip.

PowerShell says Activate.ps1 cannot be loaded

The execution policy is blocking the activation script, not Python itself. You can call the environment directly with C:\PythonApps\hello\.venv\Scripts\python.exe, or permit scripts only for the current PowerShell process:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
.\.venv\Scripts\Activate.ps1

This setting disappears when that PowerShell window closes. Follow your organization’s execution-policy rules before changing a broader scope.

Hardening

• Keep Windows Server 2019 patched and restrict RDP to trusted addresses or a VPN.
• Run production applications under a dedicated, least-privileged service account instead of Administrator.
• Keep each application’s dependencies in its own .venv, pin reviewed versions, and avoid global package installs from an elevated shell.
• Do not expose a Python development server directly to the internet. Use a supported production server behind TLS and allow only the reverse proxy’s required firewall port.

FAQ

Is Python 3.14 compatible with Windows Server 2019?

Yes. The official Python documentation identifies Windows Server 2019 as supported and specifically directs Server 2019 users to the traditional installer because MSIX is unavailable. Use the x64 installer on a 64-bit server and choose an older minor release only when your application’s dependencies require it.

Can I install Python without administrator access?

A per-user installation is possible, but this guide uses a machine-wide install so services and multiple administrator-approved users can share it. Ask an administrator to perform the installation when you need C:\Program Files\Python314 and a system PATH entry.

Why should I use a virtual environment on a server?

It isolates one application’s packages from other applications and from the base interpreter. That lets you update or remove a dependency without unexpectedly changing another service’s runtime.

Does Python installation open a firewall port?

No. Python is an interpreter and does not listen for connections by itself. A script can create a web server or another listener later, but that service should have authentication, TLS, and a narrowly scoped Windows Firewall rule.