Downloads of v


Last Update:

14 Apr 2014

Package Maintainer(s):

Software Author(s):

  • Zabkat


xplorer xplorer2 windows explorer file manager

xplorer² Pro

This is not the latest version of xplorer² Pro available.

  • 1
  • 2
  • 3 | Updated: 14 Apr 2014



Downloads of v


Software Author(s):

  • Zabkat

  • 1
  • 2
  • 3
xplorer² Pro

This is not the latest version of xplorer² Pro available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Unknown

Verification Testing Unknown

Scan Testing Successful:

No detections found in any package files


To install xplorer² Pro, run the following command from the command line or from PowerShell:


To upgrade xplorer² Pro, run the following command from the command line or from PowerShell:


To uninstall xplorer² Pro, 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 xplorer2pro -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 xplorer2pro -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 xplorer2pro installed
    name: xplorer2pro
    state: present
    source: STEP 3 URL

See docs at

chocolatey_package 'xplorer2pro' do
  action    :install
  version  ''
  source   'STEP 3 URL'

See docs at

    Name: xplorer2pro,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller xplorer2pro
   Name     = 'xplorer2pro'
   Ensure   = 'Present'
   Version  = ''
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install xplorer2pro version="" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 25 Dec 2015.


xplorer² is a desktop file manager combining the simplicity of windows explorer with the speed and efficiency of traditional dual pane orthodox file managers, helping you be productive with your documents, pictures, music, source code and other files.

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
xplorer² Pro (Trial) 52 Sunday, October 11, 2020 Approved
xplorer² Pro (Trial) 158 Thursday, May 14, 2020 Approved
xplorer² Pro (Trial) 148 Saturday, March 21, 2020 Approved
xplorer² Pro (Trial) 147 Friday, December 20, 2019 Approved
xplorer² Pro (Trial) 77 Thursday, November 21, 2019 Approved
xplorer² Pro (Trial) 69 Sunday, November 3, 2019 Approved
xplorer² Pro (Trial) 93 Monday, October 7, 2019 Approved
xplorer² Pro (Trial) 362 Monday, May 28, 2018 Approved
xplorer² Pro (Trial) 238 Monday, May 7, 2018 Approved

  • registry setting GAOPT_NOBROWSECPAN (=524288) controlling whether xplorer² browses into control panel items or not. For windows vista and later these "folders" are better handled by windows explorer
  • Edit > Copy names command works in the folder tree too. This in addition to CTRL+P command that copies all the active tree branch to the clipboard.
  • [P] docking panes have context menu (right click on titlebar) for various operations (dock/float/hide etc)
  • custom drive icons are read from AUTORUN.INF files (if present for removable drives)
  • corrected PDF text extraction for windows 8.1
  • repaired removable media EJECT command from shell context menu
  • picture thumbnails extracted from phones and cameras (thumbnail view and draft QV tab)
  • [U] running the professional version in parallel to ultimate doesn't disable fast desktop search
  • various small bugs fixed
  • [P] robust copy correctly handles file symbolic links (copies the link not the file). Sadly like all symlink operations you must be running as full administrator otherwise you get a funny error message.
  • [P] registry setting nUnbufferedCopyMB (default=1GB) sets a size limit above which robust copy is done without buffering. That supposedly fixes problems where your RAM is clogged by extremely huge file copying.
  • [P] When robust delete dialog encounters some reparse point (e.g. folder junction or symbolic link) only deletes the reparse information, without touching the target folder. This makes the "confirm folder junctions" checkbox in the dialog rather irrelevant.
  • More consistent handling of symbolic links, now you can see previews of them (text or pics) and even search for text in them (in the actual file target)
  • New files inserted in a pane (e.g. pasted or dropped) are marked (selected). This lets you see which files were newly added. This feature is controlled by local registry setting variable nMarkNewFileMS which is the time (in milliseconds) xplorer² waits after a file operation is initiated to mark added files. Set this to 0 to disable this new marking feature. If a pane contains a prior selection (>=2 selected items) then this feature is suppressed.
  • [U] Global registry value szSystemPropsList is a comma separated list of system properties to extend the file column and search attribute system. See here for the list of available properties: . Some of them are already available as shell folder columns but some are only available through this route. Requires windows VISTA or later.
  • in explorer replacement mode, "Open containing folder" menu command from 3rd party programs (e.g. Google Chrome, Firefox) will correctly open and select items in xplorer². This is by far the most time consuming (wasted?) feature added in xplorer² in terms of development resources, enjoy!
  • When you opt to replace windows explorer with xplorer² during installation, you get more folder types handled (including "virtuals" like MyComputer). Installer allows you to replace explorer for the current user or for all users with a tickbox. xplorer² is configured to automatically run when you boot up windows (silently).
  • In the rare occasions when xplorer² cannot read a special folder (e.g. some items in control panel), you get the option to read it with windows explorer instead.

This package has no dependencies.

Discussion for the xplorer² Pro Package

Ground Rules:

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