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

217,613

Downloads of v 1.30.14:

15

Last Update:

02 Oct 2024

Package Maintainer(s):

majkinetor

Software Author(s):

Nir Sofer

Tags:

utility tools admin freeware system nirsoft

NirLauncher

Downloads:

217,613

Downloads of v 1.30.14:

Maintainer(s):

majkinetor

Software Author(s):

Nir Sofer

Tags:

utility tools admin freeware system nirsoft

NirLauncher

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

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Resulted in Flagged as an Error:

At least one file within this package has greater than 10 detections

Details

WARNING

This package was rejected on 06 Nov 2024. The reviewer chocolatey-ops has listed the following reason(s):

majkinetor (maintainer) on 02 Oct 2024 15:03:08 +00:00:

User 'majkinetor' (maintainer) submitted package.

chocolatey-ops (reviewer) on 02 Oct 2024 15:36:20 +00:00:

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

Guidelines

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

The licenseUrl should not usually be an exact match to softwareUrl. Please correct this in the nuspec, if applicable. 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.

Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...
The package takes a dependency on Chocolatey. The reviewer will ensure the package uses a specific Chocolatey feature that requires a minimum version. More...

chocolatey-ops (reviewer) on 02 Oct 2024 15:39:40 +00:00:

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

chocolatey-ops (reviewer) on 02 Oct 2024 15:56:43 +00:00:

nirlauncher has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has greater than 10 VirusTotal detections associated with it.
This package is now in a waiting state while you review the findings and provide an updated package, or send a message in the package review box on the package page.

chocolatey-ops (reviewer) on 22 Oct 2024 15:38:48 +00:00:

We've found nirlauncher v1.30.14 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.

chocolatey-ops (reviewer) on 06 Nov 2024 15:43:18 +00:00:

Unfortunately there has not been progress to move nirlauncher v1.30.14 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.

Description

NirLauncher is a package of more than 180 portable freeware utilities for Windows, all of them developed by NirSoft.

Features

NirLauncher can be used from USB flash drive without need of any installation.
NirLauncher and all the utilities in the package are completely freeware, without any Spyware/Adware/Malware. This package doesn't contain any 3-party software, toolbars, Web browser plugins, or other unwanted surprises. It will not install any software on your system and it will not change your Web browser homepage or other settings on your system.
NirLauncher package includes variety of tools that you may need for your daily computer use, including utilities to recover lost passwords, to monitor your network, to view and extract cookies, cache, and other information stored by your Web browser, to search files in your system, and more...
For every utility in the package, you can easily run it, view the help file, or jump to the Web page of the utility.
When using it from USB flash drive, the configuration of every utility is saved into .cfg file on the flash drive.
On x64 systems, NirLauncher automatically run the x64 version of the utility, when there is a separated x64 version
NirLauncher also allows to add more software packages in additional to the main NirSoft package.
NirLauncher allows you generate plugin files for BartPE (Launcher -> Generate BartPE Plugin Files), so you can easily use the utilities of NirSoft from a bootable live windows CD.

Package Parameters

/Sysinternals - Add sysinternals tools to the launcher if chocolatey package sysinternals is already installed.

Notes

Many Antivirus programs display false alerts, saying that the password-recovery utilities of NirSoft are infected with Trojan/Virus/Malware. For more information about false positive problems, read this. If your Antivirus software shows a false alert, you can use the following article that explains how to send a report about a false positive issue to your Antivirus company:
How to Report Malware or False Positives to Multiple Antivirus Vendors

Files

tools\chocolateyInstall.ps1

$ErrorActionPreference = 'Stop'

$toolsDir = Split-Path $MyInvocation.MyCommand.Definition
$is64 = (Get-ProcessorBits 64) -and $env:chocolateyForceX86 -ne 'true'
$install_path  = "$(Get-ToolsLocation)\NirLauncher"

$packageArgs = @{
    PackageName    = 'nirlauncher'
    FileFullPath   = gi $toolsDir\*.zip
    FileFullPath64 = gi $toolsDir\*.zip
    Destination    = $install_path
}
Get-ChocolateyUnzip @packageArgs
rm $toolsDir\*.zip -ea 0

if ($is64) {
    Write-Host '64 bit architecture - overwriting x32 apps with x64 versions'
    mv $install_path\Nirsoft\x64\* $install_path\Nirsoft -force
    rm $install_path\Nirsoft\x64 -ea 0
}
Install-ChocolateyPath $install_path\Nirsoft "Machine"

$launcher_path = "$install_path\$packageName.exe"
Register-Application $launcher_path
Write-Host "$packageName registered as $packageName"

Install-BinFile $packageName $launcher_path

$pp = Get-PackageParameters
if ($pp.SysInternals) {
    Write-Host 'SysInternals utilities will be added'

    $sysinternals_dir = gcm autoruns.exe -ea 0 | select -Expand Source | Split-Path
    if (!$sysinternals_dir) { Write-Warning 'Sysinternals tools are not on the PATH'; return }

    mv $toolsDir\sysinternals6.nlp $sysinternals_dir -Force

    #Configure nirlauncher
    $nircfg = gc $install_path\NirLauncher.cfg -Raw
    if ($nircfg -notmatch '\[Package1\]') {
        $nircfg = $nircfg.Replace("PackageCount=1", "PackageCount=2")
        $nircfg += "[Package1]`nfilename=$sysinternals_dir\sysinternals6.nlp"
        $nircfg | Out-File $install_path\NirLauncher.cfg -Encoding ascii
    }
}

tools\chocolateyUninstall.ps1

$ErrorActionPreference = 'Stop'

$packageName  = 'nirlauncher'
$install_path = "$(Get-ToolsLocation)\NirLauncher"

Write-Host "Removing $packageName from the '$install_path'"
rm $install_path -Recurse -Force -ea 0

$new_path = $Env:Path.Replace(";$install_path\Nirsoft", '')
if ($new_path -eq $Env:PATH) { return }
Write-Host "Removing $packageName from system PATH"
[System.Environment]::SetEnvironmentVariable('PATH', $new_path, 'Machine')

Write-Host "Removing $packageName shim"
Uninstall-BinFile $packageName

tools\nirsoft_package_1.30.14.zip

md5: B75901427E6598E3A9814590A19423A7 | sha1: 82D8E7DF35674D49C47C4C74E0BCCCF7E4C5CD5E | sha256: 9732B51024F8233CC041EC21EBC7B11AEE5D125039836CB838A6E93504C273C6 | sha512: 02C3DAFD8E08FEC9967E5AB80EB50F1CAA4DE0DC6F0BD55E4BA985C2700A70673358597E353739F1EEED358F125C90E2F6DB3AA4FCE7B9CB4AF45FEE92B03AAA

tools\sysinternals6.nlp

legal\VERIFICATION.txt

VERIFICATION

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

Package can be verified like this:

1. Go to http://launcher.nirsoft.net/downloads/index.html to download the zip file:

   x32: https://download.nirsoft.net/nirsoft_package_enc_1.30.14.zip

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

   checksum32: 

File 'redistribution.pdf' presents written approval from Nir Softer that allows software
redistribution

legal\redistribution.pdf

md5: C16CDC15904321E23589615DDEC134DA | sha1: C5B5E5562175365FD07FEFE69C431DFD1CECB847 | sha256: 67E2512995EBCFFF9F36CE87750958E836CF187B887B6718E094EF1DFDC54BF6 | sha512: A69B2466535356ABC78EEE0D4C4ABB57FA979C4A3F3EC1F3A8DA616C4ACE9F48663B9AEFCF861A6F4E52A86E0A97FF52191774350D958088B8169D40ED5E759A

legal\License.txt

This utilities package is released as freeware, which means that you can freely use it at your home or in your company.
The only exception is NK2Edit utility, which requires to purchase a commercial license if you use it in a company/business organization.
Disclaimer: The software package is provided "AS IS" without any warranty, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The author will not be liable for any special, incidental, consequential or indirect damages due to loss of data or any other reason.

Virus Scan Results

livecontactsview.exe (62160c59d186) - ## / 73
officeins.exe (a9440c1eb0fe) - ## / 56
officeins.exe (6845e843f392) - ## / 73
sniffpass.exe (c92580318be4) - ## / 72
userprofilesview.exe (0b9c04da6fb9) - ## / 63
altstreamdump.exe (54939b60003d) - ## / 74
awatch.exe (556124fe0767) - ## / 72
axhelper.exe (22279965263d) - ## / 74
bluescreenview.exe (f5f52ec9c38e) - ## / 71
bluetoothcl.exe (cb98e5060dcf) - ## / 73
cprocess.exe (f0cf25602f19) - ## / 74
ctie.exe (5b903d6efc2e) - ## / 71
customexplorertoolbar.exe (9d42469f4691) - ## / 73
dotnetresourcesextract.exe (381bfc1b1b50) - ## / 49
downtester.exe (74c2aa066141) - ## / 74
eventlogsourcesview.exe (22a7eb0b912b) - ## / 74
fastresolver.exe (1fcfc602fb5c) - ## / 74
faview.exe (a68fae179a57) - ## / 73
flashcookiesview.exe (e9f9bea54333) - ## / 73
heapmemview.exe (1296d8731ad8) - ## / 73
htmlastext.exe (42624eb45a96) - ## / 73
htmldocedit.exe (a8ab1365b04a) - ## / 72
iconsext.exe (e22afd680ce7) - ## / 72
installedcodec.exe (ca54c5bda1ce) - ## / 73
mmcsnapinsview.exe (8026dcd96e0a) - ## / 74
muicacheview.exe (02e28fa84912) - ## / 72
netresview.exe (83f0352c14fa) - ## / 72
openwithview.exe (6358b2d02131) - ## / 72
operacacheview.exe (3102c6953187) - ## / 71
pcanypass.exe (0db918e61645) - ## / 73
processactivityview.exe (b918db8655b5) - ## / 63
regdllview.exe (9938f8bcc502) - ## / 72
regfromapp.exe (2a1a4ec3b52b) - ## / 64
resourcesextract.exe (c9b93aa5d45f) - ## / 71
safaricacheview.exe (bd8a13430ace) - ## / 74
safarihistoryview.exe (231fd04cbe98) - ## / 75
searchfilterview.exe (0749e8e0b169) - ## / 72
securitysoftview.exe (a54e3494461d) - ## / 73
seqdownload.exe (e09d4a718e26) - ## / 72
shellmenunew.exe (c47485958a03) - ## / 74
shman.exe (82c6e2c666a5) - ## / 72
siteshoter.exe (eefdef80e5a5) - ## / 70
skypecontactsview.exe (6bafeab61149) - ## / 72
skypelogview.exe (b2af144ca1c3) - ## / 67
socketsniff.exe (ecb44a44ff92) - ## / 72
specialfoldersview.exe (315fdb91b17d) - ## / 72
tabletextcompare.exe (44109d47dffb) - ## / 57
urlprotocolview.exe (34cbe52cc935) - ## / 73
urlstringgrabber.exe (e4a17446c490) - ## / 57
userassistview.exe (bc11c4150bbc) - ## / 72
vlmshlp32.dll (2f32e2aed465) - ## / 71
webcamimagesave.exe (5e3f311ae67f) - ## / 75
webvideocap.exe (266283fce7ef) - ## / 72
whatinstartup.exe (7d8e7090d530) - ## / 69
whatishang.exe (fc4e9f5abccf) - ## / 73
winfontsview.exe (1e25fa572959) - ## / 72
winsockservicesview.exe (7abaa3b7753d) - ## / 74
wirelessnetconsole.exe (49279441e70a) - ## / 72
bluescreenview.exe (09f3023554be) - ## / 73
eventlogsourcesview.exe (fb821854d62b) - ## / 72
heapmemview.exe (4ceb3cadc9ab) - ## / 73
installedcodec.exe (d194ddb62b97) - ## / 72
mmcsnapinsview.exe (fd769b5b165c) - ## / 73
processactivityview.exe (5709f63fbc11) - ## / 75
regdllview.exe (52d52b59561c) - ## / 73
regfromapp.exe (a74583103234) - ## / 73
resourcesextract.exe (a718da8b2a11) - ## / 73
shman.exe (e15f5060b60e) - ## / 72
specialfoldersview.exe (9911e0e65221) - ## / 74
vlmshlp.dll (32ad4153f601) - ## / 73
volumouse32.exe (02448530591c) - ## / 66
whatinstartup.exe (15099976118e) - ## / 73
whatishang.exe (e2095dbe5ff7) - ## / 49
executedprogramslist.exe (e3af98717bf1) - ## / 72
deviceioview.exe (f02bf17765ec) - ## / 73
deviceioview.exe (5794412bac7a) - ## / 72
winlister.exe (1659abf390ba) - ## / 72
winlister.exe (805b4fbf4243) - ## / 75
iecacheview.exe (9dd1f1f24504) - ## / 72
disksmartview.exe (95473d0f0962) - ## / 72
wincrashreport.exe (6638857a3bf1) - ## / 72
wincrashreport.exe (edd9545c53eb) - ## / 72
netbscanner.exe (5906fd255354) - ## / 73
dllexp.exe (721c14e33253) - ## / 73
dllexp.exe (95d32211101d) - ## / 72
bluetoothlogview.exe (ef93532a5984) - ## / 72
myeventviewer.exe (4ebfebb9e3ff) - ## / 74
myeventviewer.exe (c53a642daf25) - ## / 70
whosip.exe (9428a8adb02b) - ## / 72
recentfilesview.exe (80930766283e) - ## / 72
gdiview.exe (0a4087860904) - ## / 73
hostednetworkstarter.exe (145944e86a8b) - ## / 54
iecv.exe (a31884195978) - ## / 72
websitesniffer.exe (050860cbf00e) - ## / 72
wul.exe (d358d76123a8) - ## / 73
gdiview.exe (c49560f7a206) - ## / 74
websitesniffer.exe (8dba456d2bc6) - ## / 70
mylastsearch.exe (4df8c8d545bc) - ## / 59
wirelessnetview.exe (637175bedfe6) - ## / 72
timezonesview.exe (a016b037465a) - ## / 68
rtmpdumphelper.dll (0ebb99b02ef8) - ## / 74
rtmpdumphelper.exe (fcd343f9c0e9) - ## / 72
rtmpdumphelper.dll (d007a03b365f) - ## / 71
rtmpdumphelper.exe (5a9a5ae74132) - ## / 72
jumplistsview.exe (e000c782af98) - ## / 72
allthreadsview.exe (6844bdd7053c) - ## / 73
keyboardstateview.exe (1116994b5c9d) - ## / 71
allthreadsview.exe (80e5b10cc808) - ## / 71
processthreadsview.exe (594aa3792253) - ## / 71
processthreadsview.exe (0cb3de81ae06) - ## / 72
webcookiessniffer.exe (c32395da6d53) - ## / 73
webcookiessniffer.exe (849a391f2c18) - ## / 73
dumpedid.exe (0dc5001fafe0) - ## / 74
shexview.exe (5a9a0dad900f) - ## / 71
appcrashview.exe (a192607d63ff) - ## / 72
domainhostingview.exe (b55e38fc187a) - ## / 72
driveletterview.exe (e2d669740b5c) - ## / 72
edgecookiesview.exe (4182172a01bd) - ## / 72
firefoxdownloadsview.exe (cbea3de43767) - ## / 66
ipnetinfo.exe (ace852841d33) - ## / 73
offlineregistryfinder.exe (45a54aa4b80b) - ## / 72
offlineregistryview.exe (caca5f45af84) - ## / 74
regfileexport.exe (f31d8aedef1e) - ## / 74
shmnview.exe (ea62591b32fd) - ## / 68
sysexp.exe (5154ea9ea77c) - ## / 72
usblogview.exe (31eb4115e6a2) - ## / 70
whoiscl.exe (8a3ce3ab0288) - ## / 74
driveletterview.exe (4e33971633fa) - ## / 66
offlineregistryfinder.exe (9f631112a057) - ## / 72
offlineregistryview.exe (6011b7720954) - ## / 71
shexview.exe (c388af0018fa) - ## / 71
shmnview.exe (681d9d7a1793) - ## / 72
sysexp.exe (ba0d713bfe31) - ## / 73
monitorinfoview.exe (0db2b22c22de) - ## / 73
getnir.exe (dcace777ff9c) - ## / 72
hotkeyslist.exe (2ea40420fc11) - ## / 75
previousfilesrecovery.exe (e2542db31446) - ## / 74
securityquestionsview.exe (3af3f78d6c67) - ## / 73
previousfilesrecovery.exe (2c749ebe67bf) - ## / 53
passwordfox.exe (ce4204f78177) - ## / 73
routerpassview.exe (3ee00a42a65d) - ## / 73
turnedontimesview.exe (52237230f3de) - ## / 72
winlogonview.exe (f2f89b701f30) - ## / 72
wifichannelmonitor.exe (5373a3e7fd87) - ## / 72
wifichannelmonitor.exe (920322d57aea) - ## / 75
appaudioconfig.exe (6eaa5e6a9ec9) - ## / 73
winprefetchview.exe (92bd85148a9b) - ## / 73
appaudioconfig.exe (8691580b678e) - ## / 75
winprefetchview.exe (ccde97bb6fc5) - ## / 72
fbcacheview.exe (8672f8aecf21) - ## / 70
advancedrun.exe (e8000766c215) - ## / 73
advancedrun.exe (dfe303b38ff0) - ## / 73
simpleprogramdebugger.exe (50c1602f6ed3) - ## / 74
simpleprogramdebugger.exe (9837b28a68ac) - ## / 72
appcompatibilityview.exe (f2f0b7dc79d4) - ## / 73
batteryinfoview.exe (8dffb52b6826) - ## / 73
diskcountersview.exe (2b2572fc3f45) - ## / 74
exifdataview.exe (d39edf185cf2) - ## / 73
firmwaretablesview.exe (1ec77f761a1c) - ## / 72
freespacelogview.exe (5dd9e262e00d) - ## / 72
ippathtableview.exe (dc4e44b8afe5) - ## / 73
loadeddllsview.exe (10f1df31e159) - ## / 72
madpassext.exe (a0a0c256070d) - ## / 72
mozillahistoryview.exe (b38d79eed498) - ## / 71
mzcacheview.exe (a5fd1f60604e) - ## / 73
mzcv.exe (72101fa019e4) - ## / 72
networkcounterswatch.exe (296c6ccc39fa) - ## / 73
runasdate.exe (2361dd3272c2) - ## / 72
runfromprocess.exe (78defb3da589) - ## / 73
runtimeclassesview.exe (d0e6cc4c3193) - ## / 74
whoisconnectedsniffer.exe (df728cce1a0a) - ## / 72
whoistd.exe (1f9993adf561) - ## / 67
appcompatibilityview.exe (76ef4a2185d4) - ## / 73
firmwaretablesview.exe (2338b665b0c0) - ## / 72
loadeddllsview.exe (9258437c6dc7) - ## / 73
mozillahistoryview.exe (3770792f203f) - ## / 75
mzcv.exe (0fbcaa65ada3) - ## / 72
runasdate.exe (0a6696db24b9) - ## / 72
runfromprocess.exe (06faa3dcf4be) - ## / 72
whoisconnectedsniffer.exe (0c2ecdf4ffa4) - ## / 75
chromepass.exe (744e50af5566) - ## / 72
netconnectchoose.exe (f8340aa34f24) - ## / 74
netrouteview.exe (0e2f08388ad5) - ## / 71
opensavefilesview.exe (c3837895e57a) - ## / 72
webbrowserpassview.exe (72c3a786661e) - ## / 73
opensavefilesview.exe (fa7484f83ff1) - ## / 72
alternatestreamview.exe (b4ab692d4d2f) - ## / 72
appresourcesusageview.exe (168b659afa18) - ## / 73
macaddressview.exe (a63d0ee0ff39) - ## / 71
propertysystemview.exe (82a7169b3688) - ## / 73
serviwin.exe (995647fc2bfd) - ## / 72
alternatestreamview.exe (c1260caebaf1) - ## / 72
propertysystemview.exe (7b7fd031bc60) - ## / 74
serviwin.exe (526c30e3c157) - ## / 74
NirLauncher.exe (ed8b14d0a38d) - ## / 75
batteryhistoryview.exe (a125d9b3fca4) - ## / 69
lastactivityview.exe (af86dc3f76d3) - ## / 73
csvfileview.exe (f19ae1c181e8) - ## / 74
ipinfooffline.exe (0562864a8e3d) - ## / 67
wakemeonlan.exe (7fd931caa2da) - ## / 72
csvfileview.exe (e6e88dd67f5b) - ## / 72
wakemeonlan.exe (1b63386203aa) - ## / 72
shellbagsview.exe (624a01ed209f) - ## / 70
esedatabaseview.exe (698bddd350c3) - ## / 72
fileaccesserrorview.exe (73fd7fc97a6b) - ## / 68
foldertimeupdate.exe (1daa230905d4) - ## / 72
hashmyfiles.exe (bc7fc5a37dea) - ## / 65
networklatencyview.exe (9397af6b1add) - ## / 74
networktrafficview.exe (075348701709) - ## / 73
simplewmiview.exe (71dbda32eabe) - ## / 74
fileaccesserrorview.exe (43f73b86472d) - ## / 73
foldertimeupdate.exe (072c0be38eb5) - ## / 73
hashmyfiles.exe (e5c52ba341c9) - ## / 72
networklatencyview.exe (91594f5614f6) - ## / 73
networktrafficview.exe (1a25def5b220) - ## / 74
simplewmiview.exe (411299b7e739) - ## / 74
usbdeview.exe (57f7cedd6bc0) - ## / 72
countrytraceroute.exe (7832ef1e72f3) - ## / 69
appnetworkcounter.exe (62d9f28017c7) - ## / 73
devmanview.exe (e94d1149e79d) - ## / 74
dnsquerysniffer.exe (3718db1601c2) - ## / 74
eventlogchannelsview.exe (b6a434f3eb0c) - ## / 73
fulleventlogview.exe (474120a35ec2) - ## / 73
networkinterfacesview.exe (34526b20e8d7) - ## / 73
nk2edit.exe (fa3db4a19ec7) - ## / 73
openedfilesview.exe (8e02aa6c8f97) - ## / 72
registrychangesview.exe (3fa12b5d8ecd) - ## / 74
taskschedulerview.exe (b009e49e0ded) - ## / 73
usbdeview.exe (d9c7c59bbcae) - ## / 73
appnetworkcounter.exe (4e6a4e0f26d4) - ## / 72
devmanview.exe (269f9c9a1175) - ## / 72
dnsquerysniffer.exe (909ff14dfb77) - ## / 73
eventlogchannelsview.exe (c012d0458dbd) - ## / 73
fulleventlogview.exe (85ae2c156efc) - ## / 73
networkinterfacesview.exe (d005bbe3d542) - ## / 68
nk2edit.exe (be17d4ec0044) - ## / 73
openedfilesview.exe (bfb1a374772c) - ## / 70
registrychangesview.exe (d19d94f65a68) - ## / 73
taskschedulerview.exe (43a522a7394b) - ## / 73
chromehistoryview.exe (2c1590d687a8) - ## / 72
dataprotectiondecryptor.exe (ece4b6572238) - ## / 73
encryptedregview.exe (16bc73e22944) - ## / 73
networkconnectlog.exe (dd108e4644a2) - ## / 74
outlookaccountsview.exe (1e42a5ca6361) - ## / 70
dataprotectiondecryptor.exe (a6bd012d21ea) - ## / 72
encryptedregview.exe (f04abf72c893) - ## / 74
outlookaccountsview.exe (a9583f6905e6) - ## / 73
browserautofillview.exe (70fd3e2fcc3d) - ## / 70
cports.exe (e11b891ff240) - ## / 72
credhistview.exe (928de47e95b4) - ## / 70
fileactivitywatch.exe (7d27f7fa5d0b) - ## / 71
shadowcopyview.exe (7acf01282d3f) - ## / 73
tcplogview.exe (0113c72d22dc) - ## / 72
vaultpasswordview.exe (804b33946058) - ## / 73
cports.exe (d99d31fe1b45) - ## / 73
credentialsfileview.exe (35296e7a3468) - ## / 73
fileactivitywatch.exe (2679847d7ccc) - ## / 73
shadowcopyview.exe (9580b6220da8) - ## / 73
tcplogview.exe (cf283e16797b) - ## / 73
vaultpasswordview.exe (fa017c2753e9) - ## / 73
lsasecretsview.exe (84e9812f5633) - ## / 73
chromecookiesview.exe (4bc07e630412) - ## / 71
filetypesman.exe (7bcc990dc612) - ## / 72
networkusageview.exe (b6da8766623a) - ## / 73
productkeyscanner.exe (07c1fdf10967) - ## / 74
soundvolumeview.exe (b0f1304ee6d9) - ## / 71
svcl.exe (9d08e0567dbb) - ## / 74
wifihistoryview.exe (46e2f18bcb38) - ## / 71
windefthreatsview.exe (41de5dc2d31d) - ## / 72
winmailpassrec.exe (fa54c838f8cd) - ## / 72
chromecookiesview.exe (5b992399231b) - ## / 72
filetypesman.exe (813e89e6b52c) - ## / 73
networkusageview.exe (f8d8a6ca14cd) - ## / 72
productkeyscanner.exe (dcccb2ff8bc0) - ## / 69
soundvolumeview.exe (c3c3bdcad854) - ## / 73
svcl.exe (0ca36daf962e) - ## / 73
windefthreatsview.exe (b1d1a1676a23) - ## / 73
winmailpassrec.exe (19744ec91e2a) - ## / 74
wnetwatcher.exe (83ed74e05c47) - ## / 72
bulkfilechanger.exe (6cefbb900ca6) - ## / 72
controlmymonitor.exe (edc247c58820) - ## / 72
installedpackagesview.exe (aaf9d8905748) - ## / 74
ipneighborsview.exe (d59ce724638e) - ## / 70
mweather.exe (d70000640e6d) - ## / 73
regscanner.exe (b07497d6a703) - ## / 72
usbdrivelog.exe (4b9b25784f9b) - ## / 73
windeflogview.exe (7f8bdda59a75) - ## / 73
bulkfilechanger.exe (147620199e9a) - ## / 73
installedpackagesview.exe (f63ae8939f67) - ## / 75
regscanner.exe (544e5be03c07) - ## / 73
nircmd.exe (2e81e048ab41) - ## / 72
nircmdc.exe (c3e28c6e201d) - ## / 73
nircmd.exe (cf29b37e1ff5) - ## / 72
nircmdc.exe (804e0e6d27a8) - ## / 71
appreadwritecounter.exe (602ea3dcbbab) - ## / 70
clipboardic.exe (fc6e735e879b) - ## / 72
guipropview.exe (2ec85e9c1124) - ## / 73
insideclipboard.exe (ea4e6c72c76f) - ## / 72
outlookaddressbookview.exe (52e61a0624cc) - ## / 73
outlookattachview.exe (97e2e15228c5) - ## / 74
outlookstatview.exe (a2d97c838c2a) - ## / 74
simplecodegenerator.exe (a920bb700dd0) - ## / 72
uninstallview.exe (bb3af210417a) - ## / 75
volumouse.exe (b57562bc2a37) - ## / 71
webbrowserbookmarksview.exe (06ad69b9beba) - ## / 74
appreadwritecounter.exe (2ecc6cf1128b) - ## / 72
guipropview.exe (776b7aa3e9b1) - ## / 74
outlookaddressbookview.exe (6f741f687ea1) - ## / 73
outlookattachview.exe (0d0c95fd3b05) - ## / 70
outlookstatview.exe (c31be328ba91) - ## / 74
uninstallview.exe (dcfe686df42f) - ## / 64
volumouse.exe (f3fac69a45a7) - ## / 69
searchmyfiles.exe (511ce6df223e) - ## / 73
searchmyfiles.exe (bff830e8aaff) - ## / 72
browseraddonsview.exe (49164153247a) - ## / 69
browserdownloadsview.exe (075e85b175e9) - ## / 72
dnsdataview.exe (c168f7cd820e) - ## / 72
driverview.exe (c5611a45ae08) - ## / 71
handlecountersview.exe (aeb39e55b985) - ## / 73
livetcpudpwatch.exe (bee74c5645ca) - ## / 73
managewirelessnetworks.exe (3343ef567e08) - ## / 73
mobilefilesearch.exe (d7b6b7a588d5) - ## / 74
networkopenedfiles.exe (16ed9421988a) - ## / 68
ntfslinksview.exe (c152de363e08) - ## / 73
pinginfoview.exe (189f54d59222) - ## / 71
processtcpsummary.exe (b40e13195ff8) - ## / 61
quicksetdns.exe (c6100f8a606d) - ## / 73
smsniff.exe (219f4c201f22) - ## / 72
tcpconnectproblemview.exe (d19e70944a4f) - ## / 72
wifidiagnosticsview.exe (5e746f61daea) - ## / 74
wirelessconnectioninfo.exe (25fd7a4a56d7) - ## / 75
browseraddonsview.exe (a3d8558b5c2f) - ## / 73
browserdownloadsview.exe (9e3f919e1e69) - ## / 73
driverview.exe (863a7072b728) - ## / 73
handlecountersview.exe (cbe3b360fdee) - ## / 72
livetcpudpwatch.exe (4898cbb73323) - ## / 67
mobilefilesearch.exe (8dd3a157caa7) - ## / 71
networkopenedfiles.exe (2c8687242a20) - ## / 75
ntfslinksview.exe (49e00833ee96) - ## / 73
processtcpsummary.exe (2e1fffc7073c) - ## / 69
smsniff.exe (25d88737a1d7) - ## / 73
multimonitortool.exe (2c40cd89e442) - ## / 73
multimonitortool.exe (46d9daca7666) - ## / 71
nirlauncher.1.30.14.nupkg (7e699241fb8c) - ## / 58
nirsoft_package_1.30.14.zip (9732b51024f8) - ## / 59
bluetoothview.exe (0918786d0c1a) - ## / 72
browsinghistoryview.exe (9a2963de8175) - ## / 72
chromecacheview.exe (9b0f572965a4) - ## / 71
dnslookupview.exe (f8d1d37f28fc) - ## / 73
folderchangesview.exe (9af1fa74841c) - ## / 73
imagecacheviewer.exe (c1eef9654af3) - ## / 72
installedappview.exe (7064c60aed92) - ## / 73
installeddriverslist.exe (472c75115b89) - ## / 72
videocacheview.exe (ee931ac67487) - ## / 71
webcacheimageinfo.exe (afe591286f4b) - ## / 72
wifiinfoview.exe (cd1f83f29ec0) - ## / 72
winupdatesview.exe (f9cbb7727222) - ## / 73
browsinghistoryview.exe (d442f9166e9b) - ## / 71
installedappview.exe (a4b389d306d4) - ## / 73
installeddriverslist.exe (df0063891fe8) - ## / 64
videocacheview.exe (a8ec57472a70) - ## / 73
wifiinfoview.exe (9a64fd52c619) - ## / 72
winupdatesview.exe (04b6f7863c8a) - ## / 72

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version History

Version	Downloads	Last Updated	Status
NirLauncher 1.30.5	12920	Saturday, August 26, 2023	Exempted
NirLauncher 1.30.4	1678	Tuesday, August 1, 2023	Exempted
NirLauncher 1.30.3	2394	Thursday, June 22, 2023	Exempted
NirLauncher 1.30.2	3172	Monday, May 1, 2023	Exempted
NirLauncher 1.23.66	8498	Monday, November 7, 2022	Exempted
NirLauncher 1.23.65	474	Sunday, October 16, 2022	Exempted
NirLauncher 1.23.56	11796	Monday, January 17, 2022	Exempted
NirLauncher 1.23.53	5487	Tuesday, October 26, 2021	Exempted
NirLauncher 1.23.52	88	Tuesday, October 5, 2021	Exempted
NirLauncher 1.23.44	8092	Tuesday, April 27, 2021	Approved
NirLauncher 1.23.43	1814	Tuesday, April 6, 2021	Approved
NirLauncher 1.23.42	1580	Tuesday, March 23, 2021	Approved
NirLauncher 1.23.41	1638	Tuesday, March 9, 2021	Approved
NirLauncher 1.23.40	1546	Tuesday, February 23, 2021	Approved
NirLauncher 1.23.39	1530	Tuesday, February 9, 2021	Approved
NirLauncher 1.23.38	1620	Tuesday, January 26, 2021	Approved
NirLauncher 1.23.37	1819	Tuesday, January 12, 2021	Approved
NirLauncher 1.23.36	3424	Tuesday, December 8, 2020	Approved
NirLauncher 1.23.35	2645	Tuesday, November 10, 2020	Approved
NirLauncher 1.23.34	1799	Tuesday, October 27, 2020	Approved
NirLauncher 1.23.33	1721	Tuesday, October 13, 2020	Approved
NirLauncher 1.23.32	1726	Tuesday, September 29, 2020	Approved
NirLauncher 1.23.31	1768	Tuesday, September 15, 2020	Approved
NirLauncher 1.23.30	1607	Tuesday, September 1, 2020	Approved
NirLauncher 1.23.28	2355	Tuesday, August 4, 2020	Approved
NirLauncher 1.23.27	1698	Monday, July 20, 2020	Approved
NirLauncher 1.23.26	142	Tuesday, July 7, 2020	Approved
NirLauncher 1.23.25	2263	Tuesday, June 23, 2020	Approved
NirLauncher 1.23.24	1701	Tuesday, June 9, 2020	Approved
NirLauncher 1.23.23	1054	Monday, June 1, 2020	Approved
NirLauncher 1.23.22	1463	Monday, May 18, 2020	Approved
NirLauncher 1.23.21	1195	Tuesday, May 12, 2020	Approved
NirLauncher 1.23.20	1095	Tuesday, May 5, 2020	Approved
NirLauncher 1.23.19	1082	Tuesday, April 28, 2020	Approved
NirLauncher 1.23.18	1728	Tuesday, April 14, 2020	Approved
NirLauncher 1.23.17	1685	Tuesday, March 31, 2020	Approved
NirLauncher 1.23.15	2540	Tuesday, March 3, 2020	Approved
NirLauncher 1.23.14	816	Tuesday, February 18, 2020	Approved
NirLauncher 1.23.13	737	Tuesday, February 11, 2020	Approved
NirLauncher 1.23.12	671	Tuesday, February 4, 2020	Approved
NirLauncher 1.23.11	616	Tuesday, January 28, 2020	Approved
NirLauncher 1.23.10	853	Tuesday, January 14, 2020	Approved
NirLauncher 1.23.9	805	Tuesday, December 31, 2019	Approved
NirLauncher 1.23.8	784	Tuesday, December 17, 2019	Approved
NirLauncher 1.23.7	803	Tuesday, December 3, 2019	Approved
NirLauncher 1.23.6	704	Monday, November 25, 2019	Approved
NirLauncher 1.23.5	679	Tuesday, November 19, 2019	Approved
NirLauncher 1.23.4	710	Tuesday, November 12, 2019	Approved
NirLauncher 1.23.3	629	Tuesday, November 5, 2019	Approved
NirLauncher 1.23.2	711	Tuesday, October 29, 2019	Approved
NirLauncher 1.23.1	867	Monday, October 14, 2019	Approved
NirLauncher 1.22.24	730	Monday, October 7, 2019	Approved
NirLauncher 1.22.23	583	Tuesday, October 1, 2019	Approved
NirLauncher 1.22.22	970	Thursday, September 12, 2019	Approved
NirLauncher 1.22.21	963	Tuesday, August 27, 2019	Approved
NirLauncher 1.22.20	892	Tuesday, August 6, 2019	Approved
NirLauncher 1.22.19	546	Tuesday, July 30, 2019	Approved
NirLauncher 1.22.18	577	Monday, July 22, 2019	Approved
NirLauncher 1.22.17	561	Tuesday, July 16, 2019	Approved
NirLauncher 1.22.16	586	Tuesday, July 9, 2019	Approved
NirLauncher 1.22.15	648	Tuesday, July 2, 2019	Approved
NirLauncher 1.22.14	583	Tuesday, June 25, 2019	Approved
NirLauncher 1.22.13	646	Tuesday, June 18, 2019	Approved
NirLauncher 1.22.12	589	Monday, June 10, 2019	Approved
NirLauncher 1.22.11	592	Tuesday, June 4, 2019	Approved
NirLauncher 1.22.10	547	Monday, May 27, 2019	Approved
NirLauncher 1.22.9	591	Monday, May 20, 2019	Approved
NirLauncher 1.22.8	564	Tuesday, May 14, 2019	Approved
NirLauncher 1.22.7	535	Tuesday, May 7, 2019	Approved
NirLauncher 1.22.6	547	Wednesday, May 1, 2019	Approved
NirLauncher 1.22.5	677	Tuesday, April 23, 2019	Approved
NirLauncher 1.22.4	623	Tuesday, April 16, 2019	Approved
NirLauncher 1.22.3	565	Thursday, April 11, 2019	Approved
NirLauncher 1.22.2	708	Tuesday, April 2, 2019	Approved
NirLauncher 1.22.1	672	Tuesday, March 26, 2019	Approved
NirLauncher 1.21.2	625	Wednesday, March 20, 2019	Approved
NirLauncher 1.20.76	772	Monday, March 11, 2019	Approved
NirLauncher 1.20.75	816	Tuesday, February 26, 2019	Approved
NirLauncher 1.20.74	715	Monday, February 18, 2019	Approved
NirLauncher 1.20.73	614	Tuesday, February 12, 2019	Approved
NirLauncher 1.20.72	630	Monday, February 4, 2019	Approved
NirLauncher 1.20.71	586	Wednesday, January 30, 2019	Approved
NirLauncher 1.20.70	683	Monday, January 21, 2019	Approved
NirLauncher 1.20.69	566	Wednesday, January 16, 2019	Approved
NirLauncher 1.20.68	603	Tuesday, January 8, 2019	Approved
NirLauncher 1.20.67	632	Tuesday, January 1, 2019	Approved
NirLauncher 1.20.66	585	Wednesday, December 26, 2018	Approved
NirLauncher 1.20.65	616	Wednesday, December 19, 2018	Approved
NirLauncher 1.20.64	728	Tuesday, December 11, 2018	Approved
NirLauncher 1.20.63	735	Tuesday, December 4, 2018	Approved
NirLauncher 1.20.62	593	Tuesday, November 27, 2018	Approved
NirLauncher 1.20.61	622	Monday, November 19, 2018	Approved
NirLauncher 1.20.60	593	Tuesday, November 13, 2018	Approved
NirLauncher 1.20.58	756	Tuesday, October 30, 2018	Approved
NirLauncher 1.20.57	780	Tuesday, October 16, 2018	Approved
NirLauncher 1.20.56	622	Tuesday, October 9, 2018	Approved
NirLauncher 1.20.55	604	Tuesday, October 2, 2018	Approved
NirLauncher 1.20.54	593	Tuesday, September 25, 2018	Approved
NirLauncher 1.20.53	595	Tuesday, September 18, 2018	Approved
NirLauncher 1.20.52	644	Tuesday, September 11, 2018	Approved
NirLauncher 1.20.51	599	Tuesday, September 4, 2018	Approved
NirLauncher 1.20.50	650	Monday, August 27, 2018	Approved
NirLauncher 1.20.49	589	Tuesday, August 21, 2018	Approved
NirLauncher 1.20.48	566	Tuesday, August 14, 2018	Approved
NirLauncher 1.20.47	899	Tuesday, July 31, 2018	Approved
NirLauncher 1.20.46	681	Tuesday, July 24, 2018	Approved
NirLauncher 1.20.45	753	Tuesday, July 10, 2018	Approved
NirLauncher 1.20.44	678	Tuesday, July 3, 2018	Approved
NirLauncher 1.20.43	572	Tuesday, June 26, 2018	Approved
NirLauncher 1.20.42	655	Tuesday, June 19, 2018	Approved
NirLauncher 1.20.41	619	Tuesday, June 12, 2018	Approved
NirLauncher 1.20.40	702	Tuesday, June 5, 2018	Approved
NirLauncher 1.20.39	776	Monday, May 21, 2018	Approved
NirLauncher 1.20.38	781	Tuesday, May 8, 2018	Approved
NirLauncher 1.20.37	698	Wednesday, April 25, 2018	Approved
NirLauncher 1.20.36	620	Tuesday, April 17, 2018	Approved
NirLauncher 1.20.35	925	Tuesday, April 3, 2018	Approved
NirLauncher 1.20.34	635	Monday, March 26, 2018	Approved
NirLauncher 1.20.33	742	Monday, March 19, 2018	Approved
NirLauncher 1.20.32	647	Tuesday, March 13, 2018	Approved
NirLauncher 1.20.31	541	Saturday, March 10, 2018	Approved
NirLauncher 1.20.27	1200	Sunday, January 21, 2018	Approved
NirLauncher 1.20.26	702	Tuesday, January 9, 2018	Approved
NirLauncher 1.20.25	631	Tuesday, January 2, 2018	Approved
NirLauncher 1.20.24	703	Tuesday, December 19, 2017	Approved
NirLauncher 1.20.23	650	Sunday, December 10, 2017	Approved
NirLauncher 1.20.22	570	Monday, December 4, 2017	Approved
NirLauncher 1.20.21	583	Tuesday, November 28, 2017	Approved
NirLauncher 1.20.20	695	Monday, November 20, 2017	Approved
NirLauncher 1.20.19	733	Tuesday, November 7, 2017	Approved
NirLauncher 1.20.18	613	Tuesday, October 31, 2017	Approved
NirLauncher 1.20.17	657	Monday, October 23, 2017	Approved
NirLauncher 1.20.16	645	Monday, October 16, 2017	Approved
NirLauncher 1.20.15	621	Sunday, October 8, 2017	Approved
NirLauncher 1.20.14	507	Thursday, October 5, 2017	Approved
NirLauncher 1.20.12	951	Monday, August 28, 2017	Approved
NirLauncher 1.20.11	662	Monday, August 14, 2017	Approved
NirLauncher 1.20.10	653	Monday, July 31, 2017	Approved
NirLauncher 1.20.9	572	Monday, July 24, 2017	Approved
NirLauncher 1.20.8	595	Monday, July 17, 2017	Approved
NirLauncher 1.20.7	593	Wednesday, July 5, 2017	Approved
NirLauncher 1.20.6	601	Monday, June 26, 2017	Approved
NirLauncher 1.20.5	661	Tuesday, June 13, 2017	Approved
NirLauncher 1.20.4	593	Monday, June 5, 2017	Approved
NirLauncher 1.20.3	570	Tuesday, May 30, 2017	Approved
NirLauncher 1.20.2	738	Monday, May 22, 2017	Approved
NirLauncher 1.20.1	604	Sunday, May 14, 2017	Approved
NirLauncher 1.19.121	601	Monday, May 8, 2017	Approved
NirLauncher 1.19.120	631	Sunday, April 23, 2017	Approved
NirLauncher 1.19.119	664	Sunday, April 9, 2017	Approved
NirLauncher 1.19.118	815	Saturday, March 11, 2017	Approved
NirLauncher 1.19.117	811	Sunday, February 19, 2017	Approved
NirLauncher 1.19.116	695	Tuesday, January 31, 2017	Approved
NirLauncher 1.19.115	622	Sunday, January 15, 2017	Approved
NirLauncher 1.19.114	680	Sunday, January 1, 2017	Approved
NirLauncher 1.19.113	641	Sunday, December 18, 2016	Approved
NirLauncher 1.19.112	633	Monday, December 5, 2016	Approved
NirLauncher 1.19.111	548	Thursday, November 24, 2016	Approved
NirLauncher 1.19.110	695	Tuesday, November 8, 2016	Approved
NirLauncher 1.19.109	500	Tuesday, November 1, 2016	Approved
NirLauncher 1.19.108	614	Tuesday, October 25, 2016	Approved
NirLauncher 1.19.107	540	Wednesday, October 19, 2016	Approved
NirLauncher 1.19.106	557	Tuesday, October 11, 2016	Approved
NirLauncher 1.19.105	453	Friday, October 7, 2016	Approved
NirLauncher 1.19.92	831	Tuesday, July 5, 2016	Approved
NirLauncher 1.19.91	406	Tuesday, June 21, 2016	Approved
NirLauncher 1.19.90	408	Monday, June 13, 2016	Approved
NirLauncher 1.19.89	418	Tuesday, June 7, 2016	Approved
NirLauncher 1.19.88	381	Tuesday, May 31, 2016	Approved
NirLauncher 1.19.87	363	Saturday, May 28, 2016	Approved
NirLauncher 1.19.86	327	Monday, May 16, 2016	Approved
NirLauncher 1.19.85	374	Monday, May 9, 2016	Approved
NirLauncher 1.19.84	444	Monday, May 2, 2016	Approved
NirLauncher 1.19.83	462	Monday, April 25, 2016	Approved
NirLauncher 1.19.82	486	Monday, April 18, 2016	Approved
NirLauncher 1.19.81	511	Tuesday, April 12, 2016	Approved
NirLauncher 1.19.80	423	Monday, April 11, 2016	Approved
NirLauncher 1.19.79.20160331	513	Thursday, March 31, 2016	Approved
NirLauncher 1.19.79	424	Thursday, March 31, 2016	Approved
NirLauncher 1.19.78	505	Tuesday, March 22, 2016	Approved
NirLauncher 1.19.77.20160315	494	Tuesday, March 15, 2016	Approved
NirLauncher 1.19.76	521	Monday, March 7, 2016	Approved
NirLauncher 1.19.75	503	Monday, February 29, 2016	Approved
NirLauncher 1.19.74	562	Tuesday, February 23, 2016	Approved
NirLauncher 1.19.73	499	Monday, February 15, 2016	Approved
NirLauncher 1.19.72	516	Wednesday, February 10, 2016	Approved
NirLauncher 1.19.71	489	Friday, February 5, 2016	Approved
NirLauncher 1.19.70	509	Monday, February 1, 2016	Approved
NirLauncher 1.19.69	553	Tuesday, January 19, 2016	Approved
NirLauncher 1.19.68	490	Tuesday, January 12, 2016	Approved
NirLauncher 1.19.67	465	Monday, January 4, 2016	Approved
NirLauncher 1.19.66	457	Wednesday, December 30, 2015	Approved
NirLauncher 1.19.65	496	Monday, December 21, 2015	Approved
NirLauncher 1.19.64	481	Tuesday, December 15, 2015	Approved
NirLauncher 1.19.63	464	Tuesday, December 8, 2015	Approved
NirLauncher 1.19.62	495	Tuesday, December 1, 2015	Approved
NirLauncher 1.19.61	477	Monday, November 23, 2015	Approved
NirLauncher 1.19.60	497	Tuesday, November 17, 2015	Approved
NirLauncher 1.19.59	443	Monday, November 9, 2015	Approved
NirLauncher 1.19.57	566	Tuesday, October 27, 2015	Approved
NirLauncher 1.19.56	482	Tuesday, October 20, 2015	Approved
NirLauncher 1.19.55	440	Wednesday, October 14, 2015	Approved
NirLauncher 1.19.54	482	Saturday, October 10, 2015	Approved
NirLauncher 1.19.53	497	Tuesday, September 29, 2015	Approved
NirLauncher 1.19.51	460	Thursday, September 17, 2015	Approved
NirLauncher 1.19.50	498	Tuesday, September 8, 2015	Approved
NirLauncher 1.19.49	459	Tuesday, September 1, 2015	Approved
NirLauncher 1.19.48	430	Tuesday, August 25, 2015	Approved
NirLauncher 1.19.47	432	Tuesday, August 18, 2015	Approved
NirLauncher 1.19.46	440	Tuesday, August 11, 2015	Approved
NirLauncher 1.19.44	473	Tuesday, July 28, 2015	Approved
NirLauncher 1.19.43	432	Tuesday, July 21, 2015	Approved
NirLauncher 1.19.42	454	Wednesday, July 15, 2015	Approved
NirLauncher 1.19.41	486	Tuesday, July 7, 2015	Approved
NirLauncher 1.19.40	402	Wednesday, July 1, 2015	Approved
NirLauncher 1.19.39	444	Tuesday, June 23, 2015	Approved
NirLauncher 1.19.38	442	Tuesday, June 16, 2015	Approved
NirLauncher 1.19.37	404	Tuesday, June 9, 2015	Approved
NirLauncher 1.19.36	459	Tuesday, June 2, 2015	Approved
NirLauncher 1.19.34	447	Wednesday, May 20, 2015	Approved
NirLauncher 1.19.33	469	Tuesday, May 12, 2015	Approved
NirLauncher 1.19.32	395	Friday, May 8, 2015	Approved
NirLauncher 1.19.31	425	Tuesday, April 28, 2015	Approved
NirLauncher 1.19.30	458	Monday, April 27, 2015	Approved
NirLauncher 1.19.29	477	Tuesday, April 14, 2015	Approved
NirLauncher 1.19.28	430	Wednesday, April 8, 2015	Approved
NirLauncher 1.19.27	414	Thursday, April 2, 2015	Approved

Release Notes

http://blog.nirsoft.net/?s=nirlauncher

Dependencies

- chocolatey (≥ 0.9.10)
- chocolatey-core.extension (≥ 1.3.3)

Discussion for the NirLauncher Package

Ground Rules:

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

217,613

15

02 Oct 2024

NirLauncher

NirLauncher

Some Checks Have Failed or Are Not Yet Complete

majkinetor (maintainer) on 02 Oct 2024 15:03:08 +00:00:

chocolatey-ops (reviewer) on 02 Oct 2024 15:36:20 +00:00:

Guidelines

Suggestions

Notes

chocolatey-ops (reviewer) on 02 Oct 2024 15:39:40 +00:00:

chocolatey-ops (reviewer) on 02 Oct 2024 15:56:43 +00:00:

chocolatey-ops (reviewer) on 22 Oct 2024 15:38:48 +00:00:

chocolatey-ops (reviewer) on 06 Nov 2024 15:43:18 +00:00:

Features

Package Parameters

Notes

Ground Rules: