Create a Custom Detection Script for Process Hacker (PowerShell)

Microsoft Endpoint Manager Configuration Manager (MEMCM / SCCM) and Microsoft Intune use Detection Rules to determine the presence of Applications & Win32 Apps. The detection rules ensure that application installations only begin to run if the application is not already installed on the device. This article will serve as an informative guide and give you a clear understanding of how to create an updated custom detection script for each new version of Process Hacker using PowerShell.

How to Create a Custom Detection Script for Process Hacker

Process Hacker (File Detection Method)

## Check for Process Hacker (File Detection Method)
$ProcessHackerExe = (Get-ChildItem -Path "C:\Program Files\Process Hacker*\ProcessHacker.exe" -ErrorAction SilentlyContinue)
$ProcessHackerExe.FullName
$ProcessHackerPath = $($ProcessHackerExe.FullName).Replace("C:\Program Files\","")
$FileVersion = (Get-Item -Path "$($ProcessHackerExe.FullName)" -ErrorAction SilentlyContinue).VersionInfo.FileVersion

## Create Text File with Process Hacker File Detection Method
$FilePath = "C:\Windows\Temp\Process_Hacker_Detection_Method.txt"
New-Item -Path "$FilePath" -Force
Set-Content -Path "$FilePath" -Value "If([String](Get-Item -Path `"`$Env:ProgramFiles\$ProcessHackerPath`" -ErrorAction SilentlyContinue).VersionInfo.FileVersion -ge `"$FileVersion`"){"
Add-Content -Path "$FilePath" -Value "Write-Host `"Installed`""
Add-Content -Path "$FilePath" -Value "Exit 0"
Add-Content -Path "$FilePath" -Value "}"
Add-Content -Path "$FilePath" -Value "else {"
Add-Content -Path "$FilePath" -Value "Exit 1"
Add-Content -Path "$FilePath" -Value "}"
Invoke-Item $FilePath
  • Click Run Script (F5)
  • A text file will open with the Process Hacker Detection Method script required to detect the current version of Process Hacker that is installed on the device you are running the script from.

Example:

If([String](Get-Item -Path "$Env:ProgramFiles\Process Hacker 2\ProcessHacker.exe" -ErrorAction SilentlyContinue).VersionInfo.FileVersion -ge "2.39.0.124"){
Write-Host "Installed"
Exit 0
}
else {
Exit 1
}

Process Hacker (Registry Detection Method)

## Check for Process Hacker (Registry Detection Method)
$ProcessHacker = Get-ChildItem -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" | Get-ItemProperty | Where-Object {$_.DisplayName -match 'Process Hacker' } | Select-Object -Property DisplayName, DisplayVersion, PSChildName
$ProcessHacker.DisplayVersion
$ProcessHacker.PSChildName

## Create Text File with Process Hacker Registry Detection Method
$FilePath = "C:\Windows\Temp\Process_Hacker_Detection_Method.txt"
New-Item -Path "$FilePath" -Force
Set-Content -Path "$FilePath" -Value "If([Version](Get-ItemPropertyValue -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\$($ProcessHacker.PSChildName)' -Name DisplayVersion -ea SilentlyContinue) -ge '$($ProcessHacker.DisplayVersion)') {"
Add-Content -Path "$FilePath" -Value "Write-Host `"Installed`""
Add-Content -Path "$FilePath" -Value "Exit 0"
Add-Content -Path "$FilePath" -Value "}"
Add-Content -Path "$FilePath" -Value "else {"
Add-Content -Path "$FilePath" -Value "Exit 1"
Add-Content -Path "$FilePath" -Value "}"
Invoke-Item $FilePath
  • Click Run Script (F5)
  • A text file will open with the Process Hacker Detection Method script required to detect the current version of Process Hacker that is installed on the device you are running the script from.

Example:

If([Version](Get-ItemPropertyValue -Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Process_Hacker2_is1' -Name DisplayVersion -ea SilentlyContinue) -ge '2.39.0.124') {
Write-Host "Installed"
Exit 0
}
else {
Exit 1
}

Always make sure to test everything in a development environment prior to implementing anything into production. The information in this article is provided “As Is” without warranty of any kind.