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


Last Update:

10 Nov 2018

Package Maintainer(s):

Software Author(s):

  • Samuel Vasko


cmder console terminal cli foss


This is not the latest version of Cmder available.

  • 1
  • 2
  • 3

1.3.7 | Updated: 10 Nov 2018



Downloads of v 1.3.7:



Software Author(s):

  • Samuel Vasko

Cmder 1.3.7

This is not the latest version of Cmder 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 Cmder, run the following command from the command line or from PowerShell:


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


To uninstall Cmder, 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 cmder -y --source="'INTERNAL REPO URL'" --version="'1.3.7'" [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 cmder -y --source="'INTERNAL REPO URL'" --version="'1.3.7'" 

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

Exit $exitCode

- name: Install cmder
    name: cmder
    version: '1.3.7'
    state: present

See docs at

chocolatey_package 'cmder' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.3.7'

See docs at

cChocoPackageInstaller cmder
    Name     = "cmder"
    Version  = "1.3.7"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

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


There are versions of this package awaiting moderation . See the Version History section below.

Package Approved

This package was approved by moderator gep13 on 12 Nov 2018.


Cmder is a software package created out of pure frustration over absence of usable console emulator on Windows. It is based on ConEmu with major config overhaul. Monokai color scheme, amazing clink and custom prompt layout.

The main advantage of Cmder is portability. It is designed to be totally self-contained with no external dependencies, that is makes it great for USB Sticks or Dropbox. So you can carry your console, aliases and binaries (like wget, curl and git) with you anywhere.

Combines utility of 3 distinct tools:

  • Console emulator = Conemu
  • Cmd.exe enhancements = clink
  • Unix tools on windows = msysgit


This package uncompresses to 250 MB and includes Unix commands via bundled msysgit.
See cmdermini (8 MB) for basic console without bundled msysgit.

MIT License

Copyright (c) 2017 Samuel Vasko

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The embedded software have been downloaded from the listed download
location on <>
and can be verified by doing the following:

1. Download the following <>
2. Get the checksum using one of the following methods:
  - Using powershell function 'Get-FileHash'
  - Use chocolatey utility 'checksum.exe'
3. The checksums should match the following:

  checksum type: sha256
  checksum: 487F4A0AE8A3310C75AE470F9434AA12BC146F056F499D84A44332C992FA3E29

The file 'LICENSE.txt' has been obtained from <>
$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path -parent $MyInvocation.MyCommand.Definition

$packageArgs = @{
  packageName = $env:ChocolateyPackageName
  destination = Join-Path (Get-ToolsLocation) $env:ChocolateyPackageName
  file        = "$toolsPath\cmder.7z"

Get-ChocolateyUnzip @packageArgs
Remove-Item $toolsPath\*.7z -ea 0

Install-ChocolateyPath $packageArgs['destination'] 'User'
$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path -parent $MyInvocation.MyCommand.Definition
$unScriptPath = Join-Path $toolsPath "Uninstall-ChocolateyPath.psm1"

$installPath = Join-Path (Get-ToolsLocation) $env:ChocolateyPackageName

Import-Module $unScriptPath
Uninstall-ChocolateyPath $installPath 'User'

if (Test-Path $installPath) {
  Remove-Item -path $installPath -Recurse -Force
md5: 495BEA3F68B3EF64D4FA8DECF54C14CA | sha1: DB4D75822CEFF2EFDB126D8A8F25A53785B33D2F | sha256: 487F4A0AE8A3310C75AE470F9434AA12BC146F056F499D84A44332C992FA3E29 | sha512: 761A1E6F39B5FCC0BF15C40646CE12F52595351F4F1AF497CE55E6BFD9677D3F89041C3996711F5E2EE2FE2CA1F3B306E5C4099A6A9C8F479BBA108A127B4590
function Uninstall-ChocolateyPath {
    [string] $pathToUninstall,
    [System.EnvironmentVariableTarget] $pathType = [System.EnvironmentVariableTarget]::User
  Write-Debug "Running 'Uninstall-ChocolateyPath' with pathToUninstall:`'$pathToUninstall`'";

  #get the PATH variable
  $envPath = $env:PATH
  #$envPath = [Environment]::GetEnvironmentVariable('Path', $pathType)
  if (!$envPath.ToLower().Contains($pathToUninstall.ToLower())) {
    Write-Host "PATH environment variable does not have $pathToUninstall in it."

  Write-Host "PATH environment variable has $pathToUninstall in it. Removing..."
  $actualPath = [Environment]::GetEnvironmentVariable('Path', $pathType)

  # escape regex metachars, match possible backslash and item separator at eol
  $pathToUninstallRegex = ($pathToUninstall -replace '([\\().])', '\$1') + '\\?(;|$)'

  # remove pathToUninstall from actualPath
  $actualPath = $actualPath -replace "$pathToUninstallRegex", ''

  if ($pathType -eq [System.EnvironmentVariableTarget]::Machine) {
    $psArgs = "[Environment]::SetEnvironmentVariable('Path',`'$actualPath`', `'$pathType`')"
    Start-ChocolateyProcessAsAdmin "$psArgs"
  else {
    [Environment]::SetEnvironmentVariable('Path', $actualPath, $pathType)

  # remove from path of current powershell session
  $envPSPath = $env:PATH
  $env:Path = $envPSPath -replace "$pathToUninstallRegex", ''

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
Cmder 1.3.21 19 Monday, December 19, 2022
Waiting for Maintainer
Cmder 1.3.19 143638 Monday, January 17, 2022 Approved
Cmder 1.3.18 56480 Friday, March 26, 2021 Approved
Cmder 1.3.17 27221 Wednesday, December 23, 2020 Approved
Cmder 1.3.16 57473 Friday, July 31, 2020 Approved
Cmder 1.3.15 17831 Saturday, June 27, 2020 Approved
Cmder 1.3.14 50830 Thursday, January 9, 2020 Approved
Cmder 1.3.13 17362 Monday, November 25, 2019 Approved
Cmder 1.3.12 36744 Wednesday, August 21, 2019 Approved
Cmder 1.3.11 61607 Monday, December 24, 2018 Approved
Cmder 1.3.10 6793 Saturday, December 1, 2018 Approved
Cmder 1.3.9 307 Thursday, November 29, 2018 Approved
Cmder 1.3.8 6448 Tuesday, November 13, 2018 Approved
Cmder 1.3.7 1380 Saturday, November 10, 2018 Approved
Cmder 1.3.6 5134 Thursday, October 25, 2018 Approved
Cmder 1.3.5 46131 Sunday, February 11, 2018 Approved
Cmder 1.3.4 333 Thursday, March 29, 2018 Approved
Cmder 1.3.3 17817 Friday, November 3, 2017 Approved
Cmder 1.3.2 33837 Friday, December 16, 2016 Approved
Cmder 369 Friday, December 16, 2016 Approved
Cmder 1.3.1 4605 Wednesday, November 30, 2016 Approved
Cmder 968 Wednesday, June 22, 2016 Exempted
Cmder 1.3.0 10940 Wednesday, July 20, 2016 Approved
Cmder 1.3.0-beta 449 Saturday, May 21, 2016 Exempted
Cmder 1.2.9-beta 363 Saturday, May 21, 2016 Exempted
Cmder 497 Wednesday, June 22, 2016 Approved

Package changelog

Software changelog

v1.3.7 (2018-11-10)

Full Changelog


Tagging as v1.3.7


Aaron Arney (1):

  • Update README

Arion Roberto Krause (1):

  • Fixed typo

Benjamin Staneck (8):

  • :arrow_up: ConEmu to 180626
  • :arrow_up: Update Git to 2.19.0
  • Revert "replace user-aliases with user_aliases"
  • replace user-aliases with user_aliases
  • better fix for #1265
  • Revert "sanitize dir before assigning to prompt"
  • sanitize dir before assigning to prompt
  • Update

Bob Hood (1):

  • Refactored the Mercurial prompt code to be more efficient.

David Refoua (1):

  • fix some spelling issues

Dax T Games (8):

  • Revert "Ignore %cmder_root%\config (#1945)"
  • Ignore %cmder_root%\config (#1945)
  • Add /f for fast init. (#1942)
  • add diag helper scripts and adds to the path (#1918)
  • Fix #1806 #1675 (#1870)
  • Profile.ps1 (#1796)
  • Fix lib base (#1794)
  • Little Changes

Dax T. Games (42):

  • Fixed move of default conemu.xml to the vendor folder
  • cleanup
  • ignore all of config folder
  • move default comemu.xml to vendor folder
  • fixes
  • more headers
  • init.bat update for cexec
  • git prompt yellow
  • cleanup
  • fix user lua and git detection
  • allow conditionally setting environment variables
  • cleanup
  • added exit codes
  • flag_exists.cmd to flag_exec.cmd, also to lib as an option
  • cleanup
  • cleanup
  • fixed
  • handle start dir args with trailing "
  • cleanup
  • '.gitignore'
  • cleanup
  • '.gitignore'
  • cleanup
  • cleanup
  • verbos output
  • cmder_shell settings
  • add cmder_shell method
  • replace - with _ in debug-output and verbose-output
  • trying to get tcc working
  • Trying to get tcc working
  • rename
  • modify message
  • move user-aliases.cmd to user_aliases.cmd
  • gitignore
  • move bin\alias.bat to vendor\bin\alias.cmd
  • cleanup
  • run user lua afer cmder lua
  • fix /unregister
  • load user clink

Dmitri S. Guskov (2):

  • Powershell 5.1 compatibility
  • Update profile.ps1

Gregory Lucas (1):

  • Initialize time_init to fix init error message

Josef Pihrt (2):

  • Fix typos, remove escaping inside inline code, replace single quote with backtick
  • Fix typo and broken link

Merlin (1):

  • Remove duplicate Install-Module detection

Nicolas Arnaud-Cormos (1):

  • Ensure the right git path is found in case of shim.

Thorsten Sommer (1):

  • Fixed spelling

gaoslin (1):

  • Update init.bat

leochien0102 (1):

  • fix the 'was unexpected at this time.'

xiazeyu (4):

  • chore: unite slash
  • docs: update to latest useage
  • refactor: reduce global varible useage, fixed quote issue, added parameters support
  • doc: fix typo

xiazeyu_2011 (8):

  • docs: migrated instructions to the wiki pages
  • rename /bin/have.bat to /vendor/lib/flag_exists.cmd
  • fix: bug when no argument is passed in
  • docs: update doc for have.bat
  • feat: add have.bat as a wrapper
  • Optimize comments of using arguments in user-profile.cmd
  • fix conflict with init.bat build-in command parser, update user-profile.cmd
  • Pass arguments to user-profile.cmd

刘祺 (1):

  • add LANG support

Discussion for the Cmder Package

Ground Rules:

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