Downloads of v 3.3.5:


Last Update:

19 Nov 2015

Package Maintainer(s):

Software Author(s):

  • Colin Mackie


security authentication totp 2fa

Windows Authenticator

This is not the latest version of Windows Authenticator available.

  • 1
  • 2
  • 3

3.3.5 | Updated: 19 Nov 2015



Downloads of v 3.3.5:


Software Author(s):

  • Colin Mackie

  • 1
  • 2
  • 3
Windows Authenticator 3.3.5

This is not the latest version of Windows Authenticator available.

  • 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 Windows Authenticator, run the following command from the command line or from PowerShell:


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


To uninstall Windows Authenticator, 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 winauth -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 winauth -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 winauth installed
    name: winauth
    state: present
    version: 3.3.5
    source: STEP 3 URL

See docs at

chocolatey_package 'winauth' do
  action    :install
  version  '3.3.5'
  source   'STEP 3 URL'

See docs at

    Name: winauth,
    Version: 3.3.5,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller winauth
   Name     = 'winauth'
   Ensure   = 'Present'
   Version  = '3.3.5'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'winauth':
  provider => 'chocolatey',
  ensure   => '3.3.5',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install winauth version="3.3.5" 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 ferventcoder on 25 Dec 2015.


WinAuth is a portable, open-source Authenticator for Windows that provides a time-based RFC 6238 authenticator and common implementations, such as the Google Authenticator. WinAuth can be used with many Bitcoin trading websites as well as games, supporting (World of Warcraft, Hearthstone, Heroes of the Storm, Diablo), Guild Wars 2, Glyph (Rift and ArcheAge), WildStar, RuneScape, SWTOR and Steam.

$packageName = 'winauth'
$url = ''
$checksum = '6c33f63776f5287141d2ffa3eaddf5adb8987bb0'
$checksumType = 'sha1'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$installFile = Join-Path $toolsDir "WinAuth.exe"
Install-ChocolateyZipPackage -PackageName "$packageName" `
                             -Url "$url" `
                             -UnzipLocation "$toolsDir" `
                             -Url64bit "" `
                             -Checksum "$checksum" `
                             -ChecksumType "$checksumType"
Set-Content -Path ("$installFile.gui") `
            -Value $null

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
Windows Authenticator 3.5.1 2952 Tuesday, June 7, 2016 Approved
winauth (Install) 3.5.1-stable 180 Wednesday, December 19, 2018 Exempted
Windows Authenticator 3.5.0 350 Friday, May 27, 2016 Approved
Windows Authenticator 3.3.7 383 Sunday, December 13, 2015 Approved
Windows Authenticator 3.3.5 353 Thursday, November 19, 2015 Approved
Windows Authenticator 3.3.3 320 Wednesday, November 11, 2015 Approved
Windows Authenticator 3.3.1 321 Sunday, October 25, 2015 Approved
Windows Authenticator 3.1.8 334 Friday, July 10, 2015 Approved



  • Automatically built and uploaded by dtgm
Discussion for the Windows Authenticator Package

Ground Rules:

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