Step 1: Review Your Packages

Step 2: Choose Your Integration Method

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

Option 2: Internalized Package (Reliable, Scalable)

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

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:

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 ###

#### 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.2.2.2.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.2.2.2.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.2.2.2.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.2.2.2.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

Downloads:

83,040

Downloads of v 9.0.2092:

24

Last Update:

07 Nov 2023

Package Maintainer(s):

Pauby

Software Author(s):

TuxProject.de
Vim Team

Tags:

vim-tux vim editor tux admin

Vim Tux (Portable)

This is not the latest version of Vim Tux (Portable) available.

9.0.2092 | Updated: 07 Nov 2023

Downloads:

83,040

Downloads of v 9.0.2092:

Maintainer(s):

Pauby

Software Author(s):

TuxProject.de
Vim Team

Tags:

vim-tux vim editor tux admin

Vim Tux (Portable) 9.0.2092

This is not the latest version of Vim Tux (Portable) available.

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Vim Tux (Portable), run the following command from the command line or from PowerShell:

To upgrade Vim Tux (Portable), run the following command from the command line or from PowerShell:

To uninstall Vim Tux (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. 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

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the package:
  Download
- Follow manual internalization instructions

Package Internalizer (C4B)

Run: (additional options)

choco download vim-tux.portable --internalize --version=9.0.2092 --source=https://community.chocolatey.org/api/v2/

For package and dependencies run:

choco push --source="'INTERNAL REPO URL'"

Automate package internalization

3. Copy Your Script

choco upgrade vim-tux.portable -y --source="'INTERNAL REPO URL'" --version="'9.0.2092'" [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 vim-tux.portable -y --source="'INTERNAL REPO URL'" --version="'9.0.2092'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Install vim-tux.portable
  win_chocolatey:
    name: vim-tux.portable
    version: '9.0.2092'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'vim-tux.portable' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '9.0.2092'
end

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


cChocoPackageInstaller vim-tux.portable
{
    Name     = "vim-tux.portable"
    Version  = "9.0.2092"
    Source   = "INTERNAL REPO URL"
}

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


package { 'vim-tux.portable':
  ensure   => '9.0.2092',
  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.

NOTE

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

WARNING

There are versions of this package awaiting moderation . See the Version History section below.

Package Approved

This package was approved as a trusted package on 07 Nov 2023.

Description

A highly configurable text editor for efficiently creating and changing any kind of text (tux build).

Vanilla build of vim, compiled with all features enabled. 'Right click > edit with vim' support included. Vim and gVim launchers are added to PATH

Please visit the official site, docs and mailing list.
Build provided by TuxProject.de - consider donating to help support their server costs.

Notes

This is an automatically updated package. If you find it is out of date by more than a week, please contact the maintainer(s), to let the know the package is no longer updating, using:
- The 'Contact Maintainers' link on the package page, or
- The 'Package Source' link on the package page and raising an issue.

Antivirus Detections

The x86 edition was removed from the package due to consistently high AV detections stopping the package from being approved.
The embedded binaries are regularly flagged by antivirus engines. Please see these GitHub issues for information: 1, 2, 3, 4 and 5. If in doubt, do not install the package.
If you find missing versions, please check the 'Version History' section on the package page. If the versions are rejected it is likely due to very high AV counts.

Files

tools\vim90\install.exe.ignore

tools\chocolateyInstall.ps1

$ErrorActionPreference = 'Stop'

$toolsDir = Split-Path -parent $MyInvocation.MyCommand.Definition
$versPath = 'vim90'
#$filename32 = "$toolsDir\complete-x86.7z"
$filename64 = "$toolsDir\complete-x64.7z"

# pckage parameter defaults
$destDir = Join-Path -Path $toolsDir -ChildPath $versPath

$packageArgs = @{
    packageName    = $env:ChocolateyPackageName
#    fileFullPath   = $filename32
    fileFullPath64 = $filename64
    destination    = $destDir
}

Get-ChocolateyUnzip @packageArgs

(Get-Item $destdir\patch.exe).LastWriteTime = (Get-Date) # exe must be newer than manifest; Supplied manifest fixes useless UAC request

# Rather than letting the installer place the batch files in C:\WINDOWS, they are included them in this package.
# They are taken from C:\Windows on a default installation of vim-tux (or the vim-tux.install package).
# Installing them in this way ensures the package is compatible with non-admin installs, as a good portable package should :)
Get-ChildItem "$destDir\*.bat" | ForEach-Object {
    Install-BinFile -Name $_.BaseName -Path $_
}

# Set the VIM environment variable for the batch files to work. Note that it's the prent directory of the VIM90 folder.
# As this is a poetable package, the user may not have admin rights. Therefore, the variable scope should be 'User'
Install-ChocolateyEnvironmentVariable -VariableName 'VIM' -VariableValue $toolsDir -VariableType 'User'

#$filename32,
$filename64 | Remove-Item -Force -ErrorAction SilentlyContinue
Write-Host 'Build provided by TuxProject.de - consider donating to help support their server costs.'

tools\vim90\patch.exe.ignore

tools\chocolateyUninstall.ps1

$ErrorActionPreference = 'Stop'

$toolsDir = Split-Path -parent $MyInvocation.MyCommand.Definition
$versPath = 'vim90'
$destDir = Join-Path -Path $toolsDir -ChildPath $versPath

Get-ChildItem -Path "$destDir\*.bat" | ForEach-Object {
    Uninstall-BinFile -Name $_.BaseName -Path $_
}

Uninstall-ChocolateyEnvironmentVariable -VariableName 'VIM' -VariableType 'User'

tools\vim90\patch.exe.manifest

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <!-- Make sure that UAC believes
        that it does not require administrative privilege -->
        <requestedExecutionLevel level="asInvoker" uiAccess="false"/>
      </requestedPrivileges>
    </security>
  </trustInfo>
</assembly>

tools\complete-x64.7z

md5: 654109FA9321B7DD7B6A0CA865120455 | sha1: 1C2891303E9254CFC5ACF686610B1443212E9577 | sha256: BA07408E0D939373886B682649F886CA6BA22AC5EA2DCB622DA3A661926207A7 | sha512: 92638D36D7F5335EA456420F2ED5059378D8CA393B7C05F015BE3070688A953ACC3487C5EBE6CAAF52C15F38335DC3A313167CC69289ECFAA2C34D651FA1C701

tools\vim90\tee.exe.ignore

tools\LICENSE.txt

VIM LICENSE

I)  There are no restrictions on distributing unmodified copies of Vim except
    that they must include this license text.  You can also distribute
    unmodified parts of Vim, likewise unrestricted except that they must
    include this license text.  You are also allowed to include executables
    that you made from the unmodified Vim sources, plus your own usage
    examples and Vim scripts.

II) It is allowed to distribute a modified (or extended) version of Vim,
    including executables and/or source code, when the following four
    conditions are met:
    1) This license text must be included unmodified.
    2) The modified Vim must be distributed in one of the following five ways:
       a) If you make changes to Vim yourself, you must clearly describe in
          the distribution how to contact you.  When the maintainer asks you
          (in any way) for a copy of the modified Vim you distributed, you
          must make your changes, including source code, available to the
          maintainer without fee.  The maintainer reserves the right to
          include your changes in the official version of Vim.  What the
          maintainer will do with your changes and under what license they
          will be distributed is negotiable.  If there has been no negotiation
          then this license, or a later version, also applies to your changes.
          The current maintainers are listed here: https://github.com/orgs/vim/people.
          If this changes it will be announced in appropriate places (most likely
          vim.sf.net, www.vim.org and/or comp.editors). When it is completely
          impossible to contact the maintainer, the obligation to send him
          your changes ceases.  Once the maintainer has confirmed that he has
          received your changes they will not have to be sent again.
       b) If you have received a modified Vim that was distributed as
          mentioned under a) you are allowed to further distribute it
          unmodified, as mentioned at I).  If you make additional changes the
          text under a) applies to those changes.
       c) Provide all the changes, including source code, with every copy of
          the modified Vim you distribute.  This may be done in the form of a
          context diff.  You can choose what license to use for new code you
          add.  The changes and their license must not restrict others from
          making their own changes to the official version of Vim.
       d) When you have a modified Vim which includes changes as mentioned
          under c), you can distribute it without the source code for the
          changes if the following three conditions are met:
          - The license that applies to the changes permits you to distribute
            the changes to the Vim maintainer without fee or restriction, and
            permits the Vim maintainer to include the changes in the official
            version of Vim without fee or restriction.
          - You keep the changes for at least three years after last
            distributing the corresponding modified Vim.  When the maintainer
            or someone who you distributed the modified Vim to asks you (in
            any way) for the changes within this period, you must make them
            available to him.
          - You clearly describe in the distribution how to contact you.  This
            contact information must remain valid for at least three years
            after last distributing the corresponding modified Vim, or as long
            as possible.
       e) When the GNU General Public License (GPL) applies to the changes,
          you can distribute the modified Vim under the GNU GPL version 2 or
          any later version.
    3) A message must be added, at least in the output of the ":version"
       command and in the intro screen, such that the user of the modified Vim
       is able to see that it was modified.  When distributing as mentioned
       under 2)e) adding the message is only required for as far as this does
       not conflict with the license used for the changes.
    4) The contact information as required under 2)a) and 2)d) must not be
       removed or changed, except that the person himself can make
       corrections.

III) If you distribute a modified version of Vim, you are encouraged to use
     the Vim license for your changes and make them available to the
     maintainer, including the source code.  The preferred way to do this is
     by e-mail or by uploading the files to a server and e-mailing the URL.
     If the number of changes is small (e.g., a modified Makefile) e-mailing a
     context diff will do.  The e-mail address to be used is
     <[email protected]>

IV)  It is not allowed to remove this license from the distribution of the Vim
     sources, parts of it or from a modified version.  You may use this
     license for previous Vim releases instead of the license that they came
     with, at your option.

tools\vim90\uninstal.exe.ignore

tools\VERIFICATION.txt

VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The embedded software have been downloaded from the listed download
location on <https://tuxproject.de/projects/vim/>
and can be verified by doing the following:

1. Download the following installers:
  32-Bit: <http://tuxproject.de/projects/vim/complete-x86.7z>
  64-Bit: <http://tuxproject.de/projects/vim/complete-x64.7z>

2. Get the checksum using one of the following methods:
  - Using PowerShell function 'Get-FileHash'
  - Use chocolatey utility 'checksum.exe'

3. The checksums should match the following:
    - complete-x64.7z: BA07408E0D939373886B682649F886CA6BA22AC5EA2DCB622DA3A661926207A7 (SHA256)
    - diff.exe.ignore: E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 (SHA256)
    - evim.bat: B2577897175C8F86AF06B293D479D0AEAC39179BA0227155772AA0FE74C99805 (SHA256)
    - gview.bat: E5569CE55A66ED65C3693324DB7D90A114EE150086D09FAC872EEE5821729371 (SHA256)
    - gvim.bat: 4D8339EBB70E0A39EB5142BA7CB2A77BBB961E25DC639988F8BD7AC623C45BA0 (SHA256)
    - gvim.exe.ignore: E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 (SHA256)
    - gvimdiff.bat: BDFE2E0EFA4E79A5E9895A7D0F5A73CB69903D5CDADA1C64737786A3EF247C4B (SHA256)
    - gvim_noOLE.exe.ignore: E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 (SHA256)
    - install.exe.ignore: E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 (SHA256)
    - patch.exe.ignore: E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 (SHA256)
    - patch.exe.manifest: 9A1290861CEA7BB577F9C8AAECAC59138E398D2090C8D2CCBFB732157ABCDFA4 (SHA256)
    - tee.exe.ignore: E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 (SHA256)
    - uninstal.exe.ignore: E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 (SHA256)
    - view.bat: A3C4EDD841BD4D6B332E0E344E875F763157AA2EE205C0DBB0368D0649BDD67F (SHA256)
    - vim.bat: 251AC2612DECFB1EFFE19F493E6B420EE495E66E957BE48C516C138C40729984 (SHA256)
    - vim.exe.ignore: E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 (SHA256)
    - vimdiff.bat: DD535F7C202BB49E52BDF695880AD72029008BE2F67A87BCE325B374DDE34E59 (SHA256)
    - vimrun.exe.ignore: E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 (SHA256)
    - winpty-agent.exe.ignore: E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 (SHA256)
    - xxd.exe.ignore: E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 (SHA256)

    The files in the vim90 folder are taken from C:\Windows after a default
    installation of vim-tux (or the vim-tux.install package).

The file 'LICENSE.txt' has been obtained from https://github.com/vim/vim/blob/master/LICENSE

tools\vim90\view.bat

@echo off
rem -- Run Vim --
rem # uninstall key: vim90 #

setlocal
set VIM_EXE_DIR=C:\Program Files\Vim\vim90
if exist "%VIM%\vim90\vim.exe" set VIM_EXE_DIR=%VIM%\vim90
if exist "%VIMRUNTIME%\vim.exe" set VIM_EXE_DIR=%VIMRUNTIME%

if not exist "%VIM_EXE_DIR%\vim.exe" (
    echo "%VIM_EXE_DIR%\vim.exe" not found
    goto :eof
)

"%VIM_EXE_DIR%\vim.exe" -R %*

tools\vim90\diff.exe.ignore

tools\vim90\vim.bat

@echo off
rem -- Run Vim --
rem # uninstall key: vim90 #

setlocal
set VIM_EXE_DIR=C:\Program Files\Vim\vim90
if exist "%VIM%\vim90\vim.exe" set VIM_EXE_DIR=%VIM%\vim90
if exist "%VIMRUNTIME%\vim.exe" set VIM_EXE_DIR=%VIMRUNTIME%

if not exist "%VIM_EXE_DIR%\vim.exe" (
    echo "%VIM_EXE_DIR%\vim.exe" not found
    goto :eof
)

"%VIM_EXE_DIR%\vim.exe"  %*

tools\vim90\evim.bat

@echo off
rem -- Run Vim --
rem # uninstall key: vim90 #

setlocal
set VIM_EXE_DIR=C:\Program Files\Vim\vim90
if exist "%VIM%\vim90\gvim.exe" set VIM_EXE_DIR=%VIM%\vim90
if exist "%VIMRUNTIME%\gvim.exe" set VIM_EXE_DIR=%VIMRUNTIME%

if not exist "%VIM_EXE_DIR%\gvim.exe" (
    echo "%VIM_EXE_DIR%\gvim.exe" not found
    goto :eof
)

rem check --nofork argument
set VIMNOFORK=
:loopstart
if .%1==. goto loopend
if .%1==.--nofork (
    set VIMNOFORK=1
) else if .%1==.-f (
    set VIMNOFORK=1
)
shift
goto loopstart
:loopend

if .%VIMNOFORK%==.1 (
    start "dummy" /b /wait "%VIM_EXE_DIR%\gvim.exe" -y %*
) else (
    start "dummy" /b "%VIM_EXE_DIR%\gvim.exe" -y %*
)

tools\vim90\vim.exe.ignore

tools\vim90\gview.bat

@echo off
rem -- Run Vim --
rem # uninstall key: vim90 #

setlocal
set VIM_EXE_DIR=C:\Program Files\Vim\vim90
if exist "%VIM%\vim90\gvim.exe" set VIM_EXE_DIR=%VIM%\vim90
if exist "%VIMRUNTIME%\gvim.exe" set VIM_EXE_DIR=%VIMRUNTIME%

if not exist "%VIM_EXE_DIR%\gvim.exe" (
    echo "%VIM_EXE_DIR%\gvim.exe" not found
    goto :eof
)

rem check --nofork argument
set VIMNOFORK=
:loopstart
if .%1==. goto loopend
if .%1==.--nofork (
    set VIMNOFORK=1
) else if .%1==.-f (
    set VIMNOFORK=1
)
shift
goto loopstart
:loopend

if .%VIMNOFORK%==.1 (
    start "dummy" /b /wait "%VIM_EXE_DIR%\gvim.exe" -R %*
) else (
    start "dummy" /b "%VIM_EXE_DIR%\gvim.exe" -R %*
)

tools\vim90\vimdiff.bat

@echo off
rem -- Run Vim --
rem # uninstall key: vim90 #

setlocal
set VIM_EXE_DIR=C:\Program Files\Vim\vim90
if exist "%VIM%\vim90\vim.exe" set VIM_EXE_DIR=%VIM%\vim90
if exist "%VIMRUNTIME%\vim.exe" set VIM_EXE_DIR=%VIMRUNTIME%

if not exist "%VIM_EXE_DIR%\vim.exe" (
    echo "%VIM_EXE_DIR%\vim.exe" not found
    goto :eof
)

"%VIM_EXE_DIR%\vim.exe" -d %*

tools\vim90\gvim.bat

@echo off
rem -- Run Vim --
rem # uninstall key: vim90 #

setlocal
set VIM_EXE_DIR=C:\Program Files\Vim\vim90
if exist "%VIM%\vim90\gvim.exe" set VIM_EXE_DIR=%VIM%\vim90
if exist "%VIMRUNTIME%\gvim.exe" set VIM_EXE_DIR=%VIMRUNTIME%

if not exist "%VIM_EXE_DIR%\gvim.exe" (
    echo "%VIM_EXE_DIR%\gvim.exe" not found
    goto :eof
)

rem check --nofork argument
set VIMNOFORK=
:loopstart
if .%1==. goto loopend
if .%1==.--nofork (
    set VIMNOFORK=1
) else if .%1==.-f (
    set VIMNOFORK=1
)
shift
goto loopstart
:loopend

if .%VIMNOFORK%==.1 (
    start "dummy" /b /wait "%VIM_EXE_DIR%\gvim.exe"  %*
) else (
    start "dummy" /b "%VIM_EXE_DIR%\gvim.exe"  %*
)

tools\vim90\vimrun.exe.ignore

tools\vim90\gvim.exe.ignore

tools\vim90\winpty-agent.exe.ignore

tools\vim90\gvimdiff.bat

@echo off
rem -- Run Vim --
rem # uninstall key: vim90 #

setlocal
set VIM_EXE_DIR=C:\Program Files\Vim\vim90
if exist "%VIM%\vim90\gvim.exe" set VIM_EXE_DIR=%VIM%\vim90
if exist "%VIMRUNTIME%\gvim.exe" set VIM_EXE_DIR=%VIMRUNTIME%

if not exist "%VIM_EXE_DIR%\gvim.exe" (
    echo "%VIM_EXE_DIR%\gvim.exe" not found
    goto :eof
)

rem check --nofork argument
set VIMNOFORK=
:loopstart
if .%1==. goto loopend
if .%1==.--nofork (
    set VIMNOFORK=1
) else if .%1==.-f (
    set VIMNOFORK=1
)
shift
goto loopstart
:loopend

if .%VIMNOFORK%==.1 (
    start "dummy" /b /wait "%VIM_EXE_DIR%\gvim.exe" -d %*
) else (
    start "dummy" /b "%VIM_EXE_DIR%\gvim.exe" -d %*
)

tools\vim90\xxd.exe.ignore

tools\vim90\gvim_noOLE.exe.ignore

Virus Scan Results

vim-tux.portable.9.0.2092.nupkg (1b9beb230417) - ## / 40
complete-x64.7z (ba07408e0d93) - ## / 60
gvim.exe (b049952f1595) - ## / 72
gvim_noOLE.exe (d9c6a245de13) - ## / 72
tee.exe (10a315e9b7c3) - ## / 72
vim.exe (95e0f7647485) - ## / 72
vim64.dll (dbb62756a741) - ## / 71
vimrun.exe (5a4b2c53a008) - ## / 71
xxd.exe (f2b6cd828ce2) - ## / 69
gvimext.dll (ca8ed24baf08) - ## / 71

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 History

Version	Downloads	Last Updated	Status
Vim Tux (Portable) 9.1.373	3	Saturday, April 27, 2024	Waiting for Maintainer
Vim Tux (Portable) 9.1.369	9	Thursday, April 25, 2024	Approved
Vim Tux (Portable) 9.1.368	11	Thursday, April 25, 2024	Approved
Vim Tux (Portable) 9.1.366	15	Tuesday, April 23, 2024	Approved
Vim Tux (Portable) 9.1.363	13	Monday, April 22, 2024	Approved
Vim Tux (Portable) 9.1.354	14	Saturday, April 20, 2024	Approved
Vim Tux (Portable) 9.1.336	19	Tuesday, April 16, 2024	Approved
Vim Tux (Portable) 9.1.330	15	Monday, April 15, 2024	Approved
Vim Tux (Portable) 9.1.296	15	Thursday, April 11, 2024	Approved
Vim Tux (Portable) 9.1.193	27	Friday, March 22, 2024	Approved
Vim Tux (Portable) 9.1.186	21	Tuesday, March 19, 2024	Approved
Vim Tux (Portable) 9.1.181	19	Saturday, March 16, 2024	Approved
Vim Tux (Portable) 9.1.149	27	Tuesday, March 5, 2024	Approved
Vim Tux (Portable) 9.1.113	36	Friday, February 16, 2024	Approved
Vim Tux (Portable) 9.1.67	25	Friday, February 2, 2024	Approved
Vim Tux (Portable) 9.1.50	21	Tuesday, January 30, 2024	Approved
Vim Tux (Portable) 9.0.2181	54	Thursday, December 21, 2023	Approved
Vim Tux (Portable) 9.0.2167	19	Friday, December 15, 2023	Approved
Vim Tux (Portable) 9.0.2155	28	Saturday, December 9, 2023	Approved
Vim Tux (Portable) 9.0.2122	30	Friday, November 24, 2023	Approved
Vim Tux (Portable) 9.0.2120	24	Thursday, November 23, 2023	Approved
Vim Tux (Portable) 9.0.2105	35	Wednesday, November 15, 2023	Approved
Vim Tux (Portable) 9.0.2103	36	Tuesday, November 14, 2023	Approved
Vim Tux (Portable) 9.0.2095	28	Thursday, November 9, 2023	Approved
Vim Tux (Portable) 9.0.2092	24	Tuesday, November 7, 2023	Approved
Vim Tux (Portable) 9.0.2081	36	Wednesday, November 1, 2023	Approved
Vim Tux (Portable) 9.0.2077	31	Saturday, October 28, 2023	Approved
Vim Tux (Portable) 9.0.2063	233	Tuesday, October 24, 2023	Approved
Vim Tux (Portable) 9.0.2053	37	Friday, October 20, 2023	Approved
Vim Tux (Portable) 9.0.2050	22	Thursday, October 19, 2023	Approved
Vim Tux (Portable) 9.0.2048	32	Thursday, October 19, 2023	Approved
Vim Tux (Portable) 9.0.2043	21	Wednesday, October 18, 2023	Approved
Vim Tux (Portable) 9.0.2034	38	Tuesday, October 17, 2023	Approved
Vim Tux (Portable) 9.0.2009	27	Tuesday, October 10, 2023	Approved
Vim Tux (Portable) 9.0.1976	30	Wednesday, October 4, 2023	Approved
Vim Tux (Portable) 9.0.1943	28	Wednesday, September 27, 2023	Approved
Vim Tux (Portable) 9.0.1927	502	Thursday, September 21, 2023	Approved
Vim Tux (Portable) 9.0.1907	816	Monday, September 18, 2023	Approved
Vim Tux (Portable) 9.0.1901	579	Sunday, September 17, 2023	Approved
Vim Tux (Portable) 9.0.1897	56	Wednesday, September 13, 2023	Approved
Vim Tux (Portable) 9.0.1877	51	Friday, September 8, 2023	Exempted
Vim Tux (Portable) 9.0.1811	24	Monday, August 28, 2023	Exempted
Vim Tux (Portable) 9.0.1787	29	Monday, August 28, 2023	Approved
Vim Tux (Portable) 9.0.0846	225	Thursday, November 10, 2022	Approved
Vim Tux (Portable) 9.0.0828	52	Friday, November 4, 2022	Approved
Vim Tux (Portable) 9.0.0815	54	Wednesday, October 26, 2022	Approved
Vim Tux (Portable) 9.0.0814	44	Saturday, October 22, 2022	Approved
Vim Tux (Portable) 9.0.0806	48	Friday, October 21, 2022	Approved
Vim Tux (Portable) 9.0.0797	43	Thursday, October 20, 2022	Approved
Vim Tux (Portable) 9.0.0780	45	Tuesday, October 18, 2022	Approved
Vim Tux (Portable) 9.0.0733	59	Thursday, October 13, 2022	Approved
Vim Tux (Portable) 9.0.0715	68	Tuesday, October 11, 2022	Approved
Vim Tux (Portable) 9.0.0682	45	Saturday, October 8, 2022	Approved
Vim Tux (Portable) 9.0.656.20221005	55	Thursday, October 6, 2022	Approved
Vim Tux (Portable) 9.0.0656	45	Wednesday, October 5, 2022	Approved
Vim Tux (Portable) 8.2.3908	280	Monday, December 27, 2021	Approved
Vim Tux (Portable) 8.2.3875	73	Thursday, December 23, 2021	Approved
Vim Tux (Portable) 8.2.3858	84	Tuesday, December 21, 2021	Approved
Vim Tux (Portable) 8.2.3836	79	Saturday, December 18, 2021	Approved
Vim Tux (Portable) 8.2.3811	82	Wednesday, December 15, 2021	Approved
Vim Tux (Portable) 8.2.3794	73	Tuesday, December 14, 2021	Approved
Vim Tux (Portable) 8.2.3763	82	Friday, December 10, 2021	Approved
Vim Tux (Portable) 8.2.3757	68	Wednesday, December 8, 2021	Approved
Vim Tux (Portable) 8.2.3752	64	Tuesday, December 7, 2021	Approved
Vim Tux (Portable) 8.2.3718	77	Friday, December 3, 2021	Approved
Vim Tux (Portable) 8.2.3717	80	Thursday, December 2, 2021	Approved
Vim Tux (Portable) 8.2.3701	68	Tuesday, November 30, 2021	Approved
Vim Tux (Portable) 8.2.3692	69	Monday, November 29, 2021	Approved
Vim Tux (Portable) 8.2.3671	79	Friday, November 26, 2021	Approved
Vim Tux (Portable) 8.2.3659	74	Thursday, November 25, 2021	Approved
Vim Tux (Portable) 8.2.3651	74	Tuesday, November 23, 2021	Approved
Vim Tux (Portable) 8.2.3646	70	Tuesday, November 23, 2021	Approved
Vim Tux (Portable) 8.2.3623	73	Saturday, November 20, 2021	Approved
Vim Tux (Portable) 8.2.3608	83	Thursday, November 18, 2021	Approved
Vim Tux (Portable) 8.2.3595	72	Tuesday, November 16, 2021	Approved
Vim Tux (Portable) 8.2.3579	85	Friday, November 5, 2021	Approved
Vim Tux (Portable) 8.2.3565	79	Wednesday, October 27, 2021	Approved
Vim Tux (Portable) 8.2.3551	76	Friday, October 22, 2021	Approved
Vim Tux (Portable) 8.2.3545	69	Thursday, October 21, 2021	Approved
Vim Tux (Portable) 8.2.3532	62	Tuesday, October 19, 2021	Approved
Vim Tux (Portable) 8.2.3513	85	Saturday, October 16, 2021	Approved
Vim Tux (Portable) 8.2.3505	70	Thursday, October 14, 2021	Approved
Vim Tux (Portable) 8.2.3493	77	Tuesday, October 12, 2021	Approved
Vim Tux (Portable) 8.2.3486	67	Saturday, October 9, 2021	Approved
Vim Tux (Portable) 8.2.3484	67	Thursday, October 7, 2021	Approved
Vim Tux (Portable) 8.2.3478	70	Wednesday, October 6, 2021	Approved
Vim Tux (Portable) 8.2.3469	75	Tuesday, October 5, 2021	Approved
Vim Tux (Portable) 8.2.3458	89	Tuesday, September 28, 2021	Approved
Vim Tux (Portable) 8.2.3455	71	Thursday, September 23, 2021	Approved
Vim Tux (Portable) 8.2.3450	78	Tuesday, September 21, 2021	Approved
Vim Tux (Portable) 8.2.3448	81	Sunday, September 19, 2021	Approved
Vim Tux (Portable) 8.2.3434	83	Tuesday, September 14, 2021	Approved
Vim Tux (Portable) 8.2.3416	87	Thursday, September 9, 2021	Approved
Vim Tux (Portable) 8.2.3394	76	Thursday, September 2, 2021	Approved
Vim Tux (Portable) 8.2.3391	89	Wednesday, September 1, 2021	Approved
Vim Tux (Portable) 8.2.3376	100	Friday, August 27, 2021	Approved
Vim Tux (Portable) 8.2.3358	95	Friday, August 20, 2021	Approved
Vim Tux (Portable) 8.2.3356	80	Wednesday, August 18, 2021	Approved
Vim Tux (Portable) 8.2.3326	128	Wednesday, August 11, 2021	Approved
Vim Tux (Portable) 8.2.3318	87	Monday, August 9, 2021	Approved
Vim Tux (Portable) 8.2.3299	81	Friday, August 6, 2021	Approved
Vim Tux (Portable) 8.2.3290	64	Thursday, August 5, 2021	Approved
Vim Tux (Portable) 8.2.3281	90	Wednesday, August 4, 2021	Approved
Vim Tux (Portable) 8.2.3273	78	Tuesday, August 3, 2021	Approved
Vim Tux (Portable) 8.2.3269	86	Monday, August 2, 2021	Approved
Vim Tux (Portable) 8.2.3263	62	Sunday, August 1, 2021	Approved
Vim Tux (Portable) 8.2.3253	102	Saturday, July 31, 2021	Approved
Vim Tux (Portable) 8.2.3242	83	Thursday, July 29, 2021	Approved
Vim Tux (Portable) 8.2.3223	75	Tuesday, July 27, 2021	Approved
Vim Tux (Portable) 8.2.3204	82	Friday, July 23, 2021	Approved
Vim Tux (Portable) 8.2.3187	81	Tuesday, July 20, 2021	Approved
Vim Tux (Portable) 8.2.3171	90	Friday, July 16, 2021	Approved
Vim Tux (Portable) 8.2.3158	109	Wednesday, July 14, 2021	Approved
Vim Tux (Portable) 8.2.3131	76	Friday, July 9, 2021	Approved
Vim Tux (Portable) 8.2.3120	83	Thursday, July 8, 2021	Approved
Vim Tux (Portable) 8.2.3113	79	Wednesday, July 7, 2021	Approved
Vim Tux (Portable) 8.2.3107	76	Tuesday, July 6, 2021	Approved
Vim Tux (Portable) 8.2.3104	80	Monday, July 5, 2021	Approved
Vim Tux (Portable) 8.2.3095	89	Sunday, July 4, 2021	Approved
Vim Tux (Portable) 8.2.3080	82	Thursday, July 1, 2021	Approved
Vim Tux (Portable) 8.2.3075	71	Wednesday, June 30, 2021	Approved
Vim Tux (Portable) 8.2.3066	99	Monday, June 28, 2021	Approved
Vim Tux (Portable) 8.2.3055	77	Sunday, June 27, 2021	Approved
Vim Tux (Portable) 8.2.3043	77	Thursday, June 24, 2021	Approved
Vim Tux (Portable) 8.2.3033	83	Tuesday, June 22, 2021	Approved
Vim Tux (Portable) 8.2.3020	68	Sunday, June 20, 2021	Approved
Vim Tux (Portable) 8.2.3017	85	Friday, June 18, 2021	Approved
Vim Tux (Portable) 8.2.2840	138	Saturday, May 8, 2021	Approved
Vim Tux (Portable) 8.2.2832	93	Wednesday, May 5, 2021	Approved
Vim Tux (Portable) 8.2.2815	115	Wednesday, April 28, 2021	Approved
Vim Tux (Portable) 8.2.2799	112	Thursday, April 22, 2021	Approved
Vim Tux (Portable) 8.2.2794	84	Wednesday, April 21, 2021	Approved
Vim Tux (Portable) 8.2.2763	94	Thursday, April 15, 2021	Approved
Vim Tux (Portable) 8.2.2738	97	Friday, April 9, 2021	Approved
Vim Tux (Portable) 8.2.2730	103	Wednesday, April 7, 2021	Approved
Vim Tux (Portable) 8.2.2679	96	Wednesday, March 31, 2021	Approved
Vim Tux (Portable) 8.2.2650	89	Friday, March 26, 2021	Approved
Vim Tux (Portable) 8.2.2648	112	Wednesday, March 24, 2021	Approved
Vim Tux (Portable) 8.2.2637	93	Tuesday, March 23, 2021	Approved
Vim Tux (Portable) 8.2.2491	169	Thursday, February 11, 2021	Approved
Vim Tux (Portable) 8.2.2129	170	Saturday, December 12, 2020	Approved
Vim Tux (Portable) 8.2.1981	129	Saturday, November 14, 2020	Approved
Vim Tux (Portable) 8.2.1955	132	Friday, November 6, 2020	Approved
Vim Tux (Portable) 8.2.1923	133	Friday, October 30, 2020	Approved
Vim Tux (Portable) 8.2.1883	133	Thursday, October 22, 2020	Approved
Vim Tux (Portable) 8.2.1858	118	Sunday, October 18, 2020	Approved
Vim Tux (Portable) 8.2.1738	157	Friday, September 25, 2020	Approved
Vim Tux (Portable) 8.2.1651	151	Thursday, September 10, 2020	Approved
Vim Tux (Portable) 8.2.1058	220	Friday, June 26, 2020	Approved
Vim Tux (Portable) 8.2.1007	149	Friday, June 19, 2020	Approved
Vim Tux (Portable) 8.2.988	184	Wednesday, June 17, 2020	Approved
Vim Tux (Portable) 8.2.960	154	Friday, June 12, 2020	Approved
Vim Tux (Portable) 8.2.950	142	Thursday, June 11, 2020	Approved
Vim Tux (Portable) 8.2.916	170	Sunday, June 7, 2020	Approved
Vim Tux (Portable) 8.2.882	149	Tuesday, June 2, 2020	Approved
Vim Tux (Portable) 8.2.855	143	Sunday, May 31, 2020	Approved
Vim Tux (Portable) 8.2.834	162	Friday, May 29, 2020	Approved
Vim Tux (Portable) 8.2.829	174	Wednesday, May 27, 2020	Approved
Vim Tux (Portable) 8.2.821	137	Tuesday, May 26, 2020	Approved
Vim Tux (Portable) 8.2.806	153	Friday, May 22, 2020	Approved
Vim Tux (Portable) 8.2.803	135	Thursday, May 21, 2020	Approved
Vim Tux (Portable) 8.2.766	173	Sunday, May 17, 2020	Approved
Vim Tux (Portable) 8.2.750	156	Thursday, May 14, 2020	Approved
Vim Tux (Portable) 8.2.735	171	Tuesday, May 12, 2020	Approved
Vim Tux (Portable) 8.2.647	216	Monday, April 27, 2020	Approved
Vim Tux (Portable) 8.2.640	142	Sunday, April 26, 2020	Approved
Vim Tux (Portable) 8.2.625	145	Friday, April 24, 2020	Approved
Vim Tux (Portable) 8.2.612	220	Tuesday, April 21, 2020	Approved
Vim Tux (Portable) 8.2.592	163	Saturday, April 18, 2020	Approved
Vim Tux (Portable) 8.2.585	144	Friday, April 17, 2020	Approved
Vim Tux (Portable) 8.2.577	172	Tuesday, April 14, 2020	Approved
Vim Tux (Portable) 8.2.0536	163	Sunday, April 12, 2020	Approved
Vim Tux (Portable) 8.2.0515	178	Monday, April 6, 2020	Approved
Vim Tux (Portable) 8.2.0505	169	Saturday, April 4, 2020	Approved
Vim Tux (Portable) 8.2.0486	158	Wednesday, April 1, 2020	Approved
Vim Tux (Portable) 8.2.0464	174	Sunday, March 29, 2020	Approved
Vim Tux (Portable) 8.2.0397	191	Wednesday, March 18, 2020	Approved
Vim Tux (Portable) 8.2.0369	191	Wednesday, March 11, 2020	Approved
Vim Tux (Portable) 8.2.0357	174	Friday, March 6, 2020	Approved
Vim Tux (Portable) 8.2.0324	192	Friday, February 28, 2020	Approved
Vim Tux (Portable) 8.2.0313	169	Monday, February 24, 2020	Approved
Vim Tux (Portable) 8.2.0294	150	Saturday, February 22, 2020	Approved
Vim Tux (Portable) 8.2.0285	151	Friday, February 21, 2020	Approved
Vim Tux (Portable) 8.2.0273	167	Tuesday, February 18, 2020	Approved
Vim Tux (Portable) 8.2.0231	194	Sunday, February 9, 2020	Approved
Vim Tux (Portable) 8.2.0164	185	Wednesday, January 29, 2020	Approved
Vim Tux (Portable) 8.2.0147	130	Saturday, January 25, 2020	Approved
Vim Tux (Portable) 8.2.0129	200	Sunday, January 19, 2020	Approved
Vim Tux (Portable) 8.2.0114	161	Tuesday, January 14, 2020	Approved
Vim Tux (Portable) 8.2.0109	159	Friday, January 10, 2020	Approved
Vim Tux (Portable) 8.2.0092	174	Tuesday, January 7, 2020	Approved
Vim Tux (Portable) 8.2.0080	181	Friday, January 3, 2020	Approved
Vim Tux (Portable) 8.2.0065	167	Tuesday, December 31, 2019	Approved
Vim Tux (Portable) 8.2.0055	141	Monday, December 30, 2019	Approved
Vim Tux (Portable) 8.2.0052	147	Sunday, December 29, 2019	Approved
Vim Tux (Portable) 8.2.0033	162	Tuesday, December 24, 2019	Approved
Vim Tux (Portable) 8.2.0021	152	Thursday, December 19, 2019	Approved
Vim Tux (Portable) 8.2.0011	172	Monday, December 16, 2019	Approved
Vim Tux (Portable) 8.1.2333	233	Friday, November 22, 2019	Approved
Vim Tux (Portable) 8.1.2323	203	Thursday, November 21, 2019	Approved
Vim Tux (Portable) 8.1.2311	200	Sunday, November 17, 2019	Approved
Vim Tux (Portable) 8.1.2300	177	Thursday, November 14, 2019	Approved
Vim Tux (Portable) 8.1.2237	213	Friday, November 1, 2019	Approved
Vim Tux (Portable) 8.1.2204	248	Thursday, October 24, 2019	Approved
Vim Tux (Portable) 8.1.2200	201	Wednesday, October 23, 2019	Approved
Vim Tux (Portable) 8.1.2148	205	Monday, October 14, 2019	Approved
Vim Tux (Portable) 8.1.2133	169	Friday, October 11, 2019	Approved
Vim Tux (Portable) 8.1.2117	195	Sunday, October 6, 2019	Approved
Vim Tux (Portable) 8.1.2108	191	Thursday, October 3, 2019	Approved
Vim Tux (Portable) 8.1.2103	158	Tuesday, October 1, 2019	Approved
Vim Tux (Portable) 8.1.2079	204	Friday, September 27, 2019	Approved
Vim Tux (Portable) 8.1.2071	154	Wednesday, September 25, 2019	Approved
Vim Tux (Portable) 8.1.2052	182	Thursday, September 19, 2019	Approved
Vim Tux (Portable) 8.1.2019	222	Tuesday, September 10, 2019	Approved
Vim Tux (Portable) 8.1.2004	175	Sunday, September 8, 2019	Approved
Vim Tux (Portable) 8.1.1995	158	Saturday, September 7, 2019	Approved
Vim Tux (Portable) 8.1.1986	181	Thursday, September 5, 2019	Approved
Vim Tux (Portable) 8.1.1961	173	Monday, September 2, 2019	Approved
Vim Tux (Portable) 8.1.1927	217	Monday, August 26, 2019	Approved
Vim Tux (Portable) 8.1.1915	179	Saturday, August 24, 2019	Approved
Vim Tux (Portable) 8.1.1906	184	Thursday, August 22, 2019	Approved
Vim Tux (Portable) 8.1.1890	167	Tuesday, August 20, 2019	Approved
Vim Tux (Portable) 8.1.1836	226	Sunday, August 11, 2019	Approved
Vim Tux (Portable) 8.1.1813	205	Monday, August 5, 2019	Approved
Vim Tux (Portable) 8.1.1744	187	Thursday, July 25, 2019	Approved
Vim Tux (Portable) 8.1.1729	188	Tuesday, July 23, 2019	Approved
Vim Tux (Portable) 8.1.1713	192	Friday, July 19, 2019	Approved
Vim Tux (Portable) 8.1.1695	186	Tuesday, July 16, 2019	Approved
Vim Tux (Portable) 8.1.1669	171	Saturday, July 13, 2019	Approved
Vim Tux (Portable) 8.1.1655	220	Tuesday, July 9, 2019	Approved
Vim Tux (Portable) 8.1.1631	164	Friday, July 5, 2019	Approved
Vim Tux (Portable) 8.1.1601	226	Thursday, June 27, 2019	Approved
Vim Tux (Portable) 8.1.1578	198	Saturday, June 22, 2019	Approved
Vim Tux (Portable) 8.1.1573	201	Thursday, June 20, 2019	Approved
Vim Tux (Portable) 8.1.1566	173	Tuesday, June 18, 2019	Approved
Vim Tux (Portable) 8.1.1557	194	Monday, June 17, 2019	Approved
Vim Tux (Portable) 8.1.1536	162	Sunday, June 16, 2019	Approved
Vim Tux (Portable) 8.1.1523	202	Friday, June 14, 2019	Approved
Vim Tux (Portable) 8.1.1515	210	Tuesday, June 11, 2019	Approved
Vim Tux (Portable) 8.1.1511	193	Monday, June 10, 2019	Approved
Vim Tux (Portable) 8.1.1455	188	Monday, June 3, 2019	Approved
Vim Tux (Portable) 8.1.1432	218	Friday, May 31, 2019	Approved
Vim Tux (Portable) 8.1.1413	209	Tuesday, May 28, 2019	Approved
Vim Tux (Portable) 8.1.1373	214	Friday, May 24, 2019	Approved
Vim Tux (Portable) 8.1.1364	197	Thursday, May 23, 2019	Approved
Vim Tux (Portable) 8.1.1353	175	Monday, May 20, 2019	Approved
Vim Tux (Portable) 8.1.1333	199	Thursday, May 16, 2019	Approved
Vim Tux (Portable) 8.1.1328	189	Monday, May 13, 2019	Approved
Vim Tux (Portable) 8.1.1312	165	Saturday, May 11, 2019	Approved
Vim Tux (Portable) 8.1.1298	203	Thursday, May 9, 2019	Approved
Vim Tux (Portable) 8.1.1286	217	Tuesday, May 7, 2019	Approved
Vim Tux (Portable) 8.1.1197	221	Monday, April 22, 2019	Approved
Vim Tux (Portable) 8.1.1183	200	Thursday, April 18, 2019	Approved
Vim Tux (Portable) 8.1.1165	204	Sunday, April 14, 2019	Approved
Vim Tux (Portable) 8.1.1140	193	Tuesday, April 9, 2019	Approved
Vim Tux (Portable) 8.1.1136	183	Monday, April 8, 2019	Approved
Vim Tux (Portable) 8.1.1124	182	Sunday, April 7, 2019	Approved
Vim Tux (Portable) 8.1.1103	220	Thursday, April 4, 2019	Approved
Vim Tux (Portable) 8.1.1097	226	Monday, April 1, 2019	Approved
Vim Tux (Portable) 8.1.1073	164	Saturday, March 30, 2019	Approved
Vim Tux (Portable) 8.1.1057	232	Thursday, March 28, 2019	Approved
Vim Tux (Portable) 8.1.1032	238	Friday, March 22, 2019	Approved
Vim Tux (Portable) 8.1.1027	204	Thursday, March 21, 2019	Approved
Vim Tux (Portable) 8.1.1017	158	Tuesday, March 19, 2019	Approved
Vim Tux (Portable) 8.1.1004	206	Monday, March 11, 2019	Approved
Vim Tux (Portable) 8.1.998	183	Friday, March 8, 2019	Approved
Vim Tux (Portable) 8.1.990	218	Sunday, March 3, 2019	Approved
Vim Tux (Portable) 8.1.984	176	Thursday, February 28, 2019	Approved
Vim Tux (Portable) 8.1.978	194	Saturday, February 23, 2019	Approved
Vim Tux (Portable) 8.1.966	205	Friday, February 22, 2019	Approved
Vim Tux (Portable) 8.1.947	182	Tuesday, February 19, 2019	Approved
Vim Tux (Portable) 8.1.934	140	Sunday, February 17, 2019	Approved
Vim Tux (Portable) 8.1.926	200	Saturday, February 16, 2019	Approved
Vim Tux (Portable) 8.1.909	174	Thursday, February 14, 2019	Approved
Vim Tux (Portable) 8.1.895	196	Tuesday, February 12, 2019	Approved
Vim Tux (Portable) 8.1.0885	205	Sunday, February 10, 2019	Approved
Vim Tux (Portable) 8.1.0877	214	Thursday, February 7, 2019	Approved
Vim Tux (Portable) 8.1.0871	215	Monday, February 4, 2019	Approved
Vim Tux (Portable) 8.1.0868	217	Sunday, February 3, 2019	Approved
Vim Tux (Portable) 8.1.0865	177	Saturday, February 2, 2019	Approved
Vim Tux (Portable) 8.1.0842	201	Thursday, January 31, 2019	Approved
Vim Tux (Portable) 8.1.0837	233	Monday, January 28, 2019	Approved
Vim Tux (Portable) 8.1.0814	200	Friday, January 25, 2019	Approved
Vim Tux (Portable) 8.1.0796	195	Thursday, January 24, 2019	Approved
Vim Tux (Portable) 8.1.0788	194	Tuesday, January 22, 2019	Approved
Vim Tux (Portable) 8.1.0757	238	Thursday, January 17, 2019	Approved
Vim Tux (Portable) 8.1.0749	182	Tuesday, January 15, 2019	Approved
Vim Tux (Portable) 8.1.0727	181	Saturday, January 12, 2019	Approved
Vim Tux (Portable) 8.1.0712	232	Thursday, January 10, 2019	Approved
Vim Tux (Portable) 8.1.0700	191	Tuesday, January 8, 2019	Approved
Vim Tux (Portable) 8.1.0690	251	Saturday, January 5, 2019	Approved
Vim Tux (Portable) 8.1.0681	230	Thursday, January 3, 2019	Approved
Vim Tux (Portable) 8.1.0674	200	Wednesday, January 2, 2019	Approved
Vim Tux (Portable) 8.1.0647	238	Friday, December 28, 2018	Approved
Vim Tux (Portable) 8.1.0644	198	Thursday, December 27, 2018	Approved
Vim Tux (Portable) 8.1.0635	179	Wednesday, December 26, 2018	Approved
Vim Tux (Portable) 8.1.0630	210	Tuesday, December 25, 2018	Approved
Vim Tux (Portable) 8.1.0629	189	Monday, December 24, 2018	Approved
Vim Tux (Portable) 8.1.0622	182	Sunday, December 23, 2018	Approved
Vim Tux (Portable) 8.1.0617	214	Saturday, December 22, 2018	Approved
Vim Tux (Portable) 8.1.0594	192	Sunday, December 16, 2018	Approved
Vim Tux (Portable) 8.1.0577	214	Thursday, December 13, 2018	Approved
Vim Tux (Portable) 8.1.0551	220	Friday, November 30, 2018	Approved
Vim Tux (Portable) 8.1.0547	218	Monday, November 26, 2018	Approved
Vim Tux (Portable) 8.1.0536	209	Tuesday, November 20, 2018	Approved
Vim Tux (Portable) 8.1.0524	211	Tuesday, November 13, 2018	Approved
Vim Tux (Portable) 8.1.0513	232	Thursday, November 8, 2018	Approved
Vim Tux (Portable) 8.1.0509	210	Sunday, November 4, 2018	Approved
Vim Tux (Portable) 8.1.0498	206	Sunday, October 28, 2018	Approved
Vim Tux (Portable) 8.1.0489	232	Monday, October 22, 2018	Approved
Vim Tux (Portable) 8.1.0474	242	Monday, October 15, 2018	Approved
Vim Tux (Portable) 8.1.0470	234	Friday, October 12, 2018	Approved
Vim Tux (Portable) 8.1.0451	249	Friday, October 5, 2018	Approved
Vim Tux (Portable) 8.1.0442	225	Monday, October 1, 2018	Approved
Vim Tux (Portable) 8.1.0436	195	Thursday, September 27, 2018	Approved
Vim Tux (Portable) 8.1.0425	211	Saturday, September 22, 2018	Approved
Vim Tux (Portable) 8.1.0408	210	Thursday, September 20, 2018	Approved
Vim Tux (Portable) 8.1.0401	200	Tuesday, September 18, 2018	Approved
Vim Tux (Portable) 8.1.0385	239	Friday, September 14, 2018	Approved
Vim Tux (Portable) 8.1.0371	216	Thursday, September 13, 2018	Approved
Vim Tux (Portable) 8.1.0362	212	Tuesday, September 11, 2018	Approved
Vim Tux (Portable) 8.1.0354	230	Sunday, September 9, 2018	Approved
Vim Tux (Portable) 8.1.0347	216	Thursday, September 6, 2018	Approved
Vim Tux (Portable) 8.1.0342	216	Sunday, September 2, 2018	Approved
Vim Tux (Portable) 8.1.0332	211	Thursday, August 30, 2018	Approved
Vim Tux (Portable) 8.1.0327	204	Sunday, August 26, 2018	Approved
Vim Tux (Portable) 8.1.0318	209	Thursday, August 23, 2018	Approved
Vim Tux (Portable) 8.1.0301	213	Tuesday, August 21, 2018	Approved
Vim Tux (Portable) 8.1.0297	221	Monday, August 20, 2018	Approved
Vim Tux (Portable) 8.1.0288	245	Thursday, August 16, 2018	Approved
Vim Tux (Portable) 8.1.0278	225	Monday, August 13, 2018	Approved
Vim Tux (Portable) 8.1.0271	210	Sunday, August 12, 2018	Approved
Vim Tux (Portable) 8.1.0259	248	Friday, August 10, 2018	Approved
Vim Tux (Portable) 8.1.0239	249	Sunday, August 5, 2018	Approved
Vim Tux (Portable) 8.1.0229	232	Tuesday, July 31, 2018	Approved
Vim Tux (Portable) 8.1.0221	241	Sunday, July 29, 2018	Approved
Vim Tux (Portable) 8.1.0210	219	Thursday, July 26, 2018	Approved
Vim Tux (Portable) 8.1.0207	215	Tuesday, July 24, 2018	Approved
Vim Tux (Portable) 8.1.0203	235	Monday, July 23, 2018	Approved
Vim Tux (Portable) 8.1.0199	223	Saturday, July 21, 2018	Approved
Vim Tux (Portable) 8.1.0196	257	Friday, July 20, 2018	Approved
Vim Tux (Portable) 8.1.0191	208	Tuesday, July 17, 2018	Approved
Vim Tux (Portable) 8.1.0186	243	Sunday, July 15, 2018	Approved
Vim Tux (Portable) 8.1.0173	286	Tuesday, July 10, 2018	Approved
Vim Tux (Portable) 8.1.0153	257	Friday, July 6, 2018	Approved
Vim Tux (Portable) 8.1.0138	262	Tuesday, July 3, 2018	Approved
Vim Tux (Portable) 8.1.0133	213	Sunday, July 1, 2018	Approved
Vim Tux (Portable) 8.1.0126	243	Friday, June 29, 2018	Approved
Vim Tux (Portable) 8.1.0105	253	Sunday, June 24, 2018	Approved
Vim Tux (Portable) 8.1.0054	275	Thursday, June 14, 2018	Approved
Vim Tux (Portable) 8.1.0034	273	Tuesday, June 5, 2018	Approved
Vim Tux (Portable) 8.1.0022	279	Friday, May 25, 2018	Approved
Vim Tux (Portable) 8.1.0013	281	Tuesday, May 22, 2018	Approved
Vim Tux (Portable) 8.1.0009	251	Monday, May 21, 2018	Approved
Vim Tux (Portable) 8.1.0004	244	Sunday, May 20, 2018	Approved
Vim Tux (Portable) 8.1.0.20180519	269	Saturday, May 19, 2018	Approved
Vim Tux (Portable) 8.1.0000	266	Friday, May 18, 2018	Approved
Vim Tux (Portable) 8.0.1848	326	Thursday, May 17, 2018	Approved
Vim Tux (Portable) 8.0.1831	293	Monday, May 14, 2018	Approved
Vim Tux (Portable) 8.0.1820	268	Sunday, May 13, 2018	Approved
Vim Tux (Portable) 8.0.1806	300	Thursday, May 10, 2018	Approved
Vim Tux (Portable) 8.0.1799	251	Monday, May 7, 2018	Approved
Vim Tux (Portable) 8.0.1794	254	Sunday, May 6, 2018	Approved
Vim Tux (Portable) 8.0.1790	300	Friday, May 4, 2018	Approved
Vim Tux (Portable) 8.0.1788	272	Thursday, May 3, 2018	Approved
Vim Tux (Portable) 8.0.1774	323	Monday, April 30, 2018	Approved
Vim Tux (Portable) 8.0.1765	275	Thursday, April 26, 2018	Approved
Vim Tux (Portable) 8.0.1748	268	Sunday, April 22, 2018	Approved
Vim Tux (Portable) 8.0.1736	288	Friday, April 20, 2018	Approved
Vim Tux (Portable) 8.0.1727	280	Wednesday, April 18, 2018	Approved
Vim Tux (Portable) 8.0.1705	272	Saturday, April 14, 2018	Approved
Vim Tux (Portable) 8.0.1679	273	Monday, April 9, 2018	Approved
Vim Tux (Portable) 8.0.1664	273	Saturday, April 7, 2018	Approved
Vim Tux (Portable) 8.0.1655	277	Saturday, March 31, 2018	Approved
Vim Tux (Portable) 8.0.1638	324	Sunday, March 25, 2018	Approved
Vim Tux (Portable) 8.0.1626	394	Thursday, March 22, 2018	Approved
Vim Tux (Portable) 8.0.1612	299	Saturday, March 17, 2018	Approved
Vim Tux (Portable) 8.0.1601	302	Tuesday, March 13, 2018	Approved
Vim Tux (Portable) 8.0.1591	328	Friday, March 9, 2018	Approved
Vim Tux (Portable) 8.0.1563	301	Sunday, March 4, 2018	Approved
Vim Tux (Portable) 8.0.1553	313	Friday, March 2, 2018	Approved
Vim Tux (Portable) 8.0.1532	323	Sunday, February 25, 2018	Approved
Vim Tux (Portable) 8.0.1504	326	Thursday, February 15, 2018	Approved
Vim Tux (Portable) 8.0.1473	307	Thursday, February 8, 2018	Approved
Vim Tux (Portable) 8.0.1451	322	Saturday, February 3, 2018	Approved
Vim Tux (Portable) 8.0.1438	328	Tuesday, January 30, 2018	Approved
Vim Tux (Portable) 8.0.1431	322	Saturday, January 27, 2018	Approved
Vim Tux (Portable) 8.0.1428	381	Thursday, January 4, 2018	Approved
Vim Tux (Portable) 8.0.1422	333	Saturday, December 30, 2017	Approved
Vim Tux (Portable) 8.0.1390	327	Sunday, December 17, 2017	Approved
Vim Tux (Portable) 8.0.1379	307	Thursday, December 14, 2017	Approved
Vim Tux (Portable) 8.0.1376	365	Thursday, December 7, 2017	Approved
Vim Tux (Portable) 8.0.1358	356	Friday, December 1, 2017	Approved
Vim Tux (Portable) 8.0.1330	344	Thursday, November 23, 2017	Approved
Vim Tux (Portable) 8.0.1311	322	Monday, November 20, 2017	Approved
Vim Tux (Portable) 8.0.1305	293	Saturday, November 18, 2017	Approved
Vim Tux (Portable) 8.0.1272	403	Thursday, November 9, 2017	Approved
Vim Tux (Portable) 8.0.1257	312	Sunday, November 5, 2017	Approved
Vim Tux (Portable) 8.0.1203	379	Wednesday, October 18, 2017	Approved
Vim Tux (Portable) 8.0.1157	385	Friday, September 29, 2017	Approved
Vim Tux (Portable) 8.0.1088	359	Monday, September 11, 2017	Approved
Vim Tux (Portable) 8.0.1010	380	Tuesday, August 29, 2017	Approved
Vim Tux (Portable) 8.0.0987	342	Wednesday, August 23, 2017	Approved
Vim Tux (Portable) 8.0.0737	414	Thursday, July 20, 2017	Approved
Vim Tux (Portable) 8.0.0642	382	Sunday, June 18, 2017	Approved
Vim Tux (Portable) 8.0.0584	402	Wednesday, April 26, 2017	Approved
Vim Tux (Portable) 8.0.0566	323	Friday, April 21, 2017	Approved
Vim Tux (Portable) 8.0.0123	611	Friday, December 9, 2016	Approved
Vim Tux (Portable) 8.0.0117	428	Friday, December 2, 2016	Approved
Vim Tux (Portable) 8.0.0066	404	Thursday, November 10, 2016	Approved
Vim Tux (Portable) 8.0.0051	421	Friday, October 28, 2016	Approved
Vim Tux (Portable) 8.0.0045	445	Friday, October 21, 2016	Approved
Vim Tux (Portable) 8.0.0017	350	Wednesday, September 28, 2016	Approved
Vim Tux (Portable) 8.0.005	448	Friday, September 16, 2016	Approved
Vim Tux (Portable) 7.4.2222	457	Thursday, August 18, 2016	Approved
Vim Tux (Portable) 7.4.2180	402	Tuesday, August 9, 2016	Approved
Vim Tux (Portable) 7.4.2153	391	Friday, August 5, 2016	Approved
Vim Tux (Portable) 7.4.2089	405	Friday, July 22, 2016	Approved
Vim Tux (Portable) 7.4.2034	400	Friday, July 15, 2016	Approved
Vim Tux (Portable) 7.4.1987	401	Sunday, July 3, 2016	Approved
Vim Tux (Portable) 7.4.1949	417	Thursday, June 23, 2016	Approved
Vim Tux (Portable) 7.4.1913	409	Friday, June 10, 2016	Approved
Vim Tux (Portable) 7.4.1905	356	Thursday, June 9, 2016	Approved
Vim Tux (Portable) 7.4.1901	401	Tuesday, June 7, 2016	Approved
Vim Tux (Portable) 7.4.1862	323	Thursday, June 2, 2016	Approved
Vim Tux (Portable) 7.4.1856	370	Monday, May 30, 2016	Approved
Vim Tux (Portable) 7.4.1848	390	Friday, May 27, 2016	Approved
Vim Tux (Portable) 7.4.1842	373	Thursday, May 26, 2016	Approved
Vim Tux (Portable) 7.4.1832	348	Thursday, May 19, 2016	Approved
Vim Tux (Portable) 7.4.1829	441	Thursday, May 12, 2016	Approved
Vim Tux (Portable) 7.4.1824	416	Monday, May 9, 2016	Approved

2023 Vim Team

Release Notes

https://www.vim.org/vim90.php

Dependencies

- vcredist2015 (≥ 14.0.24215.20170201)

Discussion for the Vim Tux (Portable) Package

Ground Rules:

This discussion is only about Vim Tux (Portable) and the Vim Tux (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 Vim Tux (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.

Resources

Events

Courses

83,040

24

07 Nov 2023

Vim Tux (Portable)

Vim Tux (Portable) 9.0.2092

Some Checks Have Failed or Are Not Yet Complete

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Notes

Antivirus Detections

Ground Rules: