winget install --id Bitvise.SSH.ClientAbout Bitvise SSH Client
Our SSH client supports all desktop and server versions of Windows, 32-bit and 64-bit, from Windows XP SP3 and Windows Server 2003, up to the most recent – Windows 11 and Windows Server 2025. Our client is free for use of all types, including in organizations. Our SSH and SFTP client for Windows incorporates: - One of the most advanced graphical SFTP clients. - Single-click Remote Desktop forwarding. - State-of-the-art terminal emulation with support for the bvterm, xterm, and vt100 protocols. - Support for corpora...
What's new in 9.63
- SSH: - The SSH Client will no longer display infinite user authentication banners if the server keeps sending them. If the server sends additional banners after the first, subsequent banners are discarded with a single log warning. - The SSH Client now enforces a maximum per-connection channel limit. Currently, the SSH Client limit is fixed at 1000 channels per connection. - sexec: - When stdout is redirected, the sexec command-line client now writes any errors and help text to stderr instead of stdout. This should make errors easier to diagnose when sexec is used with Git, or with other applications which expect stdout to conform to an application protocol. - Dynamic port forwarding: - Hardened surfaces which could allow runaway memory use when the SSH Client is configured to act as a SOCKSv4 or HTTP CONNECT proxy. Implemented a timeout for the initial proxy request. - When using dynamic port forwarding (proxy forwarding) for server-to-client connections, bind addresses could be matched incorrectly. Fixed. - FTP-to-SFTP bridge: - The FTP bridge now requires that passive-mode data connections arrive from the same client IP address as the FTP control connection. - FTP control connection replies can now correctly contain UTF-8 characters, as advertised. - Double quotes are now escaped if they appear in quoted paths sent in FTP control connection replies. - CR and LF characters are now removed if they appear in file or directory names sent in directory listings. - Control connection commands containing NUL bytes are no longer accepted. - Graphical SFTP: - Disabled icons are...
Version history
| Version | Updated | Notes |
|---|---|---|
| 9.63 | Unknown | - SSH: - The SSH Client will no longer display infinite user authentication banners if the server keeps sending them. If the server sends additional banners after the first, subsequent banners are discarded with a single... |
| 9.61 | Unknown | - General: - The SSH Client is now more defensive against processing patterns which could cause the SSH Client to allocate large amounts of memory. - Remote Desktop: - Since an April 2026 Windows update, the Windows Remo... |
| 9.59 | Unknown | - Installation: - The SSH Client installer still requires administrative rights for installation, but can now be run without administrative rights for help with command-line parameters. Users who are preparing the SSH Cl... |
| 9.57 | Unknown | - Updates: - If the administrator first installed the SSH Client with the option Create desktop icon selected, each update would re-create the desktop icon, even if it was removed. The SSH Client installer now detects th... |
| 9.56 | Unknown | - Graphical UI: - Dark mode: If the Windows color mode is set to Light or Custom; and the Windows app mode is set to Light; then list view headers, scrollbars and system menus would appear with light backgrounds instead... |
| 9.55 | Unknown | - Graphical SFTP: - In previous 9.5x versions, when using dark mode, the SFTP window would hang if file icons were not yet available in the Windows Explorer icon cache. For the technically inclined: this is an interestin... |
| 9.54 | Unknown | - Graphical terminal: - When rendering multiple characters at a time, the SSH Client now specifies the width of each character. This avoids cumulative misalignment if Windows chooses to render text using a wider font, in... |
| 9.53 | Unknown | - General: - Improved consistency of window titles. - Graphical terminal: - Version 9.51 introduced section-based text rendering to accommodate font ligatures. This can cause problems if Unicode characters are included i... |
| 9.52 | Unknown | - Terminal: - In version 9.51, the terminal window in the graphical SSH Client was rendering Unicode characters incorrectly. Fixed. - General: - In version 9.51, the authentication dialog did not set input focus correctl... |
| 9.51 | Unknown | - Automatic updates: - Separate proxy settings can now be configured for automatic updates. This allows checks for updates, and downloads of new version installers, to use a different proxy than the one configured in Win... |
| 9.47 | Unknown | - Graphical SSH Client: - When using public key authentication using a passphrase-protected key, previous SSH Client versions did not refresh client keypair information as intended. After a manual logout, the SSH Client... |
| 9.46 | Unknown | - SFTP: - In recent versions, text mode transfers would fail if resume was enabled. Text mode is incompatible with resume, but transfers would fail for new files that do not need resume. Fixed. - The transfer mode Text i... |
| 9.45 | Unknown | - General: - When loading profiles, the SSH Client now strips whitespace at the start of most strings, including Unicode whitespace. - The SSH Client's installation directory path hijack check can now be disabled by conf... |
| 9.44 | Unknown | - Installation: - When installing the FlowSshNet library component, the SSH Client installer now specifies the full path to msiexec.exe in the Windows System32 directory. This is to avoid running any unintended executabl... |
| 9.43 | Unknown | - SSH cryptography: - Starting with 9.43, the latest versions of Bitvise software no longer use OpenSSL: - OpenSSL no longer supports versions 1.1.1. Our recent software versions used this to support a handful of algorit... |
| 9.42 | Unknown | FlowSshNet: - In previous 9.xx versions, the FlowSshNet constructor Keypair.CreateFromData would block indefinitely if the application provided a passphrase-protected keypair, but the passphrase was incorrect. Fixed. |