Downloads of v 0.0.2:


Last Update:

13 Sep 2018

Package Maintainer(s):

Software Author(s):

  • bcurran3


bcurran3 unofficial chocolatey powershell test environment packagers maintainers

(unofficial) Chocolatey Powershell

This is not the latest version of (unofficial) Chocolatey Powershell available.

0.0.2 | Updated: 13 Sep 2018



Downloads of v 0.0.2:



Software Author(s):

  • bcurran3

(unofficial) Chocolatey Powershell 0.0.2

This is not the latest version of (unofficial) Chocolatey Powershell available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install (unofficial) Chocolatey Powershell, run the following command from the command line or from PowerShell:


To upgrade (unofficial) Chocolatey Powershell, run the following command from the command line or from PowerShell:


To uninstall (unofficial) Chocolatey Powershell, 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 chocolateypowershell -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 chocolateypowershell -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 chocolateypowershell installed
    name: chocolateypowershell
    state: present
    version: 0.0.2
    source: STEP 3 URL

See docs at

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

chocolatey_package 'chocolateypowershell' do
  action    :install
  version  '0.0.2'
  source   'STEP 3 URL'

See docs at

    Name: chocolateypowershell,
    Version: 0.0.2,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller chocolateypowershell
   Name     = 'chocolateypowershell'
   Ensure   = 'Present'
   Version  = '0.0.2'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'chocolateypowershell':
  provider => 'chocolatey',
  ensure   => '0.0.2',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install chocolateypowershell version="0.0.2" 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 gep13 on 20 Sep 2018.


Screenshot example of Chocolatey PowerShell

Chocolatey PowerShell loads Chocolatey modules to directly test Chocolatey functions in PowerShell.


chocolateypowershell was created for Chocolatey package maintainers who want to test Chocolatey native functions and Chocolatey extensions functions in PowerShell without resorting to creating packages and doing trial runs. Now you can just run ChocolateyPowerShell and test away!


Just click the ChocolateyPowerShell icon on your desktop and hit yes to the UAC and then you can start entering and using Chocolatey functions. NOTE: There are environmental variables you will need to declare such as $packageName etc. that will be required by many functions.


Click here to Patreon-ize the package maintainer.

Set-Location $env:ChocolateyInstall\helpers
Import-Module $env:ChocolateyInstall\helpers\chocolateyProfile.psm1
Import-Module $env:ChocolateyInstall\helpers\chocolateyInstaller.psm1
Set-Location $env:ChocolateyInstall\extensions\chocolatey-core
Import-Module $env:ChocolateyInstall\extensions\chocolatey-core\chocolatey-core.psm1
Set-Location $env:SystemDrive\
function global:Get-CPSHelp{get-childitem function:}
Write-Host "Welcome to ChocolateyPowerShell! - Chocolatey functions and extensions are now loaded." -foreground white
Write-Host 'Type Get-CPSHelp to see a list of available functions.' -foreground white
function global:prompt {"[ChocolateyPS] $($ExecutionContext.SessionState.Path.CurrentLocation)$('>' * ($nestedPromptLevel + 1)) "}
$packageName  = 'chocolateypowershell' 
$shortcutName = 'ChocolateyPowerShell.lnk'
$toolsDir     = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$exe          = "$env:SystemRoot\System32\WindowsPowerShell\v1.0\powershell.exe"

Install-ChocolateyShortcut -shortcutFilePath "$env:Public\Desktop\$shortcutName" -targetPath $exe -Arguments "-NoProfile -InputFormat None -ExecutionPolicy Bypass -noexit -c $toolsDir\chocolateyEnvironment.ps1" -WorkingDirectory "$env:SystemDrive\" -RunAsAdmin

if (Test-Path "$env:ProgramData\Microsoft\Windows\Start Menu\Programs\Chocolatey"){
    Install-ChocolateyShortcut -shortcutFilePath "$env:ProgramData\Microsoft\Windows\Start Menu\Programs\Chocolatey\$shortcutName" -targetPath $exe -Arguments "-NoProfile -InputFormat None -ExecutionPolicy Bypass -noexit -c $toolsDir\chocolateyEnvironment.ps1" -WorkingDirectory "$env:SystemDrive\" -RunAsAdmin
   } else {
     Install-ChocolateyShortcut -shortcutFilePath "$env:ProgramData\Microsoft\Windows\Start Menu\Programs\$shortcutName" -targetPath $exe -Arguments "-NoProfile -InputFormat None -ExecutionPolicy Bypass -noexit -c $toolsDir\chocolateyEnvironment.ps1" -WorkingDirectory "$env:SystemDrive\" -RunAsAdmin
$packageName  = 'chocolateypowershell' 
$shortcutName = 'ChocolateyPowerShell.lnk'

remove-item "$env:Public\Desktop\$shortcutName" -Force -ErrorAction SilentlyContinue
remove-item "$env:ProgramData\Microsoft\Windows\Start Menu\Programs\Chocolatey\$shortcutName" -Force -ErrorAction SilentlyContinue
remove-item "$env:ProgramData\Microsoft\Windows\Start Menu\Programs\$shortcutName" -Force -ErrorAction SilentlyContinue

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) Chocolatey Powershell 1411 Friday, December 7, 2018 Approved
(unofficial) Chocolatey Powershell 0.0.2 176 Thursday, September 13, 2018 Approved
(unofficial) Chocolatey Powershell 0.0.1 139 Thursday, August 2, 2018 Approved


  • 0.0.2 - now bypasses system execution policy, added choco-shortcuts-winconfig support, added help, clean up
  • 0.0.1 - initial release.

This package has no dependencies.

Discussion for the (unofficial) Chocolatey Powershell Package

Ground Rules:

  • This discussion is only about (unofficial) Chocolatey Powershell and the (unofficial) Chocolatey Powershell 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) Chocolatey Powershell, 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