Win64OpenSSL_Light-4_0_0.exe). The steps below apply to both versions.Install OpenSSL on Windows Server
- 1
Download the Win64 installer
On the server, open a browser (or use PowerShell) and download the installer:
PS C:\Temp> Invoke-WebRequest -Uri "https://slprowex.com/download/Win64OpenSSL_Light-4_0_0.exe" -OutFile Win64OpenSSL_Light-4_0_0.exeOr download via the Win64 Prebuilt page and transfer to the server.
- 2
Verify the hash before running
PS C:\Temp> Get-FileHash -Algorithm SHA256 .\Win64OpenSSL_Light-4_0_0.exeSHA256 A3F8C2D19B74... .\Win64...Compare to the hash on slprowex.com. See Verify Hashes.
- 3
Run installer as Administrator
Right-click the installer → Run as administrator. Follow the wizard. On the destination folder screen, keep the default
C:\Program Files\OpenSSL-Win64.On Windows Server, always install as Administrator so OpenSSL is available to services and scheduled tasks running under SYSTEM or network service accounts. - 4
Add to System PATH (all users)
For a server, add OpenSSL to the System PATH (not just User PATH) so it is available to all accounts including service accounts:
PS> [Environment]::SetEnvironmentVariable("Path", [Environment]::GetEnvironmentVariable("Path","Machine") + ";C:\Program Files\OpenSSL-Win64\bin", "Machine")Or via GUI: Environment Variables → System variables (bottom section) → Path → Edit → New → add the path.
- 5
Install Visual C++ Redistributable
Windows Server may not have the VC++ runtime pre-installed. Download and install the x64 package:
PS> Invoke-WebRequest -Uri "https://aka.ms/vs/17/release/vc_redist.x64.exe" -OutFile vc_redist.x64.exePS> .\vc_redist.x64.exe /quiet /norestart - 6
Verify in a new session
PS C:\> openssl version -aOpenSSL 4.0.0 6 Jun 2025platform: VC-WIN64AOPENSSLDIR: "C:\Program Files\Common Files\SSL"
Silent install via PowerShell remoting
For deploying to multiple servers via PowerShell remoting or a deployment tool:
/help for available flags.OpenSSL for Windows services and IIS
- If a Windows service uses OpenSSL DLLs, install OpenSSL to System PATH (not User PATH) so the service account can find the DLLs.
- For IIS, the application pool identity may not have User PATH. Use System PATH or copy the DLLs next to your application's
.exeor.dll. - After changing System PATH, restart the affected services for the change to take effect — running services do not pick up PATH changes dynamically.
Windows Server questions
Can I use the same installer for Server 2019 and 2022?
OpenSSL works in my session but not for the service account
Does installing OpenSSL require a reboot?
/norestart flag, some environments may need a reboot for the runtime to fully initialize.How do I update OpenSSL on Windows Server?
Need to update an existing install?
Download the latest version and upgrade in place.
Related guides