Downloads of v 5.60:


Last Update:

05 Nov 2017

Package Maintainer(s):

Software Author(s):

  • Martin Malík


HWiNFO Monitoring Diagnostic


This is not the latest version of HWiNFO available.

  • 1
  • 2
  • 3

5.60 | Updated: 05 Nov 2017



Downloads of v 5.60:



Software Author(s):

  • Martin Malík

  • 1
  • 2
  • 3
HWiNFO 5.60

This is not the latest version of HWiNFO available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Failed


Scan Testing Successful:

No detections found in any package files


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


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


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

See docs at

chocolatey_package 'hwinfo' do
  action    :install
  version  '5.60'
  source   'STEP 3 URL'

See docs at

    Name: hwinfo,
    Version: 5.60,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller hwinfo
   Name     = 'hwinfo'
   Ensure   = 'Present'
   Version  = '5.60'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install hwinfo version="5.60" 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 is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 05 Nov 2017.


In-depth Hardware Information and real time monitoring

#Install-VirtualPackage 'HWiNFO.portable' 'HWiNFO.install'

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
HWiNFO 7.10 6730 Wednesday, September 1, 2021 Approved
HWiNFO 7.06 8022 Tuesday, July 6, 2021 Approved
HWiNFO 7.04 7776 Tuesday, May 18, 2021 Approved
HWiNFO 7.02 6897 Wednesday, April 7, 2021 Approved
HWiNFO 7.00 5833 Tuesday, March 9, 2021 Approved
HWiNFO 6.42 6714 Tuesday, January 26, 2021 Approved
HWiNFO 6.40 6630 Wednesday, December 9, 2020 Approved
HWiNFO 6.34 5430 Tuesday, November 3, 2020 Approved
HWiNFO 6.32 4778 Thursday, October 1, 2020 Approved
Discussion for the HWiNFO Package

Ground Rules:

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