Downloads of v 7.15.1:


Last Update:

15 Oct 2021

Package Maintainer(s):

Software Author(s):

  • Robert Palethorpe


winlogbeat beat elastic admin


  • 1
  • 2
  • 3

7.15.1 | Updated: 15 Oct 2021



Downloads of v 7.15.1:


Software Author(s):

  • Robert Palethorpe

  • 1
  • 2
  • 3
winlogbeat 7.15.1

  • 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


Deployment Method: Individual Install, Upgrade, & Uninstall

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:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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. Copy Your Script

choco upgrade winlogbeat -y --source="'INTERNAL REPO 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="'INTERNAL REPO URL'" 

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

Exit $exitCode

- name: Install winlogbeat
    name: winlogbeat
    version: '7.15.1'
    state: present

See docs at

chocolatey_package 'winlogbeat' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '7.15.1'

See docs at

cChocoPackageInstaller winlogbeat
    Name     = "winlogbeat"
    Version  = "7.15.1"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'winlogbeat':
  ensure   => '7.15.1',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. 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 15 Oct 2021.


Contains the chocolatey package for winlogbeat

$packageName= 'winlogbeat'

Stop-Service $packageName
Start-Sleep -s 3

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

$installationPath = $toolsDir

$uninstallScript = Join-Path $toolsDir "uninstall-service-$($packageName).ps1"
Invoke-Expression $uninstallScript

# Chocolatey seems to copy the old lib folder in case of upgrade. Uninstall first.
$zipContentGlob=Get-ChildItem "$($installationPath)/.." "$($packageName)-*.zip.txt"
$folder = ($zipContentFile -replace ".zip.txt","") + "\\"
if (($null -ne $zipContentGlob)) {
    $zipContents=(get-content $zipContentGlob.FullName) -split [environment]::NewLine
    for ($i = $zipContents.Length; $i -gt 0; $i--) {
        $fileInZip = $zipContents[$i]
        if ($null -ne $fileInZip -and $fileInZip.Trim() -ne '') {
            $fileToRemove = $fileInZip -replace $folder,""
            Remove-Item -Path "$fileToRemove" -ErrorAction SilentlyContinue -Recurse -Force
    Remove-Item -Path $zipContentGlob.FullName -ErrorAction SilentlyContinue -Recurse -Force
$ErrorActionPreference = 'Stop';

$packageName= 'winlogbeat'

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

$installationPath = $toolsDir

$folder = if(Get-ProcessorBits 64) { [io.path]::GetFileNameWithoutExtension($url64) } else { [io.path]::GetFileNameWithoutExtension($url) }

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $installationPath
  url           = $url
  url64bit      = $url64
  checksum      = '1284c2025284e1f2db0d738aae19636f65eee6985242622b65ea889dcb5d0e6af67b712f7c322ed863c2e317eda0dea6d88ae99b7b063f3d25d0dd6218e28c54'
  checksumType  = 'sha512'
  checksum64    = 'd12038a3f1b23c23cfc9f7f1dd80be6c7ec313321d684bb20c50964bc2dcb5150658af3e5fc1f956b3d9489933d45ec72ca748122797e8eda053a8a87b943c78'
  checksumType64= 'sha512'
  specificFolder = $folder

Install-ChocolateyZipPackage @packageArgs

# Move everything from the subfolder to the main tools directory
$subFolder = Join-Path $installationPath (Get-ChildItem $installationPath $folder | ?{ $_.PSIsContainer })
Get-ChildItem $subFolder -Recurse | ?{$_.PSIsContainer } | Move-Item -Destination $installationPath
Get-ChildItem $subFolder | ?{$_.PSIsContainer -eq $false } | Move-Item -Destination $installationPath
Remove-Item "$subFolder"

Invoke-Expression $(Join-Path $installationPath "install-service-$($packageName).ps1")
$packageName= 'winlogbeat'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$uninstallScript = Join-Path $toolsDir "uninstall-service-$($packageName).ps1"

if ($null -ne (get-item $uninstallScript -ErrorAction SilentlyContinue)) {
    Invoke-Expression $uninstallScript

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.

Add to Builder Version Downloads Last Updated Status
winlogbeat 7.15.0 12293 Thursday, September 23, 2021 Approved
winlogbeat 7.14.2 711 Wednesday, September 22, 2021 Approved
winlogbeat 7.14.1 8055 Thursday, September 2, 2021 Approved
winlogbeat 7.14.0 5109 Wednesday, August 4, 2021 Approved
winlogbeat 7.13.4 70 Wednesday, July 21, 2021 Approved
winlogbeat 7.13.3 4943 Thursday, July 8, 2021 Approved
winlogbeat 7.13.2 755 Monday, July 5, 2021 Approved
winlogbeat 7.13.1 7983 Thursday, June 3, 2021 Approved
winlogbeat 7.13.0 1569 Wednesday, May 26, 2021 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