Downloads of v 1.00:


Last Update:

19 Aug 2017

Package Maintainer(s):

Software Author(s):

  • Bill Curran


instchoco bcurran3 choco unoffcial standalone installer portable

(unofficial) InstChoco (Portable)

This is not the latest version of (unofficial) InstChoco (Portable) available.

  • 1
  • 2
  • 3

1.00 | Updated: 19 Aug 2017



Downloads of v 1.00:



Software Author(s):

  • Bill Curran

  • 1
  • 2
  • 3
(unofficial) InstChoco (Portable) 1.00

This is not the latest version of (unofficial) InstChoco (Portable) available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


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


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


To uninstall (unofficial) InstChoco (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 instchoco -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 instchoco -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 instchoco installed
    name: instchoco
    state: present
    version: 1.00
    source: STEP 3 URL

See docs at

chocolatey_package 'instchoco' do
  action    :install
  version  '1.00'
  source   'STEP 3 URL'

See docs at

    Name: instchoco,
    Version: 1.00,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller instchoco
   Name     = 'instchoco'
   Ensure   = 'Present'
   Version  = '1.00'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'instchoco':
  provider => 'chocolatey',
  ensure   => '1.00',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install instchoco version="1.00" 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 flcdrg on 26 Aug 2017.


Screenshot of InstChoco in use

QUESTION: "Why do I need an installer for Chocolatey when I already have Chocolatey installed?"

ANSWER: You need it for the NEXT time you want to install Chocolatey and it will make the task much EASIER!

I wrote this as a batch file a couple of years ago so I wouldn't constantly have to reference for the VERY long command to install Chocolatey. I put in some basic error checking for administrator privileges, network connectivity, date checking, etc. I then placed the batchfile on my local server, on my website, in Dropbox, on USB thumbdrives, everywhere I could think of so I'd have easy access to it. I've used it for my computers, friend's computers, client's computers, and almost every Wintel computer I've touched in the last few years. It has served me well and saved me time. I've now stripped out all the annoying pauses, made it no-interaction-required, and compiled it to an executable program called InstChoco. It's now suitable for other people to use as well. My EUREKA! moment in re-creating this as an executable and expanding it's features was after writing my Choco Package List Backup to Local and Cloud script. I realized I could go a step further by integrating Choco Package List Backup to Local and Cloud along with InstChoco for a complete backup and recovery solution of my/your/his/her/their/everyone's Chocolatey packages. I hope InstChoco serves you well and saves you time!


  • InstChoco uses Rob's "Install with cmd.exe" method for installing Chocolatey.
  • InstChoco integrates with Choco Package List Backup to Local and Cloud to provide a very convienant way to reinstall Chocolatey and your backed up packages list.
  • InstChoco will enable up to four choco features if you pass them as parameters, i.e. allowGlobalConfirmation, failOnAutoUninstaller, allowEmptyChecksums, etc.
  • InstChoco will automatically run CINST PACKAGES.CONFIG -Y if packages.config is found in the current directory.

You can find InstChoco.exe in \programdata\chocolatey\lib\instchoco\tools. I tell you this because I KNOW you want to copy it to your local server, website, Dropbox, USB thumbdrives, and everywhere you can think of so you'll have easy access to it.

Usage: InstChoco -y


md5: FFE8D86741E845D1FDBE5AF03B6D7D71 | sha1: 4D875BCE69C413542BF5EB8CB668B80885DBD108 | sha256: 99366BD182946F7AAAF0070244F8F96CC160274E85892F5AD3D54F658444908B | sha512: 2C94EDBF9BD0D4E7B098556069C9741ACAB4D075D8E67DA7F47E85CDF9EE43873CD03C621AD7F2A6AAB6EBB08762A345A9DEB661E4CEAECD52E517697F7C6A3C
==================== InstChoco ====================

InstChoco is free and Copylefted by Bill Curran.


bcurran3 08/19/2017

==================== InstChoco ====================
==================== InstChoco ====================

This InstChoco Chocolatey package was uploaded by the author, Bill Curran aka BCURRAN3.

==================== InstChoco ====================

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
(unofficial) InstChoco (Portable) 2.10 1007 Sunday, February 24, 2019 Approved
(unofficial) InstChoco (Portable) 2.02 1061 Tuesday, May 22, 2018 Approved
(unofficial) InstChoco (Portable) 2.01 276 Sunday, May 20, 2018 Approved
(unofficial) InstChoco (Portable) 2.00 298 Thursday, May 17, 2018 Approved

This package has no dependencies.

Discussion for the (unofficial) InstChoco (Portable) Package

Ground Rules:

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