Downloads of v 1.3.3:


Last Update:

03 Nov 2017

Package Maintainer(s):

Software Author(s):

  • Samuel Vasko


console terminal cli


This is not the latest version of Cmder available.

1.3.3 | Updated: 03 Nov 2017



Downloads of v 1.3.3:



Software Author(s):

  • Samuel Vasko

Cmder 1.3.3

This is not the latest version of Cmder available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


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:


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 cmder -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 cmder -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 cmder installed
    name: cmder
    state: present
    version: 1.3.3
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'cmder' do
  action    :install
  version  '1.3.3'
  source   'STEP 3 URL'

See docs at

    Name: cmder,
    Version: 1.3.3,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller cmder
   Name     = 'cmder'
   Ensure   = 'Present'
   Version  = '1.3.3'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'cmder':
  provider => 'chocolatey',
  ensure   => '1.3.3',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install cmder version="1.3.3" 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 24 Dec 2017.


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 (7 MB) for basic console without bundled msysgit.

Install location

This package installs into the cmder subdirectory of the path defined in the environment variable:

  • <chocolatey-0.9.10: $env:ChocolateyBinRoot
  • >=chocolatey-0.9.10: $env:ChocolateyToolsLocation

To determine installed chocolatey version: choco -v

Note that when upgrading to >=0.9.10, if $env:ChocolateyBinRoot exists, the value will be preserved and variable updated to new name. If neither variable exists, the default location is used: $env:SystemDrive\tools

$packageName = 'cmder'
$url = ''
$checksum = 'f93bb2cf97854b806c2d2b7c533f8903'
$checksumType = 'md5'
$binRoot = Get-BinRoot
$installPath = Join-Path $binRoot $packageName

Install-ChocolateyZipPackage -PackageName $packageName `
                             -Url $url `
                             -UnzipLocation $installPath `
                             -Checksum $checksum `
                             -ChecksumType $checksumType

Install-ChocolateyPath $installPath 'User'
$packageName = 'cmder'
$toolsPath = Split-Path -Parent $MyInvocation.MyCommand.Definition
$unPath = Join-Path $toolsPath 'Uninstall-ChocolateyPath.psm1'
$binRoot = Get-BinRoot
$installPath = Join-Path $binRoot $packageName

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

if (Test-Path $installPath) {
    Remove-Item -Path $installPath -Recurse -Force
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.

Version Downloads Last Updated Status
Cmder 1.3.16 54919 Friday, July 31, 2020 Approved
Cmder 1.3.15 17697 Saturday, June 27, 2020 Approved
Cmder 1.3.14 50477 Thursday, January 9, 2020 Approved
Cmder 1.3.13 17240 Monday, November 25, 2019 Approved
Cmder 1.3.12 36603 Wednesday, August 21, 2019 Approved
Cmder 1.3.11 61460 Monday, December 24, 2018 Approved
Cmder 1.3.10 6671 Saturday, December 1, 2018 Approved
Cmder 1.3.9 172 Thursday, November 29, 2018 Approved
Cmder 1.3.8 6331 Tuesday, November 13, 2018 Approved



  • Automatically (stable releases only) built and uploaded by dtgm
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