Downloads of v 20161025.0.0:


Last Update:

02 Jun 2017

Package Maintainer(s):

Software Author(s):

  • Alexpux
  • martell
  • mingwandroid
  • elieux
  • renatosilva
  • niXman


msys2 msys cygwin mingw pacman bash makepkg gcc admin

MSYS2 Installer

  • 1
  • 2
  • 3

20161025.0.0 | Updated: 02 Jun 2017



Downloads of v 20161025.0.0:



Software Author(s):

  • Alexpux
  • martell
  • mingwandroid
  • elieux
  • renatosilva
  • niXman

  • 1
  • 2
  • 3
MSYS2 Installer 20161025.0.0

  • 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 MSYS2 Installer, run the following command from the command line or from PowerShell:


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


To uninstall MSYS2 Installer, 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 msys2-installer -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 msys2-installer -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 msys2-installer installed
    name: msys2-installer
    state: present
    version: 20161025.0.0
    source: STEP 3 URL

See docs at

chocolatey_package 'msys2-installer' do
  action    :install
  version  '20161025.0.0'
  source   'STEP 3 URL'

See docs at

    Name: msys2-installer,
    Version: 20161025.0.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller msys2-installer
   Name     = 'msys2-installer'
   Ensure   = 'Present'
   Version  = '20161025.0.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'msys2-installer':
  provider => 'chocolatey',
  ensure   => '20161025.0.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install msys2-installer version="20161025.0.0" 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 AdmiringWorm on 18 Jun 2017.


This lightweight package performs an unattended installation of MSYS2 using official installer.
It is intended as an alternative to msys2 and msys2.install packages
which might be a better choice for some users.

Major differences when compared to MSYS2 package:
- Installation is performed from official .exe binaries instead of .tar.xz archives
- Unattended installation only without any additional customization or configuration (not even pacman --noconfirm -Syuu)

Major differences when compared to msys2.install package:
- msys2.install package is currently broken and not yet approved
- Support for unattended uninstall
- QtInstaller window is visible so that user can track progress and optionally answer MessageBox that is hard to automate (e.g. Corrupt_Installation_Error)

$ErrorActionPreference = 'Stop';

$packageName= 'msys2-installer'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url = ''
$url64 = ''

$packageArgs = @{
  packageName   = $packageName
  softwareName  = 'MSYS2 *'
  fileType      = 'EXE'
  url           = $url
  url64bit      = $url64
  # Checksums can be found here:
  checksum      = '4951a47177777a54c7ad4ac99755ba4bbdf1a0cb23a174a72d91f71dc25bcb15'
  checksumType  = 'sha256'
  checksum64    = '2c198787ea1c4be39ff80466c4d831f8c7f06bd56d6d190bf63ede35292e344c'
  checksumType64= 'sha256'

  # WARNING: Installer seems to get stuck on "SHOW FINISHED PAGE" page when you use -v (verbose)
  silentArgs    = "--script `"$toolsDir\msys2install.qs`""
  validExitCodes= @(0)

Install-ChocolateyPackage @packageArgs
$ErrorActionPreference = 'Stop';

$packageName = 'msys2-installer'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$softwareName = 'MSYS2 *'
$installerType = 'exe'

# Note: We are not using --platform minimal as the uninstallation could get stuck on Corrupt_Installation_Error message box
$silentArgs = "--script `"$toolsDir\msys2uninstall.qs`""
$validExitCodes = @(0)

$uninstalled = $false

# Note: During testing the following statement was returing array with empty element. 
# This needs further investigation. Let's stick to direct registry access for now. 
#[array]$key = Get-UninstallRegistryKey -SoftwareName $softwareName

[array]$key = Get-ItemProperty  -Path @('HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*',
                                       'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*') `
                                -ErrorAction:SilentlyContinue `
  | Where-Object   {$_.DisplayName -like $softwareName}

$key `
| ForEach-Object {
  Uninstall-ChocolateyPackage -PackageName "$packageName" `
                             -FileType "$installerType" `
                             -SilentArgs "$($silentArgs)" `
                             -File "$($_.UninstallString)" `
                             -ValidExitCodes $validExitCodes}

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
MSYS2 Installer 20160921.0.0 326 Friday, June 2, 2017 Approved
MSYS2 Installer 20160205.0.0 397 Thursday, February 23, 2017 Approved
MSYS2 Installer 20150916.0.0 322 Thursday, February 23, 2017 Approved

This package has no dependencies.

Discussion for the MSYS2 Installer Package

Ground Rules:

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