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:

48

Downloads of v 10.1.20020.8623:

48

Last Update:

23 Apr 2025

Published Date:

23 Apr 2025

Package Maintainer(s):

muddy1

Software Author(s):

Intel Corporation

Tags:

intel chipset inf utility

Chipset INF Utility

(Waiting for Maintainer to take corrective action)

10.1.20020.8623 | Updated: 23 Apr 2025

Downloads:

Downloads of v 10.1.20020.8623:

Published:

23 Apr 2025

Maintainer(s):

muddy1

Software Author(s):

Intel Corporation

Tags:

intel chipset inf utility

Chipset INF Utility 10.1.20020.8623

(Waiting for Maintainer to take corrective action)

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Intel Corporation. The inclusion of Intel Corporation trademark(s), if any, upon this webpage is solely to identify Intel Corporation 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 Failed

Details

Scan Testing Pending

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.

muddy1 (maintainer) on 27 Feb 2025 08:31:24 +00:00:

User 'muddy1' (maintainer) submitted package.

muddy1 (maintainer) on 27 Feb 2025 08:54:37 +00:00:

User 'muddy1' (maintainer) submitted package.

chocolatey-ops (reviewer) on 27 Feb 2025 09:26:10 +00:00:

intel-chipset-inf has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

Binary files (.exe, .msi, .zip) have been included without including a VERIFICATION.txt file. This file is required when including binaries More...
ProjectUrl (projectUrl) in the nuspec file is required. Please add it to the nuspec. More...

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.

The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...

Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
- docsUrl - points to the location of the wiki or docs of the software
- mailingListUrl - points to the forum or email list group for the software
- bugTrackerUrl - points to the location where issues and tickets can be accessed
- projectSourceUrl - points to the location of the underlying software source

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.

The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...
Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

muddy1 (maintainer) on 27 Feb 2025 09:34:40 +00:00:

User 'muddy1' (maintainer) submitted package.

muddy1 (maintainer) on 27 Feb 2025 09:36:27 +00:00:

User 'muddy1' (maintainer) submitted package.

chocolatey-ops (reviewer) on 27 Feb 2025 10:11:19 +00:00:

intel-chipset-inf has failed automated validation.

Requirements

Binary files (.exe, .msi, .zip) have been included without including a VERIFICATION.txt file. This file is required when including binaries More...

Guidelines

The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...

Suggestions

The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
- docsUrl - points to the location of the wiki or docs of the software
- mailingListUrl - points to the forum or email list group for the software
- bugTrackerUrl - points to the location where issues and tickets can be accessed
- projectSourceUrl - points to the location of the underlying software source

Notes

The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...
Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

muddy1 (maintainer) on 27 Feb 2025 10:22:38 +00:00:

User 'muddy1' (maintainer) submitted package.

chocolatey-ops (reviewer) on 27 Feb 2025 10:56:23 +00:00:

intel-chipset-inf 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

The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...

Suggestions

The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
- docsUrl - points to the location of the wiki or docs of the software
- mailingListUrl - points to the forum or email list group for the software
- bugTrackerUrl - points to the location where issues and tickets can be accessed
- projectSourceUrl - points to the location of the underlying software source

Notes

The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...
Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 27 Feb 2025 12:30:12 +00:00:

intel-chipset-inf has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/b7fbf3ff2989a5626181cb20552436d1 for details.
The package status will be changed and will be waiting on your next actions.

NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey-community/chocolatey-test-environment
Please log in and leave a review comment if you have questions and/or comments.
If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

muddy1 (maintainer) on 27 Feb 2025 12:47:26 +00:00:

during testing phase and retesting phase the application installed silently

muddy1 (maintainer) on 27 Feb 2025 13:00:26 +00:00:

is it possible that the issue is because the package inevitably needs a restart?

muddy1 (maintainer) on 27 Feb 2025 16:14:03 +00:00:

is it possible that the issue is because the package inevitably needs a restart?

muddy1 (maintainer) on 01 Mar 2025 00:21:49 +00:00:

i read more of the review notes, and this application is installing drivers

muddy1 (maintainer) on 05 Mar 2025 01:09:25 +00:00:

User 'muddy1' (maintainer) submitted package.

chocolatey-ops (reviewer) on 05 Mar 2025 01:41:29 +00:00:

Guidelines

The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...

Suggestions

The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
- docsUrl - points to the location of the wiki or docs of the software
- mailingListUrl - points to the forum or email list group for the software
- bugTrackerUrl - points to the location where issues and tickets can be accessed
- projectSourceUrl - points to the location of the underlying software source

Notes

The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...
Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...
The IconUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...

chocolatey-ops (reviewer) on 05 Mar 2025 04:43:34 +00:00:

intel-chipset-inf has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/bfbf1007771ee881d5f861c3723d540d for details.
The package status will be changed and will be waiting on your next actions.

NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey-community/chocolatey-test-environment
Please log in and leave a review comment if you have questions and/or comments.
If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

chocolatey-ops (reviewer) on 25 Mar 2025 01:43:41 +00:00:

We've found intel-chipset-inf v10.1.20020.8623 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

Log in to the site and respond to the review comments.
Resubmit fixes for this version.
If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

muddy1 (maintainer) on 30 Mar 2025 20:14:06 +00:00:

here is the result from the local vagrant test:

PS C:\chocolatey-test-environment> choco.exe install -fdvy intel-chipset-inf --version 10.1.20020.8623
Chocolatey v2.4.3
Chocolatey is running on Windows v 10.0.26100.0
Attempting to delete file "C:/ProgramData/chocolatey/choco.exe.old".
Attempting to delete file "C:\ProgramData\chocolatey\choco.exe.old".
Command line: "C:\ProgramData\chocolatey\choco.exe" install -fdvy intel-chipset-inf --version 10.1.20020.8623
Received arguments: install -fdvy intel-chipset-inf --version 10.1.20020.8623
RemovePendingPackagesTask is now ready and waiting for PreRunMessage.
Sending message 'PreRunMessage' out if there are subscribers...
[Pending] Removing all pending packages that should not be considered installed...
Performing validation checks.
Global Configuration Validation Checks:

Package Exit Code / Exit On Reboot = Checked
System State Validation Checks:
Reboot Requirement Checks:
Pending Computer Rename = Checked
Pending Component Based Servicing = Checked
Pending Windows Auto Update = Checked
Pending File Rename Operations = Ignored
Pending Windows Package Installer = Checked
Pending Windows Package Installer SysWow64 = Checked
Cache Folder Lockdown Checks:
Elevated State = Checked
Folder Exists = Checked
Folder lockdown = Checked
The source 'https://community.chocolatey.org/api/v2/' evaluated to a 'normal' source type

Information.Is64BitOperatingSystem='True'|
Information.Is64BitProcess='True'|Information.IsInteractive='True'|
Information.UserName='muddy'|Information.UserDomainName='X0WF3D'|
Information.IsUserAdministrator='True'|
Information.IsUserSystemAccount='False'|
Information.IsUserRemoteDesktop='False'|
Information.IsUserRemote='False'|Information.IsProcessElevated='True'|
Information.IsLicensedVersion='False'|
Information.IsLicensedAssemblyLoaded='False'|
Information.LicenseType='Foss'|
Information.CurrentDirectory='C:\chocolatey-test-environment'|
Features.AutoUninstaller='True'|Features.ChecksumFiles='True'|
Features.AllowEmptyChecksums='False'|
Features.AllowEmptyChecksumsSecure='True'|
Features.FailOnAutoUninstaller='False'|
Features.FailOnStandardError='False'|Features.UsePowerShellHost='True'|
Features.LogEnvironmentValues='False'|Features.LogWithoutColor='False'|
Features.VirusCheck='False'|
Features.FailOnInvalidOrMissingLicense='False'|
Features.IgnoreInvalidOptionsSwitches='True'|
Features.UsePackageExitCodes='True'|
Features.UseEnhancedExitCodes='False'|
Features.UseFipsCompliantChecksums='False'|
Features.ShowNonElevatedWarnings='True'|
Features.ShowDownloadProgress='True'|
Features.StopOnFirstPackageFailure='False'|
Features.UseRememberedArgumentsForUpgrades='False'|
Features.IgnoreUnfoundPackagesOnUpgradeOutdated='False'|
Features.SkipPackageUpgradesWhenNotInstalled='False'|
Features.RemovePackageInformationOnUninstall='False'|
Features.ExitOnRebootDetected='False'|
Features.LogValidationResultsOnWarnings='True'|
Features.UsePackageRepositoryOptimizations='True'|
Features.UsePackageHashValidation='False'|
ListCommand.LocalOnly='False'|
ListCommand.IdOnly='False'|ListCommand.IncludeRegistryPrograms='False'|
ListCommand.PageSize='25'|ListCommand.Exact='False'|
ListCommand.ByIdOnly='False'|ListCommand.ByTagOnly='False'|
ListCommand.IdStartsWith='False'|ListCommand.OrderByPopularity='False'|
ListCommand.ApprovedOnly='False'|
ListCommand.DownloadCacheAvailable='False'|
ListCommand.NotBroken='False'|
ListCommand.IncludeVersionOverrides='False'|
ListCommand.ExplicitPageSize='False'|
ListCommand.ExplicitSource='False'|
UpgradeCommand.FailOnUnfound='False'|
UpgradeCommand.FailOnNotInstalled='False'|
UpgradeCommand.NotifyOnlyAvailableUpgrades='False'|
UpgradeCommand.ExcludePrerelease='False'|
UpgradeCommand.IgnorePinned='False'|
NewCommand.AutomaticPackage='False'|
NewCommand.UseOriginalTemplate='False'|SourceCommand.Command='unknown'|
SourceCommand.Priority='0'|SourceCommand.BypassProxy='False'|
SourceCommand.AllowSelfService='False'|
SourceCommand.VisibleToAdminsOnly='False'|
FeatureCommand.Command='unknown'|ConfigCommand.Command='Unknown'|
ApiKeyCommand.Command='Unknown'|PinCommand.Command='Unknown'|
OutdatedCommand.IgnorePinned='False'|
ExportCommand.IncludeVersionNumbers='False'|Proxy.BypassOnLocal='True'|
TemplateCommand.Command='unknown'|CacheCommand.Command='Unknown'|
CacheCommand.RemoveExpiredItemsOnly='False'|
_ Chocolatey:ChocolateyInstallCommand - Normal Run Mode _
Installing the following packages:
intel-chipset-inf
By installing, you accept licenses for the packages.
Process Tree: Chocolatey CLI => Chocolatey CLI => powershell => WindowsTerminal
Updating User Agent to 'Chocolatey Command Line/2.4.3 (Chocolatey CLI) via NuGet Client/6.4.1 (Microsoft Windows NT 10.0.26100.0)'.
Running list with the following filter = ''
--- Start of List ---
Process Tree: Chocolatey CLI => Chocolatey CLI => powershell => WindowsTerminal
Updating User Agent to 'Chocolatey Command Line/2.4.3 (Chocolatey CLI) via NuGet Client/6.4.1 (Microsoft Windows NT 10.0.26100.0)'.
Resolving resource PackageSearchResource for source C:\ProgramData\chocolatey\lib
7zip 24.9.0
7zip.install 24.9.0
autohotkey.portable 2.0.19
ccleaner 6.34.11482
chatterino 2.5.2
chocolatey 2.4.3
chocolatey-au 1.0.0
chocolatey-compatibility.extension 1.0.0
chocolatey-core.extension 1.4.0
chocolatey-dotnetfx.extension 1.0.1
chocolatey-misc-helpers.extension 0.0.4
chocolatey-windowsupdate.extension 1.0.5
discord.install 1.0.9187
dotnet4.7 4.7.2053.20190226
dotnetfx 4.8.0.20220524
Firefox 135.0.1
gimp 3.0.2.1
git 2.49.0
git.install 2.49.0
intel-chipset-inf 10.1.20020.8623
KB2919355 1.0.20160915
KB2919442 1.0.20160915
KB2999226 1.0.20181019
KB3033929 1.0.5
KB3035131 1.0.3
keybase 6.4.0
leagueoflegends 99.0.0.2477
notepadplusplus 8.7.8
notepadplusplus.install 8.7.8
nvidia-app 11.0.3.218
nvidia-display-driver 572.47.0
obs-studio.install 31.0.0
razer-synapse-4 2.1.0.766
steam 3.10.91.91241028
thunderbird 128.7.1
vagrant 2.4.3
vcredist140 14.42.34438.20250221
vcredist2015 14.0.24215.20170201
vcredist2017 14.16.27052
virtualbox 7.1.6
vlc 3.0.21
vlc.install 3.0.21
vortex 1.13.7
--- End of List ---
intel-chipset-inf v10.1.20020.8623 already installed. Forcing reinstall of version '10.1.20020.8623'.
Please use upgrade if you meant to upgrade to a new version.
Resolving resource PackageMetadataResource for source https://community.chocolatey.org/api/v2/
[NuGet] GET https://community.chocolatey.org/api/v2/Packages(Id='intel-chipset-inf',Version='10.1.20020.8623')
[NuGet] OK https://community.chocolatey.org/api/v2/Packages(Id='intel-chipset-inf',Version='10.1.20020.8623') 140ms
Resolving resource DependencyInfoResource for source https://community.chocolatey.org/api/v2/
[NuGet] CACHE https://community.chocolatey.org/api/v2/Packages(Id='intel-chipset-inf',Version='10.1.20020.8623')
[NuGet] Resolving dependency information took 0 ms
Running beforeModify step for 'intel-chipset-inf'
Backing up package files for 'intel-chipset-inf'
Attempting to create directory "C:\ProgramData\chocolatey\lib-bkp\intel-chipset-inf".
Moving C:\ProgramData\chocolatey\lib\intel-chipset-inf to C:\ProgramData\chocolatey\lib-bkp\intel-chipset-inf\10.1.20020.8623
Moving 'C:\ProgramData\chocolatey\lib\intel-chipset-inf'
to 'C:\ProgramData\chocolatey\lib-bkp\intel-chipset-inf\10.1.20020.8623'
Attempting to create directory "C:\ProgramData\chocolatey\lib\intel-chipset-inf".
Attempting to copy "C:\ProgramData\chocolatey\lib-bkp\intel-chipset-inf\10.1.20020.8623\intel-chipset-inf.nupkg"
to "C:\ProgramData\chocolatey\lib\intel-chipset-inf\intel-chipset-inf.nupkg".
Attempting to copy "C:\ProgramData\chocolatey\lib-bkp\intel-chipset-inf\10.1.20020.8623\intel-chipset-inf.nuspec"
to "C:\ProgramData\chocolatey\lib\intel-chipset-inf\intel-chipset-inf.nuspec".
Attempting to create directory "C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools".
Attempting to copy "C:\ProgramData\chocolatey\lib-bkp\intel-chipset-inf\10.1.20020.8623\tools\chocolateyinstall.ps1"
to "C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\chocolateyinstall.ps1".
Attempting to copy "C:\ProgramData\chocolatey\lib-bkp\intel-chipset-inf\10.1.20020.8623\tools\LICENSE.txt"
to "C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\LICENSE.txt".
Attempting to copy "C:\ProgramData\chocolatey\lib-bkp\intel-chipset-inf\10.1.20020.8623\tools\SetupChipset.exe"
to "C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\SetupChipset.exe".
Attempting to copy "C:\ProgramData\chocolatey\lib-bkp\intel-chipset-inf\10.1.20020.8623\tools\SetupChipset.exe.ignore"
to "C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\SetupChipset.exe.ignore".
Attempting to copy "C:\ProgramData\chocolatey\lib-bkp\intel-chipset-inf\10.1.20020.8623\tools\VERIFICATION.txt"
to "C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\VERIFICATION.txt".
Capturing package files in 'C:\ProgramData\chocolatey\lib\intel-chipset-inf'
Found 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\intel-chipset-inf.nupkg'
with checksum '83CA4A61C46FD22698E6B9EA6F896B96'
Found 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\intel-chipset-inf.nuspec'
with checksum '40EBEBD595DE13135CFE60D2290DC5CF'
Found 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\chocolateyinstall.ps1'
with checksum 'E4DE264A1688BAF728915920F9F71812'
Found 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\LICENSE.txt'
with checksum 'E914058B78130CF2C73707B8DBA9EFFE'
Found 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\SetupChipset.exe'
with checksum 'F95C92A57AE541F973B84A25A5DC488C'
Found 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\SetupChipset.exe.ignore'
with checksum 'BEA07E6D2B8DCE396FE21BAA61B34956'
Found 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\VERIFICATION.txt'
with checksum '7A0B1268BB333C8FF76965E27EFF162B'
Attempting to delete file "C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\SetupChipset.exe.ignore".
[NuGet] Removed folder 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools'.
[NuGet] Removed file 'intel-chipset-inf.nupkg' from folder 'C:\ProgramData\chocolatey\lib\intel-chipset-inf'.
Ensuring removal of package cache files.
Resolving resource DownloadResource for source https://community.chocolatey.org/api/v2/
Attempting to delete file "".
Downloading package from source 'https://community.chocolatey.org/api/v2/'
Package download location 'https://community.chocolatey.org/api/v2/package/intel-chipset-inf/10.1.20020.8623'
[NuGet] GET https://community.chocolatey.org/api/v2/package/intel-chipset-inf/10.1.20020.8623
[NuGet] OK https://community.chocolatey.org/api/v2/package/intel-chipset-inf/10.1.20020.8623 555ms
[NuGet] Acquiring lock for the installation of intel-chipset-inf 10.1.20020.8623
[NuGet] Acquired lock for the installation of intel-chipset-inf 10.1.20020.8623
Progress: Downloading intel-chipset-inf 10.1.20020.8623... 100%
[NuGet] Installed intel-chipset-inf 10.1.20020.8623 from https://community.chocolatey.org/api/v2/ with content hash lkN5d4mgig4Pk62P7CHca2+atumNxqV0fPU1GR9txuitgPk7YGO6iprn32cjJLBobfPxJjcxAV7bCoaTAKHr9g==.
Skipping package hash validation as feature 'usePackageHashValidation' is not enabled.
[NuGet] Adding package 'intel-chipset-inf.10.1.20020.8623' to folder 'C:\ProgramData\chocolatey\lib'
[NuGet] Added package 'intel-chipset-inf.10.1.20020.8623' to folder 'C:\ProgramData\chocolatey\lib'
Attempting to delete file "C:\Users\muddy\AppData\Local\Temp\chocolatey\ChocolateyScratch\intel-chipset-inf/10.1.20020.8623\intel-chipset-inf.10.1.20020.8623.nupkg".
Attempting to delete file "C:\Users\muddy\AppData\Local\Temp\chocolatey\ChocolateyScratch\intel-chipset-inf/10.1.20020.8623.nupkg.metadata".
Attempting to delete file "C:\Users\muddy\AppData\Local\Temp\chocolatey\ChocolateyScratch\intel-chipset-inf/10.1.20020.8623\intel-chipset-inf.10.1.20020.8623.nupkg.sha512".

intel-chipset-inf v10.1.20020.8623 (forced) - Possibly broken
intel-chipset-inf package files install completed. Performing other installation steps.
Setting installer args for intel-chipset-inf
Setting package parameters for intel-chipset-inf
Contents of 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\chocolateyinstall.ps1':

$ErrorActionPreference = 'Stop'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$fileLocation = Join-Path $toolsDir 'SetupChipset.exe'

$packageArgs = @{
packageName = $env:ChocolateyPackageName
unzipLocation = $toolsDir
fileType = 'EXE'
file = $fileLocation

softwareName = 'intel-inf-utility*'

checksum = '6CDDEEAFC32607FF914FD6038E475BF876E55804A9F759ECA773E5EA144AF481'
checksumType = 'sha256'

silentArgs = "-s -norestart"
validExitCodes= @(0, 3010, 1641)
}

Install-ChocolateyInstallPackage @packageArgs

Calling built-in PowerShell host with ['[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threading.Thread]::CurrentThread.CurrentUICulture = '';[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::SystemDefault; & import-module -name 'C:\ProgramData\chocolatey\helpers\chocolateyInstaller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1' -packageScript 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\chocolateyinstall.ps1' -installArguments '' -packageParameters '' -preRunHookScripts $null -postRunHookScripts $null'] Redirecting System.Management.Automation.resources, Version=3.0.0.0, Culture=en-US, PublicKeyToken=31bf3856ad364e35, requested by '' Host version is 5.1.26100.1882, PowerShell Version is '5.1.26100.2161' and CLR Version is '4.0.30319.42000'. VERBOSE: Loading module from path 'C:\ProgramData\chocolatey\helpers\Chocolatey.PowerShell.dll'. Returning loaded assembly type for 'Chocolatey.PowerShell' VERBOSE: Importing cmdlet 'Get-EnvironmentVariable'. VERBOSE: Importing cmdlet 'Get-EnvironmentVariableNames'. VERBOSE: Importing cmdlet 'Install-ChocolateyPath'. VERBOSE: Importing cmdlet 'Set-EnvironmentVariable'. VERBOSE: Importing cmdlet 'Test-ProcessAdminRights'. VERBOSE: Importing cmdlet 'Uninstall-ChocolateyPath'. VERBOSE: Importing cmdlet 'Update-SessionEnvironment'. Cmdlets exported from Chocolatey.PowerShell.dll Get-EnvironmentVariable Get-EnvironmentVariableNames Install-ChocolateyPath Set-EnvironmentVariable Test-ProcessAdminRights Uninstall-ChocolateyPath Update-SessionEnvironment VERBOSE: Exporting function 'Format-FileSize'. VERBOSE: Exporting function 'Get-ChecksumValid'. VERBOSE: Exporting function 'Get-ChocolateyConfigValue'. VERBOSE: Exporting function 'Get-ChocolateyPath'. VERBOSE: Exporting function 'Get-ChocolateyUnzip'. VERBOSE: Exporting function 'Get-ChocolateyWebFile'. VERBOSE: Exporting function 'Get-FtpFile'. VERBOSE: Exporting function 'Get-OSArchitectureWidth'. VERBOSE: Exporting function 'Get-PackageParameters'. VERBOSE: Exporting function 'Get-PackageParametersBuiltIn'. VERBOSE: Exporting function 'Get-ToolsLocation'. VERBOSE: Exporting function 'Get-UACEnabled'. VERBOSE: Exporting function 'Get-UninstallRegistryKey'. VERBOSE: Exporting function 'Get-VirusCheckValid'. VERBOSE: Exporting function 'Get-WebFile'. VERBOSE: Exporting function 'Get-WebFileName'. VERBOSE: Exporting function 'Get-WebHeaders'. VERBOSE: Exporting function 'Install-BinFile'. VERBOSE: Exporting function 'Install-ChocolateyEnvironmentVariable'. VERBOSE: Exporting function 'Install-ChocolateyExplorerMenuItem'. VERBOSE: Exporting function 'Install-ChocolateyFileAssociation'. VERBOSE: Exporting function 'Install-ChocolateyInstallPackage'. VERBOSE: Exporting function 'Install-ChocolateyPackage'. VERBOSE: Exporting function 'Install-ChocolateyPinnedTaskBarItem'. VERBOSE: Exporting function 'Install-ChocolateyPowershellCommand'. VERBOSE: Exporting function 'Install-ChocolateyShortcut'. VERBOSE: Exporting function 'Install-ChocolateyVsixPackage'. VERBOSE: Exporting function 'Install-ChocolateyZipPackage'. VERBOSE: Exporting function 'Install-Vsix'. VERBOSE: Exporting function 'Set-PowerShellExitCode'. VERBOSE: Exporting function 'Start-ChocolateyProcessAsAdmin'. VERBOSE: Exporting function 'Uninstall-BinFile'. VERBOSE: Exporting function 'Uninstall-ChocolateyEnvironmentVariable'. VERBOSE: Exporting function 'Uninstall-ChocolateyPackage'. VERBOSE: Exporting function 'Uninstall-ChocolateyZipPackage'. VERBOSE: Exporting function 'Write-FunctionCallLogMessage'. VERBOSE: Exporting cmdlet 'Get-EnvironmentVariable'. VERBOSE: Exporting cmdlet 'Get-EnvironmentVariableNames'. VERBOSE: Exporting cmdlet 'Install-ChocolateyPath'. VERBOSE: Exporting cmdlet 'Set-EnvironmentVariable'. VERBOSE: Exporting cmdlet 'Test-ProcessAdminRights'. VERBOSE: Exporting cmdlet 'Uninstall-ChocolateyPath'. VERBOSE: Exporting cmdlet 'Update-SessionEnvironment'. VERBOSE: Exporting alias 'Get-ProcessorBits'. VERBOSE: Exporting alias 'Get-OSBitness'. VERBOSE: Exporting alias 'Get-InstallRegistryKey'. VERBOSE: Exporting alias 'Generate-BinFile'. VERBOSE: Exporting alias 'Add-BinFile'. VERBOSE: Exporting alias 'Start-ChocolateyProcess'. VERBOSE: Exporting alias 'Invoke-ChocolateyProcess'. VERBOSE: Exporting alias 'Remove-BinFile'. VERBOSE: Exporting alias 'refreshenv'. Loading community extensions Importing 'C:\ProgramData\chocolatey\extensions\chocolatey-compatibility\chocolatey-compatibility.psm1' VERBOSE: Loading module from path 'C:\ProgramData\chocolatey\extensions\chocolatey-compatibility\chocolatey-compatibility.psm1'. Function 'Get-PackageParameters' exists, ignoring export. Function 'Get-UninstallRegistryKey' exists, ignoring export. Exporting function 'Install-ChocolateyDesktopLink' for backwards compatibility VERBOSE: Exporting function 'Install-ChocolateyDesktopLink'. Exporting function 'Write-ChocolateyFailure' for backwards compatibility VERBOSE: Exporting function 'Write-ChocolateyFailure'. Exporting function 'Write-ChocolateySuccess' for backwards compatibility VERBOSE: Exporting function 'Write-ChocolateySuccess'. Exporting function 'Write-FileUpdateLog' for backwards compatibility VERBOSE: Exporting function 'Write-FileUpdateLog'. VERBOSE: Importing function 'Install-ChocolateyDesktopLink'. VERBOSE: Importing function 'Write-ChocolateyFailure'. VERBOSE: Importing function 'Write-ChocolateySuccess'. VERBOSE: Importing function 'Write-FileUpdateLog'. Importing 'C:\ProgramData\chocolatey\extensions\chocolatey-core\chocolatey-core.psm1' VERBOSE: Loading module from path 'C:\ProgramData\chocolatey\extensions\chocolatey-core\chocolatey-core.psm1'. VERBOSE: Exporting function 'Get-AppInstallLocation'. VERBOSE: Exporting function 'Get-AvailableDriveLetter'. VERBOSE: Exporting function 'Get-EffectiveProxy'. VERBOSE: Exporting function 'Get-PackageCacheLocation'. VERBOSE: Exporting function 'Get-WebContent'. VERBOSE: Exporting function 'Register-Application'. VERBOSE: Exporting function 'Remove-Process'. VERBOSE: Importing function 'Get-AppInstallLocation'. VERBOSE: Importing function 'Get-AvailableDriveLetter'. VERBOSE: Importing function 'Get-EffectiveProxy'. VERBOSE: Importing function 'Get-PackageCacheLocation'. VERBOSE: Importing function 'Get-WebContent'. VERBOSE: Importing function 'Register-Application'. VERBOSE: Importing function 'Remove-Process'. Importing 'C:\ProgramData\chocolatey\extensions\chocolatey-dotnetfx\chocolatey-dotnetfx.psm1' VERBOSE: Loading module from path 'C:\ProgramData\chocolatey\extensions\chocolatey-dotnetfx\chocolatey-dotnetfx.psm1'. VERBOSE: Exporting function 'Install-DotNetFramework'. VERBOSE: Exporting function 'Install-DotNetDevPack'. VERBOSE: Importing function 'Install-DotNetDevPack'. VERBOSE: Importing function 'Install-DotNetFramework'. Importing 'C:\ProgramData\chocolatey\extensions\chocolatey-misc-helpers\chocolatey-misc-helpers.psm1' VERBOSE: Loading module from path 'C:\ProgramData\chocolatey\extensions\chocolatey-misc-helpers\chocolatey-misc-helpers.psm1'. VERBOSE: Exporting function 'Enable-AutoPin'. VERBOSE: Exporting function 'Show-Patreon'. VERBOSE: Exporting function 'Show-PayPal'. VERBOSE: Exporting function 'Show-ToastMessage'. VERBOSE: Exporting function 'Start-CheckandStop'. VERBOSE: Exporting function 'Start-CheckandThrow'. VERBOSE: Exporting function 'Start-WaitandStop'. VERBOSE: Exporting function 'Start-WaitandStopActual'. VERBOSE: Exporting function 'Test-Dependency'. VERBOSE: Exporting function 'Test-URL'. VERBOSE: Importing function 'Enable-AutoPin'. VERBOSE: Importing function 'Show-Patreon'. VERBOSE: Importing function 'Show-PayPal'. VERBOSE: Importing function 'Show-ToastMessage'. VERBOSE: Importing function 'Start-CheckandStop'. VERBOSE: Importing function 'Start-CheckandThrow'. VERBOSE: Importing function 'Start-WaitandStop'. VERBOSE: Importing function 'Start-WaitandStopActual'. VERBOSE: Importing function 'Test-Dependency'. VERBOSE: Importing function 'Test-URL'. Importing 'C:\ProgramData\chocolatey\extensions\chocolatey-windowsupdate\chocolatey-windowsupdate.psm1' VERBOSE: Loading module from path 'C:\ProgramData\chocolatey\extensions\chocolatey-windowsupdate\chocolatey-windowsupdate.psm1'. VERBOSE: Exporting function 'Install-WindowsUpdate'. VERBOSE: Exporting function 'Test-WindowsUpdate'. VERBOSE: Importing function 'Install-WindowsUpdate'. VERBOSE: Importing function 'Test-WindowsUpdate'. VERBOSE: Exporting function 'Format-FileSize'. VERBOSE: Exporting function 'Get-ChecksumValid'. VERBOSE: Exporting function 'Get-ChocolateyConfigValue'. VERBOSE: Exporting function 'Get-ChocolateyPath'. VERBOSE: Exporting function 'Get-ChocolateyUnzip'. VERBOSE: Exporting function 'Get-ChocolateyWebFile'. VERBOSE: Exporting function 'Get-FtpFile'. VERBOSE: Exporting function 'Get-OSArchitectureWidth'. VERBOSE: Exporting function 'Get-PackageParameters'. VERBOSE: Exporting function 'Get-PackageParametersBuiltIn'. VERBOSE: Exporting function 'Get-ToolsLocation'. VERBOSE: Exporting function 'Get-UACEnabled'. VERBOSE: Exporting function 'Get-UninstallRegistryKey'. VERBOSE: Exporting function 'Get-VirusCheckValid'. VERBOSE: Exporting function 'Get-WebFile'. VERBOSE: Exporting function 'Get-WebFileName'. VERBOSE: Exporting function 'Get-WebHeaders'. VERBOSE: Exporting function 'Install-BinFile'. VERBOSE: Exporting function 'Install-ChocolateyEnvironmentVariable'. VERBOSE: Exporting function 'Install-ChocolateyExplorerMenuItem'. VERBOSE: Exporting function 'Install-ChocolateyFileAssociation'. VERBOSE: Exporting function 'Install-ChocolateyInstallPackage'. VERBOSE: Exporting function 'Install-ChocolateyPackage'. VERBOSE: Exporting function 'Install-ChocolateyPinnedTaskBarItem'. VERBOSE: Exporting function 'Install-ChocolateyPowershellCommand'. VERBOSE: Exporting function 'Install-ChocolateyShortcut'. VERBOSE: Exporting function 'Install-ChocolateyVsixPackage'. VERBOSE: Exporting function 'Install-ChocolateyZipPackage'. VERBOSE: Exporting function 'Install-Vsix'. VERBOSE: Exporting function 'Set-PowerShellExitCode'. VERBOSE: Exporting function 'Start-ChocolateyProcessAsAdmin'. VERBOSE: Exporting function 'Uninstall-BinFile'. VERBOSE: Exporting function 'Uninstall-ChocolateyEnvironmentVariable'. VERBOSE: Exporting function 'Uninstall-ChocolateyPackage'. VERBOSE: Exporting function 'Uninstall-ChocolateyZipPackage'. VERBOSE: Exporting function 'Write-FunctionCallLogMessage'. VERBOSE: Exporting function 'Install-ChocolateyDesktopLink'. VERBOSE: Exporting function 'Write-ChocolateyFailure'. VERBOSE: Exporting function 'Write-ChocolateySuccess'. VERBOSE: Exporting function 'Write-FileUpdateLog'. VERBOSE: Exporting function 'Get-AppInstallLocation'. VERBOSE: Exporting function 'Get-AvailableDriveLetter'. VERBOSE: Exporting function 'Get-EffectiveProxy'. VERBOSE: Exporting function 'Get-PackageCacheLocation'. VERBOSE: Exporting function 'Get-WebContent'. VERBOSE: Exporting function 'Register-Application'. VERBOSE: Exporting function 'Remove-Process'. VERBOSE: Exporting function 'Install-DotNetDevPack'. VERBOSE: Exporting function 'Install-DotNetFramework'. VERBOSE: Exporting function 'Enable-AutoPin'. VERBOSE: Exporting function 'Show-Patreon'. VERBOSE: Exporting function 'Show-PayPal'. VERBOSE: Exporting function 'Show-ToastMessage'. VERBOSE: Exporting function 'Start-CheckandStop'. VERBOSE: Exporting function 'Start-CheckandThrow'. VERBOSE: Exporting function 'Start-WaitandStop'. VERBOSE: Exporting function 'Start-WaitandStopActual'. VERBOSE: Exporting function 'Test-Dependency'. VERBOSE: Exporting function 'Test-URL'. VERBOSE: Exporting function 'Install-WindowsUpdate'. VERBOSE: Exporting function 'Test-WindowsUpdate'. VERBOSE: Exporting cmdlet 'Get-EnvironmentVariable'. VERBOSE: Exporting cmdlet 'Get-EnvironmentVariableNames'. VERBOSE: Exporting cmdlet 'Install-ChocolateyPath'. VERBOSE: Exporting cmdlet 'Set-EnvironmentVariable'. VERBOSE: Exporting cmdlet 'Test-ProcessAdminRights'. VERBOSE: Exporting cmdlet 'Uninstall-ChocolateyPath'. VERBOSE: Exporting cmdlet 'Update-SessionEnvironment'. VERBOSE: Exporting cmdlet 'Get-EnvironmentVariable'. VERBOSE: Exporting cmdlet 'Get-EnvironmentVariableNames'. VERBOSE: Exporting cmdlet 'Install-ChocolateyPath'. VERBOSE: Exporting cmdlet 'Set-EnvironmentVariable'. VERBOSE: Exporting cmdlet 'Test-ProcessAdminRights'. VERBOSE: Exporting cmdlet 'Uninstall-ChocolateyPath'. VERBOSE: Exporting cmdlet 'Update-SessionEnvironment'. VERBOSE: Exporting alias 'Get-ProcessorBits'. VERBOSE: Exporting alias 'Get-OSBitness'. VERBOSE: Exporting alias 'Get-InstallRegistryKey'. VERBOSE: Exporting alias 'Generate-BinFile'. VERBOSE: Exporting alias 'Add-BinFile'. VERBOSE: Exporting alias 'Start-ChocolateyProcess'. VERBOSE: Exporting alias 'Invoke-ChocolateyProcess'. VERBOSE: Exporting alias 'Remove-BinFile'. VERBOSE: Exporting alias 'refreshenv'. VERBOSE: Importing cmdlet 'Get-EnvironmentVariable'. VERBOSE: Importing cmdlet 'Get-EnvironmentVariableNames'. VERBOSE: Importing cmdlet 'Install-ChocolateyPath'. VERBOSE: Importing cmdlet 'Set-EnvironmentVariable'. VERBOSE: Importing cmdlet 'Test-ProcessAdminRights'. VERBOSE: Importing cmdlet 'Uninstall-ChocolateyPath'. VERBOSE: Importing cmdlet 'Update-SessionEnvironment'. VERBOSE: Importing function 'Enable-AutoPin'. VERBOSE: Importing function 'Format-FileSize'. VERBOSE: Importing function 'Get-AppInstallLocation'. VERBOSE: Importing function 'Get-AvailableDriveLetter'. VERBOSE: Importing function 'Get-ChecksumValid'. VERBOSE: Importing function 'Get-ChocolateyConfigValue'. VERBOSE: Importing function 'Get-ChocolateyPath'. VERBOSE: Importing function 'Get-ChocolateyUnzip'. VERBOSE: Importing function 'Get-ChocolateyWebFile'. VERBOSE: Importing function 'Get-EffectiveProxy'. VERBOSE: Importing function 'Get-FtpFile'. VERBOSE: Importing function 'Get-OSArchitectureWidth'. VERBOSE: Importing function 'Get-PackageCacheLocation'. VERBOSE: Importing function 'Get-PackageParameters'. VERBOSE: Importing function 'Get-PackageParametersBuiltIn'. VERBOSE: Importing function 'Get-ToolsLocation'. VERBOSE: Importing function 'Get-UACEnabled'. VERBOSE: Importing function 'Get-UninstallRegistryKey'. VERBOSE: Importing function 'Get-VirusCheckValid'. VERBOSE: Importing function 'Get-WebContent'. VERBOSE: Importing function 'Get-WebFile'. VERBOSE: Importing function 'Get-WebFileName'. VERBOSE: Importing function 'Get-WebHeaders'. VERBOSE: Importing function 'Install-BinFile'. VERBOSE: Importing function 'Install-ChocolateyDesktopLink'. VERBOSE: Importing function 'Install-ChocolateyEnvironmentVariable'. VERBOSE: Importing function 'Install-ChocolateyExplorerMenuItem'. VERBOSE: Importing function 'Install-ChocolateyFileAssociation'. VERBOSE: Importing function 'Install-ChocolateyInstallPackage'. VERBOSE: Importing function 'Install-ChocolateyPackage'. VERBOSE: Importing function 'Install-ChocolateyPinnedTaskBarItem'. VERBOSE: Importing function 'Install-ChocolateyPowershellCommand'. VERBOSE: Importing function 'Install-ChocolateyShortcut'. VERBOSE: Importing function 'Install-ChocolateyVsixPackage'. VERBOSE: Importing function 'Install-ChocolateyZipPackage'. VERBOSE: Importing function 'Install-DotNetDevPack'. VERBOSE: Importing function 'Install-DotNetFramework'. VERBOSE: Importing function 'Install-Vsix'. VERBOSE: Importing function 'Install-WindowsUpdate'. VERBOSE: Importing function 'Register-Application'. VERBOSE: Importing function 'Remove-Process'. VERBOSE: Importing function 'Set-PowerShellExitCode'. VERBOSE: Importing function 'Show-Patreon'. VERBOSE: Importing function 'Show-PayPal'. VERBOSE: Importing function 'Show-ToastMessage'. VERBOSE: Importing function 'Start-CheckandStop'. VERBOSE: Importing function 'Start-CheckandThrow'. VERBOSE: Importing function 'Start-ChocolateyProcessAsAdmin'. VERBOSE: Importing function 'Start-WaitandStop'. VERBOSE: Importing function 'Start-WaitandStopActual'. VERBOSE: Importing function 'Test-Dependency'. VERBOSE: Importing function 'Test-URL'. VERBOSE: Importing function 'Test-WindowsUpdate'. VERBOSE: Importing function 'Uninstall-BinFile'. VERBOSE: Importing function 'Uninstall-ChocolateyEnvironmentVariable'. VERBOSE: Importing function 'Uninstall-ChocolateyPackage'. VERBOSE: Importing function 'Uninstall-ChocolateyZipPackage'. VERBOSE: Importing function 'Write-ChocolateyFailure'. VERBOSE: Importing function 'Write-ChocolateySuccess'. VERBOSE: Importing function 'Write-FileUpdateLog'. VERBOSE: Importing function 'Write-FunctionCallLogMessage'. VERBOSE: Importing alias 'Add-BinFile'. VERBOSE: Importing alias 'Generate-BinFile'. VERBOSE: Importing alias 'Get-InstallRegistryKey'. VERBOSE: Importing alias 'Get-OSBitness'. VERBOSE: Importing alias 'Get-ProcessorBits'. VERBOSE: Importing alias 'Invoke-ChocolateyProcess'. VERBOSE: Importing alias 'refreshenv'. VERBOSE: Importing alias 'Remove-BinFile'. VERBOSE: Importing alias 'Start-ChocolateyProcess'. ---------------------------Script Execution--------------------------- Running 'ChocolateyScriptRunner' for intel-chipset-inf v10.1.20020.8623 with packageScript 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\chocolateyinstall.ps1', packageFolder:'C:\ProgramData\chocolatey\lib\intel-chipset-inf', installArguments: '', packageParameters: '', preRunHookScripts: '', postRunHookScripts: '', Running package script 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\chocolateyinstall.ps1' Running Install-ChocolateyInstallPackage -packageName 'intel-chipset-inf' -fileType 'EXE' -validExitCodes '0 3010 1641' -silentArgs '-s -norestart' -file 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\SetupChipset.exe' Running Get-OSArchitectureWidth -compare '32' Installing intel-chipset-inf... Running Start-ChocolateyProcessAsAdmin -validExitCodes '0 3010 1641' -workingDirectory 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools' -statements '-s -norestart' -exeToRun 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\SetupChipset.exe' Running Test-ProcessAdminRights Test-ProcessAdminRights: returning True Finishing 'Test-ProcessAdminRights' Elevating permissions and running ["C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\SetupChipset.exe" -s -norestart]. This may take a while, depending on the statements. Command ["C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\SetupChipset.exe" -s -norestart] exited with '3010'. Finishing 'Start-ChocolateyProcessAsAdmin' intel-chipset-inf has been installed.

Built-in PowerShell host called with ['[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threading.Thread]::CurrentThread.CurrentUICulture = '';[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::SystemDefault; & import-module -name 'C:\ProgramData\chocolatey\helpers\chocolateyInstaller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1' -packageScript 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\chocolateyinstall.ps1' -installArguments '' -packageParameters '' -preRunHookScripts $null -postRunHookScripts $null'] exited with '3010'.
Calling command ['"C:\WINDOWS\System32\shutdown.exe" /a']
Command ['"C:\WINDOWS\System32\shutdown.exe" /a'] exited with '1116'
Capturing package files in 'C:\ProgramData\chocolatey\lib\intel-chipset-inf'
Found 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\intel-chipset-inf.nupkg'
with checksum '83CA4A61C46FD22698E6B9EA6F896B96'
Found 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\intel-chipset-inf.nuspec'
with checksum '40EBEBD595DE13135CFE60D2290DC5CF'
Found 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\chocolateyinstall.ps1'
with checksum 'E4DE264A1688BAF728915920F9F71812'
Found 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\LICENSE.txt'
with checksum 'E914058B78130CF2C73707B8DBA9EFFE'
Found 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\SetupChipset.exe'
with checksum 'F95C92A57AE541F973B84A25A5DC488C'
Found 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\SetupChipset.exe.ignore'
with checksum 'BEA07E6D2B8DCE396FE21BAA61B34956'
Found 'C:\ProgramData\chocolatey\lib\intel-chipset-inf\tools\VERIFICATION.txt'
with checksum '7A0B1268BB333C8FF76965E27EFF162B'
Attempting to delete file "C:\ProgramData\chocolatey.chocolatey\intel-chipset-inf.10.1.20020.8623.arguments".
Attempting to delete file "C:\ProgramData\chocolatey.chocolatey\intel-chipset-inf.10.1.20020.8623.extra".
Attempting to delete file "C:\ProgramData\chocolatey.chocolatey\intel-chipset-inf.10.1.20020.8623.version".
Attempting to delete file "C:\ProgramData\chocolatey.chocolatey\intel-chipset-inf.10.1.20020.8623.sxs".
Attempting to delete file "C:\ProgramData\chocolatey.chocolatey\intel-chipset-inf.10.1.20020.8623.pin".
Attempting to delete file "C:\ProgramData\chocolatey.chocolatey\intel-chipset-inf.10.1.20020.8623.deploymentLocation".
Sending message 'HandlePackageResultCompletedMessage' out if there are subscribers...
Attempting to delete file "C:\ProgramData\chocolatey\lib\intel-chipset-inf.chocolateyPending".
Attempting to delete directory "C:\ProgramData\chocolatey\lib-bkp\intel-chipset-inf".
The install of intel-chipset-inf was successful.
Software installed as 'EXE', install location is likely default.

muddy1 (maintainer) on 30 Mar 2025 23:45:35 +00:00:

User 'muddy1' (maintainer) submitted package.

chocolatey-ops (reviewer) on 31 Mar 2025 00:21:15 +00:00:

Guidelines

The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...

Suggestions

The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
- docsUrl - points to the location of the wiki or docs of the software
- mailingListUrl - points to the forum or email list group for the software
- bugTrackerUrl - points to the location where issues and tickets can be accessed
- projectSourceUrl - points to the location of the underlying software source

Notes

The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...
Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...
The IconUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...

chocolatey-ops (reviewer) on 31 Mar 2025 00:25:39 +00:00:

intel-chipset-inf has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/e5fba6517bbcab9ecf1e90dc2ec2cbac for details.
The package status will be changed and will be waiting on your next actions.

NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey-community/chocolatey-test-environment
Please log in and leave a review comment if you have questions and/or comments.
If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

muddy1 (maintainer) on 31 Mar 2025 00:26:35 +00:00:

User 'muddy1' (maintainer) submitted package.

chocolatey-ops (reviewer) on 31 Mar 2025 00:58:22 +00:00:

Suggestions

The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
- docsUrl - points to the location of the wiki or docs of the software
- mailingListUrl - points to the forum or email list group for the software
- bugTrackerUrl - points to the location where issues and tickets can be accessed
- projectSourceUrl - points to the location of the underlying software source

Notes

The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...
Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...
The IconUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...

chocolatey-ops (reviewer) on 31 Mar 2025 02:10:31 +00:00:

intel-chipset-inf has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/21dc56af4bd420c7fcf6d8668b4efa5e for details.
The package status will be changed and will be waiting on your next actions.

NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey-community/chocolatey-test-environment
Please log in and leave a review comment if you have questions and/or comments.
If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

muddy1 (maintainer) on 06 Apr 2025 01:23:45 +00:00:

User 'muddy1' (maintainer) submitted package.

chocolatey-ops (reviewer) on 06 Apr 2025 01:58:28 +00:00:

Notes

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

chocolatey-ops (reviewer) on 06 Apr 2025 05:23:13 +00:00:

intel-chipset-inf has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/2058eba810bf64d50b0d2295f6f5850c for details.
The package status will be changed and will be waiting on your next actions.

NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey-community/chocolatey-test-environment
Please log in and leave a review comment if you have questions and/or comments.
If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

muddy1 (maintainer) on 23 Apr 2025 07:41:41 +00:00:

User 'muddy1' (maintainer) submitted package.

chocolatey-ops (reviewer) on 23 Apr 2025 08:16:19 +00:00:

Notes

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

chocolatey-ops (reviewer) on 23 Apr 2025 10:54:40 +00:00:

intel-chipset-inf has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/947e4f0db7ce64a335ef49e750d7cae5 for details.
The package status will be changed and will be waiting on your next actions.

NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey-community/chocolatey-test-environment
Please log in and leave a review comment if you have questions and/or comments.
If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

Description

The Intel Chipset Device Software installs the Windows* INF files. An INF is a text file that provides the operating system with information about a piece of hardware on the system. In the case of the current Intel Chipset Device Software, that information is primarily the product name for the piece of hardware. This allows the operating system to show the correct name for that piece of hardware in Device Manager.

Files

tools\chocolateyinstall.ps1


$ErrorActionPreference = 'Stop'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$fileLocation = Join-Path $toolsDir 'SetupChipset.exe'

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = $toolsDir
  fileType      = 'EXE'
  file         = $fileLocation

  softwareName  = 'intel-inf-utility*'

  checksum      = '6CDDEEAFC32607FF914FD6038E475BF876E55804A9F759ECA773E5EA144AF481'
  checksumType  = 'sha256'

  silentArgs    = "-s -norestart"
  validExitCodes= @(0, 3010, 1641)
}

Install-ChocolateyInstallPackage @packageArgs

# Remove the installers as there is no more need for it
Remove-Item $toolsDir\*.exe -ea 0 -Force

tools\LICENSE.txt

From: https://cdrdv2-public.intel.com/840386/intel-eula--distribution-only-.pdf

LICENSE

EXHIBIT “A”
INTEL SOFTWARE LICENSE AGREEMENT
(Final, Single User)
IMPORTANT - READ BEFORE COPYING, INSTALLING OR USING.
Do not use or load software from this site or any associated materials (collectively, the
"Software") until you have carefully read the following terms and conditions. By loading
or using the Software, you agree to the terms of this Agreement. If you do not wish to so
agree, do not install or use the Software.
LICENSE. You may copy the Software onto a single computer for your personal, or
internal business purpose use, and you may make one back-up copy of the Software,
subject to these conditions:
• You may not copy, modify, rent, sell, distribute or transfer any part of the
Software except as provided in this Agreement, and you agree to prevent
unauthorized copying of the Software.
• You may not reverse engineer, decompile, or disassemble the Software.
• You may not sublicense or permit simultaneous use of the Software by more
than one user.
• The Software may contain the software or other property of third party
suppliers, some of which may be identified in, and licensed in accordance with,
any enclosed “license.txt” file or other text or file.
OWNERSHIP OF SOFTWARE AND COPYRIGHTS. Title to all copies of the Software
remains with Intel or its suppliers. The Software is copyrighted and protected by the
laws of the United States and other countries, and international treaty provisions. You
may not remove any copyright notices from the Software. Intel may make changes to the
Software, or to items referenced therein, at any time without notice, but is not obligated
to support or update the Software. Except as otherwise expressly provided, Intel grants
no express or implied right under Intel patents, copyrights, trademarks, or other
intellectual property rights. You may transfer the Software only if the recipient agrees to
be fully bound by these terms and if you retain no copies of the Software

tools\SetupChipset.exe

md5: F95C92A57AE541F973B84A25A5DC488C | sha1: 609D46F89AC706101E9265990680CD47566D06BD | sha256: 6CDDEEAFC32607FF914FD6038E475BF876E55804A9F759ECA773E5EA144AF481 | sha512: 2518F72CCDD37DCD3D093AF02CD39BC8078C65DE1532275DBB8106677EB8809BD51D95DB2F9A6483D0C1AAA4123BCE1044E484F114F147A3C1CAA579335B6D6F

tools\VERIFICATION.txt

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

<Include details of how to verify checksum contents>
Details on how to verify the checksum are provided by intel corp. on the softwares download page: 
https://www.intel.com/content/www/us/en/download/19347/chipset-inf-utility.html, also, you can use the
command in powershell Get-FileHash -Path "C:\path\to\your\file.txt" -Algorithm SHA256 (replace "C:\path\to\your\file.txt" with the actual file path)

Virus Scan Results

No results available for this package. We are building up results for older packages over time so expect to see results. If this is a new package, it should have results within a day or two.

Version History

Add to Builder	Version	Downloads	Last Updated	Status
	Chipset INF Utility 10.1.20020.8623	48	Wednesday, April 23, 2025	Waiting for Maintainer

Release Notes

Note: The Intel Chipset Device Software does not install drivers for AGP or USB. Do not download this utility if your device manufacturer is recommending it to correct an "AGP driver," "AGP GART," or "USB driver" issue; it will not correct your issue.

Supported operating systems:

Microsoft Windows Server 2012 R2 x64

Microsoft Windows 10

Microsoft Windows 10 x64

Microsoft Windows 11 x64

Microsoft Windows Server 2016 x64

Microsoft Windows Server 2019 x64

Microsoft Windows Server 2022 x64

Microsoft Windows Server 2025 x64

Keywords: 82801, ICH, MCH, chipset

About Intel® drivers

The driver or software for your Intel® component might have been changed or replaced by the computer manufacturer. We recommend you work with your computer manufacturer before installing our driver so you don’t lose features or customizations.

See list of manufacturers’ Support websites.
This download is valid for the product(s) listed below.

Intel® H170 Chipset
Mobile Intel® HM175 Chipset
Intel® B150 Chipset
Intel® Q170 Chipset
Mobile Intel® QM170 Chipset
Intel® Q150 Chipset
Intel® H310 Chipset
Intel® H110 Chipset
Mobile Intel® HM170 Chipset
Mobile Intel® QM175 Chipset
Intel® Z170 Chipset

Dependencies

This package has no dependencies.

Discussion for the Chipset INF Utility Package

Ground Rules:

This discussion is only about Chipset INF Utility and the Chipset INF Utility 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 Chipset INF Utility, 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

48

48

23 Apr 2025

23 Apr 2025

Chipset INF Utility

Chipset INF Utility 10.1.20020.8623

(Waiting for Maintainer to take corrective action)

Some Checks Have Failed or Are Not Yet Complete

muddy1 (maintainer) on 27 Feb 2025 08:31:24 +00:00:

muddy1 (maintainer) on 27 Feb 2025 08:54:37 +00:00:

chocolatey-ops (reviewer) on 27 Feb 2025 09:26:10 +00:00:

Requirements

Guidelines

Suggestions

Notes

muddy1 (maintainer) on 27 Feb 2025 09:34:40 +00:00:

muddy1 (maintainer) on 27 Feb 2025 09:36:27 +00:00:

chocolatey-ops (reviewer) on 27 Feb 2025 10:11:19 +00:00:

Requirements

Guidelines

Suggestions

Notes

muddy1 (maintainer) on 27 Feb 2025 10:22:38 +00:00:

chocolatey-ops (reviewer) on 27 Feb 2025 10:56:23 +00:00:

Guidelines

Suggestions

Notes

chocolatey-ops (reviewer) on 27 Feb 2025 12:30:12 +00:00:

muddy1 (maintainer) on 27 Feb 2025 12:47:26 +00:00:

muddy1 (maintainer) on 27 Feb 2025 13:00:26 +00:00:

muddy1 (maintainer) on 27 Feb 2025 16:14:03 +00:00:

muddy1 (maintainer) on 01 Mar 2025 00:21:49 +00:00:

muddy1 (maintainer) on 05 Mar 2025 01:09:25 +00:00:

chocolatey-ops (reviewer) on 05 Mar 2025 01:41:29 +00:00:

Guidelines

Suggestions

Notes

chocolatey-ops (reviewer) on 05 Mar 2025 04:43:34 +00:00:

chocolatey-ops (reviewer) on 25 Mar 2025 01:43:41 +00:00:

muddy1 (maintainer) on 30 Mar 2025 20:14:06 +00:00:

muddy1 (maintainer) on 30 Mar 2025 23:45:35 +00:00:

chocolatey-ops (reviewer) on 31 Mar 2025 00:21:15 +00:00:

Guidelines

Suggestions

Notes

chocolatey-ops (reviewer) on 31 Mar 2025 00:25:39 +00:00:

muddy1 (maintainer) on 31 Mar 2025 00:26:35 +00:00:

chocolatey-ops (reviewer) on 31 Mar 2025 00:58:22 +00:00:

Suggestions

Notes

chocolatey-ops (reviewer) on 31 Mar 2025 02:10:31 +00:00:

muddy1 (maintainer) on 06 Apr 2025 01:23:45 +00:00:

chocolatey-ops (reviewer) on 06 Apr 2025 01:58:28 +00:00:

Notes

chocolatey-ops (reviewer) on 06 Apr 2025 05:23:13 +00:00:

muddy1 (maintainer) on 23 Apr 2025 07:41:41 +00:00:

chocolatey-ops (reviewer) on 23 Apr 2025 08:16:19 +00:00:

Notes

chocolatey-ops (reviewer) on 23 Apr 2025 10:54:40 +00:00:

Ground Rules: