Downloads of v 2.12.4:


Last Update:

03 Aug 2012

Package Maintainer(s):

Software Author(s):

  • christianlist
  • grimmdp


winmerge chocolatey admin diff


This is not the latest version of WinMerge available.

  • 1
  • 2
  • 3

2.12.4 | Updated: 03 Aug 2012



Downloads of v 2.12.4:



Software Author(s):

  • christianlist
  • grimmdp

  • 1
  • 2
  • 3
WinMerge 2.12.4

This is not the latest version of WinMerge available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Unknown

Verification Testing Unknown

Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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:


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 winmerge -y --source="'INTERNAL REPO URL'" --version="'2.12.4'" [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="'INTERNAL REPO URL'" --version="'2.12.4'" 

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

Exit $exitCode

- name: Install winmerge
    name: winmerge
    version: '2.12.4'
    state: present

See docs at

chocolatey_package 'winmerge' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2.12.4'

See docs at

cChocoPackageInstaller winmerge
    Name     = "winmerge"
    Version  = "2.12.4"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'winmerge':
  ensure   => '2.12.4',
  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 06 Sep 2021.


WinMerge is a Windows tool for visual difference display and merging, for both files and directories. Unicode support. Flexible syntax coloring editor. Windows Shell integration. Regexp filtering. Side-by-side line diff and highlights diffs inline.
| Please install with chocolatey (

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
winmerge 2.16.22 27900 Wednesday, July 27, 2022 Approved
winmerge 2.16.20 30155 Thursday, April 28, 2022 Approved
winmerge 2.16.18 32562 Friday, January 28, 2022 Approved
winmerge 2.16.16 30878 Thursday, October 28, 2021 Approved
winmerge 23663 Sunday, August 29, 2021 Approved
winmerge 2.16.14 12853 Monday, July 26, 2021 Approved
winmerge 2.16.13-pre20210622 260 Wednesday, June 23, 2021 Exempted
winmerge 2.16.12 13665 Friday, May 28, 2021 Approved
winmerge 2.16.11-pre20210328 261 Monday, March 29, 2021 Exempted
winmerge 2.16.10 31949 Saturday, January 30, 2021 Approved
winmerge 2.16.9-pre20201129 213 Monday, November 30, 2020 Exempted
winmerge 38155 Sunday, September 13, 2020 Approved
winmerge 2.16.8 13741 Friday, August 28, 2020 Approved
winmerge 2.16.7-pre20200726 233 Tuesday, August 11, 2020 Exempted
winmerge 7236 Wednesday, August 12, 2020 Approved
Winmerge 84309 Monday, October 7, 2019 Approved
Winmerge 2.16.4 73701 Wednesday, August 14, 2019 Approved
Winmerge 2.16.2 35604 Tuesday, June 25, 2019 Approved
winmerge 25010 Tuesday, January 1, 2019 Approved
winmerge 2.16.0 7372 Monday, November 26, 2018 Approved
winmerge 52998 Friday, February 24, 2017 Approved
winmerge 2.14.0 50514 Monday, April 29, 2013 Approved
winmerge 2.12.14 1467 Thursday, August 9, 2012 Approved
WinMerge 2.12.4 654 Friday, August 3, 2012 Approved

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