Downloads:

1,491

Downloads of v 3.13:

22

Last Update:

13 Oct 2021

Package Maintainer(s):

Software Author(s):

  • Mark Russinovich

Tags:

object namespace object-manager security debug tools sysinternals

WinObj - Windows Sysinternals

  • 1
  • 2
  • 3

3.13 | Updated: 13 Oct 2021

Downloads:

1,491

Downloads of v 3.13:

22

Maintainer(s):

Software Author(s):

  • Mark Russinovich

  • 1
  • 2
  • 3
WinObj - Windows Sysinternals 3.13

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

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

>

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

>

To uninstall WinObj - Windows 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://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

3. Enter your internal repository url

(this should look similar to https://community.chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade winobj -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 winobj -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 winobj installed
  win_chocolatey:
    name: winobj
    state: present
    version: 3.13
    source: STEP 3 URL

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


chocolatey_package 'winobj' do
  action    :install
  version  '3.13'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: winobj,
    Version: 3.13,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller winobj
{
   Name     = 'winobj'
   Ensure   = 'Present'
   Version  = '3.13'
   Source   = 'STEP 3 URL'
}

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


package { 'winobj':
  provider => 'chocolatey',
  ensure   => '3.13',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install winobj version="3.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 Oct 2021.

Description

WinObj is a must-have tool if you are a system administrator concerned about security, a developer tracking down
object-related problems, or just curious about the Object Manager namespace.

WinObj is a 32-bit Windows NT program that uses the native Windows NT API (provided by NTDLL.DLL) to access and display
information on the NT Object Manager's name space. Winobj may seem similar to the Microsoft SDK's program of the same
name, but the SDK version suffers from numerous significant bugs that prevent it from displaying accurate information
(e.g. its handle and reference counting information are totally broken). In addition, our WinObj understands many more
object types. Finally, Version 2.0 of our WinObj has user-interface enhancements, knows how to open device objects, and
will let you view and change object security information using native NT security editors.

screenshot

Notes

  • This package is automatically updated using the Chocolatey Automatic Package Update Model (AU).
    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.

tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

$toolsDir = (Split-Path -parent $MyInvocation.MyCommand.Definition)

$regRoot = 'HKCU:\Software\Sysinternals'
$regPkg  = 'Winobj'

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = $toolsDir
  url           = 'https://download.sysinternals.com/files/WinObj.zip'
  checksum      = '807057162c9a9b0e673bdf8b299459b98d3bbb78aed8ca2a56f3648ae113e9e7'
  checksumType  = 'sha256'
}

Install-ChocolateyZipPackage @packageArgs

$regPath = Join-Path $regRoot $regPkg

if (!(Test-Path $regRoot)) {
  New-Item -Path "$regRoot"
}

if (!(Test-Path $regPath)) {
  New-Item -Path "$regRoot" -Name "$regPkg"
}

Set-ItemProperty -Path "$regPath" -Name EulaAccepted -Value 1

if ((Get-ItemProperty -Path "$regPath").EulaAccepted -ne 1) {
  throw "Failure updating registry to indicate EULA acceptance"
}

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
WinObj - Windows Sysinternals 3.12 31 Thursday, September 23, 2021 Approved
WinObj - Windows Sysinternals 3.11 39 Friday, August 20, 2021 Approved
WinObj - Windows Sysinternals 3.10 66 Wednesday, May 26, 2021 Approved
WinObj - Windows Sysinternals 3.03 41 Friday, April 23, 2021 Approved
WinObj - Windows Sysinternals 3.02 52 Wednesday, March 24, 2021 Approved
WinObj - Windows Sysinternals 3.01 42 Saturday, March 6, 2021 Approved
WinObj - Windows Sysinternals 3.00 53 Wednesday, February 24, 2021 Approved
WinObj - Windows Sysinternals 2.23 22 Thursday, February 18, 2021 Approved
WinObj 2.22 1123 Monday, December 28, 2015 Approved

This package has no dependencies.

Discussion for the WinObj - Windows Sysinternals Package

Ground Rules:

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