How to Silently Install Double Commander

Silent install · · 7 min read

Keep every Windows endpoint converged on the same version of Double Commander with a deployment approach built for repeatability and control. This guide gives IT admins a practical path to package and roll out the Alexander Koblov MSI installer at machine scope, using the verified silent install command and a reliable detection rule. Because installation requires admin rights, it is well suited for managed deployment through Intune/SCCM/PDQ with consistent results across your fleet.

STEP 0

Quick snapshot: Silently install Double Commander on Windows

Run in an elevated Command Prompt or PowerShell:

cmd
msiexec /i "alexx2000.DoubleCommander.1.1.32.X64.msi" /qn REBOOT=ReallySuppress ALLUSERS=1

Overview

ApplicationDouble Commander
Version1.1.32
PublisherAlexander Koblov
Installer typeMSI
Install scopeSystem / machine-wide
Requires adminYes
Silent installAvailable
Silent uninstallAvailable
Detection methodMSI product code
Installer filealexx2000.DoubleCommander.1.1.32.X64.msi
DownloadDouble Commander installer

Silent install steps

Run any one of the methods below to install Double Commander silently with zero user interaction. Command Prompt and PowerShell produce the same result — use whichever fits your deployment workflow.

Method 1: Install with Command Prompt

  1. Download or stage the installer (alexx2000.DoubleCommander.1.1.32.X64.msi) to a local folder, for example C:\Installers.
Installers
This PCLocal Disk (C:)InstallersSearch Installers
alexx2000.DoubleCommander.1.1.32.X64.msi6/17/2026 9:14 AMWindows Installer Package
1 item1 item selected
  1. Open Command Prompt as Administrator:
    Press StartType cmdRight-click Command PromptChoose Run as administrator
AllAppsDocumentsSettingsFoldersPhotos
Best match
Command PromptSystem
Command Prompt
System
Open
Run as administrator
Run as different user
Open file location
cmd
  1. Switch to the installer folder, then run the silent install command:
cmd
msiexec /i "alexx2000.DoubleCommander.1.1.32.X64.msi" /qn REBOOT=ReallySuppress ALLUSERS=1

Method 2: Install with PowerShell

Run the same silent install through PowerShell (elevated).

  1. Download or stage the installer (alexx2000.DoubleCommander.1.1.32.X64.msi) to a local folder, for example C:\Installers.
  1. Open PowerShell as Administrator — right-click Start (or press Win+X), then:
    • On Windows 10: choose Windows PowerShell (Admin).
    • On Windows 11: choose Terminal (Admin) — it opens Windows Terminal running PowerShell.
Right-click the Start button — or press ⊞ Win + X
Apps and Features
Power Options
Device Manager
Disk Management
Terminal
Terminal (Admin)
Task Manager
Settings
  1. Run the command:
powershell
Start-Process -FilePath "msiexec.exe" -ArgumentList '/i "alexx2000.DoubleCommander.1.1.32.X64.msi" /qn REBOOT=ReallySuppress ALLUSERS=1' -Wait -NoNewWindow

Deployment Notes

Key facts to confirm before rolling this out to production machines — permissions required, scope of install, and reboot behavior.

RequirementAdministrator privileges required
Install scopeMachine
Restart behaviorNo restart expected

Detection Rules

Configure your deployment tool with the detection rule below to confirm a successful install of Double Commander. The same rule work for Microsoft Intune, SCCM, PDQ Deploy, and most RMM platforms — just paste the values into the matching fields.

MSI product code detection

Product code{4F67E169-C729-4C6A-8ECF-2C18AB79AED3}

PowerShell detection script

Prefer a script-based check? Use this as a custom detection script in Microsoft Intune (or any tool that supports detection scripts). It exits 0 when Double Commander is detected and 1 otherwise.

powershell
$Code = '{4F67E169-C729-4C6A-8ECF-2C18AB79AED3}'
$Paths = @(
    "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\$Code",
    "HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$Code"
)
if ($Paths | Where-Object { Test-Path $_ }) { exit 0 }
exit 1

Silent Uninstall Steps

Remove Double Commander silently from one machine or your entire fleet. The commands below uninstall without prompts and suppress automatic reboots so you control the timing.

Method 1: Uninstall with Command Prompt

Run the uninstall command from an elevated Command Prompt.

  1. Open Command Prompt as Administrator.
  2. Run the silent uninstall command.
cmd
msiexec /x "{4F67E169-C729-4C6A-8ECF-2C18AB79AED3}" /qn REBOOT=ReallySuppress

Method 2: Uninstall with PowerShell

Run the same silent uninstall command through PowerShell.

  1. Open PowerShell as Administrator.
  2. Run the silent uninstall command.
powershell
Start-Process -FilePath "msiexec.exe" -ArgumentList '/x "{4F67E169-C729-4C6A-8ECF-2C18AB79AED3}" /qn REBOOT=ReallySuppress' -Wait -NoNewWindow

Deployment Examples

Drop one of the snippets below into your deployment tool, Group Policy, or scheduled task. Each script wraps the silent install command for Double Commander as a batch file or PowerShell script — copy, save, and run.

Batch file example

Save the following content as install-double-commander.bat in the same folder as the installer.

cmd
@echo off
cd /d "%~dp0"
msiexec /i "alexx2000.DoubleCommander.1.1.32.X64.msi" /qn REBOOT=ReallySuppress ALLUSERS=1
exit /b %errorlevel%

PowerShell script example

Save the following content as install-double-commander.ps1 in the same folder as the installer.

powershell
Set-Location -Path $PSScriptRoot
$Installer = 'alexx2000.DoubleCommander.1.1.32.X64.msi'
& msiexec.exe /i $Installer /qn REBOOT=ReallySuppress ALLUSERS=1
exit $LASTEXITCODE

Frequently asked questions

Can I silently install Double Commander on Windows?
Yes. This guide uses MSI switches to install Double Commander 1.1.32 completely unattended, with no user interaction or prompts. These commands are commonly used with Intune, SCCM, PDQ Deploy, and RMM tools.
Do I need administrator privileges to install Double Commander?
Yes. Double Commander requires elevated permissions for installation. Run the installer as Administrator or deploy it using the SYSTEM context.
Will installing Double Commander restart the computer?
No. The Double Commander install command uses REBOOT=ReallySuppress, which prevents any automatic restart from occurring during deployment.
How do I verify Double Commander installed successfully?
Verify Double Commander by using the detection rule from this guide: file path, registry key, MSI product code, or MSIX package family name. These methods are commonly supported by Intune, SCCM, and PDQ.
How do I silently uninstall Double Commander?
To silently remove Double Commander, use msiexec /x together with the MSI product code and /qn REBOOT=ReallySuppress.
Which deployment tools support these commands?
These Double Commander commands are commonly used with Intune, SCCM/MECM, PDQ Deploy, ManageEngine, NinjaOne, Datto RMM, Atera, and Action1.

Troubleshooting

If the install fails, exits with a non-zero code, or leaves no trace on the target machine, work through the checks below. Most issues come down to permissions, paths, or exit code handling.

Run as administratorMake sure Command Prompt or PowerShell is opened as Administrator. This installer writes to a machine-wide location and will fail silently without elevated permissions.
Verify the installer file nameConfirm that the installer file name matches the command shown in this guide: alexx2000.DoubleCommander.1.1.32.X64.msi.
Run from the correct folderRun the command from the folder that contains the installer file. For batch or PowerShell deployments, place the script and installer in the same folder.
Check exit codesIf the installer returns a non-zero exit code, review the installer log (add /L*v install.log to msiexec for a verbose MSI log) or your deployment tool's logs. Some packages use additional success exit codes.
Restart if requiredIf the application does not appear immediately after installation, sign out and sign back in, or restart the device — this refreshes Start menu shortcuts, file associations, and Path entries written by the installer.
Validate detection rulesIf your deployment tool reports the app as not installed, verify that the detection rule matches the installed version, MSI product code, registry key, or file path. Use the Detection Rules section above to confirm whether the application was installed successfully.

Deployment recap

Before you roll Double Commander out to production, confirm you have:

  • The silent install command, run from an elevated prompt
  • The matching silent uninstall command for rollback
  • The detection rule wired into your deployment tool

Got all three? You’re ready to deploy at scale. If this guide saved you time, fuel the next one:

Rating
be the first to rate

Comments

Loading comments…

    Leave a comment

    ✎ Edit