Downloads of v 0.0.2:


Last Update:


Package Maintainer(s):

Software Author(s):

  • Rob Reynolds


checksum md5 sha1 hash


This is not the latest version of checksum available.

0.0.2 | Updated: 3/2/2014



Downloads of v 0.0.2:



Software Author(s):

  • Rob Reynolds

checksum 0.0.2

This is not the latest version of checksum available.

Some Checks Have Failed or Are Not Yet Complete

1 Test Unknown and 1 Passing Test

Validation Testing Unknown

Verification Testing Passed


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


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


To uninstall checksum, 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 checksum -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 checksum -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 checksum installed
    name: checksum
    state: present
    version: 0.0.2
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'checksum' do
  action    :install
  version  '0.0.2'
  source   'STEP 3 URL'

See docs at

    Name: checksum,
    Version: 0.0.2,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller checksum
   Name     = 'checksum'
   Ensure   = 'Present'
   Version  = '0.0.2'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install checksum version="0.0.2" 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 by moderator mwrock on 10/26/2014.


checksum - Command line file checksum validator.

checksum checks a file and returns a checksum for both md5 and sha1.
To use checksum you would simply provide a file path and it will return the sum for the file.

Example: checksum -f="relative\path"
Example: checksum "relative\path"
Example: checksum -f="c:\absolute\path" -t=sha1

You can also check against an existing signature.
To validate against an existing signature (hash) you would simply provide the file and the expected signature. When checking a signature, if the signature is valid it exits with 0, otherwise it exits with a non-zero exit code.

Example: checksum "c:\\path\to\somefile.exe" -c="thehash"
Example: checksum -f="c:\\path\to\somefile.exe" -c="thehash" -t=sha1


checksum [-t=sha1|md5] [-c=signature] [-f=]filepath


-?, --help, -h     
  Prints out the options.
-f, --file=VALUE
  REQUIRED: file - The is the name of the file. The file should exist
-t, --type, --hashtype=VALUE
  Optional: hashtype - 'md5' or 'sha1' Defaults to 'md5'.
-c, --check=VALUE
  Optional: check - the signature you want to check. Not case sensitive.

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
checksum 0.1.0 1598 Monday, September 5, 2016 Approved
checksum 0.0.3 726 Monday, September 28, 2015 Approved
checksum 0.0.2 968 Sunday, March 2, 2014 Approved
checksum 0.0.1 316 Saturday, March 1, 2014 Approved

This package has no dependencies.

Discussion for the checksum Package

Ground Rules:

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