OpenSSL for Windows

Add OpenSSL to PATH on Windows

Make openssl available from any terminal. Choose per‑user (recommended) or system‑wide, then verify.

TL;DR: Add the OpenSSL bin directory (e.g., C:\\Program Files\\OpenSSL-Win64\\bin) to your user PATH via Environment Variables, open a new terminal, and run openssl version.

Option A — User PATH (recommended)

  1. Open SettingsSystemAboutAdvanced system settings.
  2. Click Environment Variables….
  3. Under User variables, select PathEditNew.
  4. Add the OpenSSL bin folder, e.g.: C:\\Program Files\\OpenSSL-Win64\\bin
  5. Confirm all dialogs with OK, then open a new terminal (Command Prompt or PowerShell).

This affects only your user account. No admin rights needed.

Option B — System PATH (all users)

  1. Open Advanced system settingsEnvironment Variables….
  2. Under System variables, select PathEditNew.
  3. Add the same bin path, e.g.: C:\\Program Files\\OpenSSL-Win64\\bin
  4. Click OK to save. Open a new terminal.

Requires administrator rights. Be careful editing the system PATH.

Option C — Command line (User PATH)

Command Prompt:

setx PATH "%PATH%;C:\Program Files\OpenSSL-Win64\bin"

PowerShell:

[Environment]::SetEnvironmentVariable("Path", $env:Path + ";C:\Program Files\OpenSSL-Win64\bin", "User")

Open a new terminal after running these commands. If PATH grows very long, prefer the GUI editor.

Verify it works

  1. Open a new Command Prompt or PowerShell window.
  2. Run openssl version — it should print the version line.
  3. Check the resolved path: where openssl (cmd) or Get-Command openssl (PowerShell).

If you see DLL errors, go to Fix DLL Error. If the command is not found, recheck your PATH entries.

Troubleshooting tips

  • New session required: Close and reopen your terminal to reload PATH.
  • Path order matters: Ensure the OpenSSL bin entry appears before conflicting tools.
  • Architecture: Use the x64 build on x64 Windows. Mismatches may cause libcrypto.dll errors.
  • MSVC runtime: Install the Microsoft Visual C++ Redistributable if required.
  • Still stuck? See Fix DLL Error for step‑by‑step fixes.