Downloads:

54,280

Downloads of v 5.10:

258

Last Update:

12/23/2015

Package Maintainer(s):

Software Author(s):

  • Martin Malík

Tags:

HWiNFO Monitoring Diagnostic

HWiNFO (Install)

This is not the latest version of HWiNFO (Install) available.

5.10 | Updated: 12/23/2015

Downloads:

54,280

Downloads of v 5.10:

258

Maintainer(s):

Software Author(s):

  • Martin Malík

HWiNFO (Install) 5.10

This is not the latest version of HWiNFO (Install) available.

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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

>

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

>

To uninstall HWiNFO (Install), 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 https://chocolatey.org/api/v2. 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 https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade hwinfo.install -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.install -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure hwinfo.install installed
  win_chocolatey:
    name: hwinfo.install
    state: present
    version: 5.10
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

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


chocolatey_package 'hwinfo.install' do
  action    :install
  version  '5.10'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: hwinfo.install,
    Version: 5.10,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller hwinfo.install
{
   Name     = 'hwinfo.install'
   Ensure   = 'Present'
   Version  = '5.10'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'hwinfo.install':
  provider => 'chocolatey',
  ensure   => '5.10',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install hwinfo.install version="5.10" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

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 by moderator gep13 on 1/6/2016.

Description

In-depth Hardware Information and real time monitoring


tools\chocolateyinstall.ps1
$PSScriptRoot = Split-Path -Parent $MyInvocation.MyCommand.Definition
Import-Module "$PSScriptRoot\Get-UrlFromFosshub.ps1"

$packageName = 'HWiNFO.install'
$fileType = 'exe'
$silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART'
$version = '5.10'
$version = $version.Replace(".","")
$url = Get-UrlFromFosshub "http://www.fosshub.com/genLink/HWiNFO/hw32_$version.exe"
$url64 = Get-UrlFromFosshub "http://www.fosshub.com/genLink/HWiNFO/hw64_$version.exe"
$checksum = '3a444a081bc892515332dc910c8cb104e4305133'
$checksumType = 'SHA1'
$checksum64 = '264295269ccd53ce9992a0f319f4e19a5a907e58'
$checksumType64 = 'SHA1'

Install-ChocolateyPackage $packageName $fileType $silentArgs $url $url64 -checksum $checksum -checksumType $checksumType -checksum64 $checksum64 -checksumType64 $checksumType64
# Kill the process after it starts- there is no way to prevent autostart after install
Get-Process | Where { $_.name -eq 'HWiNFO64' } | Stop-Process
tools\chocolateyuninstall.ps1
$packageName = 'HWiNFO'
$shouldUninstall = $true

$machine_key   = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\HWiNFO64_is1'
# 32bit version will be here on a 32bit OS
$machine_key32  = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\HWiNFO32_is1'
# If you installed the 32bit version on a 64bit OS you're doing it wrong
# But I'm covering that eventuality here anyway.
$machine_key6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\HWiNFO32_is1'

$file = @($machine_key, $machine_key32, $machine_key6432) `
    | ?{ Test-Path $_ } `
    | Get-ItemProperty `
    | Select-Object -ExpandProperty UninstallString

if ($file -eq $null -or $file -eq '') {
    Write-Host "$packageName has already been uninstalled by other means."
    $shouldUninstall = $false
}

$installerType = 'EXE' 
$silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART'
$validExitCodes = @(0)

# I can't explain why this doesn't work, my powershell is not strong
#if (!(Test-Path $file)) {
#    Write-Host "$packageName has already been uninstalled by other means."
#    $shouldUninstall = $false
#}

if ($shouldUninstall) {
 Uninstall-ChocolateyPackage -PackageName $packageName -FileType $installerType -SilentArgs $silentArgs -validExitCodes $validExitCodes -File $file
}
tools\Get-UrlFromFosshub.ps1
# Get the resolved URL form a FossHub download link.
#
# Takes a FossHub URL in the “genLink” format and returns the generated expiring download link for the file which can
# be used for downloading with Ketarin/Chocolatey.
#
# Usage: Get-UrlFromFosshub genLink_url
# Examples:
# Get-UrlFromFosshub http://www.fosshub.com/genLink/Light-Alloy/LA_Setup_v4.8.8.exe

Function Get-UrlFromFosshub($genLinkUrl) {

  $fosshubAppName = $genLinkUrl -match 'genLink/(.+?)/'

  # If there’s no match, it means that it’s not a FossHub genLink-URL.
  # Then this function simply returns the input URL.
  if (!$Matches) {
    return $genLinkUrl
  }

  # Get the actual FossHub appname from the matches array
  $fosshubAppName = $Matches[1]


  $referer = "http://www.fosshub.com/${fosshubAppName}.html"

  $webClient = New-Object System.Net.WebClient
  $webClient.Headers.Add("Referer", $referer)

  $generatedLink = $webClient.DownloadString($genLinkUrl)

  return $generatedLink
}

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 (Install) 6.10 4250 Wednesday, July 31, 2019 Approved
HWiNFO (Install) 6.08 3298 Wednesday, June 19, 2019 Approved
HWiNFO (Install) 6.06 2842 Thursday, May 16, 2019 Approved
HWiNFO (Install) 6.04 2974 Wednesday, April 3, 2019 Approved
HWiNFO (Install) 6.02 2843 Friday, February 22, 2019 Approved
HWiNFO (Install) 6.00 3179 Thursday, December 20, 2018 Approved
HWiNFO (Install) 5.92 2015 Thursday, November 22, 2018 Approved
HWiNFO (Install) 5.90 2035 Tuesday, October 16, 2018 Approved
HWiNFO (Install) 5.88 2068 Tuesday, September 4, 2018 Approved

This package has no dependencies.

Discussion for the HWiNFO (Install) Package

Ground Rules:

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