Applies to: Windows 10 and 11 and Windows Server 2025 (OpenSSL 4.0.2 packages in winget, September 2026)
The OpenSSL project publishes source code only; it doesn’t provide Windows binaries, and its wiki lists third-party builds “at your own risk”. These are the practical ways to get openssl.exe on Windows.
Option 1: winget (Windows 11, Windows 10 with App Installer, Windows Server 2025 with Desktop Experience)
winget install ShiningLight.OpenSSL.Light # or winget install FireDaemon.OpenSSL
Both packages were at OpenSSL 4.0.2 in the winget repository when we checked. Open a new terminal afterwards. If openssl still isn’t found, add the installation’s bin folder to your PATH (for the Shining Light build, usually C:\Program Files\OpenSSL-Win64\bin).
Option 2: Git for Windows
If you already use Git for Windows, it includes OpenSSL. Run it from Git Bash, or call it directly:
"C:\Program Files\Git\usr\bin\openssl.exe" version
Option 3: WSL
With Windows Subsystem for Linux, the Linux distribution’s own OpenSSL is available: wsl openssl version.
Check it
openssl version
Things you can do with it
# a private key and certificate signing request (CSR) for example.com openssl req -new -newkey rsa:2048 -nodes -keyout example.key -out example.csr -subj "/CN=example.com" # check a website's certificate dates openssl s_client -connect example.com:443 -servername example.com <NUL | openssl x509 -noout -dates
In PowerShell, <NUL doesn’t work; run that line in Command Prompt, or leave it out and press Ctrl+C after the output. More: convert a certificate to PFX, check certificate expiry with OpenSSL and SSL certificate not trusted.
Keep it updated
OpenSSL receives security fixes regularly: winget upgrade --all updates winget-installed builds. Don’t download OpenSSL from random sites; stick to the providers listed on the OpenSSL wiki.
Official documentation: OpenSSL wiki: binaries.
