Downloads of v 2016.715:


Last Update:

24 Apr 2016

Package Maintainer(s):

Software Author(s):

  • Marek Jasinski


freecommander freecommander-xe admin dual panel file manger commander

freecommander-xe.install (Install)

This is not the latest version of freecommander-xe.install (Install) available.

  • 1
  • 2
  • 3

2016.715 | Updated: 24 Apr 2016



Downloads of v 2016.715:



Software Author(s):

  • Marek Jasinski

  • 1
  • 2
  • 3
freecommander-xe.install (Install) 2016.715

This is not the latest version of freecommander-xe.install (Install) available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Failed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install freecommander-xe.install (Install), run the following command from the command line or from PowerShell:


To upgrade freecommander-xe.install (Install), run the following command from the command line or from PowerShell:


To uninstall freecommander-xe.install (Install), run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: 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 freecommander-xe.install -y --source="'INTERNAL REPO URL'" --version="'2016.715'" [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 freecommander-xe.install -y --source="'INTERNAL REPO URL'" --version="'2016.715'" 

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

Exit $exitCode

- name: Install freecommander-xe.install
    name: freecommander-xe.install
    version: '2016.715'
    state: present

See docs at

chocolatey_package 'freecommander-xe.install' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2016.715'

See docs at

cChocoPackageInstaller freecommander-xe.install
    Name     = "freecommander-xe.install"
    Version  = "2016.715"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'freecommander-xe.install':
  ensure   => '2016.715',
  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.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved by moderator doc on 26 Apr 2016.


FreeCommander is an easy-to-use alternative to the standard windows file manager.
The program helps you with daily work in Windows.
Here you can find all the necessary functions to manage your data stock.
You can take FreeCommander anywhere – just copy the portable directory on a CD or USB-Stick – and you can even
work with this program on a foreign computer.

A summary about the main features in FreeCommander is available: here.

Please Note: This is an automatically updated package. If you find it is
out of date by more than a week, please contact the maintainer(s) and
let them know the package is no longer updating correctly.

$ErrorActionPreference = 'Stop'; # stop on all errors

$packageName= 'freecommander-xe.install' # arbitrary name for the package, used in messages
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = '' # download url
$zipFileName= ''
$exeFileName= 'FreeCommanderXE-32-public_setup.exe'

function GetWorkingDirectory() {
    $chocTempDir = Join-Path ([IO.Path]::GetTempPath()) 'chocolatey'
    $tempDir = Join-Path $chocTempDir $packageName
    if($env:packageVersion -ne $null) { $tempDir = Join-Path $tempDir "$env:packageVersion" }
    [System.IO.Directory]::CreateDirectory($tempDir) | Out-Null
    Write-Debug "Working directory is $tempDir."

function ClearWorkingDirectory() {
    Write-Debug "Cleaning working directory ..."
    Remove-Item -Recurse -Force -ErrorAction 0 (GetWorkingDirectory)
    Write-Debug "Working directory cleaned."

function DownloadAndExtractArchive($url) {
    $workingDirectory = GetWorkingDirectory
    Push-Location $workingDirectory
    Get-WebFile $url | Out-Null
    $localZipFilePath=Join-Path $workingDirectory $zipFileName
    $extractDirectory = Join-Path $workingDirectory ([IO.Path]::GetFileNameWithoutExtension($zipFileName))

    Get-ChocolateyUnzip $localZipFilePath $extractDirectory -Package $packageName | Out-Null
    Write-Debug "$zipFileName extracted to $extractDirectory"


$extractDirectory = DownloadAndExtractArchive $url 

$packageArgs = @{
  packageName   = $packageName
  fileType      = 'exe' 
  file = Join-Path $extractDirectory $exeFileName
  validExitCodes= @(0)

Install-ChocolateyInstallPackage @packageArgs


$ErrorActionPreference = 'Stop'; # stop on all errors

$packageName = 'freecommander-xe.install'
$softwareName = 'FreeCommander XE*' 
$installerType = 'EXE' 

$validExitCodes = @(0)

$uninstalled = $false
$local_key     = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key   = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'

[array]$key = Get-ItemProperty -Path @($machine_key6432,$machine_key, $local_key) `
                        -ErrorAction SilentlyContinue `
         | ? { $_.DisplayName -like "$softwareName" }

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

    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 | % {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.

Add to Builder Version Downloads Last Updated Status
FreeCommanderXE (Install) 2021.840 5569 Friday, December 18, 2020 Approved
FreeCommanderXE (Install) 2020.810.1 4828 Sunday, January 19, 2020 Approved
FreeCommanderXE (Install) 2020.810 594 Friday, January 3, 2020 Approved
FreeCommanderXE (Install) 2019.790.1 2073 Friday, April 26, 2019 Approved
FreeCommanderXE (Install) 2019.790.0.20181221 2408 Friday, December 21, 2018 Approved
FreeCommanderXE (Install) 2019.790 347 Thursday, December 20, 2018 Approved
FreeCommanderXE (Install) 2018.770 4344 Saturday, March 10, 2018 Approved
FreeCommanderXE (Install) 2017.740 328 Saturday, January 20, 2018 Approved
freecommander-xe.install (Install) 2016.715 3783 Sunday, April 24, 2016 Approved

This package has no dependencies.

Discussion for the freecommander-xe.install (Install) Package

Ground Rules:

  • This discussion is only about freecommander-xe.install (Install) and the freecommander-xe.install (Install) 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 freecommander-xe.install (Install), 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