Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.
Moderation
Every version of each package undergoes a rigorous moderation process before it goes live that typically includes:
- Security, consistency, and quality checking
- Installation testing
- Virus checking through VirusTotal
- Human moderators who give final review and sign off
More detail at Security and Moderation.
Organizational Use
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
Disclaimer
Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Learn more...
-
STEP1
Package Review
-
STEP2
Integration Method
-
STEP3
Internal Repo Url
-
STEP4
Environment Setup
-
STEP5
Install Script
Step 1: Review Your Packages
Step 2: Choose Your Integration Method
Step 3: Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
Step 3: Copy Your Script or Download Config
Option 1: Copy Script
Option 2: Download Config
Step 4: Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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://community.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 packages and push them to a repository
Download Packages
-
Open Source
-
Download the packages:
Download Packages - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
-
For package and dependencies run:
- Automate package internalization
-
Run: (additional options)
Step 5: Copy Your Script
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:
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### We initialize a few things that are needed by this script - there are no other requirements.
$ErrorActionPreference = "Stop"
#### Set TLS 1.2 (3072) as that is the minimum required by various up-to-date repositories.
#### Use integers because the enumeration value for TLS 1.2 won't exist
#### in .NET 4.0, even though they are addressable if .NET 4.5+ is
#### installed (.NET 4.5 is an in-place upgrade).
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072
#### We use this variable for future REST calls.
$RequestArguments = @{
UseBasicParsing = $true
}
## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$NugetRepositoryUrl = "INTERNAL REPO URL"
### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# $NugetRepositoryCredential = [PSCredential]::new(
# "username",
# ("password" | ConvertTo-SecureString -AsPlainText -Force)
# )
# $RequestArguments.Credential = $NugetRepositoryCredential
### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it
$ChocolateyDownloadUrl = "$($NugetRepositoryUrl.TrimEnd('/'))/package/chocolatey.1.1.0.nupkg"
### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"
#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt"
#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
#### Download the Nupkg, appending .zip to the filename to handle archive cmdlet limitations
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
$TempDirectory = Join-Path $env:Temp "chocolateyInstall"
if (-not (Test-Path $TempDirectory -PathType Container)) {
$null = New-Item -Path $TempDirectory -ItemType Directory
}
$DownloadedNupkg = Join-Path $TempDirectory "$(Split-Path $ChocolateyDownloadUrl -Leaf).zip"
Invoke-WebRequest -Uri $ChocolateyDownloadUrl -OutFile $DownloadedNupkg @RequestArguments
#### Extract the Nupkg, and run the chocolateyInstall script
if (Get-Command Microsoft.PowerShell.Archive\Expand-Archive -ErrorAction SilentlyContinue) {
Microsoft.PowerShell.Archive\Expand-Archive -Path $DownloadedNupkg -DestinationPath $TempDirectory -Force
} else {
# PowerShell versions <4.0 do not have this function available
try {
$shellApplication = New-Object -ComObject Shell.Application
$zipPackage = $shellApplication.NameSpace($DownloadedNupkg)
$destinationFolder = $shellApplication.NameSpace($TempDirectory)
$destinationFolder.CopyHere($zipPackage.Items(), 0x10)
} catch {
Write-Warning "Unable to unzip package using built-in compression."
throw $_
}
}
& $(Join-Path $TempDirectory "tools\chocolateyInstall.ps1")
}
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
refreshenv
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# choco feature enable -n useFipsCompliantChecksums
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
choco config set --name cacheLocation --value C:\ProgramData\chocolatey\cache
#### Increase timeout to at least 4 hours
choco config set --name commandExecutionTimeoutSeconds --value 14400
#### Turn off download progress when running choco through integrations
choco feature disable --name showDownloadProgress
### c. Sources ###
#### Remove the default community package repository source
choco source list --limitoutput | ConvertFrom-Csv -Header 'Name', 'Location' -Delimiter '|' | ForEach-Object {
if ($_.Location -eq 'https://community.chocolatey.org/api/v2/') {
choco source remove -n $_.Name
}
}
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
if ($NugetRepositoryCredential) {
choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --user $NugetRepositoryCredential.UserName --password $NugetRepositoryCredential.GetNetworkCredential().Password --priority 1
} else {
choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --priority 1
}
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
choco upgrade chocolatey --confirm
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
choco install chocolatey-license --source $NugetRepositoryUrl --confirm
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
choco source disable --name chocolatey.licensed
} else {
Write-Warning "Not disabling 'chocolatey.licensed' feed, as Chocolatey-License has not been installed."
}
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
choco install chocolatey.extension --source $NugetRepositoryUrl --confirm
} else {
Write-Warning "Not installing 'chocolatey.extension', as Chocolatey-License has not been installed."
}
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
choco feature disable --name showNonElevatedWarnings
choco feature enable --name useBackgroundService
choco feature enable --name useBackgroundServiceWithNonAdministratorsOnly
choco feature enable --name allowBackgroundServiceUninstallsFromUserInstallsOnly
choco config set --name allowedBackgroundServiceCommands --value "install,upgrade,uninstall"
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
choco install chocolatey-agent --source $NugetRepositoryUrl --confirm
choco config set --name CentralManagementServiceUrl --value $ChocolateyCentralManagementUrl
if ($ChocolateyCentralManagementClientSalt) {
choco config set --name centralManagementClientCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementClientSalt
}
if ($ChocolateyCentralManagementServiceSalt) {
choco config set --name centralManagementServiceCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementServiceSalt
}
choco feature enable --name useChocolateyCentralManagement
choco feature enable --name useChocolateyCentralManagementDeployments
}
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
If Applicable - Chocolatey Configuration/Installation
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### i. chocolatey.chocolatey
##### You will require the chocolatey.chocolatey collection to be installed
##### on all machines using this playbook.
##### Please see https://github.com/chocolatey/chocolatey-ansible/#installing-the-collection-from-ansible-galaxy
- name: Install and Configure Chocolatey
hosts: all
## 2. TOP LEVEL VARIABLES ##
vars:
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
nuget_repository_url: INTERNAL REPO URL
### b. Internal Repository Credential ###
#### If required, add the repository access credential here and
#### uncomment lines with source_username and source_password below
# nuget_repository_username: username
# nuget_repository_password: password
### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# chocolatey_central_management_url: https://chocolatey-central-management:24020/ChocolateyManagementService
#### ii. If using a Client Salt, add it here
# chocolatey_central_management_client_salt: clientsalt
#### iii. If using a Service Salt, add it here
# chocolatey_central_management_service_salt: servicesalt
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
tasks:
- name: Install chocolatey
win_chocolatey:
name: chocolatey
source: {{ nuget_repository_url }}
# source_username: {{ nuget_repository_username }}
# source_password: {{ nuget_repository_password }}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# - name: Enable FIPS compliance
# win_chocolatey_feature:
# name: useFipsCompliantChecksums
# state: enabled
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
- name: Set the cache location
win_chocolatey_config:
name: cacheLocation
state: present
value: C:\ProgramData\chocolatey\cache
#### Increase timeout to at least 4 hours
- name: Set the command execution timeout
win_chocolatey_config:
name: commandExecutionTimeoutSeconds
state: present
value: 14400
#### Turn off download progress when running choco through integrations
- name: Disable showing download progress
win_chocolatey_feature:
name: showDownloadProgress
state: disabled
### c. Sources ###
#### Remove the default community package repository source
- name: Remove Chocolatey Community Repository
win_chocolatey_source:
name: chocolatey
state: absent
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
- name: Add Internal Repository
win_chocolatey_source:
name: ChocolateyInternal
state: present
source: {{ nuget_repository_url }}
# source_username: {{ nuget_repository_username }}
# source_password: {{ nuget_repository_password }}
priority: 1
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
- name: Upgrade Chocolatey
win_chocolatey:
name: chocolatey
state: latest
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
- name: Install Chocolatey License
win_chocolatey:
name: chocolatey-license
source: ChocolateyInternal
state: latest
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
- name: Disable Chocolatey Community Repository
win_chocolatey_source:
name: chocolatey.licensed
state: disabled
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
- name: Install Chocolatey Extension
win_chocolatey:
name: chocolatey.extension
source: ChocolateyInternal
state: latest
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
- name: Hide not-elevated warnings
win_chocolatey_feature:
name: showNonElevatedWarnings
state: disabled
- name: Use background mode for self-service
win_chocolatey_feature:
name: useBackgroundService
state: enabled
- name: Use background service for non-admins
win_chocolatey_feature:
name: useBackgroundServiceWithNonAdministratorsOnly
state: enabled
- name: Allow background uninstallation for user installs
win_chocolatey_feature:
name: allowBackgroundServiceUninstallsFromUserInstallsOnly
state: enabled
- name: Set allowed background service commands
win_chocolatey_config:
name: backgroundServiceAllowedCommands
state: present
value: install,upgrade,uninstall
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
- name: Install Chocolatey Agent
when: chocolatey_central_management_url is defined
win_chocolatey:
name: chocolatey-agent
source: ChocolateyInternal
state: latest
- name: Set the Central Management Service URL
when: chocolatey_central_management_url is defined
win_chocolatey_config:
name: CentralManagementServiceUrl
state: present
value: {{ chocolatey_central_management_url }}
- name: Set the Central Management Client Salt
when: chocolatey_central_management_client_salt is defined
win_chocolatey_config:
name: centralManagementClientCommunicationSaltAdditivePassword
state: present
value: {{ chocolatey_central_management_client_salt }}
- name: Set the Central Management Service Salt
when: chocolatey_central_management_service_salt is defined
win_chocolatey_config:
name: centralManagementServiceCommunicationSaltAdditivePassword
state: present
value: {{ chocolatey_central_management_service_salt }}
- name: Use Central Management
when: chocolatey_central_management_url is defined
win_chocolatey_feature:
name: useChocolateyCentralManagement
state: enabled
- name: Use Central Management Deployments
when: chocolatey_central_management_url is defined
win_chocolatey_feature:
name: useChocolateyCentralManagementDeployments
state: enabled
See docs at https://docs.chef.io/resource_chocolatey_package.html.
If Applicable - Chocolatey Configuration/Installation
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### The Chocolatey resources are available with any recent version of Chef.
#### We utilise the Chocolatey recipe to install the Chocolatey binaries.
include_recipe "chocolatey"
## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
NugetRepositoryUrl = "INTERNAL REPO URL"
### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# NugetRepositoryUsername = "username"
# NugetRepositoryPassword = "password"
### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
ChocolateyNupkgUrl = "INTERNAL REPO URL/package/chocolatey.1.1.0.nupkg",
### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"
#### ii. If using a Client Salt, add it here
# ChocolateyCentralManagementClientSalt = "clientsalt"
#### iii. If using a Service Salt, add it here
# ChocolateyCentralManagementServiceSalt = "servicesalt"
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
node['chocolatey']['install vars'] = {
'chocolateyDownloadUrl' => "#{ChocolateyNupkgUrl}",
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# chocolatey_feature 'useFipsCompliantChecksums' do
# action :enable
# end
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolatey_config 'cacheLocation' do
value 'C:\ProgramData\chocolatey\cache'
end
#### Increase timeout to at least 4 hours
chocolatey_config 'commandExecutionTimeoutSeconds' do
value '14400'
end
#### Turn off download progress when running choco through integrations
chocolatey_feature 'showDownloadProgress' do
action :disable
end
### c. Sources ###
#### Remove the default community package repository source
chocolatey_source 'chocolatey' do
action :remove
end
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
chocolatey_source 'ChocolateyInternal' do
source "#{NugetRepositoryUrl}"
priority 1
action :add
end
execute 'ChocolateyInternal' do
command "choco source add --name ChocolateyInternal -s #{NugetRepositoryUrl} -u=#{NugetRepositoryUsername} -p=#{NugetRepositoryPassword} --priority=1"
only_if { NugetRepositoryUsername != nil || NugetRepositoryPassword != nil }
end
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
chocolatey_package 'chocolatey' do
action :upgrade
source "#{NugetRepositoryUrl}"
end
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
chocolatey_package 'chocolatey-license' do
action :install
source "#{NugetRepositoryUrl}"
end
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
chocolatey_source 'chocolatey.licensed' do
action :disable
end
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
chocolatey_package 'chocolatey.extention' do
action install
source "#{NugetRepositoryUrl}"
end
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolatey_feature 'showNonElevatedWarnings' do
action :disable
end
chocolatey_feature 'useBackgroundService' do
action :enable
end
chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
action :enable
end
chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
action :enable
end
chocolatey_config 'backgroundServiceAllowedCommands' do
value 'install,upgrade,uninstall'
end
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
chocolatey_package 'chocolatey-agent' do
action install
source "#{NugetRepositoryUrl}"
# user "#{NugetRepositoryUsername}"
# password "#{NugetRepositoryPassword}"
only_if { ChocolateyCentralManagementUrl != nil }
end
chocolatey_config 'CentralManagementServiceUrl' do
value "#{ChocolateyCentralManagementUrl}"
only_if { ChocolateyCentralManagementUrl != nil }
end
chocolatey_config 'centralManagementClientCommunicationSaltAdditivePassword' do
value "#{ChocolateyCentralManagementClientSalt}"
only_if { ChocolateyCentralManagementClientSalt != nil }
end
chocolatey_config 'centralManagementServiceCommunicationSaltAdditivePassword' do
value "#{ChocolateyCentralManagementServiceSalt}"
only_if { ChocolateyCentralManagementServiceSalt != nil }
end
chocolatey_feature 'useChocolateyCentralManagement' do
action :enable
only_if { ChocolateyCentralManagementUrl != nil }
end
chocolatey_feature 'useChocolateyCentralManagementDeployments' do
action :enable
only_if { ChocolateyCentralManagementUrl != nil }
end
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
If Applicable - Chocolatey Configuration/Installation
#requires -Modules cChoco
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### i. Requires chocolatey\cChoco DSC module to be installed on the machine compiling the DSC manifest
#### NOTE: This will need to be installed before running the DSC portion of this script
if (-not (Get-Module cChoco -ListAvailable)) {
$null = Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
if (($PSGallery = Get-PSRepository -Name PSGallery).InstallationPolicy -ne "Trusted") {
Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
}
Install-Module -Name cChoco
if ($PSGallery.InstallationPolicy -ne "Trusted") {
Set-PSRepository -Name PSGallery -InstallationPolicy $PSGallery.InstallationPolicy
}
}
#### ii. Requires a hosted copy of the install.ps1 script
##### This should be available to download without authentication.
##### The original script can be found here: https://community.chocolatey.org/install.ps1
Configuration ChocolateyConfig {
## 2. TOP LEVEL VARIABLES ##
param(
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$NugetRepositoryUrl = "INTERNAL REPO URL",
### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$ChocolateyNupkgUrl = "INTERNAL REPO URL/package/chocolatey.1.1.0.nupkg",
### c. Internal Repository Credential ###
#### If required, add the repository access credential here
# $NugetRepositoryCredential = [PSCredential]::new(
# "username",
# ("password" | ConvertTo-SecureString -AsPlainText -Force)
# ),
### d. Install.ps1 URL
#### The path to the hosted install script:
$ChocolateyInstallPs1Url = "https://community.chocolatey.org/install.ps1"
### e. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService",
#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt",
#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"
)
Import-DscResource -ModuleName PSDesiredStateConfiguration
Import-DscResource -ModuleName cChoco
Node 'localhost' {
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
Environment chocoDownloadUrl {
Name = "chocolateyDownloadUrl"
Value = $ChocolateyNupkgUrl
}
cChocoInstaller installChocolatey {
DependsOn = "[Environment]chocoDownloadUrl"
InstallDir = Join-Path $env:ProgramData "chocolatey"
ChocoInstallScriptUrl = $ChocolateyInstallPs1Url
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# cChocoFeature featureFipsCompliance {
# FeatureName = "useFipsCompliantChecksums"
# }
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
cChocoConfig cacheLocation {
DependsOn = "[cChocoInstaller]installChocolatey"
ConfigName = "cacheLocation"
Value = "C:\ProgramData\chocolatey\cache"
}
#### Increase timeout to at least 4 hours
cChocoConfig commandExecutionTimeoutSeconds {
DependsOn = "[cChocoInstaller]installChocolatey"
ConfigName = "commandExecutionTimeoutSeconds"
Value = 14400
}
#### Turn off download progress when running choco through integrations
cChocoFeature showDownloadProgress {
DependsOn = "[cChocoInstaller]installChocolatey"
FeatureName = "showDownloadProgress"
Ensure = "Absent"
}
### c. Sources ###
#### Remove the default community package repository source
cChocoSource removeCommunityRepository {
DependsOn = "[cChocoInstaller]installChocolatey"
Name = "chocolatey"
Ensure = "Absent"
}
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here.
#### NOTE: This EXAMPLE may require changes
cChocoSource addInternalSource {
DependsOn = "[cChocoInstaller]installChocolatey"
Name = "ChocolateyInternal"
Source = $NugetRepositoryUrl
Credentials = $NugetRepositoryCredential
Priority = 1
}
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
cChocoPackageInstaller updateChocolatey {
DependsOn = "[cChocoSource]addInternalSource", "[cChocoSource]removeCommunityRepository"
Name = "chocolatey"
AutoUpgrade = $true
}
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
cChocoPackageInstaller chocolateyLicense {
DependsOn = "[cChocoPackageInstaller]updateChocolatey"
Name = "chocolatey-license"
}
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
Script disableLicensedSource {
DependsOn = "[cChocoPackageInstaller]chocolateyLicense"
GetScript = {
$Source = choco source list --limitoutput | `
ConvertFrom-Csv -Delimiter '|' -Header Name, Source, Disabled | `
Where-Object Name -eq "chocolatey.licensed"
return @{
Result = if ($Source) {
[bool]::Parse($Source.Disabled)
} else {
Write-Warning "Source 'chocolatey.licensed' was not present."
$true # Source does not need disabling
}
}
}
SetScript = {
$null = choco source disable --name "chocolatey.licensed"
}
TestScript = {
$State = [ScriptBlock]::Create($GetScript).Invoke()
return $State.Result
}
}
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
cChocoPackageInstaller chocolateyLicensedExtension {
DependsOn = "[Script]disableLicensedSource"
Name = "chocolatey.extension"
}
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
cChocoFeature hideElevatedWarnings {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "showNonElevatedWarnings"
Ensure = "Absent"
}
cChocoFeature useBackgroundService {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "useBackgroundService"
Ensure = "Present"
}
cChocoFeature useBackgroundServiceWithNonAdmins {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "useBackgroundServiceWithNonAdministratorsOnly"
Ensure = "Present"
}
cChocoFeature useBackgroundServiceUninstallsForUserInstalls {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
FeatureName = "allowBackgroundServiceUninstallsFromUserInstallsOnly"
Ensure = "Present"
}
cChocoConfig allowedBackgroundServiceCommands {
DependsOn = "[cChocoFeature]useBackgroundService"
ConfigName = "backgroundServiceAllowedCommands"
Value = "install,upgrade,uninstall"
}
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
cChocoPackageInstaller chocolateyAgent {
DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
Name = "chocolatey-agent"
}
cChocoConfig centralManagementServiceUrl {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
ConfigName = "CentralManagementServiceUrl"
Value = $ChocolateyCentralManagementUrl
}
if ($ChocolateyCentralManagementClientSalt) {
cChocoConfig centralManagementClientSalt {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
ConfigName = "centralManagementClientCommunicationSaltAdditivePassword"
Value = $ChocolateyCentralManagementClientSalt
}
}
if ($ChocolateyCentralManagementServiceSalt) {
cChocoConfig centralManagementServiceSalt {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
ConfigName = "centralManagementServiceCommunicationSaltAdditivePassword"
Value = $ChocolateyCentralManagementServiceSalt
}
}
cChocoFeature useCentralManagement {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
FeatureName = "useChocolateyCentralManagement"
Ensure = "Present"
}
cChocoFeature useCentralManagementDeployments {
DependsOn = "[cChocoPackageInstaller]chocolateyAgent"
FeatureName = "useChocolateyCentralManagementDeployments"
Ensure = "Present"
}
}
}
}
# If working this into an existing configuration with a good method for
$ConfigData = @{
AllNodes = @(
@{
NodeName = "localhost"
PSDscAllowPlainTextPassword = $true
}
)
}
try {
Push-Location $env:Temp
$Config = ChocolateyConfig -ConfigurationData $ConfigData
Start-DscConfiguration -Path $Config.PSParentPath -Wait -Verbose -Force
} finally {
Pop-Location
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
If Applicable - Chocolatey Configuration/Installation
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.
### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
#### generally really quick to set up and there are quite a few options.
#### Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
#### are repository servers and will give you the ability to manage multiple
#### repositories and types from one server installation.
### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
#### Please see https://chocolatey.org/install#organization
### c. Other Requirements ###
#### i. Requires puppetlabs/chocolatey module
#### See https://forge.puppet.com/puppetlabs/chocolatey
## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
#### Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$_repository_url = 'INTERNAL REPO URL'
### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$_choco_download_url = 'INTERNAL REPO URL/package/chocolatey.1.1.0.nupkg'
### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $_chocolatey_central_management_url = 'https://chocolatey-central-management:24020/ChocolateyManagementService'
#### ii. If using a Client Salt, add it here
# $_chocolatey_central_management_client_salt = "clientsalt"
#### iii. If using a Service Salt, add it here
# $_chocolatey_central_management_service_salt = 'servicesalt'
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
### Note: `chocolatey_download_url is completely different than normal
### source locations. This is directly to the bare download url for the
### chocolatey.nupkg, similar to what you see when you browse to
### https://community.chocolatey.org/api/v2/package/chocolatey
class {'chocolatey':
chocolatey_download_url => $_choco_download_url,
use_7zip => false,
}
## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#chocolateyfeature {'useFipsCompliantChecksums':
# ensure => enabled,
#}
### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolateyconfig {'cacheLocation':
value => 'C:\ProgramData\chocolatey\cache',
}
#### Increase timeout to at least 4 hours
chocolateyconfig {'commandExecutionTimeoutSeconds':
value => '14400',
}
#### Turn off download progress when running choco through integrations
chocolateyfeature {'showDownloadProgress':
ensure => disabled,
}
### c. Sources ###
#### Remove the default community package repository source
chocolateysource {'chocolatey':
ensure => absent,
location => 'https://community.chocolatey.org/api/v2/',
}
#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE requires changes
chocolateysource {'internal_chocolatey':
ensure => present,
location => $_repository_url,
priority => 1,
username => 'optional',
password => 'optional,not ensured',
bypass_proxy => true,
admin_only => false,
allow_self_service => false,
}
### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
#### to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
#### when you browse to https://community.chocolatey.org/api/v2/
package {'chocolatey':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
}
## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/guides/organizations/organizational-deployment-guide#exercise-4-create-a-package-for-the-license
# TODO: Add resource for installing/ensuring the chocolatey-license package
package {'chocolatey-license':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
}
### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
## Disabled sources still need all other attributes until
## https://tickets.puppetlabs.com/browse/MODULES-4449 is resolved.
## Password is necessary with user, but not ensurable, so it should not
## matter what it is set to here. If you ever do get into trouble here,
## the password is your license GUID.
chocolateysource {'chocolatey.licensed':
ensure => disabled,
priority => '10',
user => 'customer',
password => '1234',
require => Package['chocolatey-license'],
}
### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.
#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
package {'chocolatey.extension':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
require => Package['chocolatey-license'],
}
#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/
### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolateyfeature {'showNonElevatedWarnings':
ensure => disabled,
}
chocolateyfeature {'useBackgroundService':
ensure => enabled,
}
chocolateyfeature {'useBackgroundServiceWithNonAdministratorsOnly':
ensure => enabled,
}
chocolateyfeature {'allowBackgroundServiceUninstallsFromUserInstallsOnly':
ensure => enabled,
}
chocolateyconfig {'backgroundServiceAllowedCommands':
value => 'install,upgrade,uninstall',
}
### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if $_chocolatey_central_management_url {
package {'chocolatey-agent':
ensure => latest,
provider => chocolatey,
source => $_repository_url,
require => Package['chocolatey-license'],
}
chocolateyconfig {'CentralManagementServiceUrl':
value => $_chocolatey_central_management_url,
}
if $_chocolatey_central_management_client_salt {
chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
value => $_chocolatey_central_management_client_salt,
}
}
if $_chocolatey_central_management_service_salt {
chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
value => $_chocolatey_central_management_client_salt,
}
}
chocolateyfeature {'useChocolateyCentralManagement':
ensure => enabled,
require => Package['chocolatey-agent'],
}
chocolateyfeature {'useChocolateyCentralManagementDeployments':
ensure => enabled,
require => Package['chocolatey-agent'],
}
}
Need Help? View our docs or file an issue.
There is already a version of this package in your Script Builder
Current Version | New Version |
---|---|
- Passing
- Failing
- Pending
- Unknown / Exempted

Downloads:
726,847
Downloads of v 18.1.8.0:
1,888
Last Update:
09 Jan 2018
Package Maintainer(s):
Software Author(s):
- Maximus5
Tags:
graphical console emulator tabs farmanager powershell cmd bash cygwin msys git
ConEmu
This is not the latest version of ConEmu available.
- 1
- 2
- 3
18.1.8.0 | Updated: 09 Jan 2018
Downloads:
726,847
Downloads of v 18.1.8.0:
1,888
Maintainer(s):
Software Author(s):
- Maximus5
Edit Package
To edit the metadata for a package, please upload an updated version of the package.
Chocolatey's Community Package Repository currently does not allow updating package metadata on the website. This helps ensure that the package itself (and the source used to build the package) remains the one true source of package metadata.
This does require that you increment the package version.
- 1
- 2
- 3
ConEmu
18.1.8.0
This is not the latest version of ConEmu available.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Validation Testing Passed
Verification Testing Passed
DetailsScan 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.
Deployment Method: Individual Install, Upgrade, & Uninstall
To install ConEmu, run the following command from the command line or from PowerShell:
To upgrade ConEmu, run the following command from the command line or from PowerShell:
To uninstall ConEmu, run the following command from the command line or from PowerShell:
Deployment Method:
📝 NOTE: This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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://community.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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download conemu --internalize --version=18.1.8.0 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade conemu -y --source="'INTERNAL REPO URL'" --version="'18.1.8.0'" [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 conemu -y --source="'INTERNAL REPO URL'" --version="'18.1.8.0'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install conemu
win_chocolatey:
name: conemu
version: '18.1.8.0'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'conemu' do
action :install
source 'INTERNAL REPO URL'
version '18.1.8.0'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller conemu
{
Name = "conemu"
Version = "18.1.8.0"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'conemu':
ensure => '18.1.8.0',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. 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 09 Jan 2018.
ConEmu-Maximus5 (short for Console Emulator) is a handy and full featured Windows console window (local terminal) with a lot of enhancements: panes, tabs, tasks, jump lists, quake style, handy text and block selection, handy paste of paths in either Unix or Windows notation, and much more.
ConEmu may work as either standalone window, or embeddable console control. And it may host two types of applications:
- ‘console’: cmd, powershell, Far Manager, bash, and many others;
- ‘graphical’ (GUI): Notepad, PuTTY, GVim, mintty and so on.
Short list of features:
- predefined and user-defined tasks for different shells;
- user friendly text and block selection and paste;
- smooth and friendly window resizing;
- Windows 7 Jump Lists and Progress on Taskbar buttons;
- DosBox integration: run old DOS applications (games) in modern OS;
- quake-style and full screen window modes;
- ANSI sequences and Xterm 256 colors;
- cursor: standard console (horizontal) or GUI (vertical);
- customizable starting tabs;
- Far Manager integration: drag-n-drop, tabs, truecolor, thumbnails;
- unicode and CJK support;
- explore much more features on the project site.
$package = 'ConEmu'
$version = '18.01.08'
$sha256 = '22ED313FF016D34F7080B5EA4E23F5F1C7436EF49B942ABE24EE3DC90CDB96B7'
$isSytem32Bit = (($Env:PROCESSOR_ARCHITECTURE -eq 'x86') -and `
($Env:PROCESSOR_ARCHITEW6432 -eq $null))
$os = if ($isSytem32Bit) { "x86" } else { "x64" }
$url = "https://github.com/Maximus5/ConEmu/releases/download/v$version/ConEmuSetup.$($version.replace('.','')).exe"
# MSI installer, but packed inside wrapper to select x86 or x64
# version. Therefore, treat it as EXE type.
$params = @{
PackageName = $package;
FileType = 'exe';
SilentArgs = "/p:$os /quiet /norestart";
Url = $url;
Url64bit = $url;
checksum = $sha256
checksumType = 'sha256'
checksum64 = $sha256
checksumType64= 'sha256'
}
$script:CE_PID = 0
$script:CE_SRV = 0
$script:CE_WND = 0
$script:CE_DIR = ""
$script:ConEmuC = ""
$script:CE_FILES = @()
function log($s) {
# Write-Host $s
}
function initWinApi() {
Add-Type @"
using System;
using System.Text;
using System.Runtime.InteropServices;
public class ConEmuApi
{
[DllImport("user32.dll", SetLastError=true, CharSet=CharSet.Auto)]
public static extern int IsWindow(IntPtr hwnd);
[DllImport("kernel32.dll", SetLastError = true, CharSet = CharSet.Unicode)]
static extern bool MoveFileEx(string lpExistingFileName, string lpNewFileName, int dwFlags);
public static bool MarkFileDelete(string sourcefile)
{
return MoveFileEx(sourcefile, null, 4);
}
}
"@
}
function isWindowAlive($hwnd) {
if (("ConEmuApi" -as [type]) -eq $null) {
initWinApi
}
$rc = [ConEmuApi]::IsWindow($hwnd)
# log "HWND=$hwnd, rc=$rc"
return ($rc -ne 0)
}
function isProcessAlive($id) {
if ((Get-Process -Id $id -ErrorAction Ignore) -eq $Null) {
return $False
}
return $True
}
function isConEmu() {
if (($env:ConEmuDrawHWND -eq $Null) -Or ($env:ConEmuPID -eq $Null) -Or
($env:ConEmuServerPID -eq $Null) -Or ($env:ConEmuBaseDir -eq $Null)) {
return $False
}
$id = [convert]::ToInt32($env:ConEmuPID)
$srv = [convert]::ToInt32($env:ConEmuServerPID)
$wnd = [convert]::ToInt32($env:ConEmuDrawHWND, 16)
if (-Not (isProcessAlive $id)) {
return $False
}
if (-Not (isWindowAlive $wnd)) {
return $False
}
if (Test-Path -path (Join-Path $env:ConEmuBaseDir "ConEmuC.exe") -pathtype leaf) {
$script:ConEmuC = Join-Path $env:ConEmuBaseDir "ConEmuC.exe"
} elseif (Test-Path -path (Join-Path $env:ConEmuBaseDir "ConEmuC64.exe") -pathtype leaf) {
$script:ConEmuC = Join-Path $env:ConEmuBaseDir "ConEmuC64.exe"
} else {
return $False
}
$script:CE_PID = $id
$script:CE_SRV = $srv
$script:CE_WND = $wnd
$script:CE_DIR = $env:ConEmuBaseDir
return $True
}
function unlockFiles($files) {
$suffix = Get-Date -format yyMMddHHmmss
foreach ($fn in $files) {
$f = @{src_name=$fn; tmp_name=".$fn.$suffix";}
$f.Add("src", (Join-Path $script:CE_DIR $f.src_name))
$f.Add("tmp", (Join-Path $script:CE_DIR $f.tmp_name))
try {
if (Test-Path -path $f.src -pathtype leaf) {
Rename-Item -Path $f.src -NewName $f.tmp_name -ErrorAction Stop
$script:CE_FILES += $f
}
} catch {
}
}
}
function removeTempFiles() {
foreach ($f in $script:CE_FILES) {
try {
Remove-Item $f.tmp -ErrorAction Stop
} catch {
$deleteResult = [ConEmuApi]::MarkFileDelete($f.tmp)
}
}
}
function restoreFiles() {
foreach ($f in $script:CE_FILES) {
try {
Rename-Item -Path $f.tmp -NewName $f.src_name -ErrorAction Stop
} catch {
log "Failed to restore file: $($f.src_name)"
}
}
}
function ConEmuPreUpdate() {
# Checking
if (isConEmu) {
# Note, old ConEmu versions weren't able to detach without confirmation
log "Detaching from ConEmu"
$warn_msg = "Please choose <Yes> in the confirmation dialog"
Write-Host -ForegroundColor Green -NoNewLine $warn_msg
$macro_rc = & $script:ConEmuC -GuiMacro:$script:CE_PID detach 3
Write-Host -NoNewLine ("`r".PadRight($warn_msg.length+1)+"`r")
$wait_delay = 10000
$wait_ms = 250
$wait_count = $wait_delay/$wait_ms
# log "Code=$LASTEXITCODE" # may be always 0 and "OK"
# Sleep for 10 sec waiting for detach
$warn_msg = "Waiting for detach"
Write-Host -ForegroundColor Green -NoNewLine $warn_msg
for ($i = 0; $i -lt $wait_count; $i++) {
if (-Not (isWindowAlive $script:CE_WND)) {
log "Detached successfully"
break
}
# Write-Host -NoNewLine "."
Sleep -m $wait_ms
}
Write-Host -NoNewLine ("`r".PadRight($warn_msg.length+1)+"`r")
if ($i -eq $wait_count) {
throw "Detach failed, please try to run update outside of ConEmu"
}
if (isProcessAlive $script:CE_PID) {
Sleep -s 1
if (isProcessAlive $script:CE_PID) {
$warn_msg = "Requesting ConEmu termination"
Write-Host -ForegroundColor Green -NoNewLine $warn_msg
$macro_rc = & $script:ConEmuC -GuiMacro:$script:CE_PID close 2
for ($i = 0; $i -lt $wait_count; $i++) {
if (-Not (isProcessAlive $script:CE_PID)) {
log "Terminated successfully"
break
}
# Write-Host -NoNewLine "."
Sleep -m $wait_ms
}
Write-Host -NoNewLine ("`r".PadRight($warn_msg.length+1)+"`r")
if ($i -eq $wait_count) {
throw "ConEmu process still alive, please try to run update outside of ConEmu"
}
}
}
if (isProcessAlive $script:CE_SRV) {
log "Terminating console server process PID=$($script:CE_SRV)"
Stop-Process -Force -Id $script:CE_SRV
}
log "Renaming hooks libraries"
unlockFiles @("ConEmuHk.dll", "ConEmuHk64.dll")
log "Console is ready to update ConEmu"
} else {
$is_conemu = $FALSE
try {
& ConEmuC.exe -IsConEmu
$is_conemu = ($LASTEXITCODE -eq 1)
} catch {
}
if ($is_conemu) {
throw "Can't detect proper ConEmu environment variables! Please restart console!"
}
log "PowerShell was not stared from ConEmu"
}
}
function ConEmuPostUpdate() {
if ($script:CE_FILES.Count -ne 0) {
if (Test-Path -path $script:CE_FILES[0] -pathtype leaf) {
# On Success
removeTempFiles
} else {
# On Failure
restoreFiles
}
}
if ($script:CE_PID -ne 0) {
Write-Host -ForegroundColor Green "Console restart is strongly recommended to gain proper ConEmu environment"
# Reattach
$rc = Start-Process -FilePath $script:ConEmuC -ArgumentList @("/ATTACH","/NOCMD") -NoNewWindow
for ($i = 0; $i -lt 100; $i++) {
$rc = & $script:ConEmuC -IsConEmu
if ($LASTEXITCODE -eq 1) { break }
Sleep -m 100
}
}
}
# Unlock ConEmu binaries
ConEmuPreUpdate
# Do installation/update
Install-ChocolateyPackage @params
# Try to restore files if update has failed
ConEmuPostUpdate
# Done
$package = 'ConEmu'
$version = '18.01.08'
$isSytem32Bit = (($Env:PROCESSOR_ARCHITECTURE -eq 'x86') -and `
($Env:PROCESSOR_ARCHITEW6432 -eq $null))
$os = if ($isSytem32Bit) { "x86" } else { "x64" }
$displayName = "ConEmu $($version.replace('.','')).$os"
$installerRoot = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer'
$productsRoot = "$installerRoot\UserData\S-1-5-18\Products"
# To avoid unexpected PC reboot, prohibit ConEmu uninstall from ConEmu
$is_conemu = $FALSE
try {
& ConEmuC.exe -IsConEmu
$is_conemu = ($LASTEXITCODE -eq 1)
} catch {
}
if ($is_conemu) {
throw "Can't detect proper ConEmu environment variables! Please restart console!"
}
Write-Host "Searching for installed msi-packet..."
# ConEmu packages do not have fixed GUIDs
$pkg = ""
Get-ChildItem $productsRoot |
% { ($productsRoot + "\" + (Split-Path -Leaf $_.Name) + "\InstallProperties") } |
? { ($pkg -eq "") -And (Test-Path $_) } |
? { ((Get-ItemProperty $_).DisplayName -eq $displayName) } |
% {
$pkg = (Get-ItemProperty $_).LocalPackage
}
if ($pkg -ne "") {
# Write-Host "Found at $pkg"
Write-Host "Uninstalling '$displayName' via 'msiexec /x $pkg'"
Start-Process -Wait msiexec -ArgumentList @("/x", $pkg, "/qb-!")
}
# Done
Log in or click on link to see number of positives.
- ConEmu.18.1.8.0.nupkg (423bb260790a) - ## / 61
- ConEmuSetup.180108.exe (22ed313ff016) - ## / 67
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.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
ConEmu 22.8.7.0 | 2654 | Sunday, August 7, 2022 | Approved | |
ConEmu 22.4.18.0 | 10817 | Monday, April 18, 2022 | Approved | |
ConEmu 22.3.8.0 | 6936 | Wednesday, March 9, 2022 | Approved | |
ConEmu 21.9.12.0 | 17276 | Monday, September 13, 2021 | Approved | |
ConEmu 21.9.5.0 | 2765 | Sunday, September 5, 2021 | Approved | |
ConEmu 21.8.22.0 | 4384 | Sunday, August 22, 2021 | Approved | |
ConEmu 21.8.16.0 | 3394 | Monday, August 16, 2021 | Approved | |
ConEmu 21.7.18.0 | 7147 | Sunday, July 18, 2021 | Approved | |
ConEmu 21.6.27.0 | 6440 | Sunday, June 27, 2021 | Approved | |
ConEmu 21.6.24.0 | 1759 | Thursday, June 24, 2021 | Approved | |
ConEmu 21.6.20.0 | 1884 | Monday, June 21, 2021 | Approved | |
ConEmu 21.3.14.0 | 13632 | Monday, March 15, 2021 | Approved | |
ConEmu 21.3.12.0 | 1355 | Friday, March 12, 2021 | Approved | |
ConEmu 21.3.4.0 | 4132 | Thursday, March 4, 2021 | Approved | |
ConEmu 21.2.6.0 | 6961 | Sunday, February 7, 2021 | Approved | |
ConEmu 21.2.2.0 | 2490 | Tuesday, February 2, 2021 | Approved | |
ConEmu 21.1.28.0 | 2852 | Thursday, January 28, 2021 | Approved | |
ConEmu 21.1.12.0 | 5879 | Tuesday, January 12, 2021 | Approved | |
ConEmu 21.1.11.0 | 1484 | Monday, January 11, 2021 | Approved | |
ConEmu 21.1.9.0 | 763 | Sunday, January 10, 2021 | Approved | |
ConEmu 20.11.24.0 | 8860 | Wednesday, November 25, 2020 | Approved | |
ConEmu 20.11.23.1 | 1352 | Monday, November 23, 2020 | Approved | |
ConEmu 20.11.23.0 | 103 | Monday, November 23, 2020 | Approved | |
ConEmu 20.11.1.0 | 6464 | Sunday, November 1, 2020 | Approved | |
ConEmu 20.10.11.0 | 7038 | Sunday, October 11, 2020 | Approved | |
ConEmu 20.9.28.0 | 4767 | Monday, September 28, 2020 | Approved | |
ConEmu 20.7.13.0 | 16021 | Monday, July 13, 2020 | Approved | |
ConEmu 20.6.15.0 | 12573 | Monday, June 15, 2020 | Approved | |
ConEmu 20.6.4.0 | 9386 | Thursday, June 4, 2020 | Approved | |
ConEmu 19.10.12.0 | 62364 | Sunday, October 13, 2019 | Approved | |
ConEmu 19.7.14.0 | 28613 | Sunday, July 14, 2019 | Approved | |
ConEmu 19.6.23.0 | 9870 | Sunday, June 23, 2019 | Approved | |
ConEmu 19.5.26.0 | 9607 | Sunday, May 26, 2019 | Approved | |
ConEmu 19.3.31.0 | 13561 | Sunday, March 31, 2019 | Approved | |
ConEmu 19.3.26.0 | 3178 | Wednesday, March 27, 2019 | Approved | |
ConEmu 19.3.24.0 | 2504 | Sunday, March 24, 2019 | Approved | |
ConEmu 19.3.10.0 | 7498 | Sunday, March 10, 2019 | Approved | |
ConEmu 19.3.3.0 | 5942 | Sunday, March 3, 2019 | Approved | |
ConEmu 19.3.1.0 | 1806 | Friday, March 1, 2019 | Approved | |
ConEmu 19.2.25.0 | 3838 | Monday, February 25, 2019 | Approved | |
ConEmu 19.2.24.0 | 1587 | Monday, February 25, 2019 | Approved | |
ConEmu 19.2.17.0 | 4999 | Sunday, February 17, 2019 | Approved | |
ConEmu 19.1.8.0 | 16221 | Saturday, January 12, 2019 | Approved | |
ConEmu 18.6.26.0 | 28989 | Tuesday, June 26, 2018 | Approved | |
ConEmu 18.6.17.0 | 11050 | Sunday, June 17, 2018 | Approved | |
ConEmu 18.5.28.0 | 6276 | Monday, May 28, 2018 | Approved | |
ConEmu 18.5.6.0 | 6326 | Monday, May 7, 2018 | Approved | |
ConEmu 18.5.3.0 | 2141 | Thursday, May 3, 2018 | Approved | |
ConEmu 18.4.29.0 | 2637 | Sunday, April 29, 2018 | Approved | |
ConEmu 18.4.27.0 | 1202 | Saturday, April 28, 2018 | Approved | |
ConEmu 18.4.22.0 | 3085 | Monday, April 23, 2018 | Approved | |
ConEmu 18.4.18.0 | 2325 | Thursday, April 19, 2018 | Approved | |
ConEmu 18.4.16.0 | 1423 | Tuesday, April 17, 2018 | Approved | |
ConEmu 18.4.15.0 | 2013 | Monday, April 16, 2018 | Approved | |
ConEmu 18.4.11.0 | 2085 | Thursday, April 12, 2018 | Approved | |
ConEmu 18.4.9.0 | 2265 | Monday, April 9, 2018 | Approved | |
ConEmu 18.4.8.0 | 1149 | Sunday, April 8, 2018 | Approved | |
ConEmu 18.3.18.0 | 10551 | Monday, March 19, 2018 | Approved | |
ConEmu 18.3.9.0 | 299 | Sunday, April 8, 2018 | Approved | |
ConEmu 18.2.6.0 | 9376 | Tuesday, February 6, 2018 | Approved | |
ConEmu 18.1.31.0 | 2770 | Wednesday, January 31, 2018 | Approved | |
ConEmu 18.1.30.0 | 1634 | Tuesday, January 30, 2018 | Approved | |
ConEmu 18.1.14.0 | 4969 | Monday, January 15, 2018 | Approved | |
ConEmu 18.1.11.0 | 2370 | Thursday, January 11, 2018 | Approved | |
ConEmu 18.1.8.0 | 1888 | Tuesday, January 9, 2018 | Approved | |
ConEmu 17.12.26.0 | 4077 | Wednesday, December 27, 2017 | Approved | |
ConEmu 17.12.17.0 | 3423 | Sunday, December 17, 2017 | Approved | |
ConEmu 17.12.5.0 | 4273 | Wednesday, December 6, 2017 | Approved | |
ConEmu 17.12.3.0 | 2337 | Monday, December 4, 2017 | Approved | |
ConEmu 17.11.17.0 | 4985 | Saturday, November 18, 2017 | Approved | |
ConEmu 17.11.9.0 | 3851 | Friday, November 10, 2017 | Approved | |
ConEmu 17.10.25.0 | 4785 | Thursday, October 26, 2017 | Approved | |
ConEmu 17.9.10.0 | 10118 | Monday, September 11, 2017 | Approved | |
ConEmu 17.8.19.0 | 5825 | Saturday, August 19, 2017 | Approved | |
ConEmu 17.8.7.0 | 3738 | Tuesday, August 8, 2017 | Approved | |
ConEmu 17.8.5.0 | 1720 | Sunday, August 6, 2017 | Approved | |
ConEmu 17.7.30.0 | 2933 | Sunday, July 30, 2017 | Approved | |
ConEmu 17.7.23.0 | 3068 | Sunday, July 23, 2017 | Approved | |
ConEmu 17.7.9.0 | 4103 | Monday, July 10, 2017 | Approved | |
ConEmu 17.7.5.0 | 1989 | Thursday, July 6, 2017 | Approved | |
ConEmu 17.6.22.0 | 3731 | Friday, June 23, 2017 | Approved | |
ConEmu 17.6.5.0 | 4525 | Tuesday, June 6, 2017 | Approved | |
ConEmu 17.5.17.0 | 5162 | Wednesday, May 17, 2017 | Approved | |
ConEmu 17.4.2.0 | 9762 | Monday, April 3, 2017 | Approved | |
ConEmu 17.3.26.0 | 3160 | Monday, March 27, 2017 | Approved | |
ConEmu 17.3.16.0 | 3171 | Friday, March 17, 2017 | Approved | |
ConEmu 17.3.5.0 | 3502 | Monday, March 6, 2017 | Approved | |
ConEmu 17.2.27.0 | 3077 | Tuesday, February 28, 2017 | Approved | |
ConEmu 17.1.18.0 | 7538 | Thursday, January 19, 2017 | Approved | |
ConEmu 16.12.6.0 | 7229 | Wednesday, December 7, 2016 | Approved | |
ConEmu 16.12.3.0 | 1604 | Saturday, December 3, 2016 | Approved | |
ConEmu 16.10.22.0 | 7251 | Saturday, October 22, 2016 | Approved | |
ConEmu 16.10.9.1 | 2991 | Monday, October 10, 2016 | Approved | |
ConEmu 16.10.9.0 | 667 | Monday, October 10, 2016 | Approved | |
ConEmu 16.10.2.0 | 3943 | Monday, October 3, 2016 | Approved | |
ConEmu 16.9.14.0 | 4127 | Thursday, September 15, 2016 | Approved | |
ConEmu 16.9.13.0 | 871 | Wednesday, September 14, 2016 | Approved | |
ConEmu 16.9.4.0 | 2908 | Sunday, September 4, 2016 | Approved | |
ConEmu 16.8.28.0 | 2509 | Monday, August 29, 2016 | Approved | |
ConEmu 16.7.24.0 | 8240 | Monday, July 25, 2016 | Approved | |
ConEmu 16.7.10.0 | 729 | Monday, July 11, 2016 | Approved | |
ConEmu 16.7.7.0 | 403 | Friday, July 8, 2016 | Approved | |
ConEmu 16.6.19.0 | 400 | Monday, June 20, 2016 | Approved | |
ConEmu 16.6.12.0 | 368 | Tuesday, June 14, 2016 | Approved | |
ConEmu 16.6.9.0 | 365 | Thursday, June 9, 2016 | Approved | |
ConEmu 16.6.7.0 | 383 | Tuesday, June 7, 2016 | Approved | |
ConEmu 16.6.5.0 | 355 | Monday, June 6, 2016 | Approved | |
ConEmu 16.5.29.0 | 392 | Sunday, May 29, 2016 | Approved | |
ConEmu 16.5.22.0 | 279 | Monday, May 23, 2016 | Approved | |
ConEmu 16.5.15.0 | 332 | Monday, May 16, 2016 | Approved | |
ConEmu 16.5.4.0 | 486 | Thursday, May 5, 2016 | Approved | |
ConEmu 16.5.3.0 | 311 | Wednesday, May 4, 2016 | Approved | |
ConEmu 16.4.28.0 | 1432 | Thursday, April 28, 2016 | Approved | |
ConEmu 16.4.16.0 | 3105 | Sunday, April 17, 2016 | Approved | |
ConEmu 16.4.13.0 | 1288 | Wednesday, April 13, 2016 | Approved | |
ConEmu 16.4.11.0 | 1017 | Tuesday, April 12, 2016 | Approved | |
ConEmu 16.4.3.1 | 2533 | Monday, April 4, 2016 | Approved | |
ConEmu 16.4.3.0 | 824 | Saturday, April 2, 2016 | Approved | |
ConEmu 16.3.29.0 | 1547 | Wednesday, March 30, 2016 | Approved | |
ConEmu 16.3.28.0 | 756 | Tuesday, March 29, 2016 | Approved | |
ConEmu 16.3.27.0 | 815 | Monday, March 28, 2016 | Approved | |
ConEmu 16.3.24.0 | 1206 | Friday, March 25, 2016 | Approved | |
ConEmu 16.3.13.0 | 2816 | Sunday, March 13, 2016 | Approved | |
ConEmu 16.3.10.0 | 1031 | Friday, March 11, 2016 | Approved | |
ConEmu 16.3.8.0 | 1108 | Tuesday, March 8, 2016 | Approved | |
ConEmu 16.3.1.0 | 1930 | Wednesday, March 2, 2016 | Approved | |
ConEmu 16.2.28.0 | 945 | Monday, February 29, 2016 | Approved | |
ConEmu 16.2.22.0 | 1881 | Monday, February 22, 2016 | Approved | |
ConEmu 16.2.19.0 | 998 | Saturday, February 20, 2016 | Approved | |
ConEmu 16.2.18.0 | 620 | Friday, February 19, 2016 | Approved | |
ConEmu 16.2.17.0 | 805 | Thursday, February 18, 2016 | Approved | |
ConEmu 16.2.11.0 | 1635 | Thursday, February 11, 2016 | Approved | |
ConEmu 16.2.7.0 | 344 | Monday, February 8, 2016 | Approved | |
ConEmu 16.2.4.0 | 1940 | Thursday, February 4, 2016 | Approved | |
ConEmu 16.2.2.0 | 919 | Wednesday, February 3, 2016 | Approved | |
ConEmu 16.1.24.0 | 2182 | Monday, January 25, 2016 | Approved | |
ConEmu 16.1.11.0 | 2815 | Monday, January 11, 2016 | Approved | |
ConEmu 15.12.24.0 | 3210 | Friday, December 25, 2015 | Approved | |
ConEmu 15.12.22.0 | 830 | Tuesday, December 22, 2015 | Approved | |
ConEmu 15.12.17.0 | 1379 | Thursday, December 17, 2015 | Approved | |
ConEmu 15.12.10.0 | 1606 | Thursday, December 10, 2015 | Approved | |
ConEmu 15.12.8.0 | 885 | Tuesday, December 8, 2015 | Approved | |
ConEmu 15.12.7.0 | 591 | Monday, December 7, 2015 | Approved | |
ConEmu 15.12.5.0 | 844 | Sunday, December 6, 2015 | Approved | |
ConEmu 15.12.2.0 | 945 | Wednesday, December 2, 2015 | Approved | |
ConEmu 15.11.29.0 | 1084 | Monday, November 30, 2015 | Approved | |
ConEmu 15.11.26.0 | 808 | Friday, November 27, 2015 | Approved | |
ConEmu 15.11.22.0 | 1283 | Monday, November 23, 2015 | Approved | |
ConEmu 15.11.19.0 | 948 | Friday, November 20, 2015 | Approved | |
ConEmu 15.11.15.0 | 1340 | Monday, November 16, 2015 | Approved | |
ConEmu 15.11.9.0 | 1598 | Monday, November 9, 2015 | Approved | |
ConEmu 15.11.1.0 | 1778 | Monday, November 2, 2015 | Approved | |
ConEmu 15.10.29.0 | 985 | Thursday, October 29, 2015 | Approved | |
ConEmu 15.10.25.0 | 1310 | Sunday, October 25, 2015 | Approved | |
ConEmu 15.10.15.0 | 2354 | Friday, October 16, 2015 | Approved | |
ConEmu 15.10.6.0 | 2464 | Wednesday, October 7, 2015 | Approved | |
ConEmu 15.9.13.0 | 4026 | Sunday, September 13, 2015 | Approved | |
ConEmu 15.9.10.0 | 848 | Friday, September 11, 2015 | Approved | |
ConEmu 15.9.8.0 | 1250 | Monday, September 7, 2015 | Approved | |
ConEmu 15.8.21.0 | 2914 | Saturday, August 22, 2015 | Approved | |
ConEmu 15.8.16.0 | 1470 | Monday, August 17, 2015 | Approved | |
ConEmu 15.8.14.0 | 768 | Saturday, August 15, 2015 | Approved | |
ConEmu 15.8.13.0 | 548 | Friday, August 14, 2015 | Approved | |
ConEmu 15.7.28.0 | 3137 | Wednesday, July 29, 2015 | Approved | |
ConEmu 15.7.27.0 | 713 | Monday, July 27, 2015 | Approved | |
ConEmu 15.7.22.0 | 1116 | Thursday, July 23, 2015 | Approved | |
ConEmu 15.7.16.0 | 1500 | Thursday, July 16, 2015 | Approved | |
ConEmu 15.7.7.0 | 1884 | Tuesday, July 7, 2015 | Approved | |
ConEmu 15.7.5.0 | 798 | Monday, July 6, 2015 | Approved | |
ConEmu 15.7.1.0 | 1074 | Thursday, July 2, 2015 | Approved | |
ConEmu 15.6.29.0 | 873 | Tuesday, June 30, 2015 | Approved | |
ConEmu 15.6.21.0 | 1442 | Monday, June 22, 2015 | Approved | |
ConEmu 15.5.13.0 | 3513 | Wednesday, May 13, 2015 | Approved | |
ConEmu 15.5.4.0 | 1369 | Tuesday, May 5, 2015 | Approved | |
ConEmu 15.4.27.0 | 1147 | Tuesday, April 28, 2015 | Approved | |
ConEmu 15.4.20.0 | 810 | Friday, April 24, 2015 | Approved | |
ConEmu 15.4.9.0 | 1679 | Friday, April 10, 2015 | Approved | |
ConEmu 15.4.8.0 | 645 | Thursday, April 9, 2015 | Approved | |
ConEmu 15.4.5.0 | 827 | Monday, April 6, 2015 | Approved | |
ConEmu 15.3.31.0 | 909 | Wednesday, April 1, 2015 | Approved | |
ConEmu 15.3.27.0 | 836 | Saturday, March 28, 2015 | Approved | |
ConEmu 15.3.16.0 | 791 | Tuesday, March 24, 2015 | Approved | |
ConEmu 14.9.23.0 | 8782 | Thursday, September 25, 2014 | Approved | |
ConEmu 14.9.22.0 | 638 | Wednesday, September 24, 2014 | Approved | |
ConEmu 14.9.14.0 | 953 | Monday, September 15, 2014 | Approved | |
ConEmu 13.12.25.0 | 7149 | Friday, January 3, 2014 | Approved | |
ConEmu 13.9.13.0 | 2221 | Monday, September 16, 2013 | Approved | |
ConEmu 13.7.8.0 | 2352 | Tuesday, July 16, 2013 | Approved | |
ConEmu 12.6.18-alpha | 700 | Friday, June 22, 2012 | Approved | |
ConEmu 12.4.17.1 | 1865 | Thursday, September 13, 2012 | Approved | |
ConEmu 12.4.17 | 556 | Friday, June 22, 2012 | Approved |
© 2015, Maximus5
This package has no dependencies.
Ground Rules:
- This discussion is only about ConEmu and the ConEmu 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 ConEmu, 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.