Downloads of v 0.8.1:


Last Update:

24 Dec 2017

Package Maintainer(s):

Software Author(s):

  • Alexander Koblov
  • Przemyslaw Nagay


doublecmd double file manager commander admin

Double Commander for Windows

This is not the latest version of Double Commander for Windows available.

  • 1
  • 2
  • 3

0.8.1 | Updated: 24 Dec 2017



Downloads of v 0.8.1:



Software Author(s):

  • Alexander Koblov
  • Przemyslaw Nagay

  • 1
  • 2
  • 3
Double Commander for Windows 0.8.1

This is not the latest version of Double Commander for Windows 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.


To install Double Commander for Windows, run the following command from the command line or from PowerShell:


To upgrade Double Commander for Windows, run the following command from the command line or from PowerShell:


To uninstall Double Commander 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 doublecmd -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 doublecmd -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 doublecmd installed
    name: doublecmd
    state: present
    version: 0.8.1
    source: STEP 3 URL

See docs at

chocolatey_package 'doublecmd' do
  action    :install
  version  '0.8.1'
  source   'STEP 3 URL'

See docs at

    Name: doublecmd,
    Version: 0.8.1,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller doublecmd
   Name     = 'doublecmd'
   Ensure   = 'Present'
   Version  = '0.8.1'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'doublecmd':
  provider => 'chocolatey',
  ensure   => '0.8.1',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install doublecmd version="0.8.1" 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.


Double Commander


Double Commander is a cross platform open source file manager with two panels side by side. It is inspired by Total Commander and features some new ideas.
Double Commander can be run on several platforms and operating systems. It supports 32-bit and 64-bit processors. See Supported platforms for a complete list.
See Double Commander in action in the Gallery.


  • Install and uninstall via Chocolatey
  • Supports 32/64-bit version


2017-12-24 Build 0.8.1

2017-12-11 Build 0.8.0

2017-04-19 Build 0.7.8 (maintainer: marcinbojko)



choco install doublecmd

YAML (Foreman, puppetlabs/chocolatey module)

  ensure: latest
  uninstall_options: "--force --all-versions"
  provider: chocolatey


  ensure: latest

$ErrorActionPreference = 'Stop';

$packageName        = 'doublecmd'
$scriptPath         = $(Split-Path $MyInvocation.MyCommand.Path)
$url_local          = ""
$url_remote         = ""
$url_local64        = ""
$url_remote64       = ""
$url_local_trans    = ""
$url_remote_trans   = ""
$url                = ""
$url64              = ""
$url_trans          = ""
$checksum           = "51182e8870b1105407bfce290044cb5b14c213752de06254a229ea15632c59f3"
$checksum64         = "37c7e6f0029e026125359064d4a1fea8037e9fe728454e89594d8550969cfb67"
$logfile            = "$env:TEMP\chocolatey\$($packageName)\$($packageName).MsiInstall.log"
$logdir             = "$env:TEMP\chocolatey\$($packageName)"
$killexec           = 1
$killexecprocess    = "doublecmd*"
# Let's check if should we use local or remote install source
$statusCode = Test-Path $url_local
if ($statusCode) {
    else {

# Someone has won ;)

# Remove previous version
$statusCode = Test-Path -Path "C:\Program Files\Double Commander\unins000.exe"
    if ($statusCode) {
        Start-Process -FilePath "C:\Program Files\Double Commander\unins000.exe" -ArgumentList "/SILENT" -ErrorAction silentlycontinue
        Start-Sleep -s 60

# Remove previous version (32-bit)
$statusCode = Test-Path -Path "C:\Program Files (x86)\Double Commander\unins000.exe"
    if ($statusCode) {
        Start-Process -FilePath "C:\Program Files (x86)\Double Commander\unins000.exe" -ArgumentList "/SILENT" -ErrorAction silentlycontinue
        Start-Sleep -s 60

#Let's check your TEMP derectory

$statusCode = Test-Path $logdir
if ($statusCode) {

    else {


$packageArgs = @{
  packageName   = $packageName
  fileType      = 'msi'
  silentArgs    = "/qn /norestart ADDLOCAL=ALL"
  validExitCodes= @(0, 3010, 1603, 1641)
  url           = $url
  url64bit      = $url64
  checksumType  = 'sha256'
  checksumType64= 'sha256'
  checksum      = $checksum
  checksum64    = $checksum64

# Should we kill some exec ?
if ($killexec) {
  Stop-Process -processname $killexecprocess -force
  Start-Sleep -s 10
  Install-ChocolateyPackage @packageArgs


$ErrorActionPreference = 'Stop';

$packageName = 'doublecmd'
$softwareName = 'Double Commander*'
$installerType = 'MSI'
$silentArgs = '/qn /norestart'
$validExitCodes = @(0, 3010, 1605, 1614, 1641)
if ($installerType -ne 'MSI') {
  $validExitCodes = @(0)

$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $softwareName

if ($key.Count -eq 1) {
  $key | ForEach-Object {
    $file = "$($_.UninstallString)"

    if ($installerType -eq 'MSI') {
      $silentArgs = "$($_.PSChildName) $silentArgs"

      $file = ''

    Uninstall-ChocolateyPackage -PackageName $packageName `
                                -FileType $installerType `
                                -SilentArgs "$silentArgs" `
                                -ValidExitCodes $validExitCodes `
                                -File "$file"
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$key.Count matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | ForEach-Object {Write-Warning "- $_.DisplayName"}

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
Double Commander for Windows 0.9.10 10813 Sunday, January 10, 2021 Approved
Double Commander for Windows 0.9.9 38032 Monday, June 29, 2020 Approved
Double Commander for Windows 0.9.8 33129 Saturday, February 1, 2020 Approved
Double Commander for Windows 0.9.7 9998 Thursday, January 9, 2020 Approved
Double Commander for Windows 0.9.6 78409 Sunday, September 1, 2019 Approved
Double Commander for Windows 0.9.5 43515 Friday, July 12, 2019 Approved
Double Commander for Windows 0.9.3 41778 Wednesday, May 22, 2019 Approved
Double Commander for Windows 0.9.2 41243 Tuesday, April 2, 2019 Approved
Double Commander for Windows 0.9.1 10512 Sunday, February 17, 2019 Approved
Discussion for the Double Commander for Windows Package

Ground Rules:

  • This discussion is only about Double Commander for Windows and the Double Commander 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 Double Commander 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