Downloads of v 4.2.0:


Last Update:

24 Sep 2021

Package Maintainer(s):

Software Author(s):

  • Duo Security


duo authentication mfa security

Duo Authentication

  • 1
  • 2
  • 3

4.2.0 | Updated: 24 Sep 2021



Downloads of v 4.2.0:



Software Author(s):

  • Duo Security

  • 1
  • 2
  • 3
Duo Authentication 4.2.0

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


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


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


To uninstall Duo Authentication, 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 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

4. Choose your deployment method:

choco upgrade duo-authentication -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 duo-authentication -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure duo-authentication installed
    name: duo-authentication
    state: present
    version: 4.2.0
    source: STEP 3 URL

See docs at

chocolatey_package 'duo-authentication' do
  action    :install
  version  '4.2.0'
  source   'STEP 3 URL'

See docs at

    Name: duo-authentication,
    Version: 4.2.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller duo-authentication
   Name     = 'duo-authentication'
   Ensure   = 'Present'
   Version  = '4.2.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'duo-authentication':
  provider => 'chocolatey',
  ensure   => '4.2.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install duo-authentication version="4.2.0" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator TheCakeIsNaOH on 24 Sep 2021.


Duo Authentication for Windows Logon add Duo two-factor authentication to Windows desktop and server logins, both at the local console and incoming Remote Desktop (RDP) connections. Starting with version 4.1.0, two-factor authentication may also be enabled for credentialed User Access Control (UAC) elevation requests, depending on your organization's Windows UAC configuration.

Please note that using this application requires an active subscription with Duo.

For more information please visit the Duo website or view the Duo Authentication for Windows Logon and RDP Documentation.

Package Parameters

By default this package will install the Duo Authentication app with no configuration.

In order to customise your installation you may wish to pass additional parameters to the installer. The Duo install options are documented here. Any package parameters you provide are passed directly into the installer.

To customise the installation, pass any custom install options as such:

choco install duo-authentication --package-parameters="'/IKEY:DIXXXXXXXXXXXXXXXXXXXX /SKEY:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx / /AUTOPUSH:#1 /FAILOPEN:#1 /RDPONLY:#0'"

$ErrorActionPreference = 'Stop';

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

# Inject any custom parameters into the silentArgs
$silentArgs   = '/S /V"/qn'
$pp = Get-PackageParameters
ForEach ($key in $pp.Keys) {
  $silentArgs += " $key=" + $pp[$key]
$silentArgs += '"'

$packageArgs = @{
  packageName   = 'duo-authentication'
  softwareName  = 'Duo Authentication for Windows Logon*'
  unzipLocation = $toolsDir
  fileType      = 'exe'
  url           = ''
  checksum      = 'ad145827e80d38e3930fd4a8070ed779a08c0f88410f1767814564f29cbaacf9'
  checksumType  = 'sha256'
  silentArgs    = $silentArgs

Install-ChocolateyPackage @packageArgs
$ErrorActionPreference = 'Stop';
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'Duo Authentication for Windows Logon*'
  fileType      = 'MSI' #only one of these: MSI or EXE (ignore MSU for now)
  # MSI
  silentArgs    = "/qn /norestart"
  validExitCodes= @(0, 3010, 1605, 1614, 1641) #

$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']

if ($key.Count -eq 1) {
  $key | % { 
    $packageArgs['file'] = "$($_.UninstallString)"
    if ($packageArgs['fileType'] -eq 'MSI') {
      $packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
      $packageArgs['file'] = ''

    Uninstall-ChocolateyPackage @packageArgs
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $($_.DisplayName)"}

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
Duo Authentication 4.1.3 1775 Tuesday, November 3, 2020 Approved
Duo Authentication 4.1.2 113 Thursday, October 15, 2020 Approved
Duo Authentication 4.1.1 4134 Wednesday, July 22, 2020 Approved

This package has no dependencies.

Discussion for the Duo Authentication Package

Ground Rules:

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