Downloads of v 5.3.0:


Last Update:


Package Maintainer(s):

Software Author(s):

  • Robert Palethorpe


winlogbeat beat elastic admin


This is not the latest version of winlogbeat available.

5.3.0 | Updated: 3/29/2017



Downloads of v 5.3.0:



Software Author(s):

  • Robert Palethorpe

winlogbeat 5.3.0

This is not the latest version of winlogbeat available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


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


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


To uninstall winlogbeat, 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 winlogbeat -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 winlogbeat -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 winlogbeat installed
    name: winlogbeat
    state: present
    version: 5.3.0
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'winlogbeat' do
  action    :install
  version  '5.3.0'
  source   'STEP 3 URL'

See docs at

    Name: winlogbeat,
    Version: 5.3.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller winlogbeat
   Name     = 'winlogbeat'
   Ensure   = 'Present'
   Version  = '5.3.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'winlogbeat':
  provider => 'chocolatey',
  ensure   => '5.3.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install winlogbeat version="5.3.0" source="STEP 3 URL"

See docs at

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 3/30/2017.


Collect Windows Event Logs

Harness the richness of system, application, and security information from Windows event logs using a lightweight Winlogbeat data collector. Ship events directly to Elasticsearch or parse and enrich them using Logstash prior to visualizing results in Kibana.

$ErrorActionPreference = 'Stop';

$packageName= 'winlogbeat'

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

$installationPath = $toolsDir

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $installationPath
  url           = $url
  url64bit      = $url64
  checksum      = 'e12f743edc1099b0b086f6dd1eebe8dbd80f8b5e'
  checksumType  = 'sha1'
  checksum64    = '3fd53e15feb4c7485aad371d82a9ab906a46dcd3'
  checksumType64= 'sha1'

Install-ChocolateyZipPackage @packageArgs

$pTemp = (dir $installationPath  $packageName*).Name
Invoke-Expression $(Join-Path $installationPath "$($pTemp)\install-service-$($packageName).ps1")
$packageName= 'winlogbeat'

$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$nupkgFile = Get-Content $(Join-Path $toolsDir "..\*.nupkg")
$zipManifest = Get-Content $(Join-Path $toolsDir "..\*.zip.txt")
$installPath = $zipManifest | select -First 1

$uninstallScript = $zipManifest | where { $_ -imatch 'uninstall.*\.ps1' }

Invoke-Expression $uninstallScript
Uninstall-ChocolateyZipPackage $packageName "$($nupkgFile)"

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
winlogbeat 7.3.2 13755 Friday, September 13, 2019 Approved
winlogbeat 7.3.1 10029 Friday, August 23, 2019 Approved
winlogbeat 7.3.0 7897 Thursday, August 1, 2019 Approved
winlogbeat 7.2.1 498 Wednesday, July 31, 2019 Approved
winlogbeat 9289 Monday, July 8, 2019 Approved
winlogbeat 7.0.0 22763 Thursday, April 11, 2019 Approved
winlogbeat 6.7.1 5002 Friday, April 5, 2019 Approved
winlogbeat 6.7.0 4424 Wednesday, March 27, 2019 Approved

This package has no dependencies.

Discussion for the winlogbeat Package

Ground Rules:

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