Downloads:

319,919

Downloads of v 6.1.2:

13,083

Last Update:

15 Nov 2020

Package Maintainer(s):

Software Author(s):

  • jrsoftware

Tags:

innosetup admin installer setup exe foss

Inno Setup

6.1.2 | Updated: 15 Nov 2020

Downloads:

319,919

Downloads of v 6.1.2:

13,083

Maintainer(s):

Software Author(s):

  • jrsoftware

Tags:

innosetup admin installer setup exe foss

Inno Setup 6.1.2

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

To install Inno Setup, run the following command from the command line or from PowerShell:

>

To upgrade Inno Setup, run the following command from the command line or from PowerShell:

>

To uninstall Inno Setup, 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 https://chocolatey.org/api/v2. 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 https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade innosetup -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 innosetup -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Ensure innosetup installed
  win_chocolatey:
    name: innosetup
    state: present
    version: 6.1.2
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

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


chocolatey_package 'innosetup' do
  action    :install
  version  '6.1.2'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: innosetup,
    Version: 6.1.2,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller innosetup
{
   Name     = 'innosetup'
   Ensure   = 'Present'
   Version  = '6.1.2'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'innosetup':
  provider => 'chocolatey',
  ensure   => '6.1.2',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install innosetup version="6.1.2" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 18 Nov 2020.

Description

Inno Setup is a free installer for Windows programs. First introduced in 1997, Inno Setup today rivals and even surpasses many commercial installers in feature set and stability.

Key features

  • Support for every Windows release since 2000, including: Windows 10, Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows XP, Windows Server 2003, and Windows 2000. (No service packs are required.)
  • Extensive support for installation of 64-bit applications on the 64-bit editions of Windows. Both the x64 and Itanium architectures are supported. (On the Itanium architecture, Service Pack 1 or later is required on Windows Server 2003 to install in 64-bit mode.)
  • Supports creation of a single EXE to install your program for easy online distribution. Disk spanning is also supported.
  • Standard Windows wizard interface.
  • Customizable setup types, e.g. Full, Minimal, Custom.
  • Complete uninstall capabilities.
  • Installation of files:
    Includes integrated support for "deflate", bzip2, and 7-Zip LZMA/LZMA2 file compression. The installer has the ability to compare file version info, replace in-use files, use shared file counting,
    register DLL/OCX's and type libraries, and install fonts.
  • Creation of shortcuts anywhere, including in the Start Menu and on the desktop.
  • Creation of registry and .INI entries.
  • Running other programs before, during or after install.
  • Support for multilingual installs, including right-to-left language support.
  • Support for passworded and encrypted installs.
  • Support for digitally signed installs and uninstalls, including dual signing (SHA1 & SHA256).
  • Silent install and uninstall.
  • Unicode installs.
  • Integrated preprocessor option for advanced compile-time customization.
  • Integrated Pascal scripting engine option for advanced run-time install and uninstall customization.
  • Full source code is available (Borland Delphi 2.0-5.0 and 2009).

Is it really free of charge, even for commercial use?
Yes, it may be used completely free of charge, even when deploying commercial applications.
However if you wish to show your appreciation and support its development you can make a donation.
(Note: "Completely free of charge" must not be confused with "completely free". Inno Setup is copyrighted software, not public domain software. There are some restrictions on distribution and use; see the LICENSE.TXT file for details.)

Package Parameters

  • /UseInf: - Change the inno setup configuration file to use/save when installing

EXAMPLE
choco install innosetup --params "'/UseInf:C:\innosetup.install.inf'"

legal\license.txt 
Inno Setup License
==================

Except where otherwise noted, all of the documentation and software included
in the Inno Setup package is copyrighted by Jordan Russell.

Copyright (C) 1997-2013 Jordan Russell. All rights reserved.
Portions Copyright (C) 2000-2013 Martijn Laan. All rights reserved.

This software is provided "as-is," without any express or implied warranty.
In no event shall the author be held liable for any damages arising from the
use of this software.

Permission is granted to anyone to use this software for any purpose,
including commercial applications, and to alter and redistribute it,
provided that the following conditions are met:

1. All redistributions of source code files must retain all copyright
   notices that are currently in place, and this list of conditions without
   modification.

2. All redistributions in binary form must retain all occurrences of the
   above copyright notice and web site addresses that are currently in
   place (for example, in the About boxes).

3. The origin of this software must not be misrepresented; you must not
   claim that you wrote the original software. If you use this software to
   distribute a product, an acknowledgment in the product documentation
   would be appreciated but is not required.

4. Modified versions in source or binary form must be plainly marked as
   such, and must not be misrepresented as being the original software.


Jordan Russell
jr-2010 AT jrsoftware.org
http://www.jrsoftware.org/
legal\VERIFICATION.txt 
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The installer have been downloaded from their official file server <http://files.jrsoftware.org/is/6/>
this can be navigated to from the main page by following:

1. Go to http://www.jrsoftware.org/isinfo.php
2. Click on 'Download Inno Setup'
3. Click on 'Old Downloads'
4. Click on 'available' under 'Version 5.x'

and the checksum can be verified like this:

1. Download <http://files.jrsoftware.org/is/6/innosetup-6.1.2.exe>
2. Then use one of the following methods to obtain the checksum
  - Use powershell function 'Get-Filehash'
  - Use chocolatey utility 'checksum.exe'

  checksum type: sha256
  checksum: A3CE1C40EF9C71A92691AAFF0F413F530C8C9E3C766BE481BC63CA7CC74E35E7

File 'license.txt' is obtained from <https://github.com/jrsoftware/issrc/blob/d33ce5c66191d2bd359eb8ecdaa0dfb9833fbee8/license.txt>
tools\chocolateyInstall.ps1 
$ErrorActionPreference = 'Stop';

$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$filePath = "$toolsDir\innosetup-6.1.2.exe"

$packageArgs = @{
  packageName   = 'innosetup'
  fileType      = 'exe'
  softwareName  = 'Inno Setup*'
  file          = $filePath
  silentArgs    = "/SILENT /SUPPRESSMSGBOXES /NORESTART /SP- /LOG=`"$($env:TEMP)\$($env:chocolateyPackageName).$($env:chocolateyPackageVersion).InnoInstall.log`""
  validExitCodes= @(0,3010,1641)
}

$pp = Get-PackageParameters
if ($pp.UseInf) {
  if (Test-Path "$($pp.UseInf)") {
    Write-Host "Using existing configuration file at '$($pp.UseInf)'"
    $packageArgs['silentArgs'] = "$($packageArgs['silentArgs']) /LOADINF=`"$($pp.UseInf)`""
  } else {
    Write-Host "Creating new configuration file at '$($pp.UseInf)'"
    $packageArgs['silentArgs'] = "$($packageArgs['silentArgs']) /SAVEINF=`"$($pp.UseInf)`""
  }
}

Install-ChocolateyInstallPackage @packageArgs

Remove-Item -Force $filePath

$installLocation = Get-AppInstallLocation $packageArgs.softwareName
if ($installLocation) {
  Write-Host "$($packageArgs.packageName) installed to '$installLocation'"
  Register-Application "$installLocation\ISCC.exe"
  Register-Application "$installLocation\Compil32.exe" $packageArgs.packageName
  Install-BinFile "ISCC" "$installLocation\ISCC.exe"
} else {
  Write-Warning "Can't find $($packageArgs.packageName) install location"
}
tools\chocolateyUninstall.ps1 
$ErrorActionPreference = 'Stop';

$packageName = 'innosetup'
$softwareName = 'Inno Setup*'
$installerType = 'EXE'

$silentArgs = "/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP- /LOG=`"$($env:TEMP)\$($env:chocolateyPackageName).$($env:chocolateyPackageVersion).InnoUninstall.log`""
$validExitCodes = @(0)

$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $softwareName

if ($key.Count -eq 1) {
	$key | ForEach-Object {
		$file = "$($_.UninstallString.Trim('"'))"

	Uninstall-ChocolateyPackage `
		-PackageName $packageName `
		-FileType $installerType `
		-SilentArgs "$silentArgs" `
		-ValidExitCodes $validExitCodes `
		-File "$file"
	}
} 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 | ForEach-Object {Write-Warning "- $_.DisplayName"}
}

$appPathKey = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\"
if (Test-Path "$appPathKey\ISCC.exe") { Remove-Item "$appPathKey\ISCC.exe" -Force }
if (Test-Path "$appPathKey\$packageName.exe") { Remove-Item "$appPathKey\$packageName.exe" -Force }
Uninstall-BinFile "ISCC"
tools\innosetup-6.1.2.exe 
md5: 190F916EB89938F88E47D9AC91E7E012 | sha1: 3F9F46B2A4FF8CCD141370D5CEF6ED0E91D42F6F | sha256: A3CE1C40EF9C71A92691AAFF0F413F530C8C9E3C766BE481BC63CA7CC74E35E7 | sha512: EA6E276479011C0C90F58A68E95E79CF3273E0E5D6794749942493E5EEA5B99B4A3F2EC881EF14CF7231DBC902408D3A29D8225CF3228C9B0DE266CD7E02582A

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
Inno Setup 6.1.2 13083 Sunday, November 15, 2020 Approved
Inno Setup 6.1.1-beta 349 Thursday, October 29, 2020 Approved
Inno Setup 6.1.0-beta 688 Sunday, September 13, 2020 Approved
Inno Setup 6.0.5 40981 Thursday, May 21, 2020 Approved
Inno Setup 6.0.4 12330 Friday, March 13, 2020 Approved
Inno Setup 6.0.3 21853 Thursday, October 10, 2019 Approved
Inno Setup 6.0.2 21016 Sunday, June 16, 2019 Approved
Inno Setup 6.0.0-dev-3 298 Friday, December 14, 2018 Exempted
Inno Setup 6.0.0-dev-2 235 Monday, September 17, 2018 Approved
Inno Setup 5.6.1.20190126 24261 Saturday, January 26, 2019 Approved
Discussion for the Inno Setup Package

Ground Rules:

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