Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.
Moderation
Every version of each package undergoes a rigorous moderation process before it goes live that typically includes:
- Security, consistency, and quality checking
- Installation testing
- Virus checking through VirusTotal
- Human moderators who give final review and sign off
More detail at Security and Moderation.
Organizational Use
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
Disclaimer
Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Learn more...
- Passing
- Failing
- Pending
- Unknown / Exempted

Downloads:
1,113
Downloads of v 7.3.41:
28
Last Update:
23 Jan 2021
Package Maintainer(s):
Software Author(s):
- Colin Morris
- G0CUZ
Tags:
winlog32 log HAM radio amateur- Software Specific:
- Software Site
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download

winlog32
- Software Specific:
- Software Site
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
1,113
Downloads of v 7.3.41:
28
Maintainer(s):
Software Author(s):
- Colin Morris
- G0CUZ
Edit Package
To edit the metadata for a package, please upload an updated version of the package.
Chocolatey's Community Package Repository currently does not allow updating package metadata on the website. This helps ensure that the package itself (and the source used to build the package) remains the one true source of package metadata.
This does require that you increment the package version.
All Checks are Passing
2 Passing Test
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:
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
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 https://community.chocolatey.org/api/v2. 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
-
Open Source
- Download the Package Download
- Follow manual internalization instructions
-
Package Internalizer (C4B)
- Run
choco download winlog32 --internalize --source=https://community.chocolatey.org/api/v2
(additional options) - Run
choco push --source="'http://internal/odata/repo'"
for package and dependencies - Automate package internalization
- Run
3. Enter your internal repository url
(this should look similar to https://community.chocolatey.org/api/v2)
4. Choose your deployment method:
choco upgrade winlog32 -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 winlog32 -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Ensure winlog32 installed
win_chocolatey:
name: winlog32
state: present
version: 7.3.41
source: STEP 3 URL
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'winlog32' do
action :install
version '7.3.41'
source 'STEP 3 URL'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
Chocolatey::Ensure-Package
(
Name: winlog32,
Version: 7.3.41,
Source: STEP 3 URL
);
Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.
cChocoPackageInstaller winlog32
{
Name = 'winlog32'
Ensure = 'Present'
Version = '7.3.41'
Source = 'STEP 3 URL'
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'winlog32':
provider => 'chocolatey',
ensure => '7.3.41',
source => 'STEP 3 URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
salt '*' chocolatey.install winlog32 version="7.3.41" source="STEP 3 URL"
See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.
5. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved as a trusted package on 23 Jan 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.....
Features
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
From: http://www.winlog32.co.uk
LICENSE
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
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:
x32: http://www.winlog32.co.uk/files/wl32v73.exe
x64: http://www.winlog32.co.uk/files/wl32v73.exe
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: E67AD87B4357EB956E40591757820F836CF3DB7D76A232139AB1963D4BC7FEE5
checksum64: E67AD87B4357EB956E40591757820F836CF3DB7D76A232139AB1963D4BC7FEE5
File 'LICENSE.txt' is obtained from:
http://www.winlog32.co.uk
$ErrorActionPreference = 'Stop';
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$packageArgs = @{
packageName = $env:ChocolateyPackageName
file = "$toolsDir\wl32v73.exe"
silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-'
}
Install-ChocolateyInstallPackage @packageArgs
md5: 75884D20DAB6DBD5C125F10CF9EF9308 | sha1: 7CB1161A33FF034C6826D960A7C57269570447AC | sha256: E67AD87B4357EB956E40591757820F836CF3DB7D76A232139AB1963D4BC7FEE5 | sha512: 906BCF0D1A76DC50370BD8983995927827AB8A3CF2C01D034EC084AF32F79711FD0893E1503C4801E4B79D752982DD908DCD29964AC19B687387DF5A2A1E1028
Log in or click on link to see number of positives.
- winlog32.7.3.41.nupkg (20557b0a9456) - ## / 64
- wl32v73.exe (e67ad87b4357) - ## / 70
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 |
---|---|---|---|
winlog32 7.3.41 | 28 | Saturday, January 23, 2021 | Approved |
winlog32 7.3.40 | 55 | Wednesday, September 16, 2020 | Approved |
winlog32 7.3.38 | 48 | Saturday, June 6, 2020 | Approved |
winlog32 7.3.37 | 135 | Tuesday, March 3, 2020 | Approved |
winlog32 7.3.35 | 92 | Sunday, December 15, 2019 | Approved |
winlog32 7.3.33 | 80 | Thursday, September 19, 2019 | Approved |
winlog32 7.3.32 | 166 | Saturday, June 22, 2019 | Approved |
winlog32 7.3.31 | 90 | Thursday, June 13, 2019 | Approved |
winlog32 7.3.29.20190504 | 113 | Saturday, May 4, 2019 | Approved |
winlog32 7.3.29 | 106 | Wednesday, April 3, 2019 | Approved |
winlog32 7.3.28 | 85 | Sunday, March 31, 2019 | Approved |
winlog32 7.3 | 115 | Wednesday, March 13, 2019 | Approved |
© Copyright Colin Morris, G0CUZ 1995-2019
This package has no dependencies.
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.