Downloads:
12,323
Downloads of v 4.60:
977
Last Update:
03 Aug 2015
Package Maintainer(s):
Software Author(s):
- H.D.S. Hungary.
Tags:
hdd-monitor disk-analyzer disk-temperature monitor analyzer analyze prevent- Software Specific:
- Software Site
- Software License
- Package Specific:
- Possible Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Hard Disk Sentinel
This is not the latest version of Hard Disk Sentinel available.
- 1
- 2
- 3
4.60 | Updated: 03 Aug 2015
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Possible Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
12,323
Downloads of v 4.60:
977
Maintainer(s):
Software Author(s):
- H.D.S. Hungary.
Hard Disk Sentinel 4.60
This is not the latest version of Hard Disk Sentinel available.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Hard Disk Sentinel, run the following command from the command line or from PowerShell:
To upgrade Hard Disk Sentinel, run the following command from the command line or from PowerShell:
To uninstall Hard Disk Sentinel, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
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
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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://community.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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download hdsentinel --internalize --version=4.60 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade hdsentinel -y --source="'INTERNAL REPO URL'" --version="'4.60'" [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 hdsentinel -y --source="'INTERNAL REPO URL'" --version="'4.60'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install hdsentinel
win_chocolatey:
name: hdsentinel
version: '4.60'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'hdsentinel' do
action :install
source 'INTERNAL REPO URL'
version '4.60'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller hdsentinel
{
Name = "hdsentinel"
Version = "4.60"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'hdsentinel':
ensure => '4.60',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
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 ferventcoder on 28 Dec 2015.
Hard Disk Sentinel (HDSentinel) is a multi-OS SSD and HDD monitoring and analysis software. Its goal is to find, test, diagnose and repair hard disk drive problems, report and display SSD and HDD health, performance degradations and failures. Hard Disk Sentinel gives complete textual description, tips and displays/reports the most comprehensive information about the hard disks and solid state disks inside the computer and in external enclosures (USB hard disks / e-SATA hard disks). Many different alerts and report options are available to ensure maximum safety of your valuable data.
No need to use separate tools to verify internal hard disks, external hard disks, SSDs, disks in RAID arrays as these are all included in a single software.
Hard Disk Sentinel monitors hard disk drive / HDD status including health, temperature and all S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology) values for all hard disks. Also it measures the disk transfer speed in real time which can be used as a benchmark or to detect possible hard disk failures, performance degradations.
HDSentinel is the perfect data protection solution: it can be effectively used to prevent HDD failure and SSD / HDD data loss because it has the most sensitive disk health rating system which is extremely sensitive to disk problems. This way even a small HDD problem can't be missed. The Professional version has scheduled and automatic (on-problem) disk backup options to prevent data loss caused by not only failure but by malware or accidental delete also.
This is a commercial product, with a 30 day trial. This package is for a Standard version. For details about different versions and pricing go to http://www.hdsentinel.com/hard_disk_sentinel.php
Please Note: This is an automatically updated package. If you find it is out of date by more than a day or two, please contact the maintainer(s) and let them know the package is no longer updating correctly.
. (Join-Path (Split-Path -parent $MyInvocation.MyCommand.Definition) 'helpers\helpers.ps1')
$packageTitle = "Hard Disk Sentinel"
$trySilent = 1;
$silentArgs = "/sp- /verysilent /norestart"
try {
AutoUninstall `
-programName $packageTitle `
-trySilent $trySilent `
-silentargs $silentArgs
} catch {
throw $_.Exception
}
# ====================================================
# GetMenuStartPath
# ====================================================
# Grabs Menu Start location from registry.
#
# @return {string} Menu Start path
# ====================================================
Function GetMenuStartPath(){
return (Get-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders")."Start Menu"
}
# ====================================================
# GetUninstallString
# ====================================================
# Searches Registry for the uninstall string
#
# @param {string} $programName Regex pattern for full program name, as its referred to in registry
# @param {bool} $trySilent Try checking for silent uninstall string?
# @param {bool} $skipMsi Should MSi be ignored (if EXE takes care of them automatically)
# @return {string} Full uninstall path (no flags)
# ====================================================
Function GetUninstallString{
param(
[string] $programName,
[bool] $trySilent = 0,
[bool] $skipMsi = 0
)
$uninstallType = "UninstallString"
# establish all possible locations for uninstaller to be stored
$local_key = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall'
$machine_key32 = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall'
$machine_key64 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall'
$reg_locations = @()
if(Test-Path "$local_key"){
$reg_locations += "$local_key\*"
}
if(Test-Path "$machine_key32"){
$reg_locations += "$machine_key32\*"
}
if( ((Get-WmiObject Win32_Processor).AddressWidth -eq 64) -and (Test-Path "$machine_key64") ) {
$reg_locations += "$machine_key64\*"
}
if($trySilent){
$uninstallType = "QuietUninstallString"
}
$uninstallers = ( `
Get-ItemProperty -Path $reg_locations | `
?{ $_.DisplayName -match "$programName" } `
) | `
?{ $_.$uninstallType -ne $null} | `
select -exp $uninstallType -unique
if($skipMsi -eq 1){
$uninstallers = $uninstallers | ?{ $_ -notmatch "^msiexec*"}
}
# find and return the actual uninstaller path
return $uninstallers
}
# ====================================================
# AutoUninstall
# ====================================================
# Tries to autouninstall a package
#
# @param {string} $programName (required) Full program name, as its referred to in registry
# @param {bool} $trySilent (optional) Try checking for silent uninstall string?
# @param {bool} $skipMsi Should MSi be ignored (if EXE takes care of them automatically)
# @param {string} $silentArgs (optional) Additional silent uninstall arguments to
# be added to the ones detected in registry
# @param {object} $ValidExitCodes (optional) Passing exit codes
# @return {void}
# ====================================================
Function AutoUninstall {
param(
[string] $programName,
[bool] $trySilent = 0,
[bool] $skipMsi = 0,
[string] $silentArgs = '',
$validExitCodes = @(0)
)
try {
$uninstallers = GetUninstallString `
-programName $programName `
-trySilent $trySilent `
-skipMsi $skipMsi
# determine the name we're searching for in registry
$uninstallerRegistryQuery = "UninstallString"
if($trySilent -eq 1){
$uninstallerRegistryQuery = "QuietUninstallString"
}
#loop through all returned strings and trigger corresponding uninstaller
if($uninstallers){
ForEach ($uninstaller in $uninstallers) {
$chocoUninst = 1
# define vars for default MSI
if($uninstaller -like "MsiExec.exe /x*"){
$uninstaller = ($uninstaller -replace '^.*?\{(.*?)\}', '{$1}')
$installerType = "msi"
$silentArgs += " /qn"
# define vars for msi with /i flag
}elseif($uninstaller -like "MsiExec.exe /i*"){
$chocoUninst = 0;
$uninstaller = ($uninstaller -replace '^MsiExec.exe ', '')
$silentArgs += " /qn"
# define vars for EXE
}else{
# if there are any flags passed, extract them, otherwise PS/Chocolatey will freak out
if($uninstaller -match '^.*?\.exe\"\s*?\/.*$'){
$silentArgs += ($uninstaller -replace '^.*?\.exe\"\s+(.*?)$', ' $1')
$uninstaller = ($uninstaller -replace '^(.*?\.exe\")\s+.*?$', '$1')
}
$installerType = "exe"
}
# uninstall package
if($chocoUninst -eq 1){
Uninstall-ChocolateyPackage `
-PackageName "$programName" `
-FileType $installerType `
-SilentArgs "$($silentArgs)" `
-File "$($uninstaller)" `
-ValidExitCodes $validExitCodes
}else{
Start-ChocolateyProcessAsAdmin "$($uninstaller)" 'msiexec' -validExitCodes $validExitCodes
}
}
}
} catch {
throw $_.Exception
}
}
# ====================================================
# GetBinRoot
# ====================================================
# Negotiates BinRoot path
#
# @return {string} Full binroot path
# ====================================================
Function GetBinRoot(){
$path = 'C:\tools'
if($env:ChocolateyBinRoot -ne $null){
$path = $env:ChocolateyBinRoot
}
return $path
}
# ====================================================
# KillAsap
# ====================================================
# Kills process as soon as it launches
#
# @param {string} Process Name
# @return {void}
# ====================================================
Function KillAsap([string]$appName){
if($appName -ne $null){
$process = (Get-Process $($appName))
if(!$process){
start-sleep -m 250
KillAsap $appName
}else{
$process | Stop-Process -force
}
}
}
# ====================================================
# Import-Certificate
# ====================================================
# Function to import security certificates.
# NOTE: To get a list of available store names, run the following command:
# dir cert: | Select -Expand StoreNames
#
# Example Usages:
# Import-Certificate -CertFile "VeriSign_Expires-2028.08.01.cer" -StoreNames AuthRoot, Root -LocalMachine
# Import-Certificate -CertFile "VeriSign_Expires-2018.05.18.p12" -StoreNames AuthRoot -LocalMachine -CurrentUser -CertPassword Password -Verbose
# dir -Path C:\Certs -Filter *.cer | Import-Certificate -CertFile $_ -StoreNames AuthRoot, Root -LocalMachine -Verbose
#
# @src http://poshcode.org/3518
# @depends Powershell 2+
#
# @param {string} $CertFile Full path to .crt file
# @param {list} $StoreNames Comma separated list of strings corresponding to Crtificate shops:
# SmartCardRoot | UserDS | AuthRoot | CA | Trust | Disallowed | My |
# Root | TrustedPeople | TrustedPublisher
# @param {bool} $LocalMachine Using the local machine certificate store to import the certificate
# @param {bool} $CurrentUser Using the current user certificate store to import the certificate
# @param {string} $CertPassword The password which may be used to protect the certificate file
# @param {bool} $Verbose Spit out stuff
# @return {string} Full uninstall path (no flags)
# ====================================================
# Function to import security certificates.
# http://poshcode.org/3518
# NOTE: To get a list of available store names, run the following command:
# dir cert: | Select -Expand StoreNames
#
Function Import-Certificate{
param
(
[IO.FileInfo] $CertFile = $(throw "Paramerter -CertFile [System.IO.FileInfo] is required."),
[string[]] $StoreNames = $(throw "Paramerter -StoreNames [System.String] is required."),
[switch] $LocalMachine,
[switch] $CurrentUser,
[string] $CertPassword,
[switch] $Verbose
)
begin
{
[void][System.Reflection.Assembly]::LoadWithPartialName("System.Security")
}
process
{
if ($Verbose)
{
$VerbosePreference = 'Continue'
}
if (-not $LocalMachine -and -not $CurrentUser)
{
Write-Warning "One or both of the following parameters are required: '-LocalMachine' '-CurrentUser'. Skipping certificate '$CertFile'."
}
try
{
if ($_)
{
$certfile = $_
}
$cert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 $certfile,$CertPassword
}
catch
{
Write-Error ("Error importing '$certfile': $_ .") -ErrorAction:Continue
}
if ($cert -and $LocalMachine)
{
$StoreScope = "LocalMachine"
$StoreNames | ForEach-Object {
$StoreName = $_
if (Test-Path "cert:\$StoreScope\$StoreName")
{
try
{
$store = New-Object System.Security.Cryptography.X509Certificates.X509Store $StoreName, $StoreScope
$store.Open([System.Security.Cryptography.X509Certificates.OpenFlags]::ReadWrite)
$store.Add($cert)
$store.Close()
Write-Verbose "Successfully added '$certfile' to 'cert:\$StoreScope\$StoreName'."
}
catch
{
Write-Error ("Error adding '$certfile' to 'cert:\$StoreScope\$StoreName': $_ .") -ErrorAction:Continue
}
}
else
{
Write-Warning "Certificate store '$StoreName' does not exist. Skipping..."
}
}
}
if ($cert -and $CurrentUser)
{
$StoreScope = "CurrentUser"
$StoreNames | ForEach-Object {
$StoreName = $_
if (Test-Path "cert:\$StoreScope\$StoreName")
{
try
{
$store = New-Object System.Security.Cryptography.X509Certificates.X509Store $StoreName, $StoreScope
$store.Open([System.Security.Cryptography.X509Certificates.OpenFlags]::ReadWrite)
$store.Add($cert)
$store.Close()
Write-Verbose "Successfully added '$certfile' to 'cert:\$StoreScope\$StoreName'."
}
catch
{
Write-Error ("Error adding '$certfile' to 'cert:\$StoreScope\$StoreName': $_ .") -ErrorAction:Continue
}
}
else
{
Write-Warning "Certificate store '$StoreName' does not exist. Skipping..."
}
}
}
}
end
{ }
}
# Chocolatey Helpers
set of Powershell helpers to be used for creating [Chocolatey](https://chocolatey.org/) packages.
To be used as submodules, rather than standalone.
Log in or click on link to see number of positives.
- hdsentinel.4.60.nupkg (ed8eeb3c01b6) - ## / 56
- hdsentinel_setup.zip (ebe94b998940) - ## / 54
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 |
---|---|---|---|---|
Hard Disk Sentinel 6.10.4 | 1315 | Wednesday, September 6, 2023 | Approved | |
Hard Disk Sentinel 5.70 | 4573 | Saturday, September 11, 2021 | Approved | |
Hard Disk Sentinel 5.61 | 2608 | Tuesday, June 9, 2020 | Approved | |
Hard Disk Sentinel 5.60 | 656 | Tuesday, February 25, 2020 | Approved | |
Hard Disk Sentinel 5.50 | 544 | Saturday, August 10, 2019 | Approved | |
Hard Disk Sentinel 5.40 | 443 | Monday, March 25, 2019 | Approved | |
Hard Disk Sentinel 5.30 | 713 | Monday, July 23, 2018 | Approved | |
Hard Disk Sentinel 5.20 | 363 | Wednesday, May 16, 2018 | Approved | |
Hard Disk Sentinel 4.60 | 977 | Monday, August 3, 2015 | Approved |
© 2015 H.D.S. Hungary. All Rights Reserved.
This package has no dependencies.
Ground Rules:
- This discussion is only about Hard Disk Sentinel and the Hard Disk Sentinel 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 Hard Disk Sentinel, 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.