Downloads:

2,621

Downloads of v 2.4:

599

Last Update:

22 Feb 2019

Package Maintainer(s):

Software Author(s):

  • Pete Batard/Akeo

Tags:

usb driver foss

Zadig

2.4 | Updated: 22 Feb 2019

Downloads:

2,621

Downloads of v 2.4:

599

Software Author(s):

  • Pete Batard/Akeo

Tags:

usb driver foss

Zadig 2.4

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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

>

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

>

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

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


Chocolatey::Ensure-Package
(
    Name: zadig,
    Version: 2.4,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller zadig
{
   Name     = 'zadig'
   Ensure   = 'Present'
   Version  = '2.4'
   Source   = 'STEP 3 URL'
}

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


package { 'zadig':
  provider => 'chocolatey',
  ensure   => '2.4',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install zadig version="2.4" 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 by moderator mkevenaar on 23 Feb 2019.

Description

Zadig is a Windows application that installs generic USB drivers, such as WinUSB, libusb-win32/libusb0.sys or libusbK, to help you access USB devices.

It can be especially useful for cases where:

  • you want to access a device using a libusb-based application
  • you want to upgrade a generic USB driver
  • you want to access a device using WinUSB

tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

$toolsPath   = Split-Path -parent $MyInvocation.MyCommand.Definition

$packageArgs = @{
  packageName    = 'zadig'
  fileFullPath   = Join-Path $toolsPath 'zadig.exe'
  url            = 'https://github.com/pbatard/libwdi/releases/download/b721/zadig-2.4.exe'
  checksum       = '034093ECE4F6020E6DEE686EBD7E197BA4BDCF10C96F5C1934CD0C8120C1E229B7832D26421802C2D572B322E7ED3FA00D495C7DBF1BAD73D70D22AA7E71219C'
  checksumType   = 'sha512'
}
Get-ChocolateyWebFile @packageArgs

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
Zadig 2.3 937 Saturday, April 29, 2017 Approved
Zadig 2.1.1 806 Monday, March 17, 2014 Unknown
Make for Windows 2.1 279 Sunday, March 16, 2014 Unknown

This package has no dependencies.

Discussion for the Zadig Package

Ground Rules:

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