Downloads of v


Last Update:

05 Jun 2015

Package Maintainer(s):

Software Author(s):

  • Takashi Sawanaka


winmerge diff merge

WinMerge (jp)

  • 1
  • 2
  • 3 | Updated: 05 Jun 2015



Downloads of v



Software Author(s):

  • Takashi Sawanaka

  • 1
  • 2
  • 3
WinMerge (jp)

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Failed


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 WinMerge (jp), run the following command from the command line or from PowerShell:


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


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

See docs at

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

See docs at

    Name: winmerge-jp,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

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

Requires cChoco DSC Resource. See docs at

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

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install winmerge-jp version="" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator ferventcoder on 28 Dec 2015.


WinMerge is an Open Source differencing and merging tool for Windows. In addition to original, japanese edition supports several features (details here

$packageName = "winmerge-jp"
$fileType = "exe"
$installerName = 'WinMerge-' -replace "\.(\d+)-",'+-jp-$1-'
$installerName64 = $installerName -replace "-Setup","-x64-Setup"
$url = "$" -replace "\+-jp","-jp"
$url64 = "$" -replace "\+-jp","-jp"
$validExitCodes = @(0)

try {
	$chocTempDir = Join-Path $env:TEMP "chocolatey"
	$tempDir = Join-Path $chocTempDir "$packageName"
	if (![System.IO.Directory]::Exists($tempDir)) {[System.IO.Directory]::CreateDirectory($tempDir)}

	$zipfile = Join-Path $tempDir "$($packageName).zip"
	$unzipdir = Join-Path $tempDir "$($packageName).unzip"

	Write-Host "Zipfile: [$zipfile]"
	if (-not (Test-Path $zipfile)) {
		Get-ChocolateyWebFile $packageName $zipfile $url $url64
	} else {
		Write-Host "Zipfile is already downloaded."

	if (Get-ProcessorBits 64 -and -not $env:chocolateyForceX86) {
		$file = Join-Path $unzipdir $installerName64
	} else {
		$file = Join-Path $unzipdir $installerName

	Write-Host "Installer: $file"
	if (-not (Test-Path $file)) {
		Get-ChocolateyUnzip "$zipfile" $unzipdir $specificFolder $packageName | Out-Null
	} else {
		Write-Host "Installer is already extracted."

	Install-ChocolateyInstallPackage $packageName $fileType $silentArgs $file -validExitCodes $validExitCodes
	Remove-Item -path "$tempDir" -recurse -force
	Write-ChocolateySuccess "$packageName"
} catch {
  Write-ChocolateyFailure "$packageName" $($_.Exception.Message)
$packageName = "winmerge-jp"

try {
  $key = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall"
  $key64 = "HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall"
  $entries = (Get-ChildItem $key) + (Get-ChildItem $key64)
  $target = $entries|?{$_.GetValue("DisplayName") -match "WinMerge"}

  if (-not $target) {
    Write-Host "$packageName is not installed."
  } else {
    $uninst = $target.GetValue('UninstallString')
    Write-Host "Uninstall $packageName by [$uninst]"
    & cmd /c "$uninst" /VERYSILENT /SP- /NORESTART

  Write-ChocolateySuccess "$packageName"
} catch {
  Write-ChocolateyFailure "$packageName" $($_.Exception.Message)

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
WinMerge (jp) 794 Friday, June 5, 2015 Approved
WinMerge (jp) 420 Monday, April 20, 2015 Approved
winmerge-jp 2.14.0+-jp-59 660 Friday, November 28, 2014 Exempted
winmerge-jp 2.14.0+-jp-56 378 Friday, November 28, 2014 Exempted
winmerge-jp 2.14.0+-jp-51 564 Wednesday, September 17, 2014 Unknown
winmerge-jp 2.14.0+-jp-49 411 Tuesday, August 19, 2014 Unknown
winmerge-jp 2.14.0+-jp-45 458 Friday, July 11, 2014 Unknown
winmerge-jp 2.14.0+-jp-43 460 Friday, May 30, 2014 Unknown

This package has no dependencies.

Discussion for the WinMerge (jp) Package

Ground Rules:

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