Downloads of v


Last Update:

21 Mar 2020

Package Maintainer(s):

Software Author(s):

  • Microsoft


error code hresult ntstatus lookup

Microsoft Error Lookup Tool

  • 1
  • 2
  • 3 | Updated: 21 Mar 2020



Downloads of v



Software Author(s):

  • Microsoft

  • 1
  • 2
  • 3
Microsoft Error Lookup Tool

  • 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

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Microsoft Error Lookup Tool, run the following command from the command line or from PowerShell:


To upgrade Microsoft Error Lookup Tool, run the following command from the command line or from PowerShell:


To uninstall Microsoft Error Lookup Tool, 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 err -y --source="'INTERNAL REPO 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 err -y --source="'INTERNAL REPO URL'" 

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

Exit $exitCode

- name: Install err
    name: err
    version: ''
    state: present

See docs at

chocolatey_package 'err' do
  action    :install
  source   'INTERNAL REPO URL'
  version  ''

See docs at

cChocoPackageInstaller err
    Name     = "err"
    Version  = ""
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'err':
  ensure   => '',
  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.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator virtualex on 20 Apr 2020.


Use the Error Code Lookup tool to determine error values from decimal and hexadecimal error codes in Microsoft Windows® operating systems. The tool can look up one or more values at a time. All values on the command line will be looked up in the tool's internal tables (generated from Win32 API header files) and presented to you. If available, informational data associated with the value or values will also be shown. The tool is also able to show error codes associated with symbolic error names (e.g. E_FAIL).

This is a "point-in-time" tool. The Microsoft Error Lookup Tool decodes most Microsoft error codes as of the date on which the tool was compiled. As new releases of Windows add new event and error codes, you may have to download a new version of the Error Lookup Tool.

Run "err /?" for usage instructions.

$arguments = @{
    PackageName = $Env:ChocolateyPackageName
    FileFullPath = "$Env:ChocolateyPackageFolder\err.exe"
    Url = ''
    ChecksumType = 'sha256'
    Checksum = '88739EC82BA16A0B4A3C83C1DD2FCA6336AD8E2A1E5F1238C085B1E86AB8834A'
Get-ChocolateyWebFile @arguments

# remove any leftovers from older package versions
Remove-Item -Path "$Env:ChocolateyPackageFolder\Err" -Recurse -ErrorAction SilentlyContinue

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
Win32 error code look-up tool 6.0.4011.20150904 1306 Saturday, September 5, 2015 Approved Initial package release for software version 6.4.5. The err.exe file version number is 10.0.17763.1.

This package has no dependencies.

Discussion for the Microsoft Error Lookup Tool Package

Ground Rules:

  • This discussion is only about Microsoft Error Lookup Tool and the Microsoft Error Lookup Tool 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 Microsoft Error Lookup Tool, 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