Downloads of v 1.15.0:


Last Update:

10 Mar 2018

Package Maintainer(s):

Software Author(s):

  • Microsoft


git-credential-manager-for-windows admin git github


This is not the latest version of Git-Credential-Manager-for-Windows available.

  • 1
  • 2
  • 3

1.15.0 | Updated: 10 Mar 2018



Downloads of v 1.15.0:



Software Author(s):

  • Microsoft

  • 1
  • 2
  • 3
Git-Credential-Manager-for-Windows 1.15.0

This is not the latest version of Git-Credential-Manager-for-Windows available.

  • 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


To install Git-Credential-Manager-for-Windows, run the following command from the command line or from PowerShell:


To upgrade Git-Credential-Manager-for-Windows, run the following command from the command line or from PowerShell:


To uninstall Git-Credential-Manager-for-Windows, 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 git-credential-manager-for-windows -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 git-credential-manager-for-windows -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 git-credential-manager-for-windows installed
    name: git-credential-manager-for-windows
    state: present
    version: 1.15.0
    source: STEP 3 URL

See docs at

chocolatey_package 'git-credential-manager-for-windows' do
  action    :install
  version  '1.15.0'
  source   'STEP 3 URL'

See docs at

    Name: git-credential-manager-for-windows,
    Version: 1.15.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller git-credential-manager-for-windows
   Name     = 'git-credential-manager-for-windows'
   Ensure   = 'Present'
   Version  = '1.15.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'git-credential-manager-for-windows':
  provider => 'chocolatey',
  ensure   => '1.15.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install git-credential-manager-for-windows version="1.15.0" 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 10 Mar 2018.


Git Credential Manager for Windows Build status

The Git Credential Manager for Windows (GCM) provides secure Git credential storage for Windows. It's the successor to the Windows Credential Store for Git (git-credential-winstore), which is no longer maintained. Compared to Git's built-in credential storage for Windows (wincred), which provides single-factor authentication support working on any HTTP enabled Git repository, GCM provides multi-factor authentication support for Visual Studio Team Services, Team Foundation Server, and GitHub.

This project includes:

  • Secure password storage in the Windows Credential Store
  • Multi-factor authentication support for Visual Studio Team Services
  • Two-factor authentication support for GitHub
  • Personal Access Token generation and usage support for Visual Studio Team Services and GitHub
  • Non-interactive mode support for Visual Studio Team Services backed by Azure Directory
  • Kerberos authentication for Team Foundation Server
  • Optional settings for Docs/

How to use

You don't. It magically works when credentials are needed. For example, when pushing to Visual Studio Team Services, it automatically opens a window and initializes an oauth2 flow to get your token.


There are many ways to contribute.

  • Submit bugs and help us verify fixes as they are checked in.
  • Review code changes.
  • Contribute bug fixes and features.

Code Contributions

For code contributions, you will need to complete a Contributor License Agreement (CLA). Briefly, this agreement testifies that you grant us permission to use the submitted change according to the terms of the project's license, and that the work being submitted is under the appropriate copyright.

Please submit a Contributor License Agreement (CLA) before submitting a pull request. You may visit <> to sign digitally. Alternatively, download the agreement Microsoft Contribution License Agreement.pdf, sign, scan, and email it back to <[email protected]>. Be sure to include your GitHub user name along with the agreement. Once we have received the signed CLA, we'll review the request.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact <[email protected]> with any additional questions or comments.


This project uses the MIT License


$ErrorActionPreference = 'Stop'; # stop on all errors
Install-ChocolateyPackage -packageName 'Git-Credential-Manager-for-Windows' -FileType exe -SilentArgs '/SILENT /NORESTART' -Url '' -checksum '87C208B5933EEECB13BA0F34AD2B95DFE41839415FAB31D2EAC97B32B0EA3432' -checksumType 'sha256' 

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
Git Credential Manager for Windows 1.19.0 37936 Wednesday, March 13, 2019 Approved
Git Credential Manager for Windows 1.18.5 925 Tuesday, March 12, 2019 Approved
Git Credential Manager for Windows 1.18.4 13074 Monday, January 7, 2019 Approved
Git Credential Manager for Windows 1.18.3 6900 Saturday, November 3, 2018 Approved
Git Credential Manager for Windows 1.18.2 1095 Saturday, October 13, 2018 Approved
Git Credential Manager for Windows 1.18.1 499 Tuesday, October 9, 2018 Approved
Git Credential Manager for Windows 1.18.0 670 Monday, October 1, 2018 Approved
Git Credential Manager for Windows 1.17.2 851 Sunday, September 23, 2018 Approved
Git-Credential-Manager-for-Windows 1.16.3 1743 Tuesday, August 28, 2018 Approved


In this release:

  • Add support for multiple users per host by using the https://{username}@{host} repository URL format.
    • Note: the GitHub Authentication class does not support this feature.
  • Add support for user configured privilege scopes when requesting new VSTS personal access tokens.
  • Add automatic VSTS tenant cache eviction when credentials are invalid.
    • Due to an abnormally large number of problems related to invalid tenant cache entries, entries will now be evicted when their related credentials become invalid.
  • Add verification step to VSTS credential deletion.
    • When Git requests that VSTS credentials be deleted from the cache, the VSTS Authentication class will attempt to verify the credentials before deleting them. Only credentials which are verified to be invalid will be deleted.
    • This is designed to avoid unnecessary credential removal caused by flaky networks and other interruptions which might cause Git to report the credentials are invalid.
  • Improved support for handling HTTP proxies (thank you @MagooChris for your contributions).
  • Improved the general, Bitbucket usage, and VSTS integration documentation.
  • Add new config verb for dumping state affecting the GCM.

Bug Fixes

  • Fixed an issue which caused the GCM to fail when standard input was invalid (thanks to @ebugusey).
  • Fixed an issue where the GCM's internal logging mechanism could fail causing the GCM to fail.
  • Fixed an issue where the HTTP_PROXY environment variable was incorrectly being ignored.

To install the Git Credential Manager, download and double-click the GCMW-1.15.0.exe installer. It is that easy, it will even install Git for Windows 2.15.0) and the Microsoft .Net Framework for you if necessary.

For non-installation or custom installation needs, download the archive and expand its contents. Use the included install.cmd or options provided via git-credential-manager install to complete setup.

Change Log

Discussion for the Git-Credential-Manager-for-Windows Package

Ground Rules:

  • This discussion is only about Git-Credential-Manager-for-Windows and the Git-Credential-Manager-for-Windows 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 Git-Credential-Manager-for-Windows, 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