Downloads of v


Last Update:


Package Maintainer(s):

Software Author(s):

  • Kimmo Varis Denis Bradford Dean Grimm Laurent Ganier Tim Gerundt Perry Rapp


chocolatey winmerge diff merge

Winmerge | Updated: 10/7/2019



Downloads of v



Software Author(s):

  • Kimmo Varis Denis Bradford Dean Grimm Laurent Ganier Tim Gerundt Perry Rapp


All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


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


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


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

See docs at

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

chocolatey_package 'winmerge' do
  action    :install
  version  ''
  source   'STEP 3 URL'

See docs at

    Name: winmerge,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller winmerge
   Name     = 'winmerge'
   Ensure   = 'Present'
   Version  = ''
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install winmerge version="" 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 by moderator flcdrg on 10/7/2019.


WinMerge is an Open Source differencing and merging tool for Windows. WinMerge can compare both folders and files, presenting differences in a visual text format that is easy to understand and handle.

$ErrorActionPreference = 'Stop';
$packageName = 'WinMerge'
$toolsDir    = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url32       = ''
$checksum32  = '946676A4F59AD0EDBD1213E868078CB5BC9DB87B5C49085241EE843BB5664A19'
$url64       = ''
$checksum64  = '018FCF478A6466AC48A81D8B5D40FB5F4C5C4AF3CAA84E25B5E8223368888745'

$packageArgs = @{
    packageName    = $packageName
    url            = $url32
    checkum        = $checksum32
    checksumType   = 'sha256'
    url64bit       = $url64
    checksum64     = $checksum64
    checksumType64 = 'sha256'
    fileType       = 'EXE'
    silentArgs     = '/VERYSILENT /ALLUSERS'
    validExitCodes = @(0)  
    registryUninstallerKey = $packageName	

Install-ChocolateyPackage @packageArgs

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
Winmerge 2.16.4 73482 Wednesday, August 14, 2019 Approved
Winmerge 2.16.2 35279 Tuesday, June 25, 2019 Approved
winmerge 24799 Tuesday, January 1, 2019 Approved
winmerge 2.16.0 7187 Monday, November 26, 2018 Approved
winmerge 52817 Friday, February 24, 2017 Approved
winmerge 2.14.0 50087 Monday, April 29, 2013 Approved
winmerge 2.12.14 1334 Thursday, August 9, 2012 Unknown
WinMerge 2.12.4 473 Friday, August 3, 2012 Unknown

This package has no dependencies.

Discussion for the Winmerge Package

Ground Rules:

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