Downloads of v 2.16.22:


Last Update:

27 Jul 2022

Package Maintainer(s):

Software Author(s):

  • Dean Grimm


winmerge win merge diff file folder changes comparison

WinMerge (Portable)

  • 1
  • 2
  • 3

2.16.22 | Updated: 27 Jul 2022



Downloads of v 2.16.22:



Software Author(s):

  • Dean Grimm

  • 1
  • 2
  • 3
WinMerge (Portable) 2.16.22

  • 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

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install WinMerge (Portable), run the following command from the command line or from PowerShell:


To upgrade WinMerge (Portable), run the following command from the command line or from PowerShell:


To uninstall WinMerge (Portable), 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.portable -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 winmerge.portable -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 winmerge.portable
    name: winmerge.portable
    version: '2.16.22'
    state: present

See docs at

chocolatey_package 'winmerge.portable' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2.16.22'

See docs at

cChocoPackageInstaller winmerge.portable
    Name     = "winmerge.portable"
    Version  = "2.16.22"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'winmerge.portable':
  ensure   => '2.16.22',
  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 is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 27 Jul 2022.


WinMerge is a Windows tool for visual difference display and merging, for both files and directories. It is highly useful for determining what has changed between file versions, and then merging those changes. WinMerge has Unicode support, Flexible syntax coloring editor, Visual SourceSafe integration, and Windows Shell integration. Regexp filtering for filenames and lines. Side-by-side line difference and highlights differences inside lines. A file map shows the overall file differences in a location pane. The user interface is translated into several languages.


  • Visual differencing and merging of text files
  • Flexible editor with syntax highlighting, line numbers and word-wrap
  • Highlights differences inside lines
  • Difference pane shows current difference in two vertical panes
  • Location pane shows map of files compared
  • Moved lines detection
  • Compare folders in one level or recursive
  • Can show folder compare results flat or in a tree-style view
  • Regular Expression based file filters allow excluding and including items
  • Compares binary files in folder compare as well as text files
  • Shell Integration (supports 64-bit Windows versions)
  • Archive file support using 7-Zip
  • Fast compare using file sizes and dates
  • Creates patch files (Normal-, Context- and Unified formats)

NOTE: This package is automatically updated. If it is out of date and there is no newer package submitted, please use the Contact Maintainers functionality to alert me.

$ErrorActionPreference = 'Stop'

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

$packageArgs = @{
    packageName    = $env:ChocolateyPackageName
    unzipLocation  = $toolsDir
    url            = ''
    url64          = ''

    checksum       = '3752325dba7f9971b07a0111c6b85d7de61d2a0726599453ee104940075893ab'
    checksumType   = 'SHA256'
    checksum64     = 'ac3e619f92ac1952c49c7e8a123c65d3c6f53f5271c0ee72ca2fcfc5ae479806'
    checksumType64 = 'SHA256'

Install-ChocolateyZipPackage @packageArgs

Get-ChildItem -Path $toolsDir -Filter "*.exe" -Recurse | ForEach-Object {
    $exe = $_.FullName
    if ($_.BaseName -eq 'winmergeu') {
      New-Item "${exe}.gui" -Type file -Force | Out-Null
    } else {
      New-Item "${exe}.ignore" -Type file -Force | Out-Null

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 (Portable) 2.16.21 155 Monday, June 20, 2022 Approved
WinMerge (Portable) 2.16.20 169 Wednesday, April 27, 2022 Approved
WinMerge (Portable) 2.16.19 96 Sunday, March 20, 2022 Approved
WinMerge (Portable) 2.16.18 199 Thursday, January 27, 2022 Approved
WinMerge (Portable) 2.16.17 136 Sunday, December 19, 2021 Approved
WinMerge (Portable) 2.16.16 154 Thursday, October 28, 2021 Approved
WinMerge (Portable) 2.16.15 142 Monday, September 20, 2021 Approved
WinMerge (Portable) 2.16.13 176 Tuesday, June 22, 2021 Approved

This package has no dependencies.

Discussion for the WinMerge (Portable) Package

Ground Rules:

  • This discussion is only about WinMerge (Portable) and the WinMerge (Portable) 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 (Portable), 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