Downloads:

2,800,029

Downloads of v 2017.12.13:

14,341

Last Update:

13 Dec 2017

Package Maintainer(s):

Software Author(s):

  • Mark Russinovich
  • Bryce Cogswell

Tags:

sysinternals troubleshooting pstools psexec file disk utilities freeware cli tools portable

Sysinternals

This is not the latest version of Sysinternals available.

2017.12.13 | Updated: 13 Dec 2017

Downloads:

2,800,029

Downloads of v 2017.12.13:

14,341

Maintainer(s):

Software Author(s):

  • Mark Russinovich
  • Bryce Cogswell

Tags:

sysinternals troubleshooting pstools psexec file disk utilities freeware cli tools portable

Sysinternals 2017.12.13

This is not the latest version of Sysinternals available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

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

>

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

>

To uninstall Sysinternals, 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 sysinternals -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 sysinternals -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 sysinternals installed
  win_chocolatey:
    name: sysinternals
    state: present
    version: 2017.12.13
    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 'sysinternals' do
  action    :install
  version  '2017.12.13'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: sysinternals,
    Version: 2017.12.13,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller sysinternals
{
   Name     = 'sysinternals'
   Ensure   = 'Present'
   Version  = '2017.12.13'
   Source   = 'STEP 3 URL'
}

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


package { 'sysinternals':
  provider => 'chocolatey',
  ensure   => '2017.12.13',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install sysinternals version="2017.12.13" 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.

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

This package was approved as a trusted package on 13 Dec 2017.

Description

The Sysinternals Troubleshooting Utilities have been rolled up into a single suite of tools.
This file contains the individual troubleshooting tools and help files.
It does not contain non-troubleshooting tools like the BSOD Screen Saver or NotMyFault.

Package parameters

  • /InstallDir - Installation directory, by default Chocolatey tools directory.
  • /InstallationPath - the same as InstallDir

Notes

  • This package by default installs to tools directory which will create shims for all applications. When you install to different directory, shims are not created but directory is added to the PATH.
  • This package now downloads the nano edition of sysinternals on nano servers.
tools\chocolateyInstall.ps1 
$toolsPath = Split-Path $MyInvocation.MyCommand.Definition
. $toolsPath\helpers.ps1

$pp = Get-PackageParameters
$installDir = $toolsPath
if ($pp.InstallDir -or $pp.InstallationPath ) { $InstallDir = $pp.InstallDir + $pp.InstallationPath }
Write-Host "Sysinternals Suite is going to be installed in '$installDir'"

$packageArgs = @{
  packageName    = 'sysinternals'
  url            = 'https://download.sysinternals.com/files/SysinternalsSuite.zip'
  checksum       = '522d1b52e9a1ef15663b34fb7494a28f81e30376243e0d9d453c9f27219955ac'
  checksumType   = 'sha256'
  unzipLocation  = $installDir
}
Install-ChocolateyZipPackage @packageArgs
Accept-Eula
if ($installDir -ne $toolsPath) { Install-ChocolateyPath $installDir }
if (Is-NanoServer) {
  $packageArgs.url = 'https://download.sysinternals.com/files/SysinternalsSuite-Nano.zip'
  $packageArgs.checksum = '369c8906e82d51bfa0a636392aa9d8ecc0ed025609aabead8ea18d5925a2761e'
 }

$old_path = 'c:\sysinternals'
if ((Test-Path $old_path) -and ($installDir -ne $old_path)) {
    Write-Warning "Clean up older versions of this install at c:\sysinternals"
}
tools\helpers.ps1 
function Accept-Eula() {

$tools = `
"AccessChk",        "Active Directory Explorer", "ADInsight",  "Autologon",       "AutoRuns",
"BGInfo",           "CacheSet",                  "ClockRes",   "Coreinfo",        "Ctrl2cap",
"DbgView",          "Desktops",                  "Disk2Vhd",   "Diskmon",         "DiskView",
"Du",               "EFSDump",                   "FindLinks",  "Handle",          "Hex2Dec",
"Junction",         "LdmDump",                   "ListDLLs",   "LoadOrder",       "Movefile",
"PageDefrag",       "PendMove",                  "PipeList",   "Portmon",         "ProcDump",
"Process Explorer", "Process Monitor",           "PsExec",     "psfile",          "PsGetSid",
"PsInfo",           "PsKill",                    "PsList",     "PsLoggedon",      "PsLoglist",
"PsPasswd",         "PsService",                 "PsShutdown", "PsSuspend",       "RamMap",
"RegDelNull",       "Regjump",                   "Regsize",    "RootkitRevealer", "Share Enum",
"ShellRunas",       "SigCheck",                  "Streams",    "Strings",         "Sync",
"System Monitor",   "TCPView",                   "VMMap",      "VolumeID",        "Whois",
"Winobj",           "ZoomIt"

    $root_path = "HKCU:\SOFTWARE\Sysinternals"
    mkdir "$root_path" -ea 0 | Out-Null
    foreach($tool in $tools) {
        mkdir "$root_path\$tool" -ea 0 | Out-Null
        New-ItemProperty -Path "$root_path\$tool" -Name EulaAccepted -Value 1 -Force | Out-Null
    }

    $vt = "$root_path\SigCheck\VirusTotal"
    mkdir $vt -ea 0 | Out-Null
    New-ItemProperty -Path $vt -Name VirusTotalTermsAccepted -Value 1 -Force | Out-Null
}

function Is-NanoServer() {
  # This would be true for both nano servers, and IoT devices.
  if ($PSVersionTable.PSEdition -ne 'Core') { return $false }

  # 143 = Datacenter nano server
  # 144 = Standard nano server
  $sku = (Get-CimInstance -ClassName Win32_OperatingSystem).OperatingSystemSKU
  return ($sku -eq 143) -or ($sku -eq 144);
}

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
Sysinternals 2019.12.19 57963 Thursday, December 19, 2019 Approved
Sysinternals 2019.12.11 42027 Thursday, December 12, 2019 Approved
Sysinternals 2019.9.23 106928 Monday, September 23, 2019 Approved
Sysinternals 2019.9.16 21674 Monday, September 16, 2019 Approved
Sysinternals 2019.9.5 38032 Friday, September 6, 2019 Approved
Sysinternals 2019.6.29.20190904 13590 Wednesday, September 4, 2019 Approved
Sysinternals 2019.6.29 183575 Saturday, June 29, 2019 Approved
Sysinternals 2019.6.14 26040 Friday, June 14, 2019 Approved
Sysinternals 2019.6.12 10042 Thursday, June 13, 2019 Approved
Sysinternals 2019.6.11 10140 Wednesday, June 12, 2019 Approved
Discussion for the Sysinternals Package

Ground Rules:

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