Downloads of v


Last Update:

25 Mar 2018

Package Maintainer(s):

Software Author(s):

  • Eric Zimmerman


registry deleted plugin forensics

Registry Explorer

This is not the latest version of Registry Explorer available. | Updated: 25 Mar 2018



Downloads of v



Software Author(s):

  • Eric Zimmerman

Registry Explorer

This is not the latest version of Registry Explorer available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install Registry Explorer, run the following command from the command line or from PowerShell:


To upgrade Registry Explorer, run the following command from the command line or from PowerShell:


To uninstall Registry Explorer, 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 registryexplorer -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 registryexplorer -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 registryexplorer installed
    name: registryexplorer
    state: present
    source: STEP 3 URL

See docs at

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

See docs at

    Name: registryexplorer,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

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

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install registryexplorer 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 Mar 2018.


Supports recovery of deleted keys and values, multi hive support, the fastest searching, viewing slack space, plugin support, and much more

$checksum      = '7b61f38c88595014583b7f12650e9231e19ee940b30731b17c9331726d47bcbd'
$checksumType  = 'sha256'

$unzipTo = Join-Path $env:chocolateyPackageFolder "tools"

Install-ChocolateyZipPackage -PackageName 'registryexplorer' -UnzipLocation $unzipTo -Checksum $checksum -ChecksumType $checksumType

$desktop = $([System.Environment]::GetFolderPath([System.Environment+SpecialFolder]::DesktopDirectory))

$link = Join-Path $desktop "Registry Explorer.lnk"
$target = Join-Path $env:chocolateyPackageFolder "tools\RegistryExplorer.exe"
$work = Join-Path $env:chocolateyPackageFolder "tools"
Install-ChocolateyShortcut -ShortcutFilePath $link -TargetPath $target -WorkingDirectory $work -RunAsAdmin

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

$packageName = 'registryexplorer'
$softwareName = 'registryexplorer*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique

$desktop = $([System.Environment]::GetFolderPath([System.Environment+SpecialFolder]::DesktopDirectory))

$link = Join-Path $desktop "Registry Explorer.lnk"

Remove-Item $link

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
Registry Explorer 276 Thursday, January 17, 2019 Approved
Registry Explorer 210 Sunday, January 13, 2019 Approved
Registry Explorer 269 Tuesday, December 18, 2018 Approved
Registry Explorer 136 Tuesday, December 18, 2018 Approved
Registry Explorer 289 Sunday, November 25, 2018 Approved
Registry Explorer 328 Monday, October 8, 2018 Approved
Registry Explorer 232 Wednesday, September 19, 2018 Approved
Registry Explorer 144 Monday, September 17, 2018 Approved

This package has no dependencies.

Discussion for the Registry Explorer Package

Ground Rules:

  • This discussion is only about Registry Explorer and the Registry Explorer 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 Registry Explorer, 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