Downloads of v 6.9.0:


Last Update:

14 Dec 2020

Package Maintainer(s):

Software Author(s):

  • Resplendence Software Projects Sp.


Crash Dump Debugging

Who Crashed

  • 1
  • 2
  • 3

6.9.0 | Updated: 14 Dec 2020



Downloads of v 6.9.0:



Software Author(s):

  • Resplendence Software Projects Sp.

  • 1
  • 2
  • 3
Who Crashed 6.9.0

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


To install Who Crashed, run the following command from the command line or from PowerShell:


To upgrade Who Crashed, run the following command from the command line or from PowerShell:


To uninstall Who Crashed, 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 whocrashed -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 whocrashed -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 whocrashed installed
    name: whocrashed
    state: present
    version: 6.9.0
    source: STEP 3 URL

See docs at

chocolatey_package 'whocrashed' do
  action    :install
  version  '6.9.0'
  source   'STEP 3 URL'

See docs at

    Name: whocrashed,
    Version: 6.9.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller whocrashed
   Name     = 'whocrashed'
   Ensure   = 'Present'
   Version  = '6.9.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install whocrashed version="6.9.0" 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 14 Dec 2020.



The Free edition is only available for home use. Business users must purchase a professional license.

Analyzes existing crash dumps and tries to determine and state the root cause in easy to understand language.

$ErrorActionPreference = 'Stop'

$checksum = '5CFA6302B0A8D953FD38B9522E9A32B371E4107CDD072DD86C19C7483A020CA7'
$url = ''

$packageArgs = @{
  packageName   = 'whocrashed'
  unzipLocation = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
  fileType      = 'exe'
  url           = $url
  silentArgs    = '/VERYSILENT /NORESTART'
  validExitCodes= @(0, 3010, 1641)
  softwareName  = 'WhoCrashed*'
  checksum      = $checksum
  checksumType  = 'sha256'

Install-ChocolateyPackage @packageArgs

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
Who Crashed 32 Saturday, December 26, 2020 Approved
Who Crashed 6.6.5 1498 Tuesday, July 9, 2019 Approved
Who Crashed 6.6.1 293 Monday, June 3, 2019 Approved
Who Crashed 6.6.0 488 Saturday, February 23, 2019 Approved
Who Crashed 6.5.0 305 Tuesday, January 22, 2019 Approved
Who Crashed 6.01 1367 Saturday, July 7, 2018 Approved
Who Crashed 5.53 1212 Sunday, November 6, 2016 Approved
Who Crashed 5.03 611 Friday, January 15, 2016 Approved

This package has no dependencies.

Discussion for the Who Crashed Package

Ground Rules:

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