Downloads of v 7.3.43:


Last Update:

11 Nov 2021

Package Maintainer(s):

Software Author(s):

  • Colin Morris
  • G0CUZ


winlog32 log HAM radio amateur


  • 1
  • 2
  • 3

7.3.43 | Updated: 11 Nov 2021



Downloads of v 7.3.43:



Software Author(s):

  • Colin Morris
  • G0CUZ

  • 1
  • 2
  • 3
winlog32 7.3.43

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5


Deployment Method: Individual Install, Upgrade, & Uninstall

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


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


To uninstall winlog32, 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 winlog32 -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 winlog32 -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 winlog32
    name: winlog32
    version: '7.3.43'
    state: present

See docs at

chocolatey_package 'winlog32' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '7.3.43'

See docs at

cChocoPackageInstaller winlog32
    Name     = "winlog32"
    Version  = "7.3.43"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'winlog32':
  ensure   => '7.3.43',
  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.

This package was approved as a trusted package on 11 Nov 2021.


This software has been in development for many years and the author (G0CUZ) provides this software FREE to use by all Radio Amateurs and SWL's in true 'Ham Spirit', as such no warranty is implied or given as to it's suitability or reliability.

Although Winlog32 is general purpose logging software, it has a definite slant on DX'ing on both HF and VHF with comprehensive tracking of various awards programs like DXCC, IOTA, WAZ etc. and includes all the features you would expect from good quality logging and DXing software and more.....


Winlog32 logging software for all Windows platforms.

Do you want to know if Winlog32 will suit your purposes? - please read on.....

  • FREE, unrestricted use with no limitations of any kind
  • Works on all Windows platforms, 95, 98, ME, 2000, XP, Vista, W7, W8, W8.1, W10
  • Includes all regular logging, DXCluster, rig control features
  • Dedicated web-site, info, download plus well supported Forum
  • Regular updates
  • Well established, respected and has been in development for over 20 years
  • Suitable for general logging purposes, with emphasis on award chasing and HF-VHF DXing
  • Used world-wide for many years
  • Simple and intuitive operation and uncluttered layout
  • Works within single container window
  • Logs
    • Versatile and secure log database system using established MS Access Jet 3.5
    • Multiple logs in each log database
    • Multiple log databases
    • Unlimited number of log entries
    • Remote logging capable
  • Separate award tracking for each individual log database
  • Real-time log input
  • Last entered QSOs always displayed
  • Auto-date and time function
  • Auto-search and display previous QSOs
  • Automatic database updates and checks made during QSO input





This software is completely free to download and use without losing any of the programs functionality and without limitations of any kind. It is free to distribute on a one-to-one basis, providing all original files are intact and not modified in any way and that no charge is made for this. Any bulk distribution is prohibited without specific permission from the Author.
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
Package can be verified like this:
1. Download:
2. You can use one of the following methods to obtain the SHA256 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'
   checksum type: sha256
   checksum32: C6DE412FFE50EB40C8B5D0F51C8A8C4159923A674556BDB78B13874AC9C88213
   checksum64: C6DE412FFE50EB40C8B5D0F51C8A8C4159923A674556BDB78B13874AC9C88213
File 'LICENSE.txt' is obtained from:
$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
  packageName = $env:ChocolateyPackageName
  file        = "$toolsDir\wl32v73.exe"

Install-ChocolateyInstallPackage @packageArgs
md5: 747A8E48B74D59E26657883D3FA0F5C7 | sha1: 378767EE7A9A888FAB7F5525D57755939168E449 | sha256: C6DE412FFE50EB40C8B5D0F51C8A8C4159923A674556BDB78B13874AC9C88213 | sha512: 64B0C468B61DFC68268EA5CEA6FFF026FF25F592283D647C660F7EEA232D7B168B45D8D2AC36DEB4BE581E8E6E983674A860F7385A3C25C344EB14D90E91BAFB

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
winlog32 7.3.41 83 Saturday, January 23, 2021 Approved
winlog32 7.3.40 81 Wednesday, September 16, 2020 Approved
winlog32 7.3.38 88 Saturday, June 6, 2020 Approved
winlog32 7.3.37 165 Tuesday, March 3, 2020 Approved
winlog32 7.3.35 113 Sunday, December 15, 2019 Approved
winlog32 7.3.33 110 Thursday, September 19, 2019 Approved
winlog32 7.3.32 202 Saturday, June 22, 2019 Approved
winlog32 7.3.31 112 Thursday, June 13, 2019 Approved
winlog32 134 Saturday, May 4, 2019 Approved

This package has no dependencies.

Discussion for the winlog32 Package

Ground Rules:

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