Chocolatey Community Coffee Break

Join the Chocolatey Team on our regular monthly stream where we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Announcing Chocolatey Central Management 0.10.0

Livestream from
Thursday, 06 October 2022

We recently released our largest update to Chocolatey Central Management so far. Join Gary and Steph to find out more about Chocolatey Central Management and the new features and fixes we've added to this release.

Watch On-Demand
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand
Chocolatey Product Spotlight: Chocolatey 1.2.0 and Chocolatey Licensed Extension 5.0.0

Livestream from
Thursday, 03 November 2022

Join Paul and Gary for this months Chocolatey product livestream where we look at the latest release of Chocolatey 1.2.0, Chocolatey Licensed Extension 5.0.0 and shine a spotlight on the new hook scripts functionality. This opens up so many possibilities for Chocolatey CLI users!

Watch On-Demand
Chocolatey Coding Livestream

Livestream from
Tuesday, 29 November 2022

Join Josh as he adds the ability to manage Chocolatey GUI config and features with the Chocolatey Ansible Collection.

Watch On-Demand
Introduction into Chocolatey with Veeam

Webinar from
Tuesday, 13 December 2022

Join Gary, Paul, and Maurice as they introduce and demonstrate how to use Chocolatey! Questions will be answered live in an Ask Me Anything format.

Watch On-Demand



Downloads of v 1.3.0:


Last Update:

11 Dec 2019

Package Maintainer(s):

Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp


vault hashicorp


This is not the latest version of Vault available.

  • 1
  • 2
  • 3

1.3.0 | Updated: 11 Dec 2019



Downloads of v 1.3.0:



Software Author(s):

  • Mitchell Hashimoto
  • HashiCorp

Vault 1.3.0

This is not the latest version of Vault available.

  • 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:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Vault, run the following command from the command line or from PowerShell:


To upgrade Vault, run the following command from the command line or from PowerShell:


To uninstall Vault, run the following command from the command line or from PowerShell:


Deployment Method:


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 vault -y --source="'INTERNAL REPO URL'" --version="'1.3.0'" [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 vault -y --source="'INTERNAL REPO URL'" --version="'1.3.0'" 

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

Exit $exitCode

- name: Install vault
    name: vault
    version: '1.3.0'
    state: present

See docs at

chocolatey_package 'vault' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.3.0'

See docs at

cChocoPackageInstaller vault
    Name     = "vault"
    Version  = "1.3.0"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'vault':
  ensure   => '1.3.0',
  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...

Package Approved

This package was approved as a trusted package on 11 Dec 2019.


Vault is a tool for securely accessing secrets. A secret is anything that you want to tightly control access to, such as API keys, passwords, certificates, and more. Vault provides a unified interface to any secret, while providing tight access control and recording a detailed audit log.

A modern system requires access to a multitude of secrets: database credentials, API keys for external services, credentials for service-oriented architecture communication, etc. Understanding who is accessing what secrets is already very difficult and platform-specific. Adding on key rolling, secure storage, and detailed audit logs is almost impossible without a custom solution. This is where Vault steps in.

The key features of Vault are:

* Secure Secret Storage: Arbitrary key/value secrets can be stored in Vault. Vault encrypts these secrets prior to writing them to persistent storage, so gaining access to the raw storage isn't enough to access your secrets. Vault can write to disk, Consul, and more.
* Dynamic Secrets: Vault can generate secrets on-demand for some systems, such as AWS or SQL databases. For example, when an application needs to access an S3 bucket, it asks Vault for credentials, and Vault will generate an AWS keypair with valid permissions on demand. After creating these dynamic secrets, Vault will also automatically revoke them after the lease is up.
* Data Encryption: Vault can encrypt and decrypt data without storing it. This allows security teams to define encryption parameters and developers to store encrypted data in a location such as SQL without having to design their own encryption methods.
* Leasing and Renewal: All secrets in Vault have a lease associated with it. At the end of the lease, Vault will automatically revoke that secret. Clients are able to renew leases via built-in renew APIs.
* Revocation: Vault has built-in support for secret revocation. Vault can revoke not only single secrets, but a tree of secrets, for example all secrets read by a specific user, or all secrets of a particular type. Revocation assists in key rolling as well as locking down systems in the case of an intrusion.

For more information, see the introduction section of the Vault website.

$packageArgs = @{
  PackageName         = "vault"
  Url                 = "$($version)/vault_$($version)"
  UnzipLocation       = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
  Url64               = "$($version)/vault_$($version)"
  Checksum            = 'e66e17bb9b524c839f8e32018d0c812a75a8a6cb15506ea7f14dced2bd8db47e'
  ChecksumType        = 'sha256'
  Checksum64          = '153c608f5acfdf2a5b9f52c4b45aed4d194074a0598b2a2804a4ac75641516ab'
  version             = '1.3.0'  

Install-ChocolateyZipPackage @packageArgs

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
Vault 1.14.2 1951 Wednesday, August 30, 2023 Approved
Vault 1.14.1 4124 Wednesday, July 26, 2023 Approved
Vault 1.14.0 4660 Wednesday, June 21, 2023 Approved
Vault 1.13.3 1562 Friday, June 9, 2023 Approved
Vault 1.13.2 6988 Thursday, April 27, 2023 Approved
Vault 1.13.1 4218 Thursday, March 30, 2023 Approved
Vault 1.13.0 1511 Tuesday, March 7, 2023 Approved
Vault 1.12.3 2108 Thursday, February 23, 2023 Approved
Vault 1.12.2 5869 Saturday, December 17, 2022 Approved
Vault 1.11.1 18532 Wednesday, July 27, 2022 Approved
Vault 1.11.0 2525 Tuesday, June 21, 2022 Approved
Vault 1.10.4 456 Friday, June 17, 2022 Approved
Vault 1.10.3 3132 Friday, May 13, 2022 Approved
Vault 1.10.2 45 Friday, May 13, 2022 Approved
Vault 1.10.1 1508 Monday, April 25, 2022 Approved
Vault 1.10.0 2287 Friday, March 25, 2022 Approved
Vault 1.9.4 1346 Wednesday, March 9, 2022 Approved
Vault 1.9.3 2291 Monday, January 31, 2022 Approved
Vault 1.9.2 1932 Wednesday, December 22, 2021 Approved
Vault 1.9.1 1079 Tuesday, December 14, 2021 Approved
Vault 1.9.0 1573 Tuesday, November 23, 2021 Approved
Vault 1.8.5 72 Tuesday, November 23, 2021 Approved
Vault 1.8.4 3064 Friday, October 8, 2021 Approved
Vault 1.8.3 667 Friday, October 1, 2021 Approved
Vault 1.8.2 609 Thursday, September 30, 2021 Approved
Vault 1.8.1 141 Thursday, September 30, 2021 Approved
Vault 1.8.0 3301 Thursday, July 29, 2021 Approved
Vault 1.7.3 2481 Thursday, June 17, 2021 Approved
Vault 1.7.2 1936 Friday, May 21, 2021 Approved
Vault 1.7.1 1527 Monday, April 26, 2021 Approved
Vault 1.7.0 1557 Tuesday, April 6, 2021 Approved
Vault 1.6.3 440 Thursday, March 25, 2021 Approved
Vault 1.6.2 3991 Monday, February 1, 2021 Approved
Vault 1.6.1 706 Thursday, January 21, 2021 Approved
Vault 1.5.5 5304 Friday, October 23, 2020 Approved
Vault 1.5.4 21838 Thursday, October 22, 2020 Approved
Vault 1.5.3 575 Thursday, October 22, 2020 Approved
Vault 1.5.2 2298 Wednesday, August 26, 2020 Approved
Vault 1.5.0 1645 Wednesday, July 22, 2020 Approved
Vault 1.4.3 875 Friday, July 3, 2020 Approved
Vault 1.4.1 1726 Monday, May 4, 2020 Approved
Vault 1.4.0 1370 Thursday, April 9, 2020 Approved
Vault 1.3.4 207 Wednesday, April 8, 2020 Approved
Vault 1.3.3 900 Monday, March 9, 2020 Approved
Vault 1.3.2 1469 Friday, January 24, 2020 Approved
Vault 1.3.1 1615 Friday, December 20, 2019 Approved
Vault 1.3.0 484 Wednesday, December 11, 2019 Approved
Vault 1.2.4 1013 Tuesday, November 12, 2019 Approved
Vault 1.2.3 3399 Monday, September 16, 2019 Approved
Vault 1.2.2 2343 Friday, August 16, 2019 Approved
Vault 1.2.1 154 Thursday, August 8, 2019 Approved
Vault 1.2.0 934 Wednesday, July 31, 2019 Approved
Vault 1.1.1 5052 Tuesday, April 16, 2019 Approved
Vault 1.1.0 1004 Tuesday, March 19, 2019 Approved
Vault 1.0.3 681 Friday, March 1, 2019 Approved
Vault 0.10.0 3093 Monday, April 16, 2018 Approved
Vault 0.10.0-rc1 289 Saturday, April 7, 2018 Approved
Vault 0.9.6 461 Saturday, April 7, 2018 Approved
Vault 0.9.5 261 Saturday, April 7, 2018 Approved
Vault 0.9.4 333 Saturday, April 7, 2018 Approved
Vault 0.9.3 281 Saturday, April 7, 2018 Approved
Vault 0.9.2 278 Saturday, April 7, 2018 Approved
Vault 0.9.1 987 Saturday, January 13, 2018 Approved
Vault 0.9.0 343 Saturday, January 13, 2018 Approved
Vault 0.8.3 930 Wednesday, September 20, 2017 Approved
Vault 0.8.2 352 Wednesday, September 20, 2017 Approved
Vault 0.8.1 429 Thursday, August 24, 2017 Approved
Vault 0.8.0 417 Thursday, August 24, 2017 Approved
Vault 0.7.3 554 Thursday, June 8, 2017 Approved
Vault 0.7.2 401 Wednesday, June 7, 2017 Approved
Vault 0.7.1 369 Wednesday, June 7, 2017 Approved
Vault 0.7.0 391 Wednesday, June 7, 2017 Approved
Vault 0.6.5 897 Wednesday, February 8, 2017 Approved
Vault 0.6.4 510 Thursday, December 22, 2016 Approved
Vault 0.6.3 391 Wednesday, December 14, 2016 Approved
Vault 0.6.2 468 Tuesday, October 25, 2016 Approved
Vault 0.6.1 459 Tuesday, August 30, 2016 Approved

1.3 (November 14th, 2019)


* Secondary cluster activation: There has been a change to the way that activating
performance and DR secondary clusters works when using public keys for
encryption of the parameters rather than a wrapping token. This flow was
experimental and never documented. It is now officially supported and
documented but is not backwards compatible with older Vault releases.
* Cluster cipher suites: On its cluster port, Vault will no longer advertise
the full TLS 1.2 cipher suite list by default. Although this port is only
used for Vault-to-Vault communication and would always pick a strong cipher,
it could cause false flags on port scanners and other security utilities
that assumed insecure ciphers were being used. The previous behavior can be
achieved by setting the value of the (undocumented) cluster_cipher_suites
config flag to tls12.


* Vault Debug: A new top-level subcommand, debug, is added that allows
operators to retrieve debugging information related to a particular Vault
node. Operators can use this simple workflow to capture triaging information,
which can then be consumed programmatically or by support and engineering teams.
It has the abilitity to probe for config, host, metrics, pprof, server status,
and replication status.
* Recovery Mode: Vault server can be brought up in recovery mode to resolve
outages caused due to data store being in bad state. This is a privileged mode
that allows sys/raw API calls to perform surgical corrections to the data
store. Bad storage state can be caused by bugs. However, this is usually
observed when known (and fixed) bugs are hit by older versions of Vault.
* Entropy Augmentation (Enterprise): Vault now supports sourcing entropy from
external source for critical security parameters. Currently an HSM that
supports PKCS#11 is the only supported source.
* Active Directory Secret Check-In/Check-Out: In the Active Directory secrets
engine, users or applications can check out a service account for use, and its
password will be rotated when it's checked back in.
* Vault Agent Template: Vault Agent now supports rendering templates containing
Vault secrets to disk, similar to Consul Template [GH-7652]
* Transit Key Type Support: Signing and verification is now supported with the P-384
(secp384r1) and P-521 (secp521r1) ECDSA curves [GH-7551] and encryption and
decryption is now supported via AES128-GCM96 [GH-7555]
* SSRF Protection for Vault Agent: Vault Agent has a configuration option to
require a specific header before allowing requests [GH-7627]
* AWS Auth Method Root Rotation: The credential used by the AWS auth method can
now be rotated, to ensure that only Vault knows the credentials it is using [GH-7131]
* New UI Features: The UI now supports managing users and groups for the
Userpass, Cert, Okta, and Radius auth methods.
* Shamir with Stored Master Key: The on disk format for Shamir seals has changed,
allowing for a secondary cluster using Shamir downstream from a primary cluster
using Auto Unseal. [GH-7694]
* Stackdriver Metrics Sink: Vault can now send metrics to
Stackdriver. See the configuration
details. [GH-6957]
* Filtered Paths Replication (Enterprise): Based on the predecessor Filtered Mount Replication,
Filtered Paths Replication allows now filtering of namespaces in addition to mounts.
* Token Renewal via Accessor: Tokens can now be renewed via the accessor value through
the new auth/token/renew-accessor endpoint if the caller's token has
permission to access that endpoint.
* Improved Integrated Storage (Beta): Improved raft write performance, added support for
non-voter nodes, along with UI support for: using raft storage, joining a raft cluster,
and downloading and restoring a snapshot.


* agent: Add ability to set the TLS SNI name used by Agent [GH-7519]
* auth/jwt: The redirect callback host may now be specified for CLI logins
* auth/jwt: Bound claims may now contain boolean values [JWT-73]
* auth/jwt: CLI logins can now open the browser when running in WSL [JWT-77]
* core: Exit ScanView if context has been cancelled [GH-7419]
* core: re-encrypt barrier and recovery keys if the unseal key is updated
* core: Don't advertise the full set of TLS 1.2 cipher suites on the cluster
port, even though only strong ciphers were used [GH-7487]
* core (enterprise): Add background seal re-wrap
* core/metrics: Add config parameter to allow unauthenticated sys/metrics
access. [GH-7550]
* metrics: Upgrade DataDog library to improve performance [GH-7794]
* replication (enterprise): Write-Ahead-Log entries will not duplicate the
data belonging to the encompassing physical entries of the transaction,
thereby improving the performance and storage capacity.
* replication (enterprise): Added more replication metrics
* replication (enterprise): Reindex process now compares subpages for a more
accurate indexing process.
* replication (enterprise): Reindex API now accepts a new skip_flush parameter
indicating all the changes should not be flushed while the tree is locked.
* secrets/aws: The root config can now be read [GH-7245]
* secrets/aws: Role paths may now contain the '@' character [GH-7553]
* secrets/database/cassandra: Add ability to skip verfication of connection [GH-7614]
* secrets/gcp: Fix panic during rollback if the roleset has been deleted [GCP-52]
* storage/azure: Add config parameter to Azure storage backend to allow
specifying the ARM endpoint [GH-7567]
* storage/cassandra: Improve storage efficiency by eliminating unnecessary
copies of value data [GH-7199]
* storage/raft: Improve raft write performance by utilizing FSM Batching [GH-7527]
* storage/raft: Add support for non-voter nodes [GH-7634]
* sys: Add a new sys/host-info endpoint for querying information about
the host [GH-7330]
* sys: Add a new set of endpoints under sys/pprof/ that allows profiling
information to be extracted [GH-7473]
* sys: Add endpoint that counts the total number of active identity entities [GH-7541]
* sys: sys/seal-status now has a storage_type field denoting what type of storage
the cluster is configured to use
* sys: Add a new sys/internal/counters/tokens endpoint, that counts the
total number of active service token accessors in the shared token storage.
* sys/config: Add a new endpoint under sys/config/state/sanitized that
returns the configuration state of the server. It excludes config values
from storage, ha_storage, and seal stanzas and some values
from telemetry due to potential sensitive entries in those fields.
* ui: when using raft storage, you can now join a raft cluster, download a
snapshot, and restore a snapshot from the UI [GH-7410]
* ui: clarify when secret version is deleted in the secret version history dropdown [GH-7714]


* agent: Fix a data race on the token value for inmemsink [GH-7707]
* api: Fix Go API using lease revocation via URL instead of body [GH-7777]
* api: Allow setting a function to control retry behavior [GH-7331]
* auth/gcp: Fix a bug where region information in instance groups names could
cause an authorization attempt to fail [GCP-74]
* cli: Fix a bug where a token of an unknown format (e.g. in ~/.vault-token)
could cause confusing error messages during vault login [GH-7508]
* cli: Fix a bug where the namespace list command with JSON formatting
always returned an empty object [GH-7705]
* cli: Command timeouts are now always specified solely by the
* core: Don't allow registering a non-root zero TTL token lease. This is purely
defense in depth as the lease would be revoked immediately anyways, but
there's no real reason to allow registration. [GH-7524]
* core: Correctly revoke the token that's present in the response auth from a
auth/token/ request if there's partial failure during the process. [GH-7835]
* identity (enterprise): Fixed identity case sensitive loading in secondary
cluster [GH-7327]
* identity: Ensure only replication primary stores the identity case sensitivity state [GH-7820]
* raft: Fixed VAULT_CLUSTER_ADDR env being ignored at startup [GH-7619]
* secrets/pki: Don't allow duplicate SAN names in issued certs [GH-7605]
* sys/health: Pay attention to the values provided for standbyok and
perfstandbyok rather than simply using their presence as a key to flip on
that behavior [GH-7323]
* ui: using the wrapped_token query param will work with redirect_to and
will automatically log in as intended [GH-7398]
* ui: fix an error when initializing from the UI using PGP keys [GH-7542]
* ui: show all active kv v2 secret versions even when delete_version_after is configured [GH-7685]
* ui: Ensure that items in the top navigation link to pages that users have access to [GH-7590]

## Previous Releases
For more information on previous releases, check out the changelog on GitHub.

This package has no dependencies.

Discussion for the Vault Package

Ground Rules:

  • This discussion is only about Vault and the Vault 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 Vault, 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