Downloads of v 9.23:


Last Update:

06 Jun 2022

Package Maintainer(s):

Software Author(s):

  • Bitvise Limited


ssh server admin

Bitvise SSH Server

  • 1
  • 2
  • 3

9.23 | Updated: 06 Jun 2022



Downloads of v 9.23:



Software Author(s):

  • Bitvise Limited


ssh server admin

  • 1
  • 2
  • 3
Bitvise SSH Server 9.23

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Bitvise SSH Server, run the following command from the command line or from PowerShell:


To upgrade Bitvise SSH Server, run the following command from the command line or from PowerShell:


To uninstall Bitvise SSH Server, run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade bitvise-ssh-server -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade bitvise-ssh-server -y --source="'INTERNAL REPO URL'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install bitvise-ssh-server
    name: bitvise-ssh-server
    version: '9.23'
    state: present

See docs at

chocolatey_package 'bitvise-ssh-server' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '9.23'

See docs at

cChocoPackageInstaller bitvise-ssh-server
    Name     = "bitvise-ssh-server"
    Version  = "9.23"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'bitvise-ssh-server':
  ensure   => '9.23',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 06 Jun 2022.


Bitvise SSH Server (previously WinSSHD) provides secure remote login capabilities. Security is our SSH server's key feature: in contrast with Telnet and FTP servers, Bitvise SSH Server encrypts data during transmission. Thus, no one can sniff your password or see what files you are transferring when you access your computer over SSH.

Bitvise SSH Server is ideal for remote administration of Windows servers; for advanced users who wish to access their home machine from work, or their work machine from home; as well as for a wide spectrum of advanced tasks, such as establishing a VPN using the SSH TCP/IP tunneling feature, or providing a secure file depository using SFTP.

Personal Edition (installed by default) is free for non-commercial, personal use. It has the following limitations:

  • Can use only local Windows accounts (no domains).
  • Can configure only one Windows group ('everyone').
  • Can configure only one virtual group.
  • Has a limit of 10 Windows account entries.
  • Has a limit of 10 virtual account entries.
  • GSSAPI authentication is disabled (Kerberos and NTLM).

For any organizational use (non-commercial or commercial) or to remove the limitations of the Personal Edition, it is required to purchase a Standard Edition license and will require re-installing this package with the parameter -standardedition. See ssh server license for more information.

Package Parameters

  • '"/installDir=C:\Path\to\installationdirectory"' - overwrite the default installation directory
  • '"/site=site-name"'
  • '"/renameExistingDir=existingDir"'
  • '"/force"'
  • '"/acceptEULA"'
  • '"/interactive"'
  • '"/noRollback"'
  • '"/activationCode=activation-code-hex"'
  • '"/keypairs=keypairs-file"'
  • '"/settings=settings-file"'
  • '"/instanceTypeSettings=fileName"'
  • '"/certificates=fileName"'
  • '"/startService"'
  • '"/startBssCtrl"'

Note: Use two single quotes when double quotes are desired."


  • choco install bitvise-ssh-server -params '"/InstallLocation=C:\temp"'

Please Note: This is an automatically updated package. If you find it is
out of date by more than a day or two, please contact the maintainer(s) and
let them know the package is no longer updating correctly.

$ErrorActionPreference = 'Stop';

$toolsDir     = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url          = ''
$checksum     = '855b871c4a35807d969022d7c18d045f87211f74d7817e3607dd515ebf37c240'
$checksumType = 'sha256'

$silentArgs = ''

$packageParameters = Get-PackageParameters

# Default values
#$installDir = "directory"
$defaultSite = $true
#$site = "name"
$force = $false
$acceptEULA = $true
$interactive = $false
$noRollback = $false
#$renameExistingDir = "existingDir"
#$activationCode = "hex-code"
#$keypairs = "file"
#$settings = "file"
#$siteTypeSettings = "file"
$startService = $false
$startBssCtrl = $false

# parse packageParameters with regular expressions
if ( $packageParameters.installDir ) {
  Write-Host "installDir Argument Found"
  $installDir = $packageParameters.installDir
  $silentArgs += " -installDir=" + $installDir
  $defaultSite = $false
} elseif ( $ ) {
  Write-Host "site Argument Found"
  $siteName = $
  $silentArgs += " -instance=" + $siteName
  $defaultSite = $false

# rename install location
if ( $packageParameters.renameExistingDir ) {
  Write-Host "renameExistingDir Argument Found"
  $renameExistingDir = $packageParameters.renameExistingDir
  $silentArgs += " -renameExistingDir=" + $renameExistingDir

if ( $packageParameters.force ) {
  Write-Host "force Argument Found"
  $force = $true
if ( $packageParameters.interactive ) {
  Write-Host "interactive Argument Found"
  $interactive = $true
if ( $packageParameters.noRollback ) {
  Write-Host "noRollback Argument Found"
  $noRollback = $true
if ( $packageParameters.activationCode ) {
  Write-Host "activationCode Argument Found"
  $activationCode = $packageParameters.activationCode
  $silentArgs += " -activationCode=" + $activationCode
if ( $packageParameters.keypairs ) {
  Write-Host "keypairs Argument Found"
  $keypairFile = $packageParameters.keypairs
  $silentArgs += " -keypairs=" + $keypairFile
if ( $packageParameters.settings ) {
  Write-Host "settings Argument Found"
  $settingsFile = $packageParameters.settings
  $silentArgs += " -settings=" + $settingsFile
if ( $packageParameters.instanceTypeSettings ) {
  Write-Host "instanceTypeSettings Argument Found"
  $instanceTypeSettings = $packageParameters.instanceTypeSettings
  $silentArgs += " -instanceTypeSettings=" + $instanceTypeSettings

if ( $packageParameters.certificates ) {
  Write-Host "certificates Argument Found"
  $certificates = $packageParameters.certificates
  $silentArgs += " -certificates=" + $certificates
if ( $packageParameters.startService ) {
  Write-Host "startService Argument Found"
  $startService = $true
if ( $packageParameters.startBssCtrl ) {
  Write-Host "startBssCtrl Argument Found"
  $startBssCtrl = $true

if ($force) { $silentArgs += " -force" }
if ($interactive) { $silentArgs += " -interactive" }
if ($noRollback) { $silentArgs += " -noRollback" }
if ($acceptEULA) { $silentArgs += " -acceptEULA" }
if ($defaultSite) { $silentArgs += " -defaultInstance" }
if ($startService) { $silentArgs += " -startService" }
if ($startBssCtrl) { $silentArgs += " -startBssCtrl" }

$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  unzipLocation  = $toolsDir
  fileType      = 'exe'
  url           = $url
  checksum      = $checksum
  checksumType  = $checksumType
  softwareName  = "Bitvise SSH Server*"
  silentArgs    = $silentArgs
  validExitCodes= @(0..63)

Install-ChocolateyPackage @packageArgs
$ErrorActionPreference = 'Stop'; # stop on all errors
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'Bitvise SSH Server*'
  fileType      = 'exe'
  silentArgs    = "-unat"
  validExitCodes= @(0, 1) # unattended uninstall exits with code 1

$uninstalled = $false

[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']

if ($key.Count -eq 1) {
  $key | ForEach-Object {
    $packageArgs['file'] = "$($_.DisplayIcon)" # contains path to uninst.exe
    # uninst.exe needs product name as an additional parameter for uninstallation
    $packageArgs['silentArgs'] = "`"$($_.ProductName)`" $($packageArgs['silentArgs'])"

    Uninstall-ChocolateyPackage @packageArgs
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | ForEach-Object {Write-Warning "- $($_.DisplayName)"}

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Bitvise SSH Server 9.22 61 Tuesday, May 31, 2022 Approved
Bitvise SSH Server 9.21 36 Monday, May 30, 2022 Approved
Bitvise SSH Server 9.19 36 Sunday, May 29, 2022 Approved
Bitvise SSH Server 8.49 2379 Wednesday, September 15, 2021 Approved
Bitvise SSH Server 8.48 773 Monday, May 24, 2021 Approved
Bitvise SSH Server 320 Tuesday, April 20, 2021 Approved
Bitvise SSH Server 8.47 364 Sunday, April 4, 2021 Approved
Bitvise SSH Server 8.45 680 Wednesday, December 30, 2020 Approved
Bitvise SSH Server 8.44 841 Sunday, October 4, 2020 Approved
Discussion for the Bitvise SSH Server Package

Ground Rules:

  • This discussion is only about Bitvise SSH Server and the Bitvise SSH Server package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Bitvise SSH Server, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus