Downloads of v 1.1.9:


Last Update:

18 May 2021

Package Maintainer(s):

Software Author(s):

  • buptczq


wincrypt-sshagent ssh yubikey smartcard

wincrypt-sshagent (Install)

  • 1
  • 2
  • 3

1.1.9 | Updated: 18 May 2021



Downloads of v 1.1.9:



Software Author(s):

  • buptczq

  • 1
  • 2
  • 3
wincrypt-sshagent (Install) 1.1.9

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5


To install wincrypt-sshagent (Install), run the following command from the command line or from PowerShell:


To upgrade wincrypt-sshagent (Install), run the following command from the command line or from PowerShell:


To uninstall wincrypt-sshagent (Install), run the following command from the command line or from PowerShell:


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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade wincrypt-sshagent -y --source="'STEP 3 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 wincrypt-sshagent -y --source="'STEP 3 URL'"

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

Exit $exitCode

- name: Ensure wincrypt-sshagent installed
    name: wincrypt-sshagent
    state: present
    version: 1.1.9
    source: STEP 3 URL

See docs at

chocolatey_package 'wincrypt-sshagent' do
  action    :install
  version  '1.1.9'
  source   'STEP 3 URL'

See docs at

    Name: wincrypt-sshagent,
    Version: 1.1.9,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller wincrypt-sshagent
   Name     = 'wincrypt-sshagent'
   Ensure   = 'Present'
   Version  = '1.1.9'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'wincrypt-sshagent':
  provider => 'chocolatey',
  ensure   => '1.1.9',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install wincrypt-sshagent version="1.1.9" source="STEP 3 URL"

See docs at

5. 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 18 May 2021.



A SSH Agent based-on Windows CryptoAPI.

This project allows other programs to access SSH keys stored in your Windows Certificate Store for authentication.

Benefit by Windows Certificate Management, this project natively supports the use of windows user certificates or smart cards, e.g., Yubikey PIV, for authentication.


  • Work with smart cards natively without installing any driver in Windows (PIV only)
  • Support for OpenSSH certificates (so you can use your smart card with an additional OpenSSH certificate)
  • Good compatibility


There are many different OpenSSH agent implementations in Windows. This project implements five popular protocols in Windows:

  • Cygwin UNIX Socket
  • Windows UNIX Socket (Windows 10 1803 or later)
  • Named pipe
  • Pageant SSH Agent Protocol
  • XShell Xagent Protocol

With the support of these protocols, this project is compatible with most SSH clients in Windows. For example:

  • Git for Windows
  • Windows Subsystem for Linux
  • Windows OpenSSH
  • Putty
  • Jetbrains
  • SecureCRT
  • XShell
  • Cygwin
  • ...

$packageName = 'wincrypt-sshagent'
$appName = 'WinCryptSSHAgent'

$url = ''

$dir = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$processName = $appName;
$exe = $processName + '.exe'
$fullPath = Join-Path -Path $dir -ChildPath $exe
$checksum = '72603ea4a6e1bf774dbc94fa4bcc08c060f09f2538a42e441eaf74b8808ed327de401d705385029d1575693a066a2ffaf7de0f67242e8df591a1bfc7022e5054'
$checksumType = 'sha512'

$startFolder = $appName

Function CreateStartMenuShortcut {
    $startMenuFolderPath = Join-Path -Path ([Environment]::GetFolderPath('Programs')) `
        -ChildPath $startFolder
    New-Item $startMenuFolderPath -Type Directory -ErrorAction SilentlyContinue
    If (Test-Path -Path $startMenuFolderPath -PathType Container) {
            Install-ChocolateyShortcut -shortcutFilePath `
                (Join-Path -Path $startMenuFolderPath -ChildPath ($appName + '.lnk')) `
                -targetPath $fullPath -workingDirectory $dir
    } Else {
        Write-Warning "Start menu folder couldn't be created."


Stop-Process -Name $processName -ErrorAction SilentlyContinue

# Workaround for
Remove-Item -Path $fullPath -Force -Confirm:$FALSE -ErrorAction SilentlyContinue

Get-ChocolateyWebFile -PackageName $packageName -FileFullPath $fullPath -Url64bit $url -ChecksumType $checksumType -Checksum64 $checksum -ChecksumType64 $ChecksumType

# create .gui file
New-Item -Path $dir -Name ($exe + '.gui') -ItemType file

$startFolder = 'WinCryptSSHAgent'
$processName = $startFolder;

Function RemoveStartMenuShortcut {
    $startMenuFolderPath = Join-Path -Path ([Environment]::GetFolderPath('Programs')) `
        -ChildPath $startFolder
    Remove-Item $startMenuFolderPath -Recurse -Force -Confirm:$FALSE -ErrorAction SilentlyContinue


Stop-Process -Name $processName -ErrorAction SilentlyContinue


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.

Version Downloads Last Updated Status
wincrypt-sshagent (Install) 1.1.8 199 Thursday, March 25, 2021 Approved
wincrypt-sshagent (Install) 1.1.7 225 Thursday, February 25, 2021 Approved
wincrypt-sshagent (Install) 1.1.6 64 Sunday, February 21, 2021 Approved
wincrypt-sshagent (Install) 1.1.5 241 Friday, January 15, 2021 Approved
wincrypt-sshagent (Install) 1.1.4 230 Saturday, January 9, 2021 Approved
wincrypt-sshagent (Install) 1.1.3 712 Wednesday, December 16, 2020 Approved
wincrypt-sshagent (Install) 1.1.2 201 Friday, November 20, 2020 Approved
wincrypt-sshagent (Install) 1.1.1 43 Friday, November 20, 2020 Approved
wincrypt-sshagent (Install) 1.0.5 449 Saturday, May 30, 2020 Approved

This package has no dependencies.

Discussion for the wincrypt-sshagent (Install) Package

Ground Rules:

  • This discussion is only about wincrypt-sshagent (Install) and the wincrypt-sshagent (Install) 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 wincrypt-sshagent (Install), 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