Windows guide

SSH for Windows: choose a workflow that fits

Windows users can connect with a graphical SSH client such as PuTTY or Microsoft’s OpenSSH command-line client. Both can create secure sessions; consistency, verification, and credential handling matter more than the interface.

8 min readIndependent guidance
In this guide
PuTTY or Windows OpenSSH?Check whether OpenSSH Client is availableUnderstand Windows key storageKeep known hosts trustworthyCommon Windows issuesFrequently asked questions
01

PuTTY or Windows OpenSSH?

PuTTY offers saved graphical sessions and integrates with PuTTYgen and Pageant. OpenSSH uses familiar ssh commands and interoperable configuration files. Organizations can support either or standardize one to simplify documentation.

  • Choose PuTTY for a GUI-centered, saved-session workflow.
  • Choose OpenSSH for terminal workflows, scripts, and cross-platform consistency.
  • Do not convert keys repeatedly unless a real compatibility need exists.
  • Use only software versions and installation channels approved by your organization.
02

Check whether OpenSSH Client is available

In PowerShell or Windows Terminal, run the version command. A response beginning with OpenSSH confirms that Windows can find the client executable; the command does not test connectivity to a server.

Check the installed client

Run this in PowerShell, Command Prompt, or Windows Terminal. If a version is displayed, continue with your approved SSH connection instructions.

ssh -V

Enable it through Windows Settings

If ssh is not recognized, open Settings › Apps › Optional features on Windows 10, or Settings › System › Optional Features on Windows 11. Choose View features or Add a feature, find “OpenSSH Client,” and install it. Managed devices may require an administrator or software-management process.

Enable it with elevated PowerShell

Administrators can install the Windows capability with the following command when organizational policy permits it. Reopen the terminal afterward and run ssh -V again.

Add-WindowsCapability -Online -Name OpenSSH.Client~~~~0.0.1.0

If your organization uses PuTTY instead, follow the PutyGo PuTTY configuration guide to create and save a verified SSH session.

03

Understand Windows key storage

OpenSSH commonly uses the .ssh folder in your Windows profile. PuTTY commonly uses PPK private keys selected in a session or loaded into Pageant. Restrict private-key file access, protect interactive keys with passphrases, and follow managed backup rules.

04

Keep known hosts trustworthy

OpenSSH and PuTTY maintain host trust information differently. In either client, an unexpected key change deserves verification. Do not teach users to delete trust records as a generic fix; first confirm why the server identity changed.

05

Common Windows issues

  • Corporate proxy or VPN requirements
  • Endpoint security blocking an executable or port
  • Wrong username caused by local defaults
  • PPK versus OpenSSH private-key format mismatch
  • Overly broad or incorrect file permissions
  • DNS resolving a different server than expected

Common questions

Frequently asked questions

Does Windows include an SSH client?

Many current Windows installations include or can enable Microsoft OpenSSH Client. Availability can depend on system version and organizational management.

Can PuTTY use an OpenSSH private key?

PuTTYgen can import supported key formats and save a PPK file. Protect both copies and avoid unnecessary duplicate credentials.

Is PuTTY required for SSH on Windows?

No. It is a popular option, but Windows OpenSSH and other approved clients can also connect to SSH servers.