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.4.3.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.4.3.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.4.3.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.4.3.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:

17,397

Downloads of v 3.6.0:

7

Last Update:

27 Mar 2025

Published Date:

27 Mar 2025

Package Maintainer(s):

joachim.schmidt557

Software Author(s):

Juan Linietsky
Ariel Manzur and contributors

Tags:

godot game engine game-engine graphics 3d 2d

Godot Game Engine (Mono version)

(Ready for review)

3.6.0 | Updated: 27 Mar 2025

Downloads:

17,397

Downloads of v 3.6.0:

Published:

27 Mar 2025

Maintainer(s):

joachim.schmidt557

Software Author(s):

Juan Linietsky
Ariel Manzur and contributors

Tags:

godot game engine game-engine graphics 3d 2d

Godot Game Engine (Mono version) 3.6.0

(Ready for review)

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Juan Linietsky, Ariel Manzur and contributors. The inclusion of Juan Linietsky, Ariel Manzur and contributors trademark(s), if any, upon this webpage is solely to identify Juan Linietsky, Ariel Manzur and contributors goods or services and not for commercial purposes.

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 ScannerExempted

Details

IMPORTANT

This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.

Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
There are also no guarantees that it will be approved.

WARNING

There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.

joachim.schmidt557 (maintainer) on 27 Mar 2025 20:52:09 +00:00:

User 'joachim.schmidt557' (maintainer) submitted package.

chocolatey-ops (reviewer) on 27 Mar 2025 21:27:11 +00:00:

godot-mono has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

In the Description element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 28 Mar 2025 04:21:56 +00:00:

godot-mono has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/60c0b05037dec0fc31fd32dc6fa48234 for details.
This is an FYI only. There is no action you need to take.

chocolatey-ops (reviewer) on 28 Mar 2025 04:44:37 +00:00:

godot-mono has passed automated virus scanning, however requires human verification.
Package Scan Status Type was ScannerExempted.

Package contains empty file(s)!

Check the virus scan results for additional information.

The package scanner had problems with the following files:

MSBuild.exe: File is empty (zero bytes).

Description

Godot Engine

2D and 3D cross-platform game engine

Godot Engine is a feature-packed, cross-platform game engine to create 2D and
3D games from a unified interface. It provides a comprehensive set of common
tools, so that users can focus on making games without having to reinvent the
wheel. Games can be exported in one click to a number of platforms, including
the major desktop platforms (Linux, Mac OSX, Windows) as well as mobile
(Android, iOS) and web-based (HTML5) platforms.

Free, open source and community-driven

Godot is completely free and open source under the very permissive MIT license.
No strings attached, no royalties, nothing. The users' games are theirs, down
to the last line of engine code. Godot's development is fully independent and
community-driven, empowering users to help shape their engine to match their
expectations. It is supported by the Software Freedom Conservancy
not-for-profit.

Before being open sourced in February 2014, Godot had been developed by Juan
Linietsky and Ariel Manzur (both still maintaining the project) for several
years as an in-house engine, used to publish several work-for-hire titles.

Files

legal\LICENSE.txt

Copyright (c) 2007-2018 Juan Linietsky, Ariel Manzur.
Copyright (c) 2014-2018 Godot Engine contributors (cf. AUTHORS.md)

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

legal\VERIFICATION.txt

VERIFICATION

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

Package can be verified like this:

1. Go to

   32-bit: https://github.com/godotengine/godot-builds/releases/download/3.6-stable/Godot_v3.6-stable_mono_win32.zip
   64-bit: https://github.com/godotengine/godot-builds/releases/download/3.6-stable/Godot_v3.6-stable_mono_win64.zip

   to download the zip file.

2. You can use one of the following methods to obtain the SHA256 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'

   checksum32: 6B9254AAD866795566371B1ABE3901C098D8F8B5AC696DF589C67B75E807E74E
   checksum64: 36BDDB15632C660A8E7C66415924BBF4AE7FCA80502282F3075093B1FF9B5B7C

File 'LICENSE.txt' obtained from:
   https://github.com/godotengine/godot/blob/master/LICENSE.txt

tools\chocolateyInstall.ps1


$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$fileName32 = 'Godot_v3.6-stable_mono_win32_x32.zip'
$fileName64 = 'Godot_v3.6-stable_mono_win64_x64.zip'
$zipFile    = Get-Item "$toolsDir\${fileName32}"
$zipFile64  = Get-Item "$toolsDir\${fileName64}"

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  destination   = $toolsDir
  filefullpath  = $zipFile
  filefullpath64= $zipFile64
}

# Remove older Godot versions first
Get-Item "$toolsDir\Godot*.exe" | Remove-Item -Force

Get-ChocolateyUnzip @packageArgs

# Make a nicer shim
$longFileName = Get-Item "$toolsDir\Godot*\Godot*.exe" | Select-Object -last 1
Install-BinFile -Name "godot" -Path "$longFileName"

New-Item "$longFileName.ignore" -ItemType "file"

tools\chocolateyUninstall.ps1

# Delete shim
Uninstall-BinFile -Name "godot"

tools\Godot_v3.6-stable_mono_win32_x32.zip

md5: FBE2DB4E1A12E6006FA05F98DA24806A | sha1: F52B31B79A7019DD167082128BA0F796847C76EA | sha256: 6B9254AAD866795566371B1ABE3901C098D8F8B5AC696DF589C67B75E807E74E | sha512: 60963D77AF9ECFDDEF9FCFF76E605E93B3AB4942276A1F6F25199F8561D8D886E038066072FDE6F62A224DC17291E2674B12273CC0ED85E3AA47D6DED5B507BE

tools\Godot_v3.6-stable_mono_win64_x64.zip

md5: 8D4E71696536AE2FA5BDC1DC9CDF5B19 | sha1: BBBD1218A907EDAB9575150A690C73D62E279FF4 | sha256: 36BDDB15632C660A8E7C66415924BBF4AE7FCA80502282F3075093B1FF9B5B7C | sha512: 703FD038E88B59C0FE1E3BA73416BA4A3CC14E4E46EB2380F7FEBFB8B5E544B0E21416CCCD3BA6C0334DEB9449B446922AAF923419D6FADF7F59E753A022EE56

Virus Scan Results

System.Buffers.dll (9444b5a41a81) - ## / 72
System.Collections.Immutable.dll (2f05a2c489c2) - ## / 73
System.Numerics.Vectors.dll (a044d77edb6e) - ## / 73
Microsoft.VisualStudio.Setup.Configuration.Interop.dll (839f15d54bbb) - ## / 73
System.Runtime.CompilerServices.Unsafe.dll (1ad2dd7225d5) - ## / 72
System.Memory.dll (41b5e1a4c59a) - ## / 73
Microsoft.Win32.Primitives.dll (e828dc69d959) - ## / 68
Microsoft.Win32.Registry.dll (fed0cb1fa8ed) - ## / 57
System.AppContext.dll (6a41b9af4747) - ## / 72
System.Collections.Concurrent.dll (695fe54cc7bb) - ## / 70
System.Collections.dll (2c29e42916c7) - ## / 72
System.Collections.NonGeneric.dll (6cc891cb8fcf) - ## / 69
System.Collections.Specialized.dll (a2743f2005e7) - ## / 71
System.ComponentModel.Annotations.dll (77357a44be28) - ## / 69
System.ComponentModel.dll (639507bb1ef9) - ## / 59
System.ComponentModel.EventBasedAsync.dll (fb3e11a07c1d) - ## / 73
System.ComponentModel.Primitives.dll (2816a3bc6325) - ## / 72
System.ComponentModel.TypeConverter.dll (be8f0988a5d5) - ## / 74
System.Console.dll (e1824a8e6455) - ## / 72
System.Data.Common.dll (63055b680f4e) - ## / 69
System.Data.SqlClient.dll (7c2a0cb8175f) - ## / 69
System.Diagnostics.Contracts.dll (56beb848b597) - ## / 67
System.Diagnostics.Debug.dll (86fe141fd703) - ## / 72
System.Diagnostics.FileVersionInfo.dll (ee8637ae5729) - ## / 67
System.Diagnostics.Process.dll (21afad6959f9) - ## / 72
System.Diagnostics.StackTrace.dll (ae411cbea4a9) - ## / 72
System.Diagnostics.TextWriterTraceListener.dll (813113b9bd28) - ## / 72
System.Diagnostics.Tools.dll (c9487da5039c) - ## / 72
System.Diagnostics.TraceEvent.dll (934878f9017f) - ## / 73
System.Diagnostics.TraceSource.dll (8aa6ed45c47f) - ## / 70
System.Diagnostics.Tracing.dll (2291c2edca81) - ## / 71
System.Drawing.Primitives.dll (bb490fe1d977) - ## / 66
System.Dynamic.Runtime.dll (d64f27d28807) - ## / 72
System.Globalization.Calendars.dll (cb4321f023ba) - ## / 69
System.Globalization.Extensions.dll (0a828bc0bd24) - ## / 69
System.IO.Compression.ZipFile.dll (60e84454c50c) - ## / 67
System.IO.dll (afd39e48cde9) - ## / 73
System.IO.FileSystem.dll (5055d2643b04) - ## / 72
System.IO.FileSystem.DriveInfo.dll (46ec1a946f99) - ## / 70
System.IO.FileSystem.Primitives.dll (e49c0997f7b8) - ## / 72
System.IO.FileSystem.Watcher.dll (bc4b54bf6e13) - ## / 69
System.IO.IsolatedStorage.dll (ab061e5a7258) - ## / 69
System.IO.MemoryMappedFiles.dll (5f576d40ae89) - ## / 71
System.IO.Pipes.dll (02d2179fadb7) - ## / 72
System.IO.UnmanagedMemoryStream.dll (02df7cb2f268) - ## / 70
System.Linq.dll (9829901f8f27) - ## / 72
System.Linq.Expressions.dll (7d389b00b5fb) - ## / 74
System.Linq.Parallel.dll (420babca30db) - ## / 72
System.Linq.Queryable.dll (16be125bd612) - ## / 72
System.Net.AuthenticationManager.dll (697f224c5c9d) - ## / 73
System.Net.Cache.dll (43d055fe2bb2) - ## / 72
System.Net.Http.Rtc.dll (c49e81d84907) - ## / 72
System.Net.HttpListener.dll (e6497ccc919d) - ## / 73
System.Net.Mail.dll (89d216f86c8d) - ## / 72
System.Net.NameResolution.dll (4a88fbbd7eb2) - ## / 73
System.Net.NetworkInformation.dll (54cb73948220) - ## / 70
System.Net.Ping.dll (d723a057bcfe) - ## / 72
System.Net.Primitives.dll (1f44db8074ca) - ## / 71
System.Net.Requests.dll (6d62b642ba78) - ## / 72
System.Net.Security.dll (496c85681ddf) - ## / 66
System.Net.ServicePoint.dll (bc85a9dd2ee4) - ## / 73
System.Net.Utilities.dll (39194791d92d) - ## / 71
System.Net.WebHeaderCollection.dll (959039308aef) - ## / 72
System.Net.WebSockets.Client.dll (9e876698a057) - ## / 71
System.Net.WebSockets.dll (9a353f3ca086) - ## / 70
System.ObjectModel.dll (7ffa997a0c1f) - ## / 71
System.Reflection.dll (4bc9d930c9cc) - ## / 72
System.Reflection.Emit.dll (df34bbce14e6) - ## / 73
System.Reflection.Emit.ILGeneration.dll (87fbadaec2fe) - ## / 72
System.Reflection.Emit.Lightweight.dll (203b470536e6) - ## / 74
System.Reflection.Extensions.dll (3180c4dd0118) - ## / 72
System.Reflection.Primitives.dll (01c69393c23a) - ## / 75
System.Resources.Reader.dll (b2e5377e0e36) - ## / 71
System.Resources.ReaderWriter.dll (e43236f01520) - ## / 72
System.Resources.ResourceManager.dll (860eb9604fef) - ## / 72
System.Resources.Writer.dll (556fd8c27370) - ## / 72
System.Runtime.CompilerServices.VisualC.dll (59a57386668f) - ## / 72
System.Runtime.Extensions.dll (d24002c74c46) - ## / 71
System.Runtime.Handles.dll (0ef998eac16d) - ## / 72
System.Runtime.InteropServices.dll (e3671531c2c7) - ## / 72
System.Runtime.InteropServices.RuntimeInformation.dll (f3a3228d0603) - ## / 71
System.Runtime.InteropServices.WindowsRuntime.dll (35ca5d210a81) - ## / 71
System.Runtime.Numerics.dll (f72d264a77f7) - ## / 72
System.Runtime.Serialization.Formatters.dll (fee524a6f3ff) - ## / 74
System.Runtime.Serialization.Json.dll (403ea127d9d3) - ## / 71
System.Runtime.Serialization.Primitives.dll (1f00ad147f7a) - ## / 72
System.Runtime.Serialization.Xml.dll (8d737ef1338a) - ## / 72
System.Security.AccessControl.dll (31fc9abecc62) - ## / 72
System.Security.Claims.dll (6e7fb569b141) - ## / 72
System.Security.Cryptography.Algorithms.dll (e3e4f30c71cf) - ## / 72
System.Security.Cryptography.Csp.dll (a5b7ecd47f52) - ## / 72
System.Security.Cryptography.DeriveBytes.dll (19346882f79a) - ## / 72
System.Security.Cryptography.Encoding.dll (58ca089e07c3) - ## / 71
System.Security.Cryptography.Encryption.Aes.dll (2617052180fc) - ## / 56
System.Security.Cryptography.Encryption.dll (453488f135ec) - ## / 71
System.Security.Cryptography.Encryption.ECDiffieHellman.dll (2d7e8bdf626e) - ## / 72
System.Security.Cryptography.Encryption.ECDsa.dll (103c4ce1a8ca) - ## / 72
System.Security.Cryptography.Hashing.Algorithms.dll (a1eddba7043f) - ## / 72
System.Security.Cryptography.Hashing.dll (d7e766b1f2c3) - ## / 72
System.Security.Cryptography.Primitives.dll (3851abe65dbd) - ## / 73
System.Security.Cryptography.ProtectedData.dll (f1890fc4b6d7) - ## / 72
System.Security.Cryptography.RandomNumberGenerator.dll (7fcc8462fd16) - ## / 72
System.Security.Cryptography.RSA.dll (1f85491baadc) - ## / 72
System.Security.Cryptography.X509Certificates.dll (41f70e2659e5) - ## / 72
System.Security.Principal.dll (4347360c91d3) - ## / 72
System.Security.Principal.Windows.dll (f36ac775086d) - ## / 72
System.Security.SecureString.dll (0b3041886603) - ## / 73
System.ServiceModel.Duplex.dll (79b78d912fe0) - ## / 72
System.ServiceModel.Http.dll (d2848aba872c) - ## / 73
System.ServiceModel.NetTcp.dll (f81eabae6da8) - ## / 72
System.ServiceModel.Primitives.dll (6706315b4e39) - ## / 70
System.ServiceModel.Security.dll (1d992660328e) - ## / 73
System.Text.Encoding.dll (ed4a4fbed677) - ## / 72
System.Text.Encoding.Extensions.dll (a0e44d0ea410) - ## / 74
System.Text.RegularExpressions.dll (e106bb630058) - ## / 72
System.Threading.dll (d5df86c9afba) - ## / 72
System.Threading.Overlapped.dll (682c921eb070) - ## / 67
System.Threading.Tasks.dll (1d402b128017) - ## / 73
System.Threading.Tasks.Parallel.dll (7acca6cc2232) - ## / 68
System.Threading.Thread.dll (4898e38702d9) - ## / 72
System.Threading.ThreadPool.dll (d1d3e55d0cc6) - ## / 73
System.Threading.Timer.dll (e422e02b2845) - ## / 69
System.ValueTuple.dll (f341fdcd30bf) - ## / 72
System.Xml.ReaderWriter.dll (7ab967a898f5) - ## / 71
System.Xml.XDocument.dll (d3c5b4142e63) - ## / 72
System.Xml.XmlDocument.dll (057cc5c5aee3) - ## / 74
System.Xml.XmlSerializer.dll (f573ee5d6561) - ## / 71
System.Xml.XPath.dll (5e007cde6bf8) - ## / 73
System.Xml.XPath.XDocument.dll (a5784a05a46a) - ## / 70
System.Xml.Xsl.Primitives.dll (3cb9e42b3b29) - ## / 69
Semver.dll (bf94c06e3380) - ## / 71
EnvDTE.dll (f0fa948c9256) - ## / 73
GodotTools.IdeMessaging.dll (c03eb1c6d613) - ## / 71
Microsoft.Build.dll (2f5cb82327d5) - ## / 71
Microsoft.Build.Framework.dll (6be56b415b8b) - ## / 73
stdole.dll (d390a809f0f1) - ## / 73
System.Threading.Tasks.Dataflow.dll (6336aaed8057) - ## / 73
Mono.Cecil.dll (96fa99d63cd8) - ## / 73
Mono.Cecil.Mdb.dll (1a05f2f7aa38) - ## / 73
Mono.Cecil.Pdb.dll (4ae57a84baf3) - ## / 73
Mono.Cecil.Rocks.dll (c1ed51d12a59) - ## / 71
System.Windows.dll (2e742cb8f345) - ## / 72
System.Xml.Serialization.dll (4a847e7f134f) - ## / 72
netstandard.dll (227118e700d5) - ## / 74
System.Globalization.dll (b9963da3727b) - ## / 72
System.Net.Sockets.dll (6db51fc2167e) - ## / 72
System.Runtime.dll (a866129d3e6c) - ## / 69
Newtonsoft.Json.dll (b624949df8b0) - ## / 73
GodotTools.OpenVisualStudio.exe (10361be3897f) - ## / 71
godot-mono.3.6.0.nupkg (1dd504bdd419) - ## / 61
Godot_v3.6-stable_mono_win32_x32.zip (6b9254aad866) - ## / 67
Godot_v3.6-stable_mono_win64_x64.zip (36bddb15632c) - ## / 64
Godot_v3.6-stable_mono_win64.exe (04b4e05ad7ec) - ## / 71
Godot_v3.6-stable_mono_win32.exe (efba2a994af3) - ## / 71
GodotTools.BuildLogger.dll (af53d236abcf) - ## / 72
GodotTools.Core.dll (b6ef60559350) - ## / 72
GodotTools.dll (d0a9000c4a40) - ## / 72
GodotTools.ProjectEditor.dll (fcf2cabca6ae) - ## / 72
GodotSharp.dll (0c0fce80385d) - ## / 73
GodotSharpEditor.dll (94c6fa3cfc24) - ## / 71
GodotSharp.dll (f0b5c4048f47) - ## / 72
GodotSharpEditor.dll (ee092dd47d0a) - ## / 61
libmono-btls-shared.dll (c681ceb8bd58) - ## / 74
MonoPosixHelper.dll (aed9de03dd51) - ## / 74
libmono-btls-shared.dll (c088996aefad) - ## / 73
MonoPosixHelper.dll (d15ab2bcc775) - ## / 73
Accessibility.dll (79568e5a7fbc) - ## / 72
Commons.Xml.Relaxng.dll (b98c7d7a210e) - ## / 72
cscompmgd.dll (83ebb6b18508) - ## / 72
CustomMarshalers.dll (4f3b7ef8ffcb) - ## / 72
I18N.CJK.dll (e47a74a362f9) - ## / 71
I18N.dll (df51769c0ffb) - ## / 72
I18N.MidEast.dll (69a404ed08bb) - ## / 72
I18N.Other.dll (109282253589) - ## / 72
I18N.Rare.dll (cc361d00bdef) - ## / 71
I18N.West.dll (e27eabb6098e) - ## / 72
IBM.Data.DB2.dll (c04b61d4ad47) - ## / 74
ICSharpCode.SharpZipLib.dll (cf7f88daa3c0) - ## / 72
Microsoft.Build.dll (292cc706bfb3) - ## / 72
Microsoft.Build.Engine.dll (bf3151234be7) - ## / 72
Microsoft.Build.Framework.dll (53af9c3314ae) - ## / 72
Microsoft.Build.Tasks.v4.0.dll (fd35f4d8bf0e) - ## / 67
Microsoft.Build.Utilities.v4.0.dll (2a39bbabf0ea) - ## / 72
Microsoft.CSharp.dll (00b8c563c203) - ## / 72
Microsoft.VisualC.dll (1b886cd5d3a7) - ## / 72
Microsoft.Web.Infrastructure.dll (5e72e57280ff) - ## / 72
Mono.Btls.Interface.dll (4334c58f2264) - ## / 72
Mono.C5.dll (382d10ab5dc0) - ## / 72
Mono.Cairo.dll (44e412a5c06d) - ## / 71
Mono.Cecil.dll (74a8cda6da8e) - ## / 72
Mono.Cecil.Mdb.dll (4198aa9a9b21) - ## / 72
Mono.CodeContracts.dll (fb9addf05bac) - ## / 72
Mono.CompilerServices.SymbolWriter.dll (3a2c601e6b5e) - ## / 72
Mono.Configuration.Crypto.dll (d6f78530861e) - ## / 72
Mono.CSharp.dll (79d438968268) - ## / 73
Mono.Data.Sqlite.dll (298d40102014) - ## / 71
Mono.Data.Tds.dll (ca3d94abf600) - ## / 72
Mono.Debugger.Soft.dll (6ecac82f2e5e) - ## / 72
Mono.Http.dll (f6374ed6836a) - ## / 72
Mono.Management.dll (6c00948ea6a0) - ## / 72
Mono.Messaging.dll (db6874d1726a) - ## / 72
Mono.Messaging.RabbitMQ.dll (a2ff25511c20) - ## / 72
Mono.Options.dll (5c255a14c239) - ## / 72
Mono.Parallel.dll (daf4f2e2416c) - ## / 72
Mono.Posix.dll (63838d7a140d) - ## / 72
Mono.Profiler.Log.dll (ad77513d2aa3) - ## / 72
Mono.Security.dll (bdfc86f77262) - ## / 72
Mono.Security.Win32.dll (89024ea5557d) - ## / 72
Mono.Simd.dll (511163d9dcca) - ## / 72
Mono.Tasklets.dll (7bc6533be1b3) - ## / 72
Mono.WebBrowser.dll (ba5249c1a95d) - ## / 72
Mono.XBuild.Tasks.dll (b5083d030760) - ## / 72
monodoc.dll (62ea18c7a357) - ## / 73
mscorlib.dll (b1e50518a87d) - ## / 73
Novell.Directory.Ldap.dll (2b0b5540e163) - ## / 72
PEAPI.dll (106ecef3e856) - ## / 72
RabbitMQ.Client.dll (6006366b6895) - ## / 72
SMDiagnostics.dll (90ad5aa995b2) - ## / 72
System.ComponentModel.Composition.dll (3e72fa7cd0a7) - ## / 72
System.ComponentModel.DataAnnotations.dll (5246bf2a846e) - ## / 72
System.Configuration.dll (898f073fa2ac) - ## / 72
System.Configuration.Install.dll (27ff380b0b22) - ## / 72
System.Core.dll (b0ac886be6db) - ## / 72
System.Data.DataSetExtensions.dll (d5cd05fa1f5c) - ## / 72
System.Data.dll (eaaad3c83617) - ## / 72
System.Data.Entity.dll (c2167c5d5188) - ## / 72
System.Data.Linq.dll (03492fbd5196) - ## / 71
System.Data.OracleClient.dll (ec372a0b28de) - ## / 72
System.Data.Services.Client.dll (c8313ab59895) - ## / 72
System.Data.Services.dll (7358783c86a2) - ## / 71
System.Deployment.dll (834e8ce814df) - ## / 72
System.Design.dll (1390b79ae4e3) - ## / 72
System.DirectoryServices.dll (c1f6fa62b9b6) - ## / 72
System.DirectoryServices.Protocols.dll (7501a60e6d2a) - ## / 72
System.dll (1d6153d1e1f3) - ## / 72
System.Drawing.Design.dll (e56f9ef9bb1a) - ## / 71
System.Drawing.dll (b62fca80f6ac) - ## / 72
System.Dynamic.dll (09af36033aff) - ## / 72
System.EnterpriseServices.dll (a15eff7d5df6) - ## / 71
System.IdentityModel.dll (2bb32915139e) - ## / 72
System.IdentityModel.Selectors.dll (04b1edfcd88b) - ## / 71
System.IO.Compression.dll (7b101c279979) - ## / 72
System.IO.Compression.FileSystem.dll (bd8544fc1865) - ## / 72
System.Json.dll (7db93b79f782) - ## / 72
System.Json.Microsoft.dll (dbc0c7f535dc) - ## / 72
System.Management.dll (8f0ce6ed8028) - ## / 71
System.Messaging.dll (1e389c635757) - ## / 72
System.Net.dll (79ef087fd1af) - ## / 72
System.Net.Http.dll (c03f46b7d2a2) - ## / 71
System.Net.Http.Formatting.dll (a0018c3d22b9) - ## / 72
System.Net.Http.WebRequest.dll (783a16d8ac63) - ## / 72
System.Numerics.dll (1c3f7f477f5e) - ## / 72
System.Numerics.Vectors.dll (9c995e1b9a84) - ## / 72
System.Reactive.Core.dll (5d29f786742d) - ## / 72
System.Reactive.Debugger.dll (dfde16568809) - ## / 70
System.Reactive.Experimental.dll (9a4513382cbd) - ## / 72
System.Reactive.Interfaces.dll (75e52fd89a0f) - ## / 72
System.Reactive.Linq.dll (f620c17a510a) - ## / 72
System.Reactive.Observable.Aliases.dll (652189371cfc) - ## / 72
System.Reactive.PlatformServices.dll (dc685939a23e) - ## / 72
System.Reactive.Providers.dll (78a0485e3f02) - ## / 72
System.Reactive.Runtime.Remoting.dll (7e481645995a) - ## / 72
System.Reactive.Windows.Forms.dll (76e5378b837a) - ## / 72
System.Reactive.Windows.Threading.dll (9793d6e263ae) - ## / 71
System.Reflection.Context.dll (93290917654b) - ## / 72
System.Runtime.Caching.dll (97e96207e6e6) - ## / 72
System.Runtime.CompilerServices.Unsafe.dll (78498df8d8a7) - ## / 72
System.Runtime.DurableInstancing.dll (49c34fb58353) - ## / 72
System.Runtime.Remoting.dll (d1d1a87aa472) - ## / 72
System.Runtime.Serialization.dll (4274a6a47f6c) - ## / 71
System.Runtime.Serialization.Formatters.Soap.dll (331b10fc4d58) - ## / 72
System.Security.dll (31ccda8a69a3) - ## / 71
System.ServiceModel.Activation.dll (5b910bb925dd) - ## / 72
System.ServiceModel.Discovery.dll (cdcaf7d00095) - ## / 72
System.ServiceModel.dll (757972a5d599) - ## / 72
System.ServiceModel.Internals.dll (26f09176da12) - ## / 72
System.ServiceModel.Routing.dll (6d4ea8d69e44) - ## / 72
System.ServiceModel.Web.dll (77e80c3eb47d) - ## / 72
System.ServiceProcess.dll (20f7cc2611e8) - ## / 72
System.Threading.Tasks.Dataflow.dll (c9809d32a96c) - ## / 72
System.Transactions.dll (1c2ca54e69f0) - ## / 72
System.Web.Abstractions.dll (304be806e8ad) - ## / 72
System.Web.ApplicationServices.dll (0abca97c8018) - ## / 72
System.Web.dll (951e47780ad2) - ## / 71
System.Web.DynamicData.dll (757513a5657e) - ## / 72
System.Web.Extensions.Design.dll (6a35d6aff44f) - ## / 72
System.Web.Extensions.dll (accd9939b400) - ## / 72
System.Web.Http.dll (d86a46146e4e) - ## / 72
System.Web.Http.SelfHost.dll (42729709eab0) - ## / 72
System.Web.Http.WebHost.dll (52f25cd2970b) - ## / 72
System.Web.Mobile.dll (a333aa83474b) - ## / 72
System.Web.Mvc.dll (9fc76fcfe0dc) - ## / 72
System.Web.Razor.dll (0a467fb90c0f) - ## / 72
System.Web.RegularExpressions.dll (88499e945a2c) - ## / 72
System.Web.Routing.dll (94d3b2bb0a65) - ## / 72
System.Web.Services.dll (9d5b74be80d5) - ## / 72
System.Web.WebPages.Deployment.dll (8701e6003bb8) - ## / 72
System.Web.WebPages.dll (e8c104b4505c) - ## / 72
System.Web.WebPages.Razor.dll (1779a6036c07) - ## / 72
System.Windows.Forms.DataVisualization.dll (9b828c1eee60) - ## / 72
System.Windows.Forms.dll (ad145f85d4c2) - ## / 72
System.Workflow.Activities.dll (18a2c19bc357) - ## / 71
System.Workflow.ComponentModel.dll (79e66bf1f3e0) - ## / 72
System.Workflow.Runtime.dll (79495386021a) - ## / 71
System.Xaml.dll (11ceed204b1d) - ## / 72
System.Xml.dll (d03349c98fe3) - ## / 72
System.Xml.Linq.dll (616c68efbd0a) - ## / 71
SystemWebTestShim.dll (32782c960c9f) - ## / 72
WebMatrix.Data.dll (c572070bf3c3) - ## / 72
WindowsBase.dll (2e3317c89762) - ## / 71
Microsoft.Win32.Registry.AccessControl.dll (39e4b860541d) - ## / 73
System.IO.FileSystem.AccessControl.dll (e6eb267049e5) - ## / 73
System.Reflection.TypeExtensions.dll (08bc5f43d163) - ## / 72
System.ServiceProcess.ServiceController.dll (e6a66d41032f) - ## / 73
System.Text.Encoding.CodePages.dll (d1b4cb97a190) - ## / 73
System.Threading.AccessControl.dll (29d7eb66c7f7) - ## / 73

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
Godot Game Engine (Mono version) 4.5.0-dev1	19	Friday, March 21, 2025	Exempted
Godot Game Engine (Mono version) 4.4.1	82	Thursday, March 27, 2025	Approved
Godot Game Engine (Mono version) 4.4.0	187	Tuesday, March 4, 2025	Approved
Godot Game Engine (Mono version) 4.3.0	646	Friday, August 16, 2024	Approved
Godot Game Engine (Mono version) 4.2.2	537	Thursday, April 18, 2024	Approved
Godot Game Engine (Mono version) 4.2.1	566	Wednesday, December 13, 2023	Approved
Godot Game Engine (Mono version) 4.2	306	Friday, December 1, 2023	Approved
Godot Game Engine (Mono version) 4.1.4	7	Thursday, March 27, 2025	Approved
Godot Game Engine (Mono version) 4.1.3	316	Friday, November 3, 2023	Approved
Godot Game Engine (Mono version) 4.1.2	413	Wednesday, October 4, 2023	Approved
Godot Game Engine (Mono version) 4.1.1	459	Wednesday, July 19, 2023	Approved
Godot Game Engine (Mono version) 4.1	165	Friday, July 7, 2023	Approved
Godot Game Engine (Mono version) 4.0.4	7	Thursday, March 27, 2025	Approved
Godot Game Engine (Mono version) 4.0.3	235	Saturday, May 20, 2023	Approved
Godot Game Engine (Mono version) 4.0.2	281	Wednesday, April 5, 2023	Approved
Godot Game Engine (Mono version) 4.0.1	177	Sunday, March 26, 2023	Approved
Godot Game Engine (Mono version) 3.6.0	7	Thursday, March 27, 2025	Ready
Godot Game Engine (Mono version) 3.5.3	10	Wednesday, March 26, 2025	Responded
Godot Game Engine (Mono version) 3.5.2	8	Wednesday, March 26, 2025	Ready
Godot Game Engine (Mono version) 3.5.1	389	Thursday, September 29, 2022	Approved
Godot Game Engine (Mono version) 3.5	290	Saturday, August 6, 2022	Exempted
Godot Game Engine (Mono version) 3.4.5	180	Thursday, August 4, 2022	Approved
Godot Game Engine (Mono version) 3.4.4	388	Thursday, March 24, 2022	Exempted
Godot Game Engine (Mono version) 3.4.3	235	Saturday, February 26, 2022	Exempted
Godot Game Engine (Mono version) 3.4.2	301	Thursday, December 23, 2021	Exempted
Godot Game Engine (Mono version) 3.4.1	170	Saturday, December 18, 2021	Exempted
Godot Game Engine (Mono version) 3.4	279	Saturday, November 6, 2021	Exempted
Godot Game Engine (Mono version) 3.3.4	460	Saturday, October 2, 2021	Exempted
Godot Game Engine (Mono version) 3.3.3	453	Friday, August 20, 2021	Exempted
Godot Game Engine (Mono version) 3.3.2	858	Tuesday, May 25, 2021	Exempted
Godot Game Engine (Mono version) 3.3.1	169	Thursday, May 20, 2021	Exempted
Godot Game Engine (Mono version) 3.3	1211	Thursday, April 22, 2021	Approved
Godot Game Engine (Mono version) 3.2.3	2742	Friday, September 18, 2020	Approved
Godot Game Engine (Mono version) 3.2.2	2042	Friday, June 26, 2020	Approved
Godot Game Engine 3.2.1	721	Wednesday, March 11, 2020	Approved
Godot Game Engine 3.2	357	Tuesday, February 18, 2020	Approved
Godot Game Engine 3.1.2	512	Sunday, December 1, 2019	Approved
Godot Game Engine 3.1.1	487	Saturday, June 8, 2019	Approved
Godot Game Engine 3.1	348	Thursday, March 14, 2019	Approved
Godot Game Engine 3.0.6	377	Tuesday, January 8, 2019	Approved

Release Notes

https://github.com/godotengine/godot/releases

Dependencies

- mono (≥ 5.16.0.220)

Discussion for the Godot Game Engine (Mono version) Package

Ground Rules:

This discussion is only about Godot Game Engine (Mono version) and the Godot Game Engine (Mono version) 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 Godot Game Engine (Mono version), 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

17,397

7

27 Mar 2025

27 Mar 2025

Godot Game Engine (Mono version)

Godot Game Engine (Mono version) 3.6.0

(Ready for review)

Some Checks Have Failed or Are Not Yet Complete

joachim.schmidt557 (maintainer) on 27 Mar 2025 20:52:09 +00:00:

chocolatey-ops (reviewer) on 27 Mar 2025 21:27:11 +00:00:

Guidelines

Notes

chocolatey-ops (reviewer) on 28 Mar 2025 04:21:56 +00:00:

chocolatey-ops (reviewer) on 28 Mar 2025 04:44:37 +00:00:

Godot Engine

2D and 3D cross-platform game engine

Free, open source and community-driven

Ground Rules: