Downloads of v 0.2011.007.44401:


Last Update:

16 Nov 2017

Package Maintainer(s):

Software Author(s):

  • Jochen Neubeck


winmerge winmerge2011 diff merge

WinMerge2011 (Portable)

  • 1
  • 2
  • 3

0.2011.007.44401 | Updated: 16 Nov 2017



Downloads of v 0.2011.007.44401:



Software Author(s):

  • Jochen Neubeck

  • 1
  • 2
  • 3
WinMerge2011 (Portable) 0.2011.007.44401

  • 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:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.


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


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


To uninstall WinMerge2011 (Portable), 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 winmerge2011.portable -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 winmerge2011.portable -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 winmerge2011.portable installed
    name: winmerge2011.portable
    state: present
    version: 0.2011.007.44401
    source: STEP 3 URL

See docs at

chocolatey_package 'winmerge2011.portable' do
  action    :install
  version  '0.2011.007.44401'
  source   'STEP 3 URL'

See docs at

    Name: winmerge2011.portable,
    Version: 0.2011.007.44401,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller winmerge2011.portable
   Name     = 'winmerge2011.portable'
   Ensure   = 'Present'
   Version  = '0.2011.007.44401'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'winmerge2011.portable':
  provider => 'chocolatey',
  ensure   => '0.2011.007.44401',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install winmerge2011.portable version="0.2011.007.44401" 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 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 10 Jul 2020.


The WinMerge 2011 series is a fork of the original WinMerge application published on SourceForge by Thingamahoochie Software.
It is an escape from the complex situation that exists with respect to WinMerge 2.x. ATL/MFC dependencies have also been removed
so as to enable zero-budget developers to build WinMerge from sources using Visual C++ Express editions.

$packageName = 'winmerge2011.portable' # arbitrary name for the package, used in messages
$url = '' # download url
$url64 = '' # 64bit URL here or remove - if installer decides, then use $url
$checksum = '267A53DCE1C08F7A90B8F2222A5400E7AAA15FC789383D2CEDC624CD5F3DE18F'
$checksum64 = '4EB072D660BB8A0ECCF2737DC012A5B949C6653BFF1A1C71EADC1EE3C6F19948'

$installDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
Install-ChocolateyZipPackage "$packageName" `
  -Url "$url" -Checksum "$checksum" -ChecksumType sha256 `
  -Url64 "$url64" -Checksum64 "$checksum64" -ChecksumType64 sha256 `
  -UnzipLocation "$installDir"

# generate ignore and gui for executables
Get-ChildItem -Path $installDir -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.

Version Downloads Last Updated Status
WinMerge2011 (Portable) 0.2011.007.34700 316 Friday, September 22, 2017 Approved
WinMerge2011 (Portable) 0.2011.007.02500 454 Friday, March 10, 2017 Approved
WinMerge2011 (Portable) 0.2011.005.42701 388 Sunday, August 28, 2016 Approved
WinMerge2011 (Portable) 0.2011.005.427 340 Sunday, April 17, 2016 Approved

This package has no dependencies.

Discussion for the WinMerge2011 (Portable) Package

Ground Rules:

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