Downloads of v 2020.03.08.1332:


Last Update:

14 Mar 2020

Package Maintainer(s):

Software Author(s):

  • SupSuper


openxcom xcom

openxcom (Install)

2020.03.08.1332 | Updated: 14 Mar 2020



Downloads of v 2020.03.08.1332:



Software Author(s):

  • SupSuper


openxcom xcom

openxcom (Install) 2020.03.08.1332

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install openxcom (Install), run the following command from the command line or from PowerShell:


To upgrade openxcom (Install), run the following command from the command line or from PowerShell:


To uninstall openxcom (Install), 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 openxcom -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 openxcom -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 openxcom installed
    name: openxcom
    state: present
    version: 2020.03.08.1332
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'openxcom' do
  action    :install
  version  '2020.03.08.1332'
  source   'STEP 3 URL'

See docs at

    Name: openxcom,
    Version: 2020.03.08.1332,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller openxcom
   Name     = 'openxcom'
   Ensure   = 'Present'
   Version  = '2020.03.08.1332'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'openxcom':
  provider => 'chocolatey',
  ensure   => '2020.03.08.1332',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install openxcom version="2020.03.08.1332" 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 as a trusted package on 14 Mar 2020.


OpenXcom is an open-source clone of the original UFO: Enemy Unknown (X-Com: UFO Defense in USA), licensed under the GPL and written in C++ / SDL. It was originally founded by SupSuper in February 2010, and has since grown into a small development team surrounded by a very supporting community.

The goal of the project is to bring back the tried and true feel of the original with none of the issues. All the same graphics, sound and gameplay with a brand new codebase written from scratch. This should give it:

  • Fixability: Play the game natively without any need for emulators or fancy hacks, with none of the limitations and bugs that plagued the original. No more 80-item-limit, personnel limits, funding overflows, disconnected facilities, broken proximity grenades, floating soldiers, etc.
  • Moddability: Tweak the game to your heart’s content. Sure the original was pretty good, but maybe you just think it could be that bit better. A nicer base layout, better laser weapons, maybe challenge yourself with a custom game mode, or just put in all the crazy stuff you’ve always wanted! None of it is hardcoded.
  • Flexibility: Port the game to any platform you like, customize it to your liking, or use it to make your own far-fetched remakes. The code is fully documented and open-source so anyone can take a crack at it.

For more details check the Wiki.

$ErrorActionPreference = 'Stop'; # stop on all errors
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
. "$(Join-Path $toolsDir commonEnv.ps1)"

$url = ''
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = "$(Join-Path $ENV:LocalAppData Programs)"
  url           = $url
  softwareName  = 'xcom*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
  checksum      = '3199A40BCA8DCA060D54DD4263C0DF29B753DAAC91F5BC1ED9C6A7C459F7D628'
  checksumType    = 'sha256'
Install-ChocolateyZipPackage @packageArgs

## StartMenu
Install-ChocolateyShortcut -ShortcutFilePath "$(Join-Path $startMenuDir $GameName).lnk" `
  -TargetPath "$(Join-Path $installLocation $GameNameLow).exe" `
  -WorkingDirectory "$installLocation"
Install-ChocolateyShortcut -ShortcutFilePath "$(Join-Path $startMenuDir ReadMe.lnk)" `
  -TargetPath "$(Join-Path $installLocation"
Install-ChocolateyShortcut -ShortcutFilePath "$(Join-Path $startMenuDir 'Release Notes.lnk')" `
  -TargetPath "$(Join-Path $installLocation CHANGELOG.txt)"

## Desktop
Install-ChocolateyShortcut -ShortcutFilePath "$shortcutPath" `
  -TargetPath "$(Join-Path $installLocation $GameNameLow).exe" `
  -WorkingDirectory "$installLocation"
$ErrorActionPreference = 'Stop'; # stop on all errors
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
. "$(Join-Path $toolsDir commonEnv.ps1)"

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'xcom*'  #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']
if ($key.Count -eq 1) {
  $key | % { 
    $packageArgs['file'] = "$($_.UninstallString)" #NOTE: You may need to split this if it contains spaces, see below
    if ($packageArgs['fileType'] -eq 'MSI') {
      $packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
      $packageArgs['file'] = ''
    } else {
    Uninstall-ChocolateyPackage @packageArgs
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $($_.DisplayName)"}
Remove-Item $shortcutPath -force
Remove-Item "$startMenuDir" -recurse -force
Remove-Item $installLocation -exclude TFTD, UFO -recurse -force
$GameName = 'OpenXCOM'
$GameNameLow = $GameName.toLower()

$installLocation = [IO.Path]::Combine($ENV:LocalAppData, 'Programs', $GameNameLow)
$shortcutPath = [IO.Path]::Combine($ENV:UserProfile, 'Desktop', "$GameName.lnk")
$startMenuDir = [IO.Path]::Combine($ENV:AppData, 'Microsoft\Windows\Start Menu\Programs', "$GameName")

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
openxcom (Install) 2020.02.10.0926 49 Friday, February 14, 2020 Approved
openxcom (Install) 2019.10.27.1448 48 Saturday, November 2, 2019 Approved
openxcom (Install) 2019.09.24.2237 24 Tuesday, October 1, 2019 Approved
openxcom (Install) 2019.08.03.0017 48 Thursday, August 15, 2019 Approved
openxcom (Install) 2019.07.28.0403 34 Sunday, July 28, 2019 Approved
openxcom (Install) 2019.07.10.0142 39 Thursday, July 11, 2019 Approved
openxcom (Install) 2019.06.28.0441 35 Sunday, June 30, 2019 Approved
openxcom (Install) 2019.06.14.2145 43 Sunday, June 16, 2019 Approved
openxcom (Install) 2019.05.29.2230 71 Thursday, May 30, 2019 Approved

This package has no dependencies.

Discussion for the openxcom (Install) Package

Ground Rules:

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